From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] softlockup in hacked 2.6.34 kernel
Date: Fri, 02 Jul 2010 12:59:49 -0700 [thread overview]
Message-ID: <4C2E4535.5050208@candelatech.com> (raw)
I'm doing a bit of hacking on ath9k, but I don't _think_ I did something
to cause this. I'm just curious if someone has seen something similar.
This was after rmmod and I had previously added a virtual wiphy before
rmmod'ing it.
Jul 2 12:34:53 atom kernel: ath9k 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jul 2 12:35:58 atom kernel: BUG: soft lockup - CPU#0 stuck for 61s! [modprobe:29791]
Jul 2 12:35:58 atom kernel: Modules linked in: ath9k(+) xt_MARK michael_mic wanlink(P) nfs lockd fscache nfs_acl auth_rpcgss xt_CT iptable_raw ipt_addrtype
xt_DSCP xt_dscp xt_string xt_owner xt_NFQUEUE xt_multiport xt_mark xt_iprange xt_hashlimit xt_CONNMARK xt_connmark ath5k 8021q garp stp llc macvlan pktgen
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc p4_clockmod ipv6 uinput arc4 ecb microcode ppdev pcspkr parport_pc parport i2c_i801 ath9k_common
mac80211 ath9k_hw ath cfg80211 iTCO_wdt iTCO_vendor_support e1000 e1000e i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: ath9k]
Jul 2 12:35:58 atom kernel: Modules linked in: ath9k(+) xt_MARK michael_mic wanlink(P) nfs lockd fscache nfs_acl auth_rpcgss xt_CT iptable_raw ipt_addrtype
xt_DSCP xt_dscp xt_string xt_owner xt_NFQUEUE xt_multiport xt_mark xt_iprange xt_hashlimit xt_CONNMARK xt_connmark ath5k 8021q garp stp llc macvlan pktgen
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc p4_clockmod ipv6 uinput arc4 ecb microcode ppdev pcspkr parport_pc parport i2c_i801 ath9k_common
mac80211 ath9k_hw ath cfg80211 iTCO_wdt iTCO_vendor_support e1000 e1000e i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: ath9k]
Jul 2 12:35:58 atom kernel:
Jul 2 12:35:58 atom kernel: Pid: 29791, comm: modprobe Tainted: P 2.6.34 #7 To be filled by O.E.M./To Be Filled By O.E.M.
Jul 2 12:35:58 atom kernel: EIP: 0060:[<c0566fd7>] EFLAGS: 00000206 CPU: 0
Jul 2 12:35:58 atom kernel: EIP is at search_extable+0xa/0x29
Jul 2 12:35:58 atom kernel: EAX: c0737860 EBX: 00000078 ECX: 00000000 EDX: c07378d8
Jul 2 12:35:58 atom kernel: ESI: 00000000 EDI: f5781c4c EBP: f5781bb8 ESP: f5781bb4
Jul 2 12:35:58 atom kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Jul 2 12:35:58 atom kernel: Process modprobe (pid: 29791, ti=f5780000 task=f644a680 task.ti=f5780000)
Jul 2 12:35:58 atom kernel: Stack:
Jul 2 12:35:58 atom kernel: 00000000 f5781bc4 c0441a78 f5781c4c f5781bd0 c041f8b2 00000000 f5781bf0
Jul 2 12:35:58 atom kernel: <0> c041f02d 00000000 00000000 c073301a f644a680 00000000 f5781c4c f5781c0c
Jul 2 12:35:58 atom kernel: <0> c041f24c f5781c44 00000000 f5781c4c 00000000 c0735280 f5781c18 c041f261
Jul 2 12:35:58 atom kernel: Call Trace:
Jul 2 12:35:58 atom kernel: [<c0441a78>] ? search_exception_tables+0x17/0x27
Jul 2 12:35:58 atom kernel: [<c041f8b2>] ? fixup_exception+0xe/0x40
Jul 2 12:35:58 atom kernel: [<c041f02d>] ? no_context+0x15/0x11a
Jul 2 12:35:58 atom kernel: [<c073301a>] ? apic_timer_interrupt+0x2a/0x30
Jul 2 12:35:58 atom kernel: [<c041f24c>] ? __bad_area_nosemaphore+0x11a/0x122
Jul 2 12:35:58 atom kernel: [<c0735280>] ? do_page_fault+0x0/0x2c5
Jul 2 12:35:58 atom kernel: [<c041f261>] ? bad_area_nosemaphore+0xd/0x10
Jul 2 12:35:58 atom kernel: [<c0735402>] ? do_page_fault+0x182/0x2c5
Jul 2 12:35:58 atom kernel: [<c0735280>] ? do_page_fault+0x0/0x2c5
Jul 2 12:35:58 atom kernel: [<c07332b6>] ? error_code+0x66/0x70
Jul 2 12:35:58 atom kernel: [<c0735280>] ? do_page_fault+0x0/0x2c5
Jul 2 12:35:58 atom kernel: [<c043aeff>] ? run_timer_softirq+0x11a/0x173
Jul 2 12:35:58 atom kernel: [<c043730b>] ? __do_softirq+0x7b/0xf5
Jul 2 12:35:58 atom kernel: [<c04373b6>] ? do_softirq+0x31/0x3c
Jul 2 12:35:58 atom kernel: [<c04374ca>] ? irq_exit+0x29/0x5c
Jul 2 12:35:58 atom kernel: [<c0416ce4>] ? smp_apic_timer_interrupt+0x6e/0x7c
Jul 2 12:35:58 atom kernel: [<c073301a>] ? apic_timer_interrupt+0x2a/0x30
Jul 2 12:35:58 atom kernel: [<c056d054>] ? delay_tsc+0x36/0x62
Jul 2 12:35:58 atom kernel: [<c056cfff>] ? __const_udelay+0x2f/0x31
Jul 2 12:35:58 atom kernel: [<f8ba4213>] ? ath9k_hw_wait+0x49/0x63 [ath9k_hw]
Jul 2 12:35:58 atom kernel: [<fab730c9>] ? ath_pci_eeprom_read+0x35/0x5b [ath9k]
Jul 2 12:35:58 atom kernel: [<f8ba7d4e>] ? ath9k_hw_nvram_read+0xd/0x10 [ath9k_hw]
Jul 2 12:35:58 atom kernel: [<f8ba958d>] ? ath9k_hw_def_fill_eeprom+0x20/0x36 [ath9k_hw]
Jul 2 12:35:58 atom kernel: [<f8ba7f7b>] ? ath9k_hw_eeprom_init+0x6c/0x84 [ath9k_hw]
Jul 2 12:35:58 atom kernel: [<f8ba7845>] ? ath9k_hw_init+0xed6/0x132d [ath9k_hw]
Jul 2 12:35:58 atom kernel: [<fab6ba58>] ? ath9k_init_device+0x125/0x669 [ath9k]
Jul 2 12:35:58 atom kernel: [<fab733ce>] ? ath_pci_probe+0x256/0x2f4 [ath9k]
Jul 2 12:35:58 atom kernel: [<c0731d10>] ? mutex_unlock+0x8/0xa
Jul 2 12:35:58 atom kernel: [<c04eabd3>] ? sysfs_addrm_finish+0x16/0xad
Jul 2 12:35:58 atom kernel: [<c04ea5d5>] ? __sysfs_add_one+0x25/0x73
Jul 2 12:35:58 atom kernel: [<c057a82e>] ? local_pci_probe+0xe/0x10
Jul 2 12:35:58 atom kernel: [<c057b370>] ? pci_device_probe+0x43/0x66
Jul 2 12:35:58 atom kernel: [<c05fa221>] ? driver_probe_device+0x87/0x107
Jul 2 12:35:58 atom kernel: [<c05fa2e4>] ? __driver_attach+0x43/0x5f
Jul 2 12:35:58 atom kernel: [<c05f9a34>] ? bus_for_each_dev+0x3d/0x67
Jul 2 12:35:58 atom kernel: [<c05fa0ea>] ? driver_attach+0x14/0x16
Jul 2 12:35:58 atom kernel: [<c05fa2a1>] ? __driver_attach+0x0/0x5f
Jul 2 12:35:58 atom kernel: [<c05f9de8>] ? bus_add_driver+0x92/0x1c2
Jul 2 12:35:58 atom kernel: [<c05fa526>] ? driver_register+0x7c/0xe3
Jul 2 12:35:58 atom kernel: [<c0531a9f>] ? debugfs_create_file+0x17b/0x19c
Jul 2 12:35:58 atom kernel: [<c057b549>] ? __pci_register_driver+0x43/0xa0
Jul 2 12:35:58 atom kernel: [<fab31000>] ? ath9k_init+0x0/0x62 [ath9k]
Jul 2 12:35:58 atom kernel: [<fab73483>] ? ath_pci_init+0x17/0x1c [ath9k]
Jul 2 12:35:58 atom kernel: [<fab3103d>] ? ath9k_init+0x3d/0x62 [ath9k]
Jul 2 12:35:58 atom kernel: [<c0401139>] ? do_one_initcall+0x4c/0x13a
Jul 2 12:35:58 atom kernel: [<c04561cc>] ? sys_init_module+0xa7/0x1db
Jul 2 12:35:58 atom kernel: [<c040301c>] ? sysenter_do_call+0x12/0x28
Jul 2 12:35:58 atom kernel: Code: 98 d8 00 00 00 8b 0c d1 39 cb 77 12 03 98 e0 00 00 00 39 d9 73 08 89 90 cc 00 00 00 eb d0 5b 5d c3 55 89 e5 53 eb 18 89 d3 29
c3 <c1> fb 04 8d 1c d8 39 0b 73 05 8d 43 08 eb 05 76 09 8d 53 f8 39
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2010-07-02 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 19:59 Ben Greear [this message]
2010-07-02 20:55 ` [ath9k-devel] softlockup in hacked 2.6.34 kernel Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C2E4535.5050208@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.