This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Wed May 29 12:42:22 2024 Received: from lml.valinux.com (postfix@lml.varesearch.com [209.81.8.228]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id KAA26657 for ; Fri, 17 Dec 1999 10:49:12 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by lml.valinux.com (Postfix) with ESMTP id 584F759C1A; Fri, 17 Dec 1999 07:50:06 -0800 (PST) Received: by vger.rutgers.edu via listexpand id ; Fri, 17 Dec 1999 10:22:40 -0500 Received: by vger.rutgers.edu id ; Fri, 17 Dec 1999 10:17:54 -0500 Received: from eamail1-out.unisys.com ([192.61.61.99]:48621 "EHLO eamail1-out.unisys.com") by vger.rutgers.edu with ESMTP id ; Fri, 17 Dec 1999 10:04:34 -0500 Received: from us-lacd-gtwy-1.ea.unisys.com (us-lacd-gtwy-1.ea.unisys.com [192.61.145.103]) by eamail1-out.unisys.com (8.9.3/8.9.3) with ESMTP id PAA03935; Fri, 17 Dec 1999 15:03:41 GMT Received: by us-lacd-gtwy-1.ea.unisys.com with Internet Mail Service (5.5.2650.21) id ; Fri, 17 Dec 1999 09:03:45 -0600 Message-Id: From: "Leeuw van der, Tim" To: "'Manfred Spraul'" Cc: "'linux-kernel@vger.rutgers.edu'" Subject: RE: Oops in 2.2.14pre12 (and 2.3.33, network related) Date: Fri, 17 Dec 1999 08:56:59 -0600 Mime-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig Hello Manfred, 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 > > > > Trace: c2861219 > > > > Trace: c0164995 > > > > Trace: c01687c6 > > > > Trace: c0107609 > > 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/