From: Larry Finger <Larry.Finger@lwfinger.net>
To: Andre Heider <a.heider@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Michael Büsch" <m@bues.ch>,
linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
"Rafał Miłecki" <zajec5@gmail.com>
Subject: chip id 4318 regression: WARN_ON_ONCE(sdata->vif.hw_queue[i] >= n_queues))
Date: Fri, 08 Jun 2012 11:24:07 -0500 [thread overview]
Message-ID: <4FD22727.7000500@lwfinger.net> (raw)
In-Reply-To: <CAHsu+b9EgAfq6_G8xqRzf0qHkmyQnvs7j=g4wWcSVJXstAz4mw@mail.gmail.com>
On 06/08/2012 11:05 AM, Andre Heider wrote:
> On Fri, Jun 8, 2012 at 5:59 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
>> On Fri, 2012-06-08 at 17:56 +0200, Andre Heider wrote:
>>
>>>> Hopefully this is better: http://p.sipsolutions.net/017d73ac0688f863.txt
>>>
>>> The previous patched all had the mac suspend failure. This one:
>>>
>>> drivers/net/wireless/b43/main.c: In function 'b43_qos_upload_all':
>>> drivers/net/wireless/b43/main.c:3483: error: size of array 'type name'
>>> is negative
>>> drivers/net/wireless/b43/main.c: In function 'b43_qos_clear':
>>> drivers/net/wireless/b43/main.c:3502: error: size of array 'type name'
>>> is negative
>>> drivers/net/wireless/b43/main.c: In function 'b43_op_conf_tx':
>>> drivers/net/wireless/b43/main.c:3578: error: size of array 'type name'
>>> is negative
>>
>> Huh, I thought I compiled it ... guess I had the wrong version.
>>
>> http://p.sipsolutions.net/511dda98892d2c9a.txt
>
> It's getting warmer:
>
> [ 9.456216] b43-phy0: Loading OpenSource firmware version 410.31754
> [ 9.473798] b43-phy0: Hardware crypto acceleration not supported by firmware
> [ 9.491781] b43-phy0: QoS not supported by firmware
> [ 9.868750] b43-phy0 debug: Chip initialized
> [ 9.888580] b43-phy0 debug: PIO initialized
> [ 9.899273] b43-phy0 debug: QoS disabled
> [ 10.088420] b43-phy0 debug: Wireless interface started
> [ 10.212209] b43-phy0 debug: Adding Interface type 2
> [ 12.739776] wlan0: authenticate with d8:5d:4c:9c:31:14
> [ 12.796248] wlan0: send auth to d8:5d:4c:9c:31:14 (try 1/3)
> [ 12.811768] wlan0: authenticated
> [ 12.823310] wlan0: associate with d8:5d:4c:9c:31:14 (try 1/3)
> [ 12.844942] wlan0: RX AssocResp from d8:5d:4c:9c:31:14 (capab=0x411
> status=0 aid=2)
> [ 12.863966] wlan0: associated
> [ 16.319097] ieee80211 phy0: wlan0: No probe response from AP
> d8:5d:4c:9c:31:14 after 500ms, disconnecting.
> [ 16.349674] cfg80211: Calling CRDA for country: DE
> [ 17.597307] wlan0: authenticate with d8:5d:4c:9c:31:14
> [ 17.638399] wlan0: send auth to d8:5d:4c:9c:31:14 (try 1/3)
> [ 17.851085] wlan0: send auth to d8:5d:4c:9c:31:14 (try 2/3)
> [ 18.063086] wlan0: send auth to d8:5d:4c:9c:31:14 (try 3/3)
> [ 18.275081] wlan0: authentication with d8:5d:4c:9c:31:14 timed out
>
> Tried it 3 times, always times out.
Strange. I commented out the BUILD_BUG statements in version 017d73a, and it
worked for me with both flavors of fw.
Larry
next prev parent reply other threads:[~2012-06-08 16:24 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 19:10 chip id 4318 regression: WARN_ON_ONCE(sdata->vif.hw_queue[i] >= n_queues)) Andre Heider
2012-06-06 20:35 ` Johannes Berg
2012-06-07 7:10 ` Andre Heider
2012-06-07 7:16 ` Johannes Berg
2012-06-07 15:24 ` Andre Heider
2012-06-07 16:03 ` Michael Büsch
2012-06-07 17:25 ` Larry Finger
2012-06-07 17:30 ` Michael Büsch
2012-06-07 18:29 ` Larry Finger
2012-06-07 18:34 ` Andre Heider
2012-06-07 18:36 ` Johannes Berg
2012-06-07 20:56 ` Johannes Berg
2012-06-07 21:21 ` Larry Finger
2012-06-07 21:47 ` Andre Heider
2012-06-08 6:27 ` Johannes Berg
2012-06-08 6:41 ` Johannes Berg
2012-06-08 13:49 ` Andre Heider
2012-06-08 14:52 ` Johannes Berg
2012-06-08 15:04 ` Andre Heider
2012-06-08 15:14 ` Johannes Berg
2012-06-08 15:16 ` Johannes Berg
2012-06-08 15:25 ` Andre Heider
2012-06-08 15:38 ` Larry Finger
2012-06-08 15:43 ` Johannes Berg
2012-06-08 15:44 ` Johannes Berg
2012-06-08 15:48 ` Johannes Berg
2012-06-08 15:52 ` Johannes Berg
2012-06-08 15:56 ` Andre Heider
2012-06-08 15:59 ` Johannes Berg
2012-06-08 16:05 ` Andre Heider
2012-06-08 16:08 ` Johannes Berg
2012-06-08 16:16 ` Andre Heider
2012-06-08 16:20 ` Johannes Berg
2012-06-08 16:24 ` Johannes Berg
2012-06-08 16:41 ` Johannes Berg
2012-06-08 16:54 ` Andre Heider
2012-06-08 16:56 ` Johannes Berg
2012-06-08 16:24 ` Larry Finger [this message]
2012-06-08 16:28 ` Johannes Berg
2012-06-08 16:33 ` Michael Büsch
2012-06-08 17:43 ` Larry Finger
2012-06-08 17:56 ` Johannes Berg
2012-06-08 18:11 ` Johannes Berg
2012-06-08 18:28 ` Andre Heider
2012-06-08 18:38 ` Johannes Berg
2012-06-08 18:10 ` Michael Büsch
2012-06-08 18:23 ` Larry Finger
2012-06-08 18:31 ` Michael Büsch
2012-06-08 19:37 ` Larry Finger
2012-06-08 19:42 ` Andre Heider
2012-06-08 18:36 ` Johannes Berg
2012-06-08 18:42 ` Johannes Berg
2012-06-08 19:04 ` Johannes Berg
2012-06-13 8:31 ` Johannes Berg
2012-06-13 15:39 ` Andre Heider
2012-06-13 15:46 ` Johannes Berg
2012-06-13 18:42 ` Michael Büsch
2012-06-14 16:26 ` Andre Heider
2012-06-14 16:37 ` Johannes Berg
2012-06-14 17:00 ` Andre Heider
2012-06-14 17:09 ` Johannes Berg
2012-06-14 17:17 ` Johannes Berg
2012-06-14 17:23 ` Andre Heider
2012-06-14 17:27 ` Johannes Berg
2012-06-15 2:03 ` Larry Finger
2012-06-15 8:17 ` Johannes Berg
2012-06-15 17:14 ` Andre Heider
2012-06-08 15:38 ` Johannes Berg
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=4FD22727.7000500@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=a.heider@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--cc=zajec5@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).