PROBLEM: Periodic kernel panics when using a serial device

selig@chez.com
Thu, 26 Aug 1999 13:25:27 +0200


[1.] One line summary of the problem:
Periodic kernel panics when using a serial device

[2.] Full description of the problem/report:
>From time to time, one of our computers hangs during bootup, apparently
while trying to establish a vital PPP connection over nullmodem cable.
A kernel panic is printed.

[3.] Keywords (i.e., modules, networking, kernel):
serial

[4.] Kernel version (from /proc/version):
Linux version 2.2.5-15 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Apr 19 22:21:09 EDT 1999

[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)

Options used: -V (default)
-o /lib/modules/2.2.5-15/ (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-m /boot/System.map (specified)
-c 1 (default)

Unable to handle kernel NULL pointer dereference at virtual address 00000000
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c01a3972>]
EFLAGS: 00010093
eax: 00000000 ebx: c0ee3000 ecx: 0000007e edx: c02b02f8
esi: c02afc80 edi: c020d1bc ebp: c0217f10 esp: c0217ef4
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=c0217000)
Stack: 00000003 c0217f68 0000007e 00000000 c023db4c 00000000 00000000 00000061
c010a649 00000003 00000000 c0217f68 c01fb790 00000003 c02ba300 c0217f60
c010a39f 00000003 c0217f68 c02ba300 00000000 c0216000 00000ee6 c0117a91
Call Trace: [<c010a649>] [<c010a39f>] [<c0117a91>] [<c010a748>] [<c0109644>] [<c0107e95>] [<c0106000>]
[<c0107eb8>] [<c01095a8>] [<c0106000>] [<c010607b>] [<c0106000>] [<c0100176>]
Code: 88 08 ff 47 14 8b 83 50 01 00 00 c6 00 00 8b 55 00 89 54 24

>>EIP: c01a3972 <rs_interrupt_single+15a/444>
Trace: c010a649 <handle_IRQ_event+31/68>
Trace: c010a39f <do_8259A_IRQ+77/a8>
Trace: c0117a91 <find_gap+25/4c>
Trace: c010a748 <do_IRQ+24/40>
Trace: c0109644 <ret_from_intr+0/20>
Trace: c0107e95 <cpu_idle+59/68>
Trace: c0106000 <get_options+0/74>
Trace: c0107eb8 <sys_idle+14/24>
Code: c01a3972 <rs_interrupt_single+15a/444> 00000000 <_EIP>: <===
Code: c01a3972 <rs_interrupt_single+15a/444> 0: 88 08 movb %cl,(%eax) <===
Code: c01a3974 <rs_interrupt_single+15c/444> 2: ff 47 14 incl 0x14(%edi)
Code: c01a3977 <rs_interrupt_single+15f/444> 5: 8b 83 50 01 00 00 movl 0x150(%ebx),%eax
Code: c01a397d <rs_interrupt_single+165/444> b: c6 00 00 movb $0x0,(%eax)
Code: c01a3980 <rs_interrupt_single+168/444> e: 8b 55 00 movl 0x0(%ebp),%edx
Code: c01a3983 <rs_interrupt_single+16b/444> 11: 89 54 24 00 movl %edx,0x0(%esp,1)

Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing

1 warning issued. Results may not be reliable.

[6.] A small shell script or example program which triggers the
problem (if possible)
/etc/rc.d/init.d/network start

[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
-- Versions installed: (if some fields are empty or looks
-- unusual then possibly you have very old versions)
Linux zusanli.not-for-mail 2.2.5-15 #1 Mon Apr 19 22:21:09 EDT 1999 i586 unknownKernel modules 2.1.121
Gnu C egcs-2.91.66
Binutils 2.9.1.0.23
Linux C Library 2.1.1
Dynamic linker ldd (GNU libc) 2.1.1
Procps 2.0.2
Mount 2.9o
Net-tools (1999-01-31)
Kbd [option...]
Sh-utils 1.16
Modules Loaded nfs lockd sunrpc ppp slhc

[7.2.] Processor information (from /proc/cpuinfo):
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 1
model name : AMD-K5(tm) Processor
stepping : 1
cpu MHz : 100.229956
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 pge
bogomips : 199.88

[7.3.] Module information (from /proc/modules):
nfs 29944 1 (autoclean)
lockd 30856 1 (autoclean) [nfs]
sunrpc 52356 1 (autoclean) [nfs lockd]
ppp 18316 2 (autoclean)
slhc 4328 1 (autoclean) [ppp]

[7.4.] SCSI information (from /proc/scsi/scsi)
Attached devices: none

[7.5.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):

[X.] Other notes, patches, fixes, workarounds:
Problem usually goes away with a reboot, coming back after a week at the
latest.

On or after Aug 30, please redirect mail about this to
johanna.finsterwald@stud.uni-muenchen.de (who uses Linux for scientific
work and is no expert with system administration).

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