Re: Oops in 2.2.14pre12 (and 2.3.33, network related)

Manfred Spraul (manfreds@colorfullife.com)
Fri, 17 Dec 1999 15:30:23 +0100

"Leeuw van der, Tim" wrote:
>
> >
> > Tim, did you load/unload any modules immedialy prior to the oops? How
> > much memory do you have?
>
> I was not loading / unloading any modules, at least not myself - don't know
> what happened behind my back.
> I have 32Mb of memory, 18Mb of swap,
[...]
> > > Trace: c0108ead <error_code+2d/40>
> > > Trace: c2861219 <END_OF_CODE+266a395/????>
> > > Trace: c0164995 <tcp_transmit_skb+3d1/3dc>
> > > Trace: c01687c6 <tcp_v4_rcv+66/3a4>
> > > Trace: c0107609 <cpu_idle+a1/b4>

It sounds like a module unload bug:
memory starts at 0xc000 0000
memory ends at 0xc200 0000
then an 8 megabyte hole 0xc280 0000
and now the vmalloc area starts.

The offending address is 0xc286129, ie a few kilobytes into the typical
module area [but this could be a coincidence].
1) Could you check your cron entries? Redhat installs a cron job that
unloads superflous modules every minute.

2) which network modules do you load?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/