linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Using compat-wireless w/ 2.6.27.26
Date: Fri, 24 Jul 2009 09:58:48 -0400	[thread overview]
Message-ID: <b6c5339f0907240658o38f4ee76t2de8a071cd2f37f4@mail.gmail.com> (raw)
In-Reply-To: <4A68E80C.808@redfish-solutions.com>

On Thu, Jul 23, 2009 at 6:45 PM, Philip A.
Prindeville<philipp_subx@redfish-solutions.com> wrote:
> Bob Copeland wrote:
>> On Thu, Jul 23, 2009 at 5:53 PM, Philip A.
>> Prindeville<philipp_subx@redfish-solutions.com> wrote:
>>>> Getting closer :-)
>>>>
>>>> ath5k_tx_processq(sc, &sc->txqs[i]);
>>>>
>>> Didn't work with rc4:
>>
>> What did you apply against?  It's supposed to be against
>> wireless-testing (or, at worst, latest compat-wireless).
>>
>>> BUG: unable to handle kernel NULL pointer dereference at 00000000
>>> IP: [<d0935658>] :ath5k:ath5k_tasklet_tx+0x5e/0x27b
>>

> This was against compat-wireless-2.6.31-rc4.
>
> Alas, I already blew away the build directory...

I think you need to use the unstable compat-wireless snapshots;
I have a feeling that the above doesn't have all of the tx queues.

Check out ath5k.h, the txq array in struct ath5k_softc should have
NUM_TX_QUEUES entries, an earlier version only had 2.

Although your compiler generates rather different code from mine
(different config or whatever), it looks like the oops happened
in the list_for_each_entry(... txq->q ...) -- but I don't see how
that can happen in my copy, since txq[i].q is initialized at the
same time as txq[i].setup.

-- 
Bob Copeland %% www.bobcopeland.com

  reply	other threads:[~2009-07-24 13:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18  1:27 Using compat-wireless w/ 2.6.27.26 Philip A. Prindeville
2009-07-19  8:58 ` Philip A. Prindeville
2009-07-19 13:38 ` Bob Copeland
2009-07-19 17:55   ` Philip A. Prindeville
2009-07-19 20:31     ` Bob Copeland
2009-07-20  3:05       ` Philip A. Prindeville
2009-07-20 11:52         ` Bob Copeland
2009-07-20 19:16           ` Philip A. Prindeville
2009-07-20 19:47             ` Luis R. Rodriguez
2009-07-20 23:52               ` Philip A. Prindeville
2009-07-21 20:10                 ` Philip A. Prindeville
2009-07-21 23:24                   ` Luis R. Rodriguez
2009-07-22  3:28                   ` Bob Copeland
2009-07-23 11:24                   ` Bob Copeland
2009-07-23 11:59                     ` Bob Copeland
2009-07-23 20:29                       ` Philip A. Prindeville
2009-07-23 20:33                         ` Bob Copeland
2009-07-23 21:53                         ` Philip A. Prindeville
2009-07-23 22:21                           ` Bob Copeland
2009-07-23 22:45                             ` Philip A. Prindeville
2009-07-24 13:58                               ` Bob Copeland [this message]
2009-07-30  4:36                                 ` Philip A. Prindeville
2009-07-21 23:26               ` Luis R. Rodriguez

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=b6c5339f0907240658o38f4ee76t2de8a071cd2f37f4@mail.gmail.com \
    --to=me@bobcopeland.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=philipp_subx@redfish-solutions.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).