On Thu, May 06, 2004 at 10:40:41PM +1000, Ramon Buckland said > Hi, > > sometime in the past month, I performed an upgrade > to my unstable debian. (apt-get update/upgrade) and possibly (i can't > remember, a dist-upgrade. > > I'm now getting a seg fault on a few commands., but repeatable is > when attempting to run df. > > Can anyone suggest a way I can resolve the issue? My ultimate aim is to > fix without a reinstall the box. (but if needed, I guess I will). > > Probably the one thing that might be the issue is I am running > 2.5.72 kernel. > > Here's my seg fault (not that it will help much, but show my pain I > guess :-) > > sebago:~# df > Filesystem 1K-blocks Used Available Use% Mounted on > <1>Unable to handle kernel NULL pointer dereference at virtual address > 00000018 > printing eip: > 00000018 > *pde = 00000000 > Oops: 0000 [#14] > CPU: 0 > EIP: 0060:[<00000018>] Not tainted > EFLAGS: 00010246 > eax: 0000010c ebx: 08051228 ecx: 00000054 edx: 0000007b > esi: bffff420 edi: 40156510 ebp: c438a000 esp: c438bfc0 > ds: 007b es: 007b ss: 0068 > Process df (pid: 9407, threadinfo=c438a000 task=c326ace0) > Stack: c010904f 08051228 00000054 bffff420 bffff420 40156510 bffff408 > 0000010c > 0000007b 0000007b 0000010c 400f0334 00000073 00000246 bffff3b0 > 0000007b > Call Trace: [<c010904f>] > Code: Bad EIP value. > Segmentation fault
Just for the record, note that this is what's called a "kernel oops", which is the kernel version of a segfault. No user space process should be able to cause this to happen, and it usually means a kernel bug or bad physical memory. In this case it looks like it was the former, which is good and far cheaper to fix :) -- Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: CESID secure cryptanalysis propaganda clandestine e-cash
signature.asc
Description: Digital signature
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
