From: Maxim Nikulin <nikulin@gorodok.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k, compat-wireless-old: kernel panic
Date: Sat, 17 Jan 2009 19:33:06 +0600 [thread overview]
Message-ID: <4971DE12.9010004@gorodok.net> (raw)
Hi,
I try to get wifi working on my laptop, but the result is 'kernel
panic'. The driver is ath9k from compat-wireless-old built for 2.6.24
kernel. Is it supported yet?
Some details:
Commands to reproduce:
modprobe ath9k
rmmod ath9k
Kernel log:
> [ 242.621288] ath9k: 0.1
> [ 242.621343] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 17
> [ 242.621357] PCI: Setting latency timer of device 0000:02:00.0 to 64
> [ 243.055928] phy0: Selected rate control algorithm 'ath9k_rate_control'
> [ 243.176163] Registered led device: ath9k-phy0:radio
> [ 243.176179] Registered led device: ath9k-phy0:assoc
> [ 243.176193] Registered led device: ath9k-phy0:tx
> [ 243.176208] Registered led device: ath9k-phy0:rx
> [ 243.176600] phy0: Atheros 9280: mem=0xf8f00000, irq=17
> [ 269.820518] BUG: unable to handle kernel NULL pointer dereference at virtual address 0000001c
> [ 269.820625] printing eip: c02bcaa6 *pde = 00000000
> [ 269.820746] Oops: 0000 [#1] SMP
> [ 269.820863] Modules linked in: arc4 ecb blkcipher ath9k lbm_cw_mac80211 lbm_cw_cfg80211 nfs lockd nfs_acl sunrpc iptable_filter ip_tables x_tables aes_i586 dm_crypt dm_mod parport_pc lp parport loop joydev serio_raw snd_hda_intel psmouse snd_hwdep snd_pcm_oss pcspkr snd_pcm evdev snd_page_alloc snd_mixer_oss hci_usb bluetooth snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event iTCO_wdt iTCO_vendor_support snd_seq snd_timer snd_seq_device snd shpchp pci_hotplug soundcore battery video output ac asus_laptop led_class button intel_agp agpgart ext3 jbd mbcache usbhid hid sg sr_mod cdrom sd_mod ata_generic pata_acpi ata_piix libata scsi_mod r8169 ehci_hcd uhci_hcd usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse
> [ 269.823948]
> [ 269.823995] Pid: 4985, comm: rmmod Not tainted (2.6.24-22-generic #1)
> [ 269.824050] EIP: 0060:[<c02bcaa6>] EFLAGS: 00010286 CPU: 0
> [ 269.824106] EIP is at tcf_destroy+0x6/0x20
> [ 269.824157] EAX: dfe6f084 EBX: dfe6f084 ECX: 00000292 EDX: 00000000
> [ 269.824210] ESI: dfe6f080 EDI: dfe20180 EBP: f8fffebc ESP: dfda9e6c
> [ 269.824264] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
> [ 269.824317] Process rmmod (pid: 4985, ti=dfda8000 task=dfb8e5c0 task.ti=dfda8000)
> [ 269.824372] Stack: 00000000 c02bcad0 dfe6f000 f8fa5eff dfe6f000 f8fc5820 dfe20180 c02bb37a
> [ 269.824743] df834800 dfe20180 c02bb3da 00000000 00000001 dfda9ea0 dfda9ea0 df834800
> [ 269.825114] c02a9ec9 f8f9b8d8 dfe25eb0 c031b908 dfe25e90 df834800 c02a9f78 dfe20180
> [ 269.825485] Call Trace:
> [ 269.825581] [<c02bcad0>] tcf_destroy_chain+0x10/0x20
> [ 269.825670] [<f8fa5eff>] wme_qdiscop_destroy+0x2f/0x80 [lbm_cw_mac80211]
> [ 269.825782] [<c02bb37a>] qdisc_destroy+0x6a/0xa0
> [ 269.825869] [<c02bb3da>] dev_shutdown+0x2a/0x80
> [ 269.825956] [<c02a9ec9>] rollback_registered+0x99/0x140
> [ 269.826044] [<f8f9b8d8>] ieee80211_remove_interfaces+0x48/0x80 [lbm_cw_mac80211]
> [ 269.826163] [<c031b908>] down_write+0x8/0x20
> [ 269.826250] [<c02a9f78>] unregister_netdevice+0x8/0x50
> [ 269.826338] [<f8f8e720>] lbm_cw_ieee80211_unregister_hw+0x30/0xd0 [lbm_cw_mac80211]
> [ 269.826456] [<f8fdb038>] ath_detach+0x38/0x60 [ath9k]
> [ 269.826555] [<f8fdc661>] ath_pci_remove+0x31/0x60 [ath9k]
> [ 269.826652] [<c0227336>] pci_device_remove+0x16/0x40
> [ 269.826740] [<c0282744>] __device_release_driver+0x64/0xa0
> [ 269.826830] [<c0282c9b>] driver_detach+0xcb/0xd0
> [ 269.826918] [<c0282293>] bus_remove_driver+0x73/0xa0
> [ 269.827006] [<c022740e>] pci_unregister_driver+0xe/0x70
> [ 269.827095] [<f8fe636d>] exit_ath_pci+0xd/0x4a [ath9k]
> [ 269.827191] [<c01520e2>] sys_delete_module+0x112/0x190
> [ 269.827280] [<c031e38f>] do_page_fault+0x13f/0x730
> [ 269.827368] [<c0180450>] do_munmap+0x180/0x1f0
> [ 269.827459] [<c01043b2>] sysenter_past_esp+0x6b/0xa9
> [ 269.827549] [<c0310000>] unix_seqpacket_sendmsg+0x20/0x90
> [ 269.827640] =======================
> [ 269.827689] Code: c5 74 ec 8b 4c 24 18 89 c2 89 d8 89 34 24 ff 17 89 ea 89 c6 89 d8 ff 57 10 eb b0 8d 76 00 8d bc 27 00 00 00 00 53 8b 50 20 89 c3 <ff> 52 1c 8b 43 20 8b 40 38 e8 6c 39 e9 ff 89 d8 5b e9 54 0f ed
> [ 269.829983] EIP: [<c02bcaa6>] tcf_destroy+0x6/0x20 SS:ESP 0068:dfda9e6c
Versions info:
Ubuntu 8.04 hardy, 2.6.24-22-generic kernel
linux-image-2.6.24-22-generic
linux-backports-modules-2.6.24-22-generic
Device info:
> # lspci -vv -s 02:00
> 02:00.0 Network controller: Atheros Communications Inc. Unknown device 002a (rev 01)
> Subsystem: Unknown device 1a3b:1067
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0, Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 5
> Region 0: Memory at fdef0000 (64-bit, non-prefetchable) [size=64K]
> Capabilities: [40] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
> Address: 00000000 Data: 0000
> Capabilities: [60] Express Legacy Endpoint IRQ 0
> Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
> Device: Latency L0s <512ns, L1 <64us
> Device: AtnBtn- AtnInd- PwrInd-
> Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
> Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
> Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
> Link: Supported Speed 2.5Gb/s, Width x1, ASPM unknown, Port 0
> Link: Latency L0s <512ns, L1 <64us
> Link: ASPM L1 Enabled RCB 128 bytes CommClk+ ExtSynch-
> Link: Speed 2.5Gb/s, Width x1
> Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
> Vector table: BAR=0 offset=00000000
> PBA: BAR=0 offset=00000000
ASUS F80L laptop with Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz
The ath9k directory seems to be essentially the same for
compat-wireless-old-2008-10-18.tar.bz2
compat-wireless-old-2009-01-08.tar.bz2
linux-backports-modules-2.6.24-2.6.24
I found ubuntu bug https://bugs.edge.launchpad.net/ubuntu/+bug/272156
and patch for it
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-intrepid.git;a=blobdiff;f=drivers/net/wireless/ath9k/core.h;h=88f4cc3cb8267243aeea999ec5e77c7d59f85508;hp=2f84093331ee79253e58f33ff59006392c54d891;hb=d20a41e5475ded4f2a94e280723c5049a198506b;hpb=8039aec6f6379db690b2ab8ce8fb4a2cd89b4f8a
but it doesn't fix my issue.
Thanks in advance.
--
Maxim Nikulin
next reply other threads:[~2009-01-17 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 13:33 Maxim Nikulin [this message]
2009-01-17 16:21 ` [ath9k-devel] ath9k, compat-wireless-old: kernel panic Sujith
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=4971DE12.9010004@gorodok.net \
--to=nikulin@gorodok.net \
--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.