After a promising start (it didn't die after ten seconds), I left it overnight.
When I came in this morning, it was no longer connecting to the outside world,
and I found this on the console...
kmem_free: Either bad obj addr or double free (objp=c1bac000, name=size-2048)
kmem_free: Either bad obj addr or double free (objp=c1a52c00, name=size-1024)
kmem_free: Either bad obj addr or double free (objp=c1a53800, name=size-1024)
kmem_free: Either bad obj addr or double free (objp=c0383c00, name=size-1024)
kmem_free: Either bad obj addr or double free (objp=c0383c00, name=size-1024)
kmem_free: Either bad obj addr or double free (objp=c0383c00, name=size-1024)
kmem_free: Either bad obj addr or double free (objp=c0383c00, name=size-1024)
kmem_free: Either bad obj addr or double free (objp=c0383c00, name=size-1024)
kmem_free: Either bad obj addr or double free (objp=c0383c00, name=size-1024)
kmem_free: Either bad obj addr or double free (objp=c0383800, name=size-1024)
HiSax: if_command 14 called with invalid driverId 0!
HiSax: if_command 5 called with invalid driverId 0!
HiSax: if_command 6 called with invalid driverId 0!
HiSax: if_command 10 called with invalid driverId 0!
HiSax: if_command 12 called with invalid driverId 0!
HiSax: if_command 1 called with invalid driverId 0!
HiSax: if_command 10 called with invalid driverId 0!
HiSax: if_command 12 called with invalid driverId 0!
HiSax: if_command 1 called with invalid driverId 0!
HiSax: if_command 10 called with invalid driverId 0!
HiSax: if_command 12 called with invalid driverId 0!
HiSax: if_command 1 called with invalid driverId 0!
HiSax: if_command 10 called with invalid driverId 0!
HiSax: if_command 12 called with invalid driverId 0!
HiSax: if_command 1 called with invalid driverId 0!
HiSax: if_command 4 called with invalid driverId 0!
HiSax: if_command 6 called with invalid driverId 0!
HiSax: if_command 15 called with invalid driverId 0!
... The 'if_command %d call with invalid driverId 0!' lines were repeated
lots of times - every time diald attempted to bring up or take down
the link.
When I arrived, I stopped diald, killed ipppd, and removed the 'hisax' module.
I attempted to remove the isdn module, and couldn't, because a couple of
mgettys were running.
Upon typing 'killall mgetty ; rmmod isdn', I got this oops:
Unable to handle kernel paging request at virtual address c2a57e14
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00298063
*pte = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c2a57e14>]
EFLAGS: 00010202
eax: c2a57e14 ebx: c1b635e0 ecx: 0000000a edx: c1b635e0
esi: 00000001 edi: 0000000a ebp: c0201f68 esp: c0201f18
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=c0201000)
Stack: c1bc2800 c0201f68 c01ed1d0 0000000a c0201f68 00000001 c010a7c3 0000000a
c0201f68 c1b635e0 00000000 c0200000 00401b9d c0201f60 00000000 c010a8ab
0000000a c0201f68 00001ff0 c01097c8 00000000 c0200000 c01ec890 c0200000
Call Trace: [<c010a7c3>] [<c010a8ab>] [<c01097c8>] [<c0107f75>] [<c0106000>] [<c
0107f98>] [<c010972c>]
[<c0106000>] [<c010607b>] [<c0106000>] [<c0100176>]
Code: <1>Unable to handle kernel paging request at virtual address c2a57e14
I don't trust the trace, but here it is anyway. I'll put in a section of code
to print the load address of all modules at the same time as it prints the
oops, and see if it happens again.
>>EIP: c2a57e14 <isdn_audio_calc_dtmf+1309c/1f2d4>
Trace: c010a7c3 <do_8259A_IRQ+77/a0>
Trace: c010a8ab <do_IRQ+23/40>
Trace: c01097c8 <ret_from_intr+0/20>
Trace: c0107f75 <cpu_idle+5d/6c>
Trace: c0106000 <get_options+0/74>
---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
-
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/