At Wed, 11 Jul 2001 12:38:34 -0400,
David Ford wrote:
>
> Hrm. Third time I've reported this, it's happened since the early 2.4
> kernels and I can get at least one every day or so. The odd thing is
> that the first oops normally happens within a couple hours after boot
> but it may take weeks before another oops will happen. The oops always
> has a trace similar to below. The second oops is new to me, it happened
> last night and I haven't seen it before, culled from syslog.
>
> # uname -r
> 2.4.5-ac15
2.4.5-ac19 fixes the minor tty layer bug which modifies the memory after
kfree() was called and it causes Oops if memory allocations debugging is enabled.
So, upgrading to newer kernel may fix your problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/