Messages in this thread | | | Date | Sun, 3 Mar 1996 13:25:04 +0100 (MET) | From | Michael De La Rue <> | Subject | Kernel crash in 1.3.68 (oops followed by General Protections) |
| |
Think this may be interesting since it seems abnormal on my hardware..
Linux version 1.3.68 (mikedlr@wolfgang) (gcc version 2.6.3) #7 Tue Feb 27 09:07:05 MET 1996
Contents
1 general description 2 kysmoops of messages 3 original messages 4 contents of some proc files
1 general description
software Kernel 1.3.68 with NE2000 networking + IDE extfs tcp ip networking (active, but not connected at crash) `new' ide driver, but without the special code for the problem cards kerneld isofs module (+ others not loaded) slackware a.out random sloppy upgrades (strictly for buggy software)
hardware (cheapo clone)
486/66 cyrix 8M ram IDE ATAPI cdrom #9 GXE 64 badly setup second serial card NE2000 SB pro (sound system being ignored though)
I was attempting to log in to do some editing (so noticable level of disk access).. girlfriend's emacs was running, but abandoned, but that dosen't seem relevant..
The only special thing was that, a few hours before, I had been playing around with VESA blanking and had run the program included in a comment in the Vesa blanking kernel file. First
vesablank on
which caused ugly flashing on my monitors console, so then
vesablank hsync
which seemed to work
1.3.x series have all been stable as Edinburgh Castle for me otherwise (cheap and nasty hardware wins every time :-), though 1.3.57 collapsed occasionally under extreme disk IO (mainly when trying to compile a new kernel of a higher version). 1.3.68 had previously been up for two days solid and was just taken down to move the machine.
2 kysmoops of messages
These are the first two error messages (lots and lots more followed) as fed through kysmoops
Using `/zImage.3.68-kd.nm-map' to map addresses to symbols.
>>EIP: 11e84a <_generic_file_read+342/3a0> Trace: 12d835 <_read_exec+10d/180> Trace: 12f104 <_permission+24/c0> Trace: 12ddc7 <_do_execve+29f/780> Trace: 10a192 <_sys_execve+32/5c> Trace: 10a9a1 <_system_call+59/a0> Trace: 19002b <_NS8390_init+9b/210>
Code: 11e84a <_generic_file_read+342/3a0> movl %edx,0x4(%edi) Code: 11e84d <_generic_file_read+345/3a0> movl %ecx,0x8(%edi) Code: 11e850 <_generic_file_read+348/3a0> movl $0x1,0x10(%edi) Code: 11e857 <_generic_file_read+34f/3a0> cmpl $0x0,0x20(%esp,1) Code: 11e85c <_generic_file_read+354/3a0> je 11e86d <_generic_file_read+365/3a0>
second message (rest similar)
Using `/zImage.3.68-kd.nm-map' to map addresses to symbols.
>>EIP: 11e87a <_generic_file_read+372/3a0> Trace: 12d835 <_read_exec+10d/180> Trace: 12f104 <_permission+24/c0> Trace: 12ddc7 <_do_execve+29f/780> Trace: 10a192 <_sys_execve+32/5c> Trace: 10a9a1 <_system_call+59/a0> Trace: 19002b <_NS8390_init+9b/210>
Code: 11e87a <_generic_file_read+372/3a0> testb $0x1,0x18(%edx) Code: 11e87e <_generic_file_read+376/3a0> jne 11e891 <_generic_file_read+389/3a0> Code: 11e880 <_generic_file_read+378/3a0> movl 0x1ac9e0,%edx Code: 11e886 <_generic_file_read+37e/3a0> movl 0x30(%esp,1),%esi Code: 11e88a <_generic_file_read+382/3a0> movl %edx,0x18(%esi) Code: 11e88d <_generic_file_read+385/3a0> movb $0x90,(%eax) Code: 11e890 <_generic_file_read+388/3a0> nop
3 original messages
Error messages as came out ('cos I'm not sure that kysymoops does the right thing.. or whether I should send them anyway probably a slanderous thought, but I'd like to know)
Oops: 0002 CPU: 0 EIP: 0010:[<0011e84a>] EFLAGS: 00010246 eax: 004d3c00 ebx: 00000000 ecx: 00000000 edx: 0019a7c0 esi: 0019a7c0 edi: 00000000 ebp: 00001000 esp: 007bed80 ds: 0018 es: 0018 fs: 0018 gs: 002b ss: 0018 Process init (pid: 610, process nr: 4, stackpage=007be000) Stack: 00000003 00000000 ffffffff 007bee70 0000002b 00669f00 00000080 007bede0 00000000 0019a7c0 0000001c 004d3000 00000000 00000000 0012d835 00669f00 007bede4 007bee70 00000080 007bee70 00669f00 007beef0 00000000 0000002b Call Trace: [<0012d835>] [<0012f104>] [<0012ddc7>] [<0010a192>] [<0010a9a1>] [<0019002b>] Code: 89 57 04 89 4f 08 c7 47 10 01 00 00 00 83 7c 24 20 00 74 0f
general protection: 0000 CPU: 0 EIP: 0010:[<0011e87a>] EFLAGS: 00010282 eax: 00471c00 ebx: 00000000 ecx: 00000000 edx: c00056b0 esi: 0019a7c0 edi: 00000000 ebp: 00001000 esp: 007bed80 ds: 0018 es: 0018 fs: 0018 gs: 002b ss: 0018 Process init (pid: 611, process nr: 4, stackpage=007be000) Stack: 00000003 00000000 ffffffff 007bee70 0000002b 00669f00 00000080 007bede0 00000000 0019a7c0 0000001c 00471000 00000000 00000000 0012d835 00669f00 007bede4 007bee70 00000080 007bee70 00669f00 007beef0 00000000 0000002b Call Trace: [<0012d835>] [<0012f104>] [<0012ddc7>] [<0010a192>] [<0010a9a1>] [<0019002b>] Code: f6 42 18 01 75 11 8b 15 e0 c9 1a 00 8b 74 24 30 89 56 18 c6
4 contents of some proc files
I thought these might help clarify hardware?
/proc/interrupts 0: 284950 timer 1: 6466 keyboard 2: 0 + cascade 3: 0 + serial 4: 172 + serial 10: 1 NE2000 13: 1 math error 14: 71339 + ide0
/proc/devices Character devices: 1 mem 2 pty 3 ttyp 4 tty 5 cua 7 vcs
Block devices: 2 fd 3 ide0
/proc/ioports 0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : kbd 0070-007f : rtc 0080-009f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : npu 01f0-01f7 : ide0 02f8-02ff : serial(auto) 0300-031f : NE2000 03c0-03df : vga+ 03e8-03ef : serial(auto) 03f0-03f5 : floppy 03f6-03f6 : ide0 03f7-03f7 : floppy DIR 03f8-03ff : serial(auto)
<http://www.tardis.ed.ac.uk/~mikedlr/biography.html> Scottish Climbing Archive: <http://www.tardis.ed.ac.uk/~mikedlr/climbing/> Linux/Unix clone@ftp://src.doc.ic.ac.uk/packages/linux/sunsite.unc-mirror/docs/
| |