An oops for your enjoyment

From: Robert Norris (Robert.Norris@its.monash.edu.au)
Date: Fri Aug 11 2000 - 00:58:45 EST


Hi all,

Got this oops recently:

Aug 11 13:31:15 broink kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000410
Aug 11 13:31:15 broink kernel: current->tss.cr3 = 1f7e2000, %cr3 = 1f7e2000
Aug 11 13:31:15 broink kernel: *pde = 00000000
Aug 11 13:31:15 broink kernel: Oops: 0000
Aug 11 13:31:15 broink kernel: CPU: 1
Aug 11 13:31:15 broink kernel: EIP: 0010:[prune_dcache+194/312]
Aug 11 13:31:15 broink kernel: EFLAGS: 00010206
Aug 11 13:31:15 broink kernel: eax: 00000400 ebx: cc5dcf40 ecx: cf6e0f80 edx: cf6e0328
Aug 11 13:31:15 broink kernel: esi: cf6e0380 edi: 00000000 ebp: ffffffff esp: cc8edf0c
Aug 11 13:31:15 broink kernel: ds: 0018 es: 0018 ss: 0018
Aug 11 13:31:15 broink kernel: Process bonnie++ (pid: 1073, process nr: 13, stackpage=cc8ed000)
Aug 11 13:31:15 broink kernel: Stack: fffffffe cc3c6000 0805170e fffffff4 00000000 ffffffff c8de6680 cc8edf78
Aug 11 13:31:15 broink kernel: cc8ec000 c0135a07 0000363b ffffffff cc3c600d 00000206 cc5dcf40 d8fe5320
Aug 11 13:31:15 broink kernel: fffffffe c0130b75 c8de6680 cc5dcf40 00000000 c01313c6 cc5dcf40 00000003
Aug 11 13:31:15 broink kernel: Call Trace: [shrink_dcache_parent+23/48] [lookup_dentry+365/504] [vfs_rmdir+254/308] [schedule+497/972] [sys_rmdir+201/320] [sys_unlink+204/236] [system_call+52/56]
Aug 11 13:31:15 broink kernel: [startup_32+43/164]
Aug 11 13:31:15 broink kernel: Code: 8b 40 10 85 c0 74 09 83 c4 f4 56 ff d0 83 c4 10 8d 46 60 8b

I know very little about the kernel, so I was hoping someone could help
me to track down the problem.

Kernel version is 2.2.17pre16, with reiserfs-3.5.23 patch applied. Also
have the DAC960 driver installed (using a DAC1164P card).

bonnie++ was running at the time, on a reiserfs partition on top of a
RAID 0+1 set. After the oops happened, I was unable to use or unmount
the partition (a reboot was required).

I'm not bothered if noone can offer a solution, but I do need to know
which part of the kernel actually has a problem, and how likely it is
that this problem will be fixed (I'm evaluating this machine, so if
this is going to be a recurring problem I need to know now).

If you need any more information, please let me know.

Regards,
Rob.



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



This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:23 EST