lkml.org 
[lkml]   [1999]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Help Tracking Down Oops
Hi,

On Fri, 29 Jan 1999 10:14:36 -0800, Steve Shah <sshah@cert.UCR.EDU>
said:

> When
> we updated the kernel to 2.0.36 straight from the distribution we
> hit 58 days of uptime until the box oops'd itself to death. What
> makes this particular crash worrysome is tht is the same function
> that it is oopsing on.

Seeing a single oops multiple times during a single kernel boot does not
necessarily point to a fault in that code. The particular error you are
seeing in find_candidate really indicates a buffer_head list corruption,
and those are almost always associated with hardware problems either in
the memory or cache.

> I'm seeing this oops spattered all over my logs right now. Not all of them
> are bad enough to cause the system to crash. It seems though that if
> it happens during a dump, dump goes ballistic.

Dump is a very heavy user of the buffer cache.

--Stephen

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

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.032 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site