Re: Kernel 2.6 on alpha
I was able to create the oops on my box. I used a second computer
hooked up to the serial console to capture the oops at boot time.
Attached is the ksymoops output. It's looks like something
may not be right with the device interrupt handling.
On the plus side, I found out what was causing the USB oops.
There appears to be a problem with the verbose machine checking
option. If I specify verbose, I get a oops in cia_decode_mchk.
If I specify uninterpreted checks, it works ok with the mouse
and keyboard.
Alan
----------------------------------------------------------------------------------------
ksymoops 2.4.9 on alpha 2.6.0. Options used
-V (default)
-k /proc/kallsyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.0/ (default)
-m /System-b.map (specified)
Warning (read_ksyms): no kernel symbols in ksyms, is /proc/kallsyms a valid ksyms file?
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel paging request at virtual address 0000000000000048
swapper(0): Oops 0
pc = [<fffffc000046d3a0>] ra = [<fffffc000046da64>] ps = 0007 Not tainted
Using defaults from ksymoops -t elf64-alpha -a alpha
v0 = 0000000000000000 t0 = 000001ff80819ad0 t1 = ffffffff80819ad0
t2 = 0000000000000000 t3 = 0000000000000000 t4 = 0000000000000004
t5 = 00000000000013ff t6 = 000ee66fa3fc87a8 t7 = fffffc0000584000
s0 = fffffc001fd62698 s1 = fffffc001fd442c0 s2 = fffffc0000000000
s3 = 000001ffffffffff s4 = fffffc0000541e80 s5 = 0000000000000000
s6 = 0000000000000000
a0 = fffffc001fd442c0 a1 = fffffc001fd442c0 a2 = fffffc0000587df0
a3 = fffffc0000587df0 a4 = 0000000000000000 a5 = 0000000000001800
t8 = 000000000000001f t9 = 000000008f836e44 t10= 0000000000000000
t11= 0000000000100100 pv = fffffc000046d920 at = fffffc00006467c0
gp = fffffc0000611e80 sp = fffffc0000587d20
Trace:fffffc000046da64 fffffc00003180f8 fffffc0000318b04 fffffc0000321854 fffffc00003191b4
fffffc0000312e80 fffffc0000314b60 fffffc0000314ba8 fffffc0000314b60 fffffc0000314bb0
fffffc0000310098 fffffc000031001c Code: 40430522 444c0001 402b0403 44401c83 2ffe0000
f480000c <28230048> 47e30410
>>RA; fffffc000046da64 <BusLogic_InterruptHandler+144/150>
>>PC; fffffc000046d3a0 <BusLogic_ScanIncomingMailboxes+80/110> <=====
Trace; fffffc000046da64 <BusLogic_InterruptHandler+144/150>
Trace; fffffc00003180f8 <handle_IRQ_event+78/f0>
Trace; fffffc0000318b04 <handle_irq+f4/1f0>
Trace; fffffc0000321854 <srm_device_interrupt+24/40>
Trace; fffffc00003191b4 <do_entInt+104/150>
Trace; fffffc0000312e80 <ret_from_sys_call+0/10>
Trace; fffffc0000314b60 <default_idle+0/10>
Trace; fffffc0000314ba8 <cpu_idle+38/60>
Trace; fffffc0000314b60 <default_idle+0/10>
Trace; fffffc0000314bb0 <cpu_idle+40/60>
Trace; fffffc0000310098 <rest_init+38/50>
Trace; fffffc000031001c <_stext+1c/20>
Code; fffffc000046d388 <BusLogic_ScanIncomingMailboxes+68/110>
0000000000000000 <_PC>:
Code; fffffc000046d388 <BusLogic_ScanIncomingMailboxes+68/110>
0: 22 05 43 40 subq t1,t2,t1
Code; fffffc000046d38c <BusLogic_ScanIncomingMailboxes+6c/110>
4: 01 00 4c 44 and t1,s3,t0
Code; fffffc000046d390 <BusLogic_ScanIncomingMailboxes+70/110>
8: 03 04 2b 40 addq t0,s2,t2
Code; fffffc000046d394 <BusLogic_ScanIncomingMailboxes+74/110>
c: 83 1c 40 44 cmovle t1,0,t2
Code; fffffc000046d398 <BusLogic_ScanIncomingMailboxes+78/110>
10: 00 00 fe 2f unop
Code; fffffc000046d39c <BusLogic_ScanIncomingMailboxes+7c/110>
14: 0c 00 80 f4 bne t3,48 <_PC+0x48>
Code; fffffc000046d3a0 <BusLogic_ScanIncomingMailboxes+80/110> <=====
18: 48 00 23 28 ldbu t0,72(t2) <=====
Code; fffffc000046d3a4 <BusLogic_ScanIncomingMailboxes+84/110>
1c: 10 04 e3 47 mov t2,a0
Kernel panic: Aiee, killing interrupt handler!
1 warning issued. Results may not be reliable.
Reply to: