Hi everyone, On Mon, Sep 30, 2002 at 08:13:24PM +0800, Federico Sevilla III wrote: > On our server that had been running for 55 days with this 2.4.19-xfs > kernel (XFS CVS snapshot 20020809 patched with RML's preempt patches > for 2.4.19-rc3 and sys-magic 20020314 from Randy Dunlap, built using > GCC 3.1.1 running Debian GNU/Linux) And then after approximately 1.5 hours on 2.4.19-xfs (XFS CVS snapshot 20020930 patched only with Randy Dunlap's sys-magic 20020314, built using gcc 2.95.4 running Debian GNU/Linux). > I hit a kernel panic in the process running the distributed-net > client. Now in the process running syslogd. Attached kernel-panic-3.out is the oops. > After copying the oops message, I attempted to sync the disks using > the (Alt + SysRq + S) key combination and after the sync messages I > hit a kernel BUG at sched.c:568. I did this, as well, and hit a kernel BUG at sched.c:566. My sched.c is now exactly the same as the one in the XFS tree (which I think is the same as the one in vanilla 2.4.19). Oops is attached as kernel-bug-2.out. > Pointers as to what probably caused this are welcome. If this is a > "new" issue I hope the decoded oops messages will be help. Thank you > everyone for your time. System has been up for two hours so far and is thankfully alive. I hope someone can point me to what the probably cause of this problem is. I did an xfs_check -- which is from the latest 2.3.1 package -- and all my XFS partitions are okay. I will be looking for a memory scanning tool shortly to make sure I don't suddenly have bad RAM, although the problem doesn't seem to be that. Thanks again to everyone for your time. --> Jijo -- Federico Sevilla III : http://jijo.free.net.ph Network Administrator : The Leather Collection, Inc. GnuPG Key ID : 0x93B746BE