> Oct 25 21:02:13 lameter kernel: Oops: 0000
> Oct 25 21:02:13 lameter kernel: CPU: 0
> Oct 25 21:02:13 lameter kernel: EIP: 0010:[ret_from_sys_call+0/17]
> Oct 25 21:02:13 lameter kernel: EFLAGS: 00010296
> Oct 25 21:02:13 lameter kernel: eax: 00000002 ebx: c65e4000 ecx:
> c1406754 edx: c627b7e0
> Oct 25 21:02:13 lameter kernel: esi: 00000000 edi: 00000000 ebp:
> bffff08c esp: c65e5fcc
> Oct 25 21:02:13 lameter kernel: ds: 0018 es: 0018 ss: 0018
> Oct 25 21:02:13 lameter kernel: Process tcplog (pid: 164, process nr: 21,
> stackpage=c65e5000)
> Oct 25 21:02:13 lameter kernel: Stack: 400ca36c 00000000 00000000 bffff08c
> 00000002 c010002b 0000002b 00000066
> Oct 25 21:02:13 lameter kernel: 4007f2c2 00000023 00000246 bfffee10
> 0000002b
> Oct 25 21:02:13 lameter kernel: Call Trace: [startup_32+43/286]
> Oct 25 21:02:13 lameter kernel: Code: a1 f0 d3 1d 00 01 00 84 d3 1d c0 0f
> 00 00 00 00 00 83 7b 14
This code has been overwritten in at least 2 places: comparing it with my
machines gives:
Yours: a1 f0 d3 1d 00 01 00 84 d3 1d c0 0f 00 00 00 00 00 83 7b 14
Mine: a1 b4 34 1f c0 23 05 b0 34 1f c0 0f 85 bf 00 00 00 83 7b 14
Ok Ok Ok Ok ^^ ^^ ^^ ^^ Ok Ok Ok Ok ^^ ^^ ?? ?? ?? Ok Ok Ok
Ok means same or expected differences due to different kernel options
changing absolute adddresses (I don't use modules and have everything
I need compiled in).
^^ obviously bad, overwritten from some place, or bad memory.
?? Impossible to determine is bad or good since overwriting zeroes goes
so easily unnoticed.
>From the pattern, it might be that you have one bad 72 pins SIMM which
occasionally gives bad data on alternate 32 bit words. Did the system
continue or did it hang ?
>
>
>
>
> Oct 25 23:51:00 lameter kernel: Oops: 0002
> Oct 25 23:51:00 lameter kernel: CPU: 0
> Oct 25 23:51:00 lameter kernel: EIP: 0010:[prune_dcache+73/224]
> Oct 25 23:51:00 lameter kernel: EFLAGS: 00010246
> Oct 25 23:51:00 lameter kernel: eax: 00000341 ebx: c1bc6a40 ecx:
> c19b5980 edx: c1bc6dc8
> Oct 25 23:51:00 lameter kernel: esi: 00000008 edi: c1bc6a20 ebp:
> 00000009 esp: c66a9eac
> Oct 25 23:51:00 lameter kernel: ds: 0018 es: 0018 ss: 0018
> Oct 25 23:51:00 lameter kernel: Process innd (pid: 155, process nr: 19,
> stackpage=c66a9000)
> Oct 25 23:51:00 lameter kernel: Stack: 000081b4 c3e9a218 c012e4a0 00000009
> 00000000 c66a9f50 c012e6bd 00000008
> Oct 25 23:51:00 lameter kernel: 00000000 c0138599 00000000 c66a9f50
> 000081b4 c3e9a218 00000000 c2283240
> Oct 25 23:51:00 lameter kernel: c2283240 c3e9a218 c013a653 c2283240
> 00000000 c2283240 c66a9f48 c2283240
> Oct 25 23:51:00 lameter kernel: Call Trace: [try_to_free_inodes+60/72]
> [get_empty_inode+17/164] [ext2_new_inode+53/1648] [ext2_lookup+119
> /132] [do_follow_link+120/132] [lookup_dentry+332/452]
> [ext2_create+35/348]
> Oct 25 23:51:00 lameter kernel: [open_namei+347/724]
> [do_open+71/304] [sys_open+57/104] [system_call+52/56]
> Oct 25 23:51:00 lameter kernel: Code: 89 50 04 89 02 8b 73 e8 85 f6 74 3c
> c7 43 e8 00 00 00 00 8d
>
>
> -
> 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/
>
-
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/