Re: PROBLEM: (kern.log) kernel BUG at shmem.c:486!

Hugh Dickins (hugh@veritas.com)
Mon, 17 Mar 2003 16:25:24 +0000 (GMT)


On Mon, 17 Mar 2003 phillip@lougher.demon.co.uk wrote:
> Dan Searle wrote:
> >
> >Mar 7 16:13:16 censornet-halewood kernel: Neighbour tabe overflow.
> >Mar 7 16:13:21 censornet-halewood kernel: NET: 445 messages suppressed.
> >Mar 7 16:13:21 censornet-halewood kernel: Neighbour table overflow.
> >
> >Mar 7 18:44:48 censornet-halewood kernel: kernel BUG at shmem.c:486!
> >Mar 7 18:44:48 censornet-halewood kernel: invalid operand: 0000
>
> The kernel BUG at shmem.c:486 is not the real bug, you've
> hit a kernel sanity check which has failed, because
> something beforehand has got the kernel in an fscked state.

I agree with Phillip, that BUG at shmem.c:486 is not one I've heard
of people hitting. But you could easily hit it if memory is getting
corrupted: worth running memtest86 for the evening and overnight.

Hugh

-
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/