* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
@ 2009-01-21 6:14 Joseph Cheek
2009-01-21 18:49 ` Luis R. Rodriguez
0 siblings, 1 reply; 20+ messages in thread
From: Joseph Cheek @ 2009-01-21 6:14 UTC (permalink / raw)
To: ath9k-devel
Not sure how reproduceable this is as it's the only one i have seen
yet. but i just got it with 2.6.28.1 and compat-wireless-2009-01-19.
the kernel didn't oops but ifconfig did hang. I could login on another
VC and get a responsive system, but trying to ifconfig the interface
down did not work. i ended up hard-resetting.
Jan 21 00:52:48 harrisburg ath9k 0000:00:07.0: PCI INT A
disabled
Jan 21 00:52:48 harrisburg ath9k: Driver
unloaded
Jan 21 00:52:48 harrisburg ath9k:
0.1
Jan 21 00:52:48 harrisburg ath9k 0000:00:07.0: PCI INT A -> Link[LNKC]
-> GSI 10 (level, low) -> IRQ
10
Jan 21 00:52:48 harrisburg modprobe: page allocation failure. order:1,
mode:0x20
Jan 21 00:52:48 harrisburg Pid: 15273, comm: modprobe Not tainted
2.6.28-gentoo-r1
#1
Jan 21 00:52:48 harrisburg Call
Trace:
Jan 21 00:52:48 harrisburg [<c013cca9>]
0xc013cca9
Jan 21 00:52:48 harrisburg [<c0153a41>]
0xc0153a41
Jan 21 00:52:48 harrisburg [<c0153c92>]
0xc0153c92
Jan 21 00:52:48 harrisburg [<c02ae615>]
0xc02ae615
Jan 21 00:52:48 harrisburg [<c02aee93>]
0xc02aee93
Jan 21 00:52:48 harrisburg [<d9052e70>]
0xd9052e70
Jan 21 00:52:48 harrisburg [<d905364c>]
0xd905364c
Jan 21 00:52:48 harrisburg [<d90527d4>]
0xd90527d4
Jan 21 00:52:48 harrisburg [<d9057524>]
0xd9057524
Jan 21 00:52:48 harrisburg [<c020e8ed>]
0xc020e8ed
Jan 21 00:52:48 harrisburg [<c025b2b9>]
0xc025b2b9
Jan 21 00:52:48 harrisburg [<c025b393>]
0xc025b393
Jan 21 00:52:48 harrisburg [<c025ad0a>]
0xc025ad0a
Jan 21 00:52:48 harrisburg [<c025b16d>]
0xc025b16d
Jan 21 00:52:48 harrisburg [<c025b34a>]
0xc025b34a
Jan 21 00:52:48 harrisburg [<c025a78f>]
0xc025a78f
Jan 21 00:52:48 harrisburg [<d8830000>]
0xd8830000
Jan 21 00:52:48 harrisburg [<c025b4f9>]
0xc025b4f9
Jan 21 00:52:48 harrisburg [<d8830000>]
0xd8830000
Jan 21 00:52:48 harrisburg [<c020eb01>]
0xc020eb01
Jan 21 00:52:48 harrisburg [<d8830000>]
0xd8830000
Jan 21 00:52:48 harrisburg [<d8830038>]
0xd8830038
Jan 21 00:52:48 harrisburg [<c010104c>]
0xc010104c
Jan 21 00:52:48 harrisburg [<c02011e8>]
0xc02011e8
Jan 21 00:52:48 harrisburg [<c013c3c0>]
0xc013c3c0
Jan 21 00:52:48 harrisburg [<c01345a2>]
0xc01345a2
Jan 21 00:52:48 harrisburg [<c020aa6c>]
0xc020aa6c
Jan 21 00:52:48 harrisburg [<c013480e>]
0xc013480e
Jan 21 00:52:48 harrisburg [<c0102c4d>]
0xc0102c4d
Jan 21 00:52:48 harrisburg
Mem-Info:
Jan 21 00:52:48 harrisburg DMA
per-cpu:
Jan 21 00:52:48 harrisburg CPU 0: hi: 0, btch: 1 usd:
0
Jan 21 00:52:48 harrisburg Normal
per-cpu:
Jan 21 00:52:48 harrisburg CPU 0: hi: 186, btch: 31 usd:
156
Jan 21 00:52:48 harrisburg Active_anon:3777 active_file:4577
inactive_anon:3094
Jan 21 00:52:48 harrisburg inactive_file:79345 unevictable:3 dirty:40
writeback:0
unstable:0
Jan 21 00:52:48 harrisburg free:831 slab:3339 mapped:2025 pagetables:124
bounce:0
Jan 21 00:52:48 harrisburg DMA free:1504kB min:100kB low:124kB
high:148kB active_anon:0kB inactive_anon:40kB active_file:116kB
inactive_file:11000kB unevictable:0kB present:15808kB pages_scanned:10
all_unreclaimable? no
Jan 21 00:52:48 harrisburg lowmem_reserve[]: 0 365 365
365
Jan 21 00:52:48 harrisburg Normal free:1820kB min:2392kB low:2988kB
high:3588kB active_anon:15108kB inactive_anon:12336kB
active_file:18192kB inactive_file:306380kB unevictable:12kB
present:373824kB pages_scanned:0 all_unreclaimable? no
Jan 21 00:52:48 harrisburg lowmem_reserve[]: 0 0 0
0
Jan 21 00:52:48 harrisburg DMA: 0*4kB 0*8kB 0*16kB 1*32kB 1*64kB 1*128kB
1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB =
1504kB
Jan 21 00:52:48 harrisburg Normal: 343*4kB 0*8kB 0*16kB 0*32kB 1*64kB
1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB =
1820kB
Jan 21 00:52:48 harrisburg 83959 total pagecache
pages
Jan 21 00:52:48 harrisburg 0 pages in swap
cache
Jan 21 00:52:48 harrisburg Swap cache stats: add 0, delete 0, find
0/0
Jan 21 00:52:48 harrisburg Free swap =
530104kB
Jan 21 00:52:48 harrisburg Total swap =
530104kB
Jan 21 00:52:48 harrisburg 98272 pages
RAM
Jan 21 00:52:48 harrisburg 0 pages
HighMem
Jan 21 00:52:48 harrisburg 1752 pages
reserved
Jan 21 00:52:48 harrisburg 9692 pages
shared
Jan 21 00:52:48 harrisburg 90435 pages
non-shared
Jan 21 00:52:48 harrisburg BUG: unable to handle kernel NULL pointer
dereference at
000001dc
Jan 21 00:52:48 harrisburg IP: [<c02b39be>]
0xc02b39be
Jan 21 00:52:48 harrisburg *pde =
00000000
Jan 21 00:52:48 harrisburg Oops: 0000 [#1]
PREEMPT
Jan 21 00:52:48 harrisburg last sysfs file:
/sys/class/net/wlan0/carrier
Jan 21 00:52:48 harrisburg Modules linked in: ath9k(+) ipv6 snd_via82xx
snd_ac97_codec mac80211 ac97_bus snd_pcm cfg80211 fan snd_page_alloc
thermal snd_mpu401_uart rfkill via_rhine floppy processor snd_rawmidi
mii thermal_sys led_class via_agp agpgart button nfs lockd sunrpc
scsi_wait_scan sbp2 ohci1394 ieee1394 sl811_hcd usbhid ohci_hcd uhci_hcd
usb_storage ehci_hcd usbcore lpfc scsi_transport_fc megaraid_sas
megaraid_mbox megaraid_mm megaraid aacraid 3w_9xxx 3w_xxxx atp870u
dc395x qla1280 dmx3191d sym53c8xx gdth initio BusLogic aic7xxx aic79xx
scsi_transport_spi sg [last unloaded:
ath9k]
Jan 21 00:52:48
harrisburg
Jan 21 00:52:48 harrisburg Pid: 15273, comm: modprobe Not tainted
(2.6.28-gentoo-r1 #1)
KM266-8235
Jan 21 00:52:48 harrisburg EIP: 0060:[<c02b39be>] EFLAGS: 00010202 CPU:
0
Jan 21 00:52:48 harrisburg EAX: 00000001 EBX: 00000000 ECX: d7ae87e8
EDX:
d9004048
Jan 21 00:52:48 harrisburg ESI: d7ae81a0 EDI: fffffff4 EBP: d7ae8d80
ESP:
ce081d2c
Jan 21 00:52:48 harrisburg DS: 007b ES: 007b FS: 0000 GS: 0033 SS:
0068
Jan 21 00:52:48 harrisburg Process modprobe (pid: 15273, ti=ce080000
task=d79a4aa0
task.ti=ce080000)
Jan 21 00:52:48 harrisburg
Stack:
Jan 21 00:52:48 harrisburg 00000000 c02b3b6f d7ae81a0 d8e11145 d7ae8d80
d90521d3 00000000
d7af0000
Jan 21 00:52:48 harrisburg fffffff4 d9052ab3 d7ae81a0 0000000b d7ae9420
d7ae8060 d7ae81a0
d7ae8040
Jan 21 00:52:48 harrisburg 00000000 0000000b 00000008 d7ae81a0 d7ae8d80
d7970800 00000000
d7ae81a0
Jan 21 00:52:48 harrisburg Call
Trace:
Jan 21 00:52:48 harrisburg [<c02b3b6f>]
0xc02b3b6f
Jan 21 00:52:48 harrisburg [<d8e11145>]
0xd8e11145
Jan 21 00:52:48 harrisburg [<d90521d3>]
0xd90521d3
Jan 21 00:52:48 harrisburg [<d9052ab3>]
0xd9052ab3
Jan 21 00:52:48 harrisburg [<d9057524>]
0xd9057524
Jan 21 00:52:48 harrisburg [<c020e8ed>]
0xc020e8ed
Jan 21 00:52:48 harrisburg [<c025b2b9>]
0xc025b2b9
Jan 21 00:52:48 harrisburg [<c025b393>]
0xc025b393
Jan 21 00:52:48 harrisburg [<c025ad0a>]
0xc025ad0a
Jan 21 00:52:48 harrisburg [<c025b16d>]
0xc025b16d
Jan 21 00:52:48 harrisburg [<c025b34a>]
0xc025b34a
Jan 21 00:52:48 harrisburg [<c025a78f>]
0xc025a78f
Jan 21 00:52:48 harrisburg [<d8830000>]
0xd8830000
Jan 21 00:52:48 harrisburg [<c025b4f9>]
0xc025b4f9
Jan 21 00:52:48 harrisburg [<d8830000>]
0xd8830000
Jan 21 00:52:48 harrisburg [<c020eb01>]
0xc020eb01
Jan 21 00:52:48 harrisburg [<d8830000>]
0xd8830000
Jan 21 00:52:48 harrisburg [<d8830038>] 0xd8830038
Jan 21 00:52:48 harrisburg [<c010104c>] 0xc010104c
Jan 21 00:52:48 harrisburg [<c02011e8>] 0xc02011e8
Jan 21 00:52:48 harrisburg [<c013c3c0>] 0xc013c3c0
Jan 21 00:52:48 harrisburg [<c01345a2>] 0xc01345a2
Jan 21 00:52:48 harrisburg [<c020aa6c>] 0xc020aa6c
Jan 21 00:52:48 harrisburg [<c013480e>] 0xc013480e
Jan 21 00:52:48 harrisburg [<c0102c4d>] 0xc0102c4d
Jan 21 00:52:48 harrisburg Code: 74 04 0f 0b eb fe e8 86 61 00 00 85 c0
75 1c 68 2f 0f 00 00 68 28 71 36 c0 68 37 71 36 c0 e8 d1 30 05 00 e8 9e
2f 05 00 83 c4 0c <8b> 83 dc 01 00 00 85 c0 75 1f 53 53 68 dd 73 36 c0
e8 b3 30 05
Jan 21 00:52:48 harrisburg EIP: [<c02b39be>] SS:ESP 0068:ce081d2c
Jan 21 00:52:48 harrisburg ---[ end trace 1e19b49a280dcaa4 ]---
thanks!
Joseph Cheek
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-21 6:14 [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
@ 2009-01-21 18:49 ` Luis R. Rodriguez
2009-01-21 19:54 ` Joseph Cheek
0 siblings, 1 reply; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-01-21 18:49 UTC (permalink / raw)
To: ath9k-devel
On Tue, Jan 20, 2009 at 10:14 PM, Joseph Cheek <joseph@cheek.com> wrote:
> Not sure how reproduceable this is as it's the only one i have seen
> yet. but i just got it with 2.6.28.1 and compat-wireless-2009-01-19.
> the kernel didn't oops
>
> but ifconfig did hang. I could login on another
> VC and get a responsive system, but trying to ifconfig the interface
> down did not work. i ended up hard-resetting.
Can you reproduce?
> Jan 21 00:52:48 harrisburg EIP: [<c02b39be>] SS:ESP 0068:ce081d2c
Enable kernel debugging and then the above will have the routine where
this came from.
Luis
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-21 18:49 ` Luis R. Rodriguez
@ 2009-01-21 19:54 ` Joseph Cheek
2009-01-21 22:18 ` Joseph Cheek
0 siblings, 1 reply; 20+ messages in thread
From: Joseph Cheek @ 2009-01-21 19:54 UTC (permalink / raw)
To: ath9k-devel
I got another repro. I'll rebuild the kernel with debugging support and
send you the syslog when it happens next time.
Luis R. Rodriguez wrote:
> On Tue, Jan 20, 2009 at 10:14 PM, Joseph Cheek <joseph@cheek.com> wrote:
>
>> Not sure how reproduceable this is as it's the only one i have seen
>> yet. but i just got it with 2.6.28.1 and compat-wireless-2009-01-19.
>> the kernel didn't oops
>>
>> but ifconfig did hang. I could login on another
>> VC and get a responsive system, but trying to ifconfig the interface
>> down did not work. i ended up hard-resetting.
>>
>
> Can you reproduce?
>
>
>> Jan 21 00:52:48 harrisburg EIP: [<c02b39be>] SS:ESP 0068:ce081d2c
>>
>
> Enable kernel debugging and then the above will have the routine where
> this came from.
>
> Luis
>
>
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-21 19:54 ` Joseph Cheek
@ 2009-01-21 22:18 ` Joseph Cheek
2009-01-22 19:19 ` Joseph Cheek
0 siblings, 1 reply; 20+ messages in thread
From: Joseph Cheek @ 2009-01-21 22:18 UTC (permalink / raw)
To: ath9k-devel
debug was already on in the kernel. i enabled a few more options but
don' t know which options prints the calling function at EIP. are there
specific options you would like turned on? Here's the latest call trace.
Jan 21 16:21:11 harrisburg modprobe: page allocation failure. order:1,
mode:0x20
Jan 21 16:21:11 harrisburg Pid: 10616, comm: modprobe Not tainted
2.6.28-gentoo-r1
#1
Jan 21 16:21:11 harrisburg Call
Trace:
Jan 21 16:21:11 harrisburg [<c013cd39>]
0xc013cd39
Jan 21 16:21:11 harrisburg [<c0153b79>]
0xc0153b79
Jan 21 16:21:11 harrisburg [<c0153dca>]
0xc0153dca
Jan 21 16:21:11 harrisburg [<c02ae791>]
0xc02ae791
Jan 21 16:21:11 harrisburg [<c02af00f>]
0xc02af00f
Jan 21 16:21:11 harrisburg [<d8d44e70>]
0xd8d44e70
Jan 21 16:21:11 harrisburg [<d8d4564c>]
0xd8d4564c
Jan 21 16:21:11 harrisburg [<d8d447d4>]
0xd8d447d4
Jan 21 16:21:11 harrisburg [<d8d49528>]
0xd8d49528
Jan 21 16:21:11 harrisburg [<c020ea75>]
0xc020ea75
Jan 21 16:21:11 harrisburg [<c025b435>]
0xc025b435
Jan 21 16:21:11 harrisburg [<c025b50f>]
0xc025b50f
Jan 21 16:21:11 harrisburg [<c025ae86>]
0xc025ae86
Jan 21 16:21:11 harrisburg [<c025b2e9>]
0xc025b2e9
Jan 21 16:21:11 harrisburg [<c025b4c6>]
0xc025b4c6
Jan 21 16:21:11 harrisburg [<c025a90b>]
0xc025a90b
Jan 21 16:21:11 harrisburg [<d8834000>]
0xd8834000
Jan 21 16:21:11 harrisburg [<c025b675>]
0xc025b675
Jan 21 16:21:11 harrisburg [<d8834000>]
0xd8834000
Jan 21 16:21:11 harrisburg [<c020ec89>]
0xc020ec89
Jan 21 16:21:11 harrisburg [<d8834000>]
0xd8834000
Jan 21 16:21:11 harrisburg [<d8834038>]
0xd8834038
Jan 21 16:21:11 harrisburg [<c010104c>]
0xc010104c
Jan 21 16:21:11 harrisburg [<c013c236>]
0xc013c236
Jan 21 16:21:11 harrisburg [<c013c440>]
0xc013c440
Jan 21 16:21:11 harrisburg [<c0134606>]
0xc0134606
Jan 21 16:21:11 harrisburg [<c020abf0>]
0xc020abf0
Jan 21 16:21:11 harrisburg [<c0134872>]
0xc0134872
Jan 21 16:21:11 harrisburg [<c0102c4d>]
0xc0102c4d
Jan 21 16:21:11 harrisburg
Mem-Info:
Jan 21 16:21:11 harrisburg DMA
per-cpu:
Jan 21 16:21:11 harrisburg CPU 0: hi: 0, btch: 1 usd:
0
Jan 21 16:21:11 harrisburg Normal
per-cpu:
Jan 21 16:21:11 harrisburg CPU 0: hi: 186, btch: 31 usd:
51
Jan 21 16:21:11 harrisburg Active_anon:7443 active_file:7679
inactive_anon:7428
Jan 21 16:21:11 harrisburg inactive_file:65044 unevictable:2 dirty:375
writeback:0
unstable:0
Jan 21 16:21:11 harrisburg free:784 slab:3701 mapped:1576 pagetables:238
bounce:0
Jan 21 16:21:11 harrisburg DMA free:1504kB min:100kB low:124kB
high:148kB active_anon:32kB inactive_anon:296kB active_file:100kB
inactive_file:10236kB unevictable:0kB present:15808kB pages_scanned:0
all_unreclaimable? no
Jan 21 16:21:11 harrisburg lowmem_reserve[]: 0 365 365
365
Jan 21 16:21:11 harrisburg Normal free:1632kB min:2392kB low:2988kB
high:3588kB active_anon:29740kB inactive_anon:29416kB
active_file:30616kB inactive_file:249940kB unevictable:8kB
present:373824kB pages_scanned:0 all_unreclaimable? no
Jan 21 16:21:11 harrisburg lowmem_reserve[]: 0 0 0
0
Jan 21 16:21:11 harrisburg DMA: 0*4kB 0*8kB 0*16kB 1*32kB 1*64kB 1*128kB
1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB =
1504kB
Jan 21 16:21:11 harrisburg Normal: 296*4kB 0*8kB 0*16kB 0*32kB 1*64kB
1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB =
1632kB
Jan 21 16:21:11 harrisburg 72757 total pagecache
pages
Jan 21 16:21:11 harrisburg 0 pages in swap
cache
Jan 21 16:21:11 harrisburg Swap cache stats: add 0, delete 0, find
0/0
Jan 21 16:21:11 harrisburg Free swap =
530104kB
Jan 21 16:21:11 harrisburg Total swap =
530104kB
Jan 21 16:21:11 harrisburg 98272 pages
RAM
Jan 21 16:21:11 harrisburg 0 pages
HighMem
Jan 21 16:21:11 harrisburg 4397 pages
reserved
Jan 21 16:21:11 harrisburg 22474 pages
shared
Jan 21 16:21:11 harrisburg 84761 pages
non-shared
Jan 21 16:21:11 harrisburg BUG: unable to handle kernel NULL pointer
dereference at
000001dc
Jan 21 16:21:11 harrisburg IP: [<c02b3b3a>]
0xc02b3b3a
Jan 21 16:21:11 harrisburg *pde =
00000000
Jan 21 16:21:11 harrisburg Oops: 0000 [#1] PREEMPT
DEBUG_PAGEALLOC
Jan 21 16:21:11 harrisburg last sysfs file:
/sys/class/net/wlan0/carrier
Jan 21 16:21:11 harrisburg Modules linked in: ath9k(+) ipv6 mac80211
snd_via82xx snd_ac97_codec cfg80211 ac97_bus snd_pcm fan via_rhine
thermal rfkill snd_page_alloc via_agp floppy processor mii
snd_mpu401_uart led_class agpgart snd_rawmidi button thermal_sys nfs
lockd sunrpc scsi_wait_scan sbp2 ohci1394 ieee1394 sl811_hcd usbhid
ohci_hcd uhci_hcd usb_storage ehci_hcd usbcore lpfc scsi_transport_fc
megaraid_sas megaraid_mbox megaraid_mm megaraid aacraid 3w_9xxx 3w_xxxx
atp870u dc395x qla1280 dmx3191d sym53c8xx gdth initio BusLogic aic7xxx
aic79xx scsi_transport_spi sg [last unloaded:
ath9k]
Jan 21 16:21:11
harrisburg
Jan 21 16:21:11 harrisburg Pid: 10616, comm: modprobe Not tainted
(2.6.28-gentoo-r1 #1)
KM266-8235
Jan 21 16:21:11 harrisburg EIP: 0060:[<c02b3b3a>] EFLAGS: 00010202 CPU:
0
Jan 21 16:21:11 harrisburg EAX: 00000001 EBX: 00000000 ECX: d65007e8
EDX:
d8e84048
Jan 21 16:21:11 harrisburg ESI: d65001a0 EDI: fffffff4 EBP: d6500d80
ESP:
cc66fd2c
Jan 21 16:21:11 harrisburg DS: 007b ES: 007b FS: 0000 GS: 0033 SS:
0068
Jan 21 16:21:11 harrisburg Process modprobe (pid: 10616, ti=cc66e000
task=d57f2ee0
task.ti=cc66e000)
Jan 21 16:21:11 harrisburg
Stack:
Jan 21 16:21:11 harrisburg 00000000 c02b3ceb d65001a0 d8c04145 d6500d80
d8d441d3 00000000
d5310000
Jan 21 16:21:11 harrisburg fffffff4 d8d44ab3 d65001a0 0000000b d6501420
d6500060 d65001a0
d6500040
Jan 21 16:21:11 harrisburg 00000000 0000000b 00000008 d65001a0 d6500d80
d7170800 00000000
d65001a0
Jan 21 16:21:11 harrisburg Call
Trace:
Jan 21 16:21:11 harrisburg [<c02b3ceb>]
0xc02b3ceb
Jan 21 16:21:11 harrisburg [<d8c04145>]
0xd8c04145
Jan 21 16:21:11 harrisburg [<d8d441d3>]
0xd8d441d3
Jan 21 16:21:11 harrisburg [<d8d44ab3>]
0xd8d44ab3
Jan 21 16:21:11 harrisburg [<d8d49528>]
0xd8d49528
Jan 21 16:21:11 harrisburg [<c020ea75>]
0xc020ea75
Jan 21 16:21:11 harrisburg [<c025b435>]
0xc025b435
Jan 21 16:21:11 harrisburg [<c025b50f>]
0xc025b50f
Jan 21 16:21:11 harrisburg [<c025ae86>]
0xc025ae86
Jan 21 16:21:11 harrisburg [<c025b2e9>]
0xc025b2e9
Jan 21 16:21:11 harrisburg [<c025b4c6>]
0xc025b4c6
Jan 21 16:21:11 harrisburg [<c025a90b>]
0xc025a90b
Jan 21 16:21:11 harrisburg [<d8834000>]
0xd8834000
Jan 21 16:21:11 harrisburg [<c025b675>]
0xc025b675
Jan 21 16:21:11 harrisburg [<d8834000>]
0xd8834000
Jan 21 16:21:11 harrisburg [<c020ec89>]
0xc020ec89
Jan 21 16:21:11 harrisburg [<d8834000>]
0xd8834000
Jan 21 16:21:11 harrisburg [<d8834038>]
0xd8834038
Jan 21 16:21:11 harrisburg [<c010104c>]
0xc010104c
Jan 21 16:21:11 harrisburg [<c013c236>]
0xc013c236
Jan 21 16:21:11 harrisburg [<c013c440>]
0xc013c440
Jan 21 16:21:11 harrisburg [<c0134606>]
0xc0134606
Jan 21 16:21:11 harrisburg [<c020abf0>]
0xc020abf0
Jan 21 16:21:11 harrisburg [<c0134872>]
0xc0134872
Jan 21 16:21:11 harrisburg [<c0102c4d>] 0xc0102c4d
Jan 21 16:21:11 harrisburg Code: 74 04 0f 0b eb fe e8 86 61 00 00 85 c0
75 1c 68 2f 0f 00 00 68 2a 7d 36 c0 68 ef 7f 36 c0 e8 a9 30 05 00 e8 76
2f 05 00 83 c4 0c <8b> 83 dc 01 00 00 85 c0 75 1f 53 53 68 95 82 36 c0
e8 8b 30 05
Jan 21 16:21:11 harrisburg EIP: [<c02b3b3a>] SS:ESP 0068:cc66fd2c
Jan 21 16:21:11 harrisburg ---[ end trace d33038261cc054eb ]---
Joseph Cheek wrote:
> I got another repro. I'll rebuild the kernel with debugging support and
> send you the syslog when it happens next time.
>
>
> Luis R. Rodriguez wrote:
>
>> On Tue, Jan 20, 2009 at 10:14 PM, Joseph Cheek <joseph@cheek.com> wrote:
>>
>>
>>> Not sure how reproduceable this is as it's the only one i have seen
>>> yet. but i just got it with 2.6.28.1 and compat-wireless-2009-01-19.
>>> the kernel didn't oops
>>>
>>> but ifconfig did hang. I could login on another
>>> VC and get a responsive system, but trying to ifconfig the interface
>>> down did not work. i ended up hard-resetting.
>>>
>>>
>> Can you reproduce?
>>
>>
>>
>>> Jan 21 00:52:48 harrisburg EIP: [<c02b39be>] SS:ESP 0068:ce081d2c
>>>
>>>
>> Enable kernel debugging and then the above will have the routine where
>> this came from.
>>
>> Luis
>>
>>
>>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-21 22:18 ` Joseph Cheek
@ 2009-01-22 19:19 ` Joseph Cheek
2009-01-22 19:44 ` Luis R. Rodriguez
0 siblings, 1 reply; 20+ messages in thread
From: Joseph Cheek @ 2009-01-22 19:19 UTC (permalink / raw)
To: ath9k-devel
I just got a repro of this on 2.6.27.12 with compat-wireless
2009-01-19. i'm going back to 2.6.27.11 with compat-wireless 2008-12-31
to see if it is more stable (I never got the bug on that one).
here are the config_debug options i had on for this last strace. please
let me know what other options you would like me to turn on so i can
make the trace more useful.
thanks!
Joseph Cheek
$ grep CONFIG_DEBUG /etc/kernels/kernel-config-x86-2.6.28-gentoo-r1
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_FS is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
CONFIG_DEBUG_PAGEALLOC=y
# CONFIG_DEBUG_RODATA is not set
# CONFIG_DEBUG_NX_TEST is not set
Joseph Cheek wrote:
> debug was already on in the kernel. i enabled a few more options but
> don' t know which options prints the calling function at EIP. are there
> specific options you would like turned on? Here's the latest call trace.
>
> Jan 21 16:21:11 harrisburg modprobe: page allocation failure. order:1,
> mode:0x20
> Jan 21 16:21:11 harrisburg Pid: 10616, comm: modprobe Not tainted
> 2.6.28-gentoo-r1
> #1
>
> Jan 21 16:21:11 harrisburg Call
> Trace:
> Jan 21 16:21:11 harrisburg [<c013cd39>]
> 0xc013cd39
> Jan 21 16:21:11 harrisburg [<c0153b79>]
> 0xc0153b79
> Jan 21 16:21:11 harrisburg [<c0153dca>]
> 0xc0153dca
> Jan 21 16:21:11 harrisburg [<c02ae791>]
> 0xc02ae791
> Jan 21 16:21:11 harrisburg [<c02af00f>]
> 0xc02af00f
> Jan 21 16:21:11 harrisburg [<d8d44e70>]
> 0xd8d44e70
> Jan 21 16:21:11 harrisburg [<d8d4564c>]
> 0xd8d4564c
> Jan 21 16:21:11 harrisburg [<d8d447d4>]
> 0xd8d447d4
> Jan 21 16:21:11 harrisburg [<d8d49528>]
> 0xd8d49528
> Jan 21 16:21:11 harrisburg [<c020ea75>]
> 0xc020ea75
> Jan 21 16:21:11 harrisburg [<c025b435>]
> 0xc025b435
> Jan 21 16:21:11 harrisburg [<c025b50f>]
> 0xc025b50f
> Jan 21 16:21:11 harrisburg [<c025ae86>]
> 0xc025ae86
> Jan 21 16:21:11 harrisburg [<c025b2e9>]
> 0xc025b2e9
> Jan 21 16:21:11 harrisburg [<c025b4c6>]
> 0xc025b4c6
> Jan 21 16:21:11 harrisburg [<c025a90b>]
> 0xc025a90b
> Jan 21 16:21:11 harrisburg [<d8834000>]
> 0xd8834000
> Jan 21 16:21:11 harrisburg [<c025b675>]
> 0xc025b675
> Jan 21 16:21:11 harrisburg [<d8834000>]
> 0xd8834000
> Jan 21 16:21:11 harrisburg [<c020ec89>]
> 0xc020ec89
> Jan 21 16:21:11 harrisburg [<d8834000>]
> 0xd8834000
> Jan 21 16:21:11 harrisburg [<d8834038>]
> 0xd8834038
> Jan 21 16:21:11 harrisburg [<c010104c>]
> 0xc010104c
> Jan 21 16:21:11 harrisburg [<c013c236>]
> 0xc013c236
> Jan 21 16:21:11 harrisburg [<c013c440>]
> 0xc013c440
> Jan 21 16:21:11 harrisburg [<c0134606>]
> 0xc0134606
> Jan 21 16:21:11 harrisburg [<c020abf0>]
> 0xc020abf0
> Jan 21 16:21:11 harrisburg [<c0134872>]
> 0xc0134872
> Jan 21 16:21:11 harrisburg [<c0102c4d>]
> 0xc0102c4d
> Jan 21 16:21:11 harrisburg
> Mem-Info:
> Jan 21 16:21:11 harrisburg DMA
> per-cpu:
> Jan 21 16:21:11 harrisburg CPU 0: hi: 0, btch: 1 usd:
> 0
> Jan 21 16:21:11 harrisburg Normal
> per-cpu:
> Jan 21 16:21:11 harrisburg CPU 0: hi: 186, btch: 31 usd:
> 51
> Jan 21 16:21:11 harrisburg Active_anon:7443 active_file:7679
> inactive_anon:7428
> Jan 21 16:21:11 harrisburg inactive_file:65044 unevictable:2 dirty:375
> writeback:0
> unstable:0
>
> Jan 21 16:21:11 harrisburg free:784 slab:3701 mapped:1576 pagetables:238
> bounce:0
>
> Jan 21 16:21:11 harrisburg DMA free:1504kB min:100kB low:124kB
> high:148kB active_anon:32kB inactive_anon:296kB active_file:100kB
> inactive_file:10236kB unevictable:0kB present:15808kB pages_scanned:0
> all_unreclaimable? no
> Jan 21 16:21:11 harrisburg lowmem_reserve[]: 0 365 365
> 365
> Jan 21 16:21:11 harrisburg Normal free:1632kB min:2392kB low:2988kB
> high:3588kB active_anon:29740kB inactive_anon:29416kB
> active_file:30616kB inactive_file:249940kB unevictable:8kB
> present:373824kB pages_scanned:0 all_unreclaimable? no
> Jan 21 16:21:11 harrisburg lowmem_reserve[]: 0 0 0
> 0
> Jan 21 16:21:11 harrisburg DMA: 0*4kB 0*8kB 0*16kB 1*32kB 1*64kB 1*128kB
> 1*256kB 0*512kB 1*1024kB 0*2048kB 0*4096kB =
> 1504kB
> Jan 21 16:21:11 harrisburg Normal: 296*4kB 0*8kB 0*16kB 0*32kB 1*64kB
> 1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB =
> 1632kB
> Jan 21 16:21:11 harrisburg 72757 total pagecache
> pages
> Jan 21 16:21:11 harrisburg 0 pages in swap
> cache
> Jan 21 16:21:11 harrisburg Swap cache stats: add 0, delete 0, find
> 0/0
> Jan 21 16:21:11 harrisburg Free swap =
> 530104kB
> Jan 21 16:21:11 harrisburg Total swap =
> 530104kB
> Jan 21 16:21:11 harrisburg 98272 pages
> RAM
> Jan 21 16:21:11 harrisburg 0 pages
> HighMem
> Jan 21 16:21:11 harrisburg 4397 pages
> reserved
> Jan 21 16:21:11 harrisburg 22474 pages
> shared
> Jan 21 16:21:11 harrisburg 84761 pages
> non-shared
> Jan 21 16:21:11 harrisburg BUG: unable to handle kernel NULL pointer
> dereference at
> 000001dc
> Jan 21 16:21:11 harrisburg IP: [<c02b3b3a>]
> 0xc02b3b3a
> Jan 21 16:21:11 harrisburg *pde =
> 00000000
> Jan 21 16:21:11 harrisburg Oops: 0000 [#1] PREEMPT
> DEBUG_PAGEALLOC
> Jan 21 16:21:11 harrisburg last sysfs file:
> /sys/class/net/wlan0/carrier
> Jan 21 16:21:11 harrisburg Modules linked in: ath9k(+) ipv6 mac80211
> snd_via82xx snd_ac97_codec cfg80211 ac97_bus snd_pcm fan via_rhine
> thermal rfkill snd_page_alloc via_agp floppy processor mii
> snd_mpu401_uart led_class agpgart snd_rawmidi button thermal_sys nfs
> lockd sunrpc scsi_wait_scan sbp2 ohci1394 ieee1394 sl811_hcd usbhid
> ohci_hcd uhci_hcd usb_storage ehci_hcd usbcore lpfc scsi_transport_fc
> megaraid_sas megaraid_mbox megaraid_mm megaraid aacraid 3w_9xxx 3w_xxxx
> atp870u dc395x qla1280 dmx3191d sym53c8xx gdth initio BusLogic aic7xxx
> aic79xx scsi_transport_spi sg [last unloaded:
> ath9k]
> Jan 21 16:21:11
> harrisburg
> Jan 21 16:21:11 harrisburg Pid: 10616, comm: modprobe Not tainted
> (2.6.28-gentoo-r1 #1)
> KM266-8235
> Jan 21 16:21:11 harrisburg EIP: 0060:[<c02b3b3a>] EFLAGS: 00010202 CPU:
> 0
> Jan 21 16:21:11 harrisburg EAX: 00000001 EBX: 00000000 ECX: d65007e8
> EDX:
> d8e84048
>
> Jan 21 16:21:11 harrisburg ESI: d65001a0 EDI: fffffff4 EBP: d6500d80
> ESP:
> cc66fd2c
>
> Jan 21 16:21:11 harrisburg DS: 007b ES: 007b FS: 0000 GS: 0033 SS:
> 0068
> Jan 21 16:21:11 harrisburg Process modprobe (pid: 10616, ti=cc66e000
> task=d57f2ee0
> task.ti=cc66e000)
>
> Jan 21 16:21:11 harrisburg
> Stack:
> Jan 21 16:21:11 harrisburg 00000000 c02b3ceb d65001a0 d8c04145 d6500d80
> d8d441d3 00000000
> d5310000
> Jan 21 16:21:11 harrisburg fffffff4 d8d44ab3 d65001a0 0000000b d6501420
> d6500060 d65001a0
> d6500040
> Jan 21 16:21:11 harrisburg 00000000 0000000b 00000008 d65001a0 d6500d80
> d7170800 00000000
> d65001a0
> Jan 21 16:21:11 harrisburg Call
> Trace:
> Jan 21 16:21:11 harrisburg [<c02b3ceb>]
> 0xc02b3ceb
> Jan 21 16:21:11 harrisburg [<d8c04145>]
> 0xd8c04145
> Jan 21 16:21:11 harrisburg [<d8d441d3>]
> 0xd8d441d3
> Jan 21 16:21:11 harrisburg [<d8d44ab3>]
> 0xd8d44ab3
> Jan 21 16:21:11 harrisburg [<d8d49528>]
> 0xd8d49528
> Jan 21 16:21:11 harrisburg [<c020ea75>]
> 0xc020ea75
> Jan 21 16:21:11 harrisburg [<c025b435>]
> 0xc025b435
> Jan 21 16:21:11 harrisburg [<c025b50f>]
> 0xc025b50f
> Jan 21 16:21:11 harrisburg [<c025ae86>]
> 0xc025ae86
> Jan 21 16:21:11 harrisburg [<c025b2e9>]
> 0xc025b2e9
> Jan 21 16:21:11 harrisburg [<c025b4c6>]
> 0xc025b4c6
> Jan 21 16:21:11 harrisburg [<c025a90b>]
> 0xc025a90b
> Jan 21 16:21:11 harrisburg [<d8834000>]
> 0xd8834000
> Jan 21 16:21:11 harrisburg [<c025b675>]
> 0xc025b675
> Jan 21 16:21:11 harrisburg [<d8834000>]
> 0xd8834000
> Jan 21 16:21:11 harrisburg [<c020ec89>]
> 0xc020ec89
> Jan 21 16:21:11 harrisburg [<d8834000>]
> 0xd8834000
> Jan 21 16:21:11 harrisburg [<d8834038>]
> 0xd8834038
> Jan 21 16:21:11 harrisburg [<c010104c>]
> 0xc010104c
> Jan 21 16:21:11 harrisburg [<c013c236>]
> 0xc013c236
> Jan 21 16:21:11 harrisburg [<c013c440>]
> 0xc013c440
> Jan 21 16:21:11 harrisburg [<c0134606>]
> 0xc0134606
> Jan 21 16:21:11 harrisburg [<c020abf0>]
> 0xc020abf0
> Jan 21 16:21:11 harrisburg [<c0134872>]
> 0xc0134872
> Jan 21 16:21:11 harrisburg [<c0102c4d>] 0xc0102c4d
> Jan 21 16:21:11 harrisburg Code: 74 04 0f 0b eb fe e8 86 61 00 00 85 c0
> 75 1c 68 2f 0f 00 00 68 2a 7d 36 c0 68 ef 7f 36 c0 e8 a9 30 05 00 e8 76
> 2f 05 00 83 c4 0c <8b> 83 dc 01 00 00 85 c0 75 1f 53 53 68 95 82 36 c0
> e8 8b 30 05
> Jan 21 16:21:11 harrisburg EIP: [<c02b3b3a>] SS:ESP 0068:cc66fd2c
> Jan 21 16:21:11 harrisburg ---[ end trace d33038261cc054eb ]---
>
>
> Joseph Cheek wrote:
>
>> I got another repro. I'll rebuild the kernel with debugging support and
>> send you the syslog when it happens next time.
>>
>>
>> Luis R. Rodriguez wrote:
>>
>>
>>> On Tue, Jan 20, 2009 at 10:14 PM, Joseph Cheek <joseph@cheek.com> wrote:
>>>
>>>
>>>
>>>> Not sure how reproduceable this is as it's the only one i have seen
>>>> yet. but i just got it with 2.6.28.1 and compat-wireless-2009-01-19.
>>>> the kernel didn't oops
>>>>
>>>> but ifconfig did hang. I could login on another
>>>> VC and get a responsive system, but trying to ifconfig the interface
>>>> down did not work. i ended up hard-resetting.
>>>>
>>>>
>>>>
>>> Can you reproduce?
>>>
>>>
>>>
>>>
>>>> Jan 21 00:52:48 harrisburg EIP: [<c02b39be>] SS:ESP 0068:ce081d2c
>>>>
>>>>
>>>>
>>> Enable kernel debugging and then the above will have the routine where
>>> this came from.
>>>
>>> Luis
>>>
>>>
>>>
>>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-22 19:19 ` Joseph Cheek
@ 2009-01-22 19:44 ` Luis R. Rodriguez
2009-01-25 0:32 ` Joseph Cheek
0 siblings, 1 reply; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-01-22 19:44 UTC (permalink / raw)
To: ath9k-devel
On Thu, Jan 22, 2009 at 11:19:00AM -0800, Joseph Cheek wrote:
> I just got a repro of this on 2.6.27.12 with compat-wireless
> 2009-01-19. i'm going back to 2.6.27.11 with compat-wireless 2008-12-31
> to see if it is more stable (I never got the bug on that one).
>
> here are the config_debug options i had on for this last strace. please
> let me know what other options you would like me to turn on so i can
> make the trace more useful.
>
> thanks!
>
> Joseph Cheek
>
> CONFIG_DEBUG_KERNEL=y
> CONFIG_DEBUG_PREEMPT=y
> CONFIG_DEBUG_BUGVERBOSE=y
> CONFIG_DEBUG_INFO=y
> CONFIG_DEBUG_MEMORY_INIT=y
> CONFIG_DEBUG_PAGEALLOC=y
These are good, CONFIG_DEBUG_INFO=y is what I was looking for too.
Not sure why you don't get what I expect. Try using ksymoops then,
or you can also just recompile using wireless-testing kernel directly:
http://wireless.kernel.org/en/developers/Documentation/git-guide
This has the latest RC kernel + all the wireless stuff we have queued up
for 2.6.30 (what compat-wireless picks up).
Luis
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-22 19:44 ` Luis R. Rodriguez
@ 2009-01-25 0:32 ` Joseph Cheek
2009-01-25 2:23 ` Luis R. Rodriguez
` (2 more replies)
0 siblings, 3 replies; 20+ messages in thread
From: Joseph Cheek @ 2009-01-25 0:32 UTC (permalink / raw)
To: ath9k-devel
ok. I just got a repro on 2.6.27.11 with compat-wireless-2008-12-31.
it appears to occur when i bring down the interface, rmmod ath9k, and
then modprobe ath9k while I am trying to rsync from or to the box. I
bounce the interface like this often when I lose transmission for
several seconds at a time. most of the time it recovers ok, but
sometimes it doesn't.
i'll try git tip on monday.
Thanks!
Joseph
Luis R. Rodriguez wrote:
> On Thu, Jan 22, 2009 at 11:19:00AM -0800, Joseph Cheek wrote:
>
>> I just got a repro of this on 2.6.27.12 with compat-wireless
>> 2009-01-19. i'm going back to 2.6.27.11 with compat-wireless 2008-12-31
>> to see if it is more stable (I never got the bug on that one).
>>
>> here are the config_debug options i had on for this last strace. please
>> let me know what other options you would like me to turn on so i can
>> make the trace more useful.
>>
>> thanks!
>>
>> Joseph Cheek
>>
>> CONFIG_DEBUG_KERNEL=y
>> CONFIG_DEBUG_PREEMPT=y
>> CONFIG_DEBUG_BUGVERBOSE=y
>> CONFIG_DEBUG_INFO=y
>> CONFIG_DEBUG_MEMORY_INIT=y
>> CONFIG_DEBUG_PAGEALLOC=y
>>
>
> These are good, CONFIG_DEBUG_INFO=y is what I was looking for too.
> Not sure why you don't get what I expect. Try using ksymoops then,
> or you can also just recompile using wireless-testing kernel directly:
>
> http://wireless.kernel.org/en/developers/Documentation/git-guide
>
> This has the latest RC kernel + all the wireless stuff we have queued up
> for 2.6.30 (what compat-wireless picks up).
>
> Luis
>
>
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-25 0:32 ` Joseph Cheek
@ 2009-01-25 2:23 ` Luis R. Rodriguez
2009-01-25 2:27 ` Stephen Gutknecht
2009-02-02 22:21 ` Joseph Cheek
2 siblings, 0 replies; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-01-25 2:23 UTC (permalink / raw)
To: ath9k-devel
On Sat, Jan 24, 2009 at 4:32 PM, Joseph Cheek <joseph@cheek.com> wrote:
> ok. I just got a repro on 2.6.27.11 with compat-wireless-2008-12-31.
> it appears to occur when i bring down the interface, rmmod ath9k, and
> then modprobe ath9k while I am trying to rsync from or to the box. I
> bounce the interface like this often when I lose transmission for
> several seconds at a time. most of the time it recovers ok, but
> sometimes it doesn't.
>
> i'll try git tip on monday.
Yes please try to upgrade, compat-wireless-2008-12-31 is ancient now :)
Luis
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-25 0:32 ` Joseph Cheek
2009-01-25 2:23 ` Luis R. Rodriguez
@ 2009-01-25 2:27 ` Stephen Gutknecht
2009-02-02 22:21 ` Joseph Cheek
2 siblings, 0 replies; 20+ messages in thread
From: Stephen Gutknecht @ 2009-01-25 2:27 UTC (permalink / raw)
To: ath9k-devel
On Sat, Jan 24, 2009 at 4:32 PM, Joseph Cheek <joseph@cheek.com> wrote:
> ok. I just got a repro on 2.6.27.11 with compat-wireless-2008-12-31.
> it appears to occur when i bring down the interface, rmmod ath9k, and
> then modprobe ath9k while I am trying to rsync from or to the box. I
> bounce the interface like this often when I lose transmission for
> several seconds at a time. most of the time it recovers ok, but
> sometimes it doesn't.
Perhaps this is unrelated, but posting it.... modprobe on ahb bus
routers has a chance of crashing and rebooting with no message to
console. I'd estimate it is about 1/30 chance of happening. If I do
the sequence you describe... down, rmmod, modprobe ath9k it sometimes
reboots the router on the modprobe. This is on compat-wireless
2009-01-23 with 2.6.28 kernel, OpenWRT, Trendnet TEW-652BRP router. I
had seen this on earlier releases... but wanted to confirm it is on
recent I tested today.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-01-25 0:32 ` Joseph Cheek
2009-01-25 2:23 ` Luis R. Rodriguez
2009-01-25 2:27 ` Stephen Gutknecht
@ 2009-02-02 22:21 ` Joseph Cheek
2009-02-02 23:50 ` Luis R. Rodriguez
2 siblings, 1 reply; 20+ messages in thread
From: Joseph Cheek @ 2009-02-02 22:21 UTC (permalink / raw)
To: ath9k-devel
I've been trying git tip for a week and no more kernel OOPS! great job,
thanks!
I also did NOT have to change IEEE_MONITORING_INTERVAL to stay
connected. *But* I still lose connectivity for several seconds during a
large file transfer (most often transferring 50M or more via scp or
rsync -e ssh).
Joseph Cheek
Joseph Cheek wrote:
> ok. I just got a repro on 2.6.27.11 with compat-wireless-2008-12-31.
> it appears to occur when i bring down the interface, rmmod ath9k, and
> then modprobe ath9k while I am trying to rsync from or to the box. I
> bounce the interface like this often when I lose transmission for
> several seconds at a time. most of the time it recovers ok, but
> sometimes it doesn't.
>
> i'll try git tip on monday.
>
> Thanks!
>
> Joseph
>
> Luis R. Rodriguez wrote:
>
>> On Thu, Jan 22, 2009 at 11:19:00AM -0800, Joseph Cheek wrote:
>>
>>
>>> I just got a repro of this on 2.6.27.12 with compat-wireless
>>> 2009-01-19. i'm going back to 2.6.27.11 with compat-wireless 2008-12-31
>>> to see if it is more stable (I never got the bug on that one).
>>>
>>> here are the config_debug options i had on for this last strace. please
>>> let me know what other options you would like me to turn on so i can
>>> make the trace more useful.
>>>
>>> thanks!
>>>
>>> Joseph Cheek
>>>
>>> CONFIG_DEBUG_KERNEL=y
>>> CONFIG_DEBUG_PREEMPT=y
>>> CONFIG_DEBUG_BUGVERBOSE=y
>>> CONFIG_DEBUG_INFO=y
>>> CONFIG_DEBUG_MEMORY_INIT=y
>>> CONFIG_DEBUG_PAGEALLOC=y
>>>
>>>
>> These are good, CONFIG_DEBUG_INFO=y is what I was looking for too.
>> Not sure why you don't get what I expect. Try using ksymoops then,
>> or you can also just recompile using wireless-testing kernel directly:
>>
>> http://wireless.kernel.org/en/developers/Documentation/git-guide
>>
>> This has the latest RC kernel + all the wireless stuff we have queued up
>> for 2.6.30 (what compat-wireless picks up).
>>
>> Luis
>>
>>
>>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-02-02 22:21 ` Joseph Cheek
@ 2009-02-02 23:50 ` Luis R. Rodriguez
2009-02-03 4:01 ` Joseph Cheek
0 siblings, 1 reply; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-02 23:50 UTC (permalink / raw)
To: ath9k-devel
On Mon, Feb 2, 2009 at 2:21 PM, Joseph Cheek <joseph@cheek.com> wrote:
> I've been trying git tip for a week and no more kernel OOPS! great job,
> thanks!
Good to hear :)
> I also did NOT have to change IEEE_MONITORING_INTERVAL to stay
> connected. *But* I still lose connectivity for several seconds during a
> large file transfer (most often transferring 50M or more via scp or
> rsync -e ssh).
Check the logs for reason given for the disassociation, see another
thread recently where I posted the reason number to reason
description.
Luis
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-02-02 23:50 ` Luis R. Rodriguez
@ 2009-02-03 4:01 ` Joseph Cheek
2009-02-03 5:04 ` Luis R. Rodriguez
0 siblings, 1 reply; 20+ messages in thread
From: Joseph Cheek @ 2009-02-03 4:01 UTC (permalink / raw)
To: ath9k-devel
looks like i was a little hasty. checking syslog I see:
Feb 2 22:49:31 harrisburg ath9k: received PCI FATAL interrupt
Feb 2 22:49:36 harrisburg wlan0: No ProbeResp from current AP
00:21:91:df:00:29
- assume out of range
can I assume that the lack of a ProbeResp is because of the fatal
interrupt 5 seconds earlier?
Joseph Cheek
Luis R. Rodriguez wrote:
> On Mon, Feb 2, 2009 at 2:21 PM, Joseph Cheek <joseph@cheek.com> wrote:
>
>> I've been trying git tip for a week and no more kernel OOPS! great job,
>> thanks!
>>
>
> Good to hear :)
>
>
>> I also did NOT have to change IEEE_MONITORING_INTERVAL to stay
>> connected. *But* I still lose connectivity for several seconds during a
>> large file transfer (most often transferring 50M or more via scp or
>> rsync -e ssh).
>>
>
> Check the logs for reason given for the disassociation, see another
> thread recently where I posted the reason number to reason
> description.
>
> Luis
>
>
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-02-03 4:01 ` Joseph Cheek
@ 2009-02-03 5:04 ` Luis R. Rodriguez
2009-02-03 11:11 ` [ath9k-devel] Problem with 80211n Speed and packet drop Amit Sood
2009-02-08 3:14 ` [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
0 siblings, 2 replies; 20+ messages in thread
From: Luis R. Rodriguez @ 2009-02-03 5:04 UTC (permalink / raw)
To: ath9k-devel
On Mon, Feb 02, 2009 at 08:01:11PM -0800, Joseph Cheek wrote:
> looks like i was a little hasty. checking syslog I see:
>
> Feb 2 22:49:31 harrisburg ath9k: received PCI FATAL interrupt
> Feb 2 22:49:36 harrisburg wlan0: No ProbeResp from current AP
> 00:21:91:df:00:29
> - assume out of range
>
> can I assume that the lack of a ProbeResp is because of the fatal
> interrupt 5 seconds earlier?
Yeah that's what I would think, can you reproduce? If so
please enable debugging and see if you can find something
a bit more indicative of what happened.
modprobe ath9k debug=0xfffffffff
Luis
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] Problem with 80211n Speed and packet drop
2009-02-03 5:04 ` Luis R. Rodriguez
@ 2009-02-03 11:11 ` Amit Sood
2009-02-04 20:58 ` Pavel Roskin
2009-02-08 3:14 ` [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
1 sibling, 1 reply; 20+ messages in thread
From: Amit Sood @ 2009-02-03 11:11 UTC (permalink / raw)
To: ath9k-devel
Hi,
I'm using AR5416 (WMP300N v2) chipset compiled with compate-wireless-2009-01-30. I'm using it in AP mode with latest hostapd. I'm able to run it and able to connect my mac book pro running 80211n and it showing connected speed 139Mbps. However I've lot of packet loss and communication is slower then 80211g. I'm not usre if its ath9k related problem or hostapd. However I read couple of forums and some folks are talking about libnl20. Is there any dependency on LIBNL20 specially of iw?
kind regards,
-amit-
Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] Problem with 80211n Speed and packet drop
2009-02-03 11:11 ` [ath9k-devel] Problem with 80211n Speed and packet drop Amit Sood
@ 2009-02-04 20:58 ` Pavel Roskin
2009-02-04 23:21 ` Amit Sood
0 siblings, 1 reply; 20+ messages in thread
From: Pavel Roskin @ 2009-02-04 20:58 UTC (permalink / raw)
To: ath9k-devel
On Tue, 2009-02-03 at 16:41 +0530, Amit Sood wrote:
> Hi,
>
> I'm using AR5416 (WMP300N v2) chipset compiled with
> compate-wireless-2009-01-30. I'm using it in AP mode with latest
> hostapd. I'm able to run it and able to connect my mac book pro
> running 80211n and it showing connected speed 139Mbps. However I've
> lot of packet loss and communication is slower then 80211g. I'm not
> usre if its ath9k related problem or hostapd. However I read couple of
> forums and some folks are talking about libnl20. Is there any
> dependency on LIBNL20 specially of iw?
iw can use libnl 1.1 or 2.0. Either way, the functionality is the same.
Use of libnl 2.0 doesn't enable any additional functionality in iw.
In any case, packet drops are entirely in the domain of the driver. iw
should not affect it.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] Problem with 80211n Speed and packet drop
2009-02-04 20:58 ` Pavel Roskin
@ 2009-02-04 23:21 ` Amit Sood
2009-02-05 4:37 ` Pavel Roskin
0 siblings, 1 reply; 20+ messages in thread
From: Amit Sood @ 2009-02-04 23:21 UTC (permalink / raw)
To: ath9k-devel
Hi Pavel,
Thanks for your response.
But i could not find libnl 2..0 any where over the net. Is there any place I can download it?
cheers,
-amit-
----- Original Message ----
From: Pavel Roskin <proski@gnu.org>
To: Amit Sood <as22_2000@yahoo.com>
Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Sent: Thursday, 5 February, 2009 7:58:03 AM
Subject: Re: [ath9k-devel] Problem with 80211n Speed and packet drop
On Tue, 2009-02-03 at 16:41 +0530, Amit Sood wrote:
> Hi,
>
> I'm using AR5416 (WMP300N v2) chipset compiled with
> compate-wireless-2009-01-30. I'm using it in AP mode with latest
> hostapd. I'm able to run it and able to connect my mac book pro
> running 80211n and it showing connected speed 139Mbps. However I've
> lot of packet loss and communication is slower then 80211g. I'm not
> usre if its ath9k related problem or hostapd. However I read couple of
> forums and some folks are talking about libnl20. Is there any
> dependency on LIBNL20 specially of iw?
iw can use libnl 1.1 or 2.0. Either way, the functionality is the same.
Use of libnl 2.0 doesn't enable any additional functionality in iw..
In any case, packet drops are entirely in the domain of the driver. iw
should not affect it.
--
Regards,
Pavel Roskin
Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] Problem with 80211n Speed and packet drop
2009-02-04 23:21 ` Amit Sood
@ 2009-02-05 4:37 ` Pavel Roskin
0 siblings, 0 replies; 20+ messages in thread
From: Pavel Roskin @ 2009-02-05 4:37 UTC (permalink / raw)
To: ath9k-devel
Quoting Amit Sood <as22_2000@yahoo.com>:
> Hi Pavel,
>
> Thanks for your response.
>
> But i could not find libnl 2..0 any where over the net. Is there any
> place I can download it?
The libnl site seems to be down, but thanks to Google cache I could
easily find their git repository. It can be checked out by:
git clone git://git.kernel.org/pub/scm/libs/netlink/libnl.git
The version in configure.in is given as 2.0. I believe it's the best
you can get for now. I don't see a released version called 2.0.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
2009-02-03 5:04 ` Luis R. Rodriguez
2009-02-03 11:11 ` [ath9k-devel] Problem with 80211n Speed and packet drop Amit Sood
@ 2009-02-08 3:14 ` Joseph Cheek
1 sibling, 0 replies; 20+ messages in thread
From: Joseph Cheek @ 2009-02-08 3:14 UTC (permalink / raw)
To: ath9k-devel
i did get another OOPS but i haven't gotten a verbose debug log of that
yet.
not all PCI FATAL interrupts generated No ProbeResponses, but every No
ProbeResp happened 4-6 seconds after a PCI FATAL interrupt:
# egrep '(No.Probe|PCI.FATAL)' /var/log/messages
Feb 7 15:12:50 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 15:13:49 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 15:14:28 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 15:15:33 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 16:15:36 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 16:31:38 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 16:31:43 harrisburg wlan0: No ProbeResp from current AP
00:21:91:df:00:29 - assume out of range
Feb 7 16:45:23 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 17:11:43 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 18:06:42 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 18:06:46 harrisburg wlan0: No ProbeResp from current AP
00:21:91:df:00:29 - assume out of range
Feb 7 19:02:24 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 19:02:30 harrisburg wlan0: No ProbeResp from current AP
00:21:91:df:00:29 - assume out of range
Feb 7 21:06:43 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 21:06:48 harrisburg wlan0: No ProbeResp from current AP
00:21:91:df:00:29 - assume out of range
Feb 7 21:06:59 harrisburg ath9k: received PCI FATAL interrupt
here's a little of what i have surrounding the pci fatal interrupt at
16:31:38 today and the no proberesp five seconds later:
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x918404b4
Feb 7 16:31:38 harrisburg ath9k: enable IER
Feb 7 16:31:38 harrisburg ath9k: AR_IMR 0x918404b4 IER 0x1
Feb 7 16:31:38 harrisburg ath9k: 0xf0040071 => 0x0
Feb 7 16:31:38 harrisburg ath9k: disable IER
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x0
Feb 7 16:31:38 harrisburg ath9k: tx queue 1 (2d521200), link ed521200
Feb 7 16:31:38 harrisburg ath9k: 0x0 => 0xf0040071
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x918404b4
Feb 7 16:31:38 harrisburg ath9k: enable IER
Feb 7 16:31:38 harrisburg ath9k: AR_IMR 0x918404b4 IER 0x1
Feb 7 16:31:38 harrisburg ath9k: 0xf0040071 => 0x0
Feb 7 16:31:38 harrisburg ath9k: disable IER
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x0
Feb 7 16:31:38 harrisburg ath9k: tx queue 1 (2d521200), link ed521200
Feb 7 16:31:38 harrisburg ath9k: TX complete: skb: d8585964
Feb 7 16:31:38 harrisburg ath9k: 0x0 => 0xf0040071
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x918404b4
Feb 7 16:31:38 harrisburg ath9k: enable IER
Feb 7 16:31:38 harrisburg ath9k: 0xf0040071 => 0x0
Feb 7 16:31:38 harrisburg ath9k: disable IER
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x0
Feb 7 16:31:38 harrisburg ath9k: AR_IMR 0x0 IER 0x1
Feb 7 16:31:38 harrisburg ath9k: 0x0 => 0xf0040071
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x918404b4
Feb 7 16:31:38 harrisburg ath9k: enable IER
Feb 7 16:31:38 harrisburg ath9k: AR_IMR 0x918404b4 IER 0x1
Feb 7 16:31:38 harrisburg ath9k: 0xf0040071 => 0x0
Feb 7 16:31:38 harrisburg ath9k: disable IER
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x0
Feb 7 16:31:38 harrisburg ath9k: 0x0 => 0xf0040071
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x918404b4
Feb 7 16:31:38 harrisburg ath9k: enable IER
Feb 7 16:31:38 harrisburg ath9k: AR_IMR 0x918404b4 IER 0x1
Feb 7 16:31:38 harrisburg ath9k: received PCI FATAL interrupt
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: 0xf0040071 => 0x0
Feb 7 16:31:38 harrisburg ath9k: disable IER
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x0
Feb 7 16:31:38 harrisburg ath9k: 0x0 => 0xf0040071
Feb 7 16:31:38 harrisburg ath9k: new IMR 0x918404b4
Feb 7 16:31:38 harrisburg ath9k: enable IER
Feb 7 16:31:38 harrisburg ath9k: AR_IMR 0x918404b4 IER 0x1
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:38 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
and then 5 seconds later
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: receive FIFO overrun interrupt
Feb 7 16:31:43 harrisburg ath9k: 0xf0040071 => 0x0
Feb 7 16:31:43 harrisburg ath9k: disable IER
Feb 7 16:31:43 harrisburg ath9k: new IMR 0x0
Feb 7 16:31:43 harrisburg ath9k: 0x0 => 0xf0040071
Feb 7 16:31:43 harrisburg ath9k: new IMR 0x918404b4
Feb 7 16:31:43 harrisburg ath9k: enable IER
Feb 7 16:31:43 harrisburg ath9k: AR_IMR 0x918404b4 IER 0x1
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k: Writing ofdmbase=12582412
cckbase=12582712
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg ath9k:
AR_INTR_SYNC_LOCAL_TIMEOUT
Feb 7 16:31:43 harrisburg wlan0: No ProbeResp from current AP
00:21:91:df:00:29 - assume out of
range
Feb 7 16:31:43 harrisburg ath9k: transmitting packet, skb:
d84939a0
Feb 7 16:31:43 harrisburg ath9k: qnum: 3, txq depth:
2
Feb 7 16:31:43 harrisburg ath9k: link[3] (ed521b90)=2d521560
(ed521560)
Feb 7 16:31:43 harrisburg ath9k: queue
3
Feb 7 16:31:43 harrisburg ath9k: transmitting packet, skb:
ed64c5c0
Feb 7 16:31:43 harrisburg ath9k: qnum: 3, txq depth:
3
Feb 7 16:31:43 harrisburg ath9k: link[3] (ed521560)=2d521680
(ed521680)
Feb 7 16:31:43 harrisburg ath9k: queue
3
Feb 7 16:31:43 harrisburg ath9k: transmitting packet, skb:
d8493e20
Feb 7 16:31:43 harrisburg ath9k: qnum: 3, txq depth:
4
Feb 7 16:31:43 harrisburg ath9k: link[3] (ed521680)=2d5217a0
(ed5217a0)
Feb 7 16:31:43 harrisburg ath9k: queue
3
Feb 7 16:31:43 harrisburg ath9k: Set channel: 2427
MHz
Feb 7 16:31:43 harrisburg ath9k: tx chmask: 1, rx chmask:
1
Feb 7 16:31:43 harrisburg ath9k: 0xf0040071 =>
0x0
Feb 7 16:31:43 harrisburg ath9k: disable
IER
Feb 7 16:31:43 harrisburg ath9k: new IMR
0x0
Feb 7 16:31:43 harrisburg ath9k: ath9k_hw_stoptxdma: Num of pending TX
Frames 1 on Q
1
Feb 7 16:31:43 harrisburg ath9k: Failed to stop Tx DMA in 100 msec
after killing last
frame
Feb 7 16:31:43 harrisburg ath9k: ath9k_hw_stoptxdma: Num of pending TX
Frames 1 on Q
3
Feb 7 16:31:43 harrisburg ath9k: Failed to stop Tx DMA in 100 msec
after killing last
frame
Feb 7 16:31:43 harrisburg ath9k: Unable to stop TxDMA. Reset
HAL!
Feb 7 16:31:43 harrisburg ath9k: AWAKE -> AWAKE (set chip
)
Feb 7 16:31:43 harrisburg ath9k: NF calibrated [ctl] [chain 0] is
-84
Feb 7 16:31:43 harrisburg ath9k: NF calibrated [ctl] [chain 1] is
-81
Feb 7 16:31:43 harrisburg ath9k: NF calibrated [ctl] [chain 2] is
0
Feb 7 16:31:43 harrisburg ath9k: NF calibrated [ext] [chain 0] is
-83
Feb 7 16:31:43 harrisburg ath9k: NF calibrated [ext] [chain 1] is
-82
Feb 7 16:31:43 harrisburg ath9k: NF calibrated [ext] [chain 2] is
0
Feb 7 16:31:43 harrisburg ath9k: AWAKE -> AWAKE (set chip
)
Feb 7 16:31:43 harrisburg ath9k: LOOP-Mode ctlMode 0 < 3, isHt40CtlMode
0, EXT_ADDITIVE
0
Feb 7 16:31:43 harrisburg ath9k: LOOP-Ctlidx 0: cfgCtl 0x12 pCtlMode
0x01 ctlIndex 0x11 chan
2427
Feb 7 16:31:43 harrisburg ath9k: MATCH-EE_IDX 0: ch 2427 is2 1
2xMinEdge 41 chainmask 1 chains
1
Feb 7 16:31:43 harrisburg ath9k: SEL-Min ctlMode 0 pCtlMode 1
2xMaxEdge 41 sP 40 minCtlPwr
40
Feb 7 16:31:43 harrisburg ath9k: LOOP-Mode ctlMode 1 < 3, isHt40CtlMode
0, EXT_ADDITIVE
0
Feb 7 16:31:43 harrisburg ath9k: LOOP-Ctlidx 0: cfgCtl 0x12 pCtlMode
0x02 ctlIndex 0x11 chan
2427
Feb 7 16:31:43 harrisburg ath9k: LOOP-Ctlidx 1: cfgCtl 0x12 pCtlMode
0x02 ctlIndex 0x12 chan
2427
Feb 7 16:31:43 harrisburg ath9k: MATCH-EE_IDX 1: ch 2427 is2 1
2xMinEdge 41 chainmask 1 chains
1
Feb 7 16:31:43 harrisburg ath9k: SEL-Min ctlMode 1 pCtlMode 2
2xMaxEdge 41 sP 40 minCtlPwr
40
Feb 7 16:31:43 harrisburg ath9k: LOOP-Mode ctlMode 2 < 3, isHt40CtlMode
0, EXT_ADDITIVE
0
Feb 7 16:31:43 harrisburg ath9k: LOOP-Ctlidx 0: cfgCtl 0x12 pCtlMode
0x05 ctlIndex 0x11 chan
2427
Feb 7 16:31:43 harrisburg ath9k: LOOP-Ctlidx 1: cfgCtl 0x12 pCtlMode
0x05 ctlIndex 0x12 chan
2427
Feb 7 16:31:43 harrisburg ath9k: LOOP-Ctlidx 2: cfgCtl 0x12 pCtlMode
0x05 ctlIndex 0x15 chan
2427
Feb 7 16:31:43 harrisburg ath9k: MATCH-EE_IDX 2: ch 2427 is2 1
2xMinEdge 41 chainmask 1 chains
1
Feb 7 16:31:43 harrisburg ath9k: SEL-Min ctlMode 2 pCtlMode 5
2xMaxEdge 41 sP 40 minCtlPwr
40
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a280
1412100f
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 0 Value 15 |
PDADC 1 Value 16 | PDADC 2 Value 18 | PDADC 3 Value 20
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a284
1b191816
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 4 Value 22 |
PDADC 5 Value 24 | PDADC 6 Value 25 | PDADC 7 Value 27
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a288
2623201d
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 8 Value 29 |
PDADC 9 Value 32 | PDADC 10 Value 35 | PDADC 11 Value 38
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a28c
33302d2a
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 12 Value 42 |
PDADC 13 Value 45 | PDADC 14 Value 48 | PDADC 15 Value 51
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a290
46413b36
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 16 Value 54 |
PDADC 17 Value 59 | PDADC 18 Value 65 | PDADC 19 Value 70
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a294
5b56514c
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 20 Value 76 |
PDADC 21 Value 81 | PDADC 22 Value 86 | PDADC 23 Value 91
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a298
79726961
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 24 Value 97 |
PDADC 25 Value 105 | PDADC 26 Value 114 | PDADC 27 Value 121
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a29c
9c938a82
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 28 Value 130 |
PDADC 29 Value 138 | PDADC 30 Value 147 | PDADC 31 Value 156
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a2a0
17b7aea5
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 32 Value 165 |
PDADC 33 Value 174 | PDADC 34 Value 183 | PDADC 35 Value 23
|
Feb 7 16:31:43 harrisburg ath9k: PDADC (0, 0): a2a4
1f1d1b19
Feb 7 16:31:43 harrisburg ath9k: PDADC: Chain 0 | PDADC 36 Value 25 |
PDADC 37 Value 27 | PDADC 38 Value 29 | PDADC 39 Value 31 |
let me know what else you need.
thanks!
Joseph Cheek
Luis R. Rodriguez wrote:
> On Mon, Feb 02, 2009 at 08:01:11PM -0800, Joseph Cheek wrote:
>
>> looks like i was a little hasty. checking syslog I see:
>>
>> Feb 2 22:49:31 harrisburg ath9k: received PCI FATAL interrupt
>> Feb 2 22:49:36 harrisburg wlan0: No ProbeResp from current AP
>> 00:21:91:df:00:29
>> - assume out of range
>>
>> can I assume that the lack of a ProbeResp is because of the fatal
>> interrupt 5 seconds earlier?
>>
>
> Yeah that's what I would think, can you reproduce? If so
> please enable debugging and see if you can find something
> a bit more indicative of what happened.
>
> modprobe ath9k debug=0xfffffffff
>
> Luis
>
>
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
@ 2009-04-06 7:36 Masashi Honma
0 siblings, 0 replies; 20+ messages in thread
From: Masashi Honma @ 2009-04-06 7:36 UTC (permalink / raw)
To: ath9k-devel
> On Sun Feb 8 04:14:02 CET 2009, Joseph Cheek wrote:
> # egrep '(No.Probe|PCI.FATAL)' /var/log/messages
> Feb 7 15:12:50 harrisburg ath9k: received PCI FATAL interrupt
Hello.
I encountered identical error on Debian sid.
[ 467.614789] ath9k: received PCI FATAL interrupt
[ 714.384969] ath9k: received PCI FATAL interrupt
[ 729.166142] ath9k: received PCI FATAL interrupt
[ 774.222352] ath9k: received PCI FATAL interrupt
[ 819.272511] ath9k: received PCI FATAL interrupt
I can't ping with wpa_supplicant + ath9k driver.
WPA2-PSK connection is ok (GTK exchange succeeded).
But wpa_supplicant doesn't sends ping request.
I'm capturing wpa_supplicant wireless frame, but it doesn't
send any frame.
After that, I changed the card to ath5k device.
Then I can ping with same settings.
But I need to use ath9k, because I wnat 802.11w support.
My environment is these.
[uname -a]
Linux debian 2.6.29 #1 SMP Mon Apr 6 10:56:46 JST 2009 i686 GNU/Linux
[wireless card]
WL300NC (AR5416+AR5133)
[compat-wireless]
compat-wireless-2009-04-05
[CRDA]
crda-1.0.1
[CRDA-rule]
/etc/udev/rules.d/91-regulatory.rules
KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda"
[CRDA log]
debian:~# dmesg | grep CRDA
[ 6.669048] cfg80211: Calling CRDA for country: US
[ 7.377956] cfg80211: Calling CRDA for country: JP
debian:~#
[wireless-regdb]
wireless-regdb-2009.03.09
[wpa_supplicant]
newest on git snapshot
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=snapshot;h=a0b2f99bd7f608236e8a2e650655a79280248740;sf=tgz
[.config]
CONFIG_DRIVER_NL80211=y
CONFIG_DRIVER_WIRED=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_TLS=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_TNC=y
CONFIG_WPS=y
CONFIG_PKCS12=y
CONFIG_SMARTCARD=y
CONFIG_CTRL_IFACE=y
CONFIG_BACKEND=file
CONFIG_PEERKEY=y
CONFIG_IEEE80211W=y
CONFIG_TLS=internal
CONFIG_INTERNAL_LIBTOMMATH=y
CONFIG_IEEE80211R=y
[wpa_supplicant.conf]
ctrl_interface=/var/run/wpa_supplicant
country=JP
network={
ssid="wpa-eap"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
group=CCMP
psk="12345678"
}
Is there any idea ?
Regards,
Masashi Honma.
^ permalink raw reply [flat|nested] 20+ messages in thread
* [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
@ 2009-04-06 7:43 Masashi Honma
0 siblings, 0 replies; 20+ messages in thread
From: Masashi Honma @ 2009-04-06 7:43 UTC (permalink / raw)
To: ath9k-devel
> On Sun Feb 8 04:14:02 CET 2009, Joseph Cheek wrote:
> > # egrep '(No.Probe|PCI.FATAL)' /var/log/messages
> > Feb 7 15:12:50 harrisburg ath9k: received PCI FATAL interrupt
Hello.
I encountered identical error on Debian sid.
[ 467.614789] ath9k: received PCI FATAL interrupt
[ 714.384969] ath9k: received PCI FATAL interrupt
[ 729.166142] ath9k: received PCI FATAL interrupt
[ 774.222352] ath9k: received PCI FATAL interrupt
[ 819.272511] ath9k: received PCI FATAL interrupt
I can't ping with wpa_supplicant + ath9k driver.
WPA2-PSK connection is ok (GTK exchange succeeded).
But wpa_supplicant doesn't sends ping request.
I'm capturing wpa_supplicant wireless frame, but it doesn't
send any frame.
After that, I changed the card to ath5k device.
Then I can ping with same settings.
But I need to use ath9k, because I wnat 802.11w support.
My environment is these.
[uname -a]
Linux debian 2.6.29 #1 SMP Mon Apr 6 10:56:46 JST 2009 i686 GNU/Linux
[wireless card]
WL300NC (AR5416+AR5133)
[compat-wireless]
compat-wireless-2009-04-05
[CRDA]
crda-1.0.1
[CRDA-rule]
/etc/udev/rules.d/91-regulatory.rules
KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda"
[CRDA log]
debian:~# dmesg | grep CRDA
[ 6.669048] cfg80211: Calling CRDA for country: US
[ 7.377956] cfg80211: Calling CRDA for country: JP
debian:~#
[wireless-regdb]
wireless-regdb-2009.03.09
[wpa_supplicant]
newest on git snapshot
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=snapshot;h=a0b2f99bd7f608236e8a2e650655a79280248740;sf=tgz
[.config]
CONFIG_DRIVER_NL80211=y
CONFIG_DRIVER_WIRED=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_TLS=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_TNC=y
CONFIG_WPS=y
CONFIG_PKCS12=y
CONFIG_SMARTCARD=y
CONFIG_CTRL_IFACE=y
CONFIG_BACKEND=file
CONFIG_PEERKEY=y
CONFIG_IEEE80211W=y
CONFIG_TLS=internal
CONFIG_INTERNAL_LIBTOMMATH=y
CONFIG_IEEE80211R=y
[wpa_supplicant.conf]
ctrl_interface=/var/run/wpa_supplicant
country=JP
network={
ssid="wpa-eap"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
group=CCMP
psk="12345678"
}
Is there any idea for solving this ?
Regards,
Masashi Honma.
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2009-04-06 7:43 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-21 6:14 [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
2009-01-21 18:49 ` Luis R. Rodriguez
2009-01-21 19:54 ` Joseph Cheek
2009-01-21 22:18 ` Joseph Cheek
2009-01-22 19:19 ` Joseph Cheek
2009-01-22 19:44 ` Luis R. Rodriguez
2009-01-25 0:32 ` Joseph Cheek
2009-01-25 2:23 ` Luis R. Rodriguez
2009-01-25 2:27 ` Stephen Gutknecht
2009-02-02 22:21 ` Joseph Cheek
2009-02-02 23:50 ` Luis R. Rodriguez
2009-02-03 4:01 ` Joseph Cheek
2009-02-03 5:04 ` Luis R. Rodriguez
2009-02-03 11:11 ` [ath9k-devel] Problem with 80211n Speed and packet drop Amit Sood
2009-02-04 20:58 ` Pavel Roskin
2009-02-04 23:21 ` Amit Sood
2009-02-05 4:37 ` Pavel Roskin
2009-02-08 3:14 ` [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
-- strict thread matches above, loose matches on Subject: below --
2009-04-06 7:36 Masashi Honma
2009-04-06 7:43 Masashi Honma
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.