On Wednesday, 24 March 1999 at 19:50, Brendan Cully wrote:
> On Wednesday, 24 March 1999 at 20:00, Alan Cox wrote:
> > Is everyone who is having 2.2.4 crash on them using egcs ?
>
> My machine spontaneously rebooted after 17 hours of light use (plus
> rc5). Nothing peculiar was in the logs - it was like the reset button
> was hit (oh wait ... :) )
>
> I compiled it with egcs-1.1.2.
> It is the 2.2.4 SMP kernel on a dual PII/350 system. Other data:
>
> * lm_sensors 2.2.2 installed (I mention it because it looks like it
> was involved in an oops under 2.2.3)
> * alsa-0.3.0-pre4 installed for an es1370.
> * matroxfb running a G200
>
> I'll attach the oops as well.
and not 15 minutes later, a second Oops/total freeze. Nothing logged,
but I copied down the oops by hand (hopefully faithfully).
I forgot to add, I'm running /usr/share and /opt off of raid0 md
devices across a UDMA drive and a SCSI drive sitting on an aic7895.
While the freeze happened, I was playing mp3s off of /usr/share.
Before and after the oops, I got some strange filesystem messages,
looking like this:
ll_rw_block: device 08:06: only 119539488-char blocks implemented
(1024)
EXT2-fs error (device sd(8,6)): ext2_write_inode: unable to read inobe
block - inode=15169, block=122892
/dev/sda6 (if it's the same device) is my /home, but does not
participate in a raid.
Attached is the output of ksymoops on my handwritten oops.
-Brendan
-- Brendan Cully <brendan@kublai.com> "I hope I don't win The rules say to bring a friend I don't have any"--45Z9DzgjV8m4Oswq Content-Type: text/plain Content-Disposition: attachment; filename="oops2.txt"
Options used: -v /usr/src/linux/vmlinux (specified) -o /lib/modules/2.2.4 (specified) -k /proc/ksyms (default) -l /proc/modules (default) -m /boot/System.map-2.2.4 (specified) -c 1 (default)
current->tss.cr3 = 01b52000, %cr3 = 01b52000 *pde = 00000000 Oops: 0000 CPU: 1 EIP: 0010:[<c0142f04>] EFLAGS: 00010202 eax: c0204000 ebx: 07200720 ecx: 00000720 edx: c0018660 esi: c2e9b280 edi: c0018660 ebp: 00000000 esp: c2f4beec ds: 0018 es: 0018 ss: 0018 Process wmmon (pid: 1923, process nr: 42, stackpage=c2f4b000) Stack: c0018660 c2e9b280 c7e79a80 fffffffe c0142ff2 c0018660 c2e0b280 c2e0b280 c0018660 c2f4bf50 c00186ac c012ec5f c0018660 c2e9b280 c2f4bf50 00000000 c586f00d 00000001 c012ee2a c7e79a40 c2f4bf50 c49faa80 ffffffe9 00000001 Call Trace: [<c0142ff2>] [<c012ec5f>] [<c012ee2a>] [<c012efb2>] [<c0127664>] [<c0127816>] [<c01097d0>] Code: 66 83 3b 00 79 4e 31 c9 8b 74 24 20 66 8b 4b 02 3b 4e 44 75
>>EIP: c0142f04 <proc_lookup+4c/e0> Trace: c0142ff2 <proc_root_lookup+5a/12c> Trace: c012ec5f <real_lookup+4b/74> Trace: c012ee2a <lookup_dentry+126/1f0> Trace: c012efb2 <open_namei+66/2f0> Trace: c0127664 <filp_open+44/f0> Trace: c0127816 <sys_open+52/a0> Trace: c01097d0 <system_call+34/38> Code: c0142f04 <proc_lookup+4c/e0> 00000000 <_EIP>: <=== Code: c0142f04 <proc_lookup+4c/e0> 0: 66 83 3b 00 cmpw $0x0,(%ebx) <=== Code: c0142f08 <proc_lookup+50/e0> 4: 79 4e jns c0142f58 <proc_lookup+a0/e0> Code: c0142f0a <proc_lookup+52/e0> 6: 31 c9 xorl %ecx,%ecx Code: c0142f0c <proc_lookup+54/e0> 8: 8b 74 24 20 movl 0x20(%esp,1),%esi Code: c0142f10 <proc_lookup+58/e0> c: 66 8b 4b 02 movw 0x2(%ebx),%cx Code: c0142f14 <proc_lookup+5c/e0> 10: 3b 4e 44 cmpl 0x44(%esi),%ecx Code: c0142f17 <proc_lookup+5f/e0> 13: 75 00 jne c0142f19 <proc_lookup+61/e0>
745 warnings issued. Results may not be reliable.
--45Z9DzgjV8m4Oswq--
- 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/