All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Magnus Therning <magnus@therning.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	b43-dev@lists.infradead.org,
	wireless <linux-wireless@vger.kernel.org>
Subject: Problems with b43 wirelesss
Date: Sat, 19 Jun 2010 08:26:56 -0500	[thread overview]
Message-ID: <4C1CC5A0.7080600@lwfinger.net> (raw)
In-Reply-To: <AANLkTimxOgQySTag7u4DlZugbveWr7csDSAERkewAYhp@mail.gmail.com>

On 06/19/2010 07:35 AM, Magnus Therning wrote:
> 2010/6/19 Rafa? Mi?ecki <zajec5@gmail.com>:
>> You can Google for b43 & DMA errors. Simply try "pio" option for b43
>> module. Or switch to newer kernel, which will pick up pio for you
>> after first DMA error.
> 
> Given the following messages in dmesg, I thought this was already happening:
> 
> b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000,
> 0x00000000, 0x00000000, 0x00000000
> b43-phy0 ERROR: This device does not support DMA on your system.
> Please use PIO instead.
> b43-phy0: Controller RESET (DMA error) ...
> b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> b43-phy0: Controller restarted
> 
> I'm running the 2.6.33 (latest stable is 2.6.34), but I am using the
> latest daily (2010-06-17) from compat-wireless[1], so unless I'm
> missing something there isn't much to be gained from switching to the
> latest kernel.  In any case I will try it to see if that improves the
> situation.
> 
> My naive reading of the messages tells me that this *isn't* a DMA
> error... I also don't really understand how I could ever get an
> initial connection, which I do, if that were the problem I'm having.

No, it is a fatal DMA error and your device did switch to PIO mode. The
dmesg output does not make that clear. I'm sending a patch to change the
logged message.

> It looks like the following is more relevant to my problem:
> 
> No probe response from AP 00:22:3f:c3:99:a8 after 500ms, disconnecting.
> cfg80211: Calling CRDA to update world regulatory domain
> wlan0: authenticate with 00:22:3f:c3:99:a8 (try 1)
> wlan0: authenticated
> wlan0: associate with 00:22:3f:c3:99:a8 (try 1)
> wlan0: RX AssocResp from 00:22:3f:c3:99:a8 (capab=0x431 status=0 aid=1)
> wlan0: associated
> wlan0: deauthenticated from 00:22:3f:c3:99:a8 (Reason: 15)
> 
> Especially since that sequence of messages is repeated over an over.
> 
> My next test will be to turn off all security on the wireless, just to
> rule out WPA completley.

I looked for an explanation of Reason 15 deauthentications. Perhaps
someone on the wireless ML will know the answer.

Larry

WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Magnus Therning <magnus@therning.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	b43-dev@lists.infradead.org,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: Problems with b43 wirelesss
Date: Sat, 19 Jun 2010 08:26:56 -0500	[thread overview]
Message-ID: <4C1CC5A0.7080600@lwfinger.net> (raw)
In-Reply-To: <AANLkTimxOgQySTag7u4DlZugbveWr7csDSAERkewAYhp@mail.gmail.com>

On 06/19/2010 07:35 AM, Magnus Therning wrote:
> 2010/6/19 Rafał Miłecki <zajec5@gmail.com>:
>> You can Google for b43 & DMA errors. Simply try "pio" option for b43
>> module. Or switch to newer kernel, which will pick up pio for you
>> after first DMA error.
> 
> Given the following messages in dmesg, I thought this was already happening:
> 
> b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000,
> 0x00000000, 0x00000000, 0x00000000
> b43-phy0 ERROR: This device does not support DMA on your system.
> Please use PIO instead.
> b43-phy0: Controller RESET (DMA error) ...
> b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> b43-phy0: Controller restarted
> 
> I'm running the 2.6.33 (latest stable is 2.6.34), but I am using the
> latest daily (2010-06-17) from compat-wireless[1], so unless I'm
> missing something there isn't much to be gained from switching to the
> latest kernel.  In any case I will try it to see if that improves the
> situation.
> 
> My naive reading of the messages tells me that this *isn't* a DMA
> error... I also don't really understand how I could ever get an
> initial connection, which I do, if that were the problem I'm having.

No, it is a fatal DMA error and your device did switch to PIO mode. The
dmesg output does not make that clear. I'm sending a patch to change the
logged message.

> It looks like the following is more relevant to my problem:
> 
> No probe response from AP 00:22:3f:c3:99:a8 after 500ms, disconnecting.
> cfg80211: Calling CRDA to update world regulatory domain
> wlan0: authenticate with 00:22:3f:c3:99:a8 (try 1)
> wlan0: authenticated
> wlan0: associate with 00:22:3f:c3:99:a8 (try 1)
> wlan0: RX AssocResp from 00:22:3f:c3:99:a8 (capab=0x431 status=0 aid=1)
> wlan0: associated
> wlan0: deauthenticated from 00:22:3f:c3:99:a8 (Reason: 15)
> 
> Especially since that sequence of messages is repeated over an over.
> 
> My next test will be to turn off all security on the wireless, just to
> rule out WPA completley.

I looked for an explanation of Reason 15 deauthentications. Perhaps
someone on the wireless ML will know the answer.

Larry



  reply	other threads:[~2010-06-19 13:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18 21:51 Problems with b43 wirelesss Magnus Therning
2010-06-19  9:33 ` Rafał Miłecki
2010-06-19 12:35   ` Magnus Therning
2010-06-19 13:26     ` Larry Finger [this message]
2010-06-19 13:26       ` Larry Finger
2010-06-20 16:57       ` Magnus Therning
2010-06-20 16:57         ` Magnus Therning
2010-06-20  0:59     ` William Bourque
2010-06-20 17:02       ` Magnus Therning
2010-06-20 18:18         ` Gábor Stefanik
2010-06-20 18:31           ` Magnus Therning
2010-06-20 18:37             ` Gábor Stefanik
2010-06-24 22:27               ` Magnus Therning

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=4C1CC5A0.7080600@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=magnus@therning.org \
    --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 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.