>
> Connect a serial line and capture that OOPS.
I overcame my laziness and carried a second machine to the server-room.
You asked for it, then so it should be...
Kernel BUG at include/linux/timer.h:83
invalid operand: 0000 [1] SMP
last sysfs file: /class/net/visdn1.3/ifindex
CPU 0
Modules linked in: lapd(U) visdn_hfc_usb(U) visdn_hfc_pci(U) visdn_ec(U)
visdn_t
imer_system(U) visdn_ppp(U) ppp_generic slhc visdn_streamport(U)
visdn_netdev(U)
ipv6 parport_pc lp parport autofs4 sunrpc pcmcia yenta_socket
rsrc_nonstatic pc
mcia_core ipt_REJECT ipt_state ip_conntrack nfnetlink iptable_filter
ip_tables v
ideo button battery ac ohci_hcd ehci_hcd i2c_nforce2 i2c_core
snd_intel8x0 snd_a
c97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event
snd_seq snd_
seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore
snd_page_al
loc visdn_hfc_4s(U) visdn_softcxc(U) visdn_core(U) 3c59x mii forcedeth
floppy dm
_snapshot dm_zero dm_mirror ext3 jbd dm_mod sata_nv libata sd_mod
scsi_mod
Pid: 4, comm: events/0 Not tainted 2.6.15-1.1831_FC4 #1
RIP: 0010:[<ffffffff88162e27>]
<ffffffff88162e27>{:visdn_hfc_4s:hfc_led_update+3
05}
RSP: 0018:ffff810037d41dc8 EFLAGS: 00010282
RAX: 00000000fffff41e RBX: ffff81003bb00000 RCX: 0000000000000019
RDX: 00000000fffff412 RSI: ffffc20000064041 RDI: ffff81003bb114b8
RBP: ffff81003bb11498 R08: ffff810037d40000 R09: 0000000000000003
R10: 0000000000000173 R11: 0000000000000000 R12: ffff81003bb02c70
R13: ffff81003bb00000 R14: 0000000000000206 R15: ffffffff88164a65
FS: 00000000400c2960(0000) GS:ffffffff8059b000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00002aaaaaaac000 CR3: 0000000035794000 CR4: 00000000000006e0
Process events/0 (pid: 4, threadinfo ffff810037d40000, task
ffff8100023c4090)
Stack: ffff81003bb00000 0000000000000008 ffff81003bb00000
ffffffff88164c58
ffff81003bb03c50 ffff81003bb03c58 ffff81003ff926c0
ffff81003bb02c70
0000000000000206 ffffffff8014dc9e
Call
Trace:<ffffffff88164c58>{:visdn_hfc_4s:hfc_st_port_state_change_work+499
}
<ffffffff8014dc9e>{worker_thread+481}
<ffffffff80137e56>{default_wake_fun
ction+0}
<ffffffff8014dabd>{worker_thread+0}
<ffffffff801524ea>{kthread+276}
<ffffffff801387c8>{schedule_tail+70}
<ffffffff80110c22>{child_rip+8}
<ffffffff801523d6>{kthread+0} <ffffffff80110c1a>{child_rip+0}
Code: 0f 0b 68 5c 87 16 88 c2 53 00 48 8b 77 10 48 83 c4 08 5b 5d
RIP <ffffffff88162e27>{:visdn_hfc_4s:hfc_led_update+305} RSP
<ffff810037d41dc8>
<3>Debug: sleeping function called from invalid context at
include/linux/rwsem.
h:43
in_atomic():1, irqs_disabled():0
Call Trace:<ffffffff8013d9e5>{profile_task_exit+21}
<ffffffff8013ef9e>{do_exit+3
4}
<ffffffff80357acb>{_spin_unlock_irqrestore+11}
<ffffffff88164a65>{:visdn_
hfc_4s:hfc_st_port_state_change_work+0}
<ffffffff801119d2>{default_do_nmi+0}
<ffffffff80112177>{do_invalid_op+163
}
<ffffffff88162e27>{:visdn_hfc_4s:hfc_led_update+305}
<ffffffff8016a2b2>{free_pages_bulk+877}
<ffffffff80110a6d>{error_exit+0}
<ffffffff88164a65>{:visdn_hfc_4s:hfc_st_port_state_change_work+0}
<ffffffff88162e27>{:visdn_hfc_4s:hfc_led_update+305}
<ffffffff88162df5>{:visdn_hfc_4s:hfc_led_update+255}
<ffffffff88164c58>{:visdn_hfc_4s:hfc_st_port_state_change_work+499}
<ffffffff8014dc9e>{worker_thread+481}
<ffffffff80137e56>{default_wake_fun
ction+0}
<ffffffff8014dabd>{worker_thread+0}
<ffffffff801524ea>{kthread+276}
<ffffffff801387c8>{schedule_tail+70}
<ffffffff80110c22>{child_rip+8}
<ffffffff801523d6>{kthread+0} <ffffffff80110c1a>{child_rip+0}
Kernel panic - not syncing: Aiee, killing interrupt handler!
Call
Trace:<ffffffff88164a65>{:visdn_hfc_4s:hfc_st_port_state_change_work+0}
<ffffffff8013c1d1>{panic+133}
<ffffffff8014fa7d>{kernel_text_address+28}
<ffffffff801113b2>{show_trace+505}
<ffffffff80357ae5>{_spin_unlock_irq+9}
<ffffffff8035746c>{__down_read+50}
<ffffffff80357a88>{_spin_lock_irqsave+
9}
<ffffffff80215991>{__up_read+19} <ffffffff8013effb>{do_exit+127}
<ffffffff80357acb>{_spin_unlock_irqrestore+11}
<ffffffff88164a65>{:visdn_
hfc_4s:hfc_st_port_state_change_work+0}
<ffffffff801119d2>{default_do_nmi+0}
<ffffffff80112177>{do_invalid_op+163
}
<ffffffff88162e27>{:visdn_hfc_4s:hfc_led_update+305}
<ffffffff8016a2b2>{free_pages_bulk+877}
<ffffffff80110a6d>{error_exit+0}
<ffffffff88164a65>{:visdn_hfc_4s:hfc_st_port_state_change_work+0}
<ffffffff88162e27>{:visdn_hfc_4s:hfc_led_update+305}
<ffffffff88162df5>{:visdn_hfc_4s:hfc_led_update+255}
<ffffffff88164c58>{:visdn_hfc_4s:hfc_st_port_state_change_work+499}
<ffffffff8014dc9e>{worker_thread+481}
<ffffffff80137e56>{default_wake_fun
ction+0}
<ffffffff8014dabd>{worker_thread+0}
<ffffffff801524ea>{kthread+276}
<ffffffff801387c8>{schedule_tail+70}
<ffffffff80110c22>{child_rip+8}
<ffffffff801523d6>{kthread+0} <ffffffff80110c1a>{child_rip+0}
That was all I could get. Though having no experience with those
messages at all the lines " Kernel BUG at include/linux/timer.h:83"
and "Kernel panic - not syncing: Aiee, killing interrupt handler!" look
like a timing problem on the PCI-Bus...
ANY comments reeeeaaaallly welcome!
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers
