From: Joseph Cheek <joseph@cheek.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
Date: Sat, 07 Feb 2009 22:14:02 -0500 [thread overview]
Message-ID: <498E4DFA.6040106@cheek.com> (raw)
In-Reply-To: <20090203050420.GA16853@tesla>
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
>
>
next prev parent reply other threads:[~2009-02-08 3:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Joseph Cheek [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-06 7:36 [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Masashi Honma
2009-04-06 7:43 Masashi Honma
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=498E4DFA.6040106@cheek.com \
--to=joseph@cheek.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.