I just sent you an e-mail with a list of modules that I have typically
loaded.
I haven't found any regular cron jobs that would do module-unloading
(Running a SuSE system btw).
I remember that last time I was at home and transferring files between the
laptop and the desktop I also had problems when the network load was high,
but then I just experienced it has lockups of the laptop - because I was
running X on the laptop, I didn't see any oopses if there were any. But now,
at the office, I shut down the X server on the laptop so I do see them.
When the network load is low, the system is as solid as a rock.
--Tim
> -----Original Message-----
> From: Manfred Spraul [mailto:manfreds@colorfullife.com]
> Sent: 17 December 1999 14:30
> To: Leeuw van der, Tim; linux-kernel@vger.rutgers.edu
> Subject: Re: Oops in 2.2.14pre12 (and 2.3.33, network related)
>
>
> "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/