From mboxrd@z Thu Jan 1 00:00:00 1970 From: Larry Finger Date: Thu, 14 Jun 2012 21:03:17 -0500 Subject: chip id 4318 regression: WARN_ON_ONCE(sdata->vif.hw_queue[i] >= n_queues)) In-Reply-To: <1339694837.9786.8.camel@jlt3.sipsolutions.net> References: <4FD22727.7000500@lwfinger.net> <1339180580.5748.32.camel@jlt3.sipsolutions.net> <1339180948.5748.35.camel@jlt3.sipsolutions.net> <1339182289.5748.36.camel@jlt3.sipsolutions.net> <1339576294.4519.17.camel@jlt3.sipsolutions.net> <1339602402.4519.48.camel@jlt3.sipsolutions.net> <20120613204230.474d1b6c@milhouse> <1339691877.9786.0.camel@jlt3.sipsolutions.net> <1339693777.9786.6.camel@jlt3.sipsolutions.net> <1339694227.9786.7.camel@jlt3.sipsolutions.net> (sfid-20120614_192302_952190_7ED159EF) <1339694837.9786.8.camel@jlt3.sipsolutions.net> Message-ID: <4FDA97E5.3090208@lwfinger.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Johannes Berg Cc: Andre Heider , =?UTF-8?B?TWljaGFlbCBCw7xzY2g=?= , linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org, =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= On 06/14/2012 12:27 PM, Johannes Berg wrote: > On Thu, 2012-06-14 at 19:23 +0200, Andre Heider wrote: >> On Thu, Jun 14, 2012 at 7:17 PM, Johannes Berg >> wrote: >>> On Thu, 2012-06-14 at 19:09 +0200, Johannes Berg wrote: >>>> On Thu, 2012-06-14 at 19:00 +0200, Andre Heider wrote: >>>> >>>>>> http://p.sipsolutions.net/9c830800d14f3ff8.txt >>>>> >>>>> This still oopses: if (!modparam_qos || wldev->fw.opensource) >>>>> >>>>> I do get a working wlan0 if I force "hw->queues = 1;" without that >>>>> offending line, but just a `dmesg` over wlan+ssh yields another one >>>>> (prolly the same one I already described on an older patch): >>>>> http://i.imgur.com/epdRF.jpg >>>> >>>> Doh, of course, I still have wldev ... I'm in a meeting now, will check >>>> again later. >>> >>> Let's just move the hw->queues setup ... >>> >>> http://p.sipsolutions.net/e45e57bbc9509e69.txt >> >> No oops during loading the fw or bringing the device up, but same >> crash as in the picture above ;) > > I guess I shouldn't be doing this right now ... > > Can't somebody else help me out? Rafal? Larry? Michael? I clearly don't > know this code well enough and you should be able to identify the intent > from the patch ... I will give it a try. I was in the Canadian wilderness for 5 days fishing, which is why I have not responded earlier. The device does not fail on my hardware, but I can prepare things for Andre to test. Larry