Oops 0000 while booting 1.3.4 kernel

William M. Perkins (bill@grnwood.cais.com)
Wed, 28 Jun 1995 22:13:29 -0400 (EDT)

I encounter the following message in /var/adm/messages after I tried to
reboot my 486 DX2 PCI system after a power failure. I am using the
1.3.4 kernel with the standard 2.2.0 Slackware release. The system was
hanging on reboot after starting the X server with xdm. The gray screen
would display with a movable mouse pointer, but the login window did not
appear. I also could not login on any of the VC's.

Oops: 0000
EIP: 0010:0011afb2
EFLAGS: 00010246
eax: 00000001 ebx: 00000006 ecx: 001f9e24 edx: 00000000
esi: ffffffff edi: 00000003 ebp: fffffff0 esp: 00738cf0
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process xrdb (pid: 84, process nr: 29, stackpage=00738000)
Stack: 00000006 ffffffff 00000003 00000040 001dabd0 0011b3b9 00000003 ffffffff
001e8948 00000000 001dabd0 00000000 00000802 00000293 001201ae 00000003
00000000 ffffffff 001e8948 00000000 001dabd0 001209e2 001e8948 00120cb4
Call Trace: 0011b3b9 001201ae 001209e2 00120cb4 0015a733 0012a201 0012a331
0012a59f 0012835d 00123d45 00129f4f 00109ee2 0010a6c1
Code: 00 00 83 c4 08 85 c0 75 dd c7 05 e4 75 1c 00 01 00 00 00 56

I rebooted three times with the 1.3.4 kernel and received virtual the
same behavior and message. I than rebooted the system with the backup
kernel (1.2.6) and the system booted without any problem. I than
rebooted with the 1.3.4 kernel and it booted okey. I do not understand
why this happened. I assume some temp files were left after the power
failure. I just wonder why the 1.2.6 kernel appeared to handle the
problem, but the 1.3.4 kernel did not.


William M. Perkins              Internet - bill@cais.cais.com
The Greenwood                      or    - bill@grnwood.cais.com
Commodore is dead.  Long lives the Amiga!  (AmigaOS/Linux/NetBSD)