Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ehud Gavron <gavron@wetwork.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Buesch <mb@bu3sch.de>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	bcm43xx-dev@lists.berlios.de
Subject: Re: suspend vs. b43
Date: Fri, 30 May 2008 08:02:51 -0700	[thread overview]
Message-ID: <4840171B.5080604@wetwork.net> (raw)
In-Reply-To: <1212158238.4117.4.camel@johannes.berg>



Johannes Berg wrote:
> On Fri, 2008-05-30 at 16:06 +0200, Michael Buesch wrote:
>   
>> On Friday 30 May 2008 14:31:53 Johannes Berg wrote:
>>     
>>> Since a while ago I've had trouble resuming when b43 was connected to an
>>> AP while suspended.
>>>
>>> I did a test today where this was the only difference, but I failed to
>>> see whether ssb or b43 were causing the problem.
>>>
>>> Does anyone have a machine with b43 in it that can suspend and supports
>>> the RTC-trace feature so we can narrow it down? Even reproducing might
>>> help to make sure it's not just something weird with my powerbook.
>>>       
>> Resume is pretty broken since some time for me.
>> It sometimes works fine and sometimes just hangs with a black screen.
>> I have no idea what's going on.
>>     
>
> Odd. Resume itself works just fine here, except when b43 is up. But then
> again, you might not notice that this is the problem because by default,
> nothing gets printed on the resume console and then it will indeed hang
> with a black screen.
>
> johannes
>   
>   
With NM disabled 2.6.25-wl  4311 after a suspend/resume I can:
1. Successfully scan for APs (ifconfig wlan0 up... iwlist wlan0 scan)
2. Associate with an AP  (iwconfig ...essid...key...)
3. Get a DHCP address (dhclient... offer... bound to address such and such)
but
4. NO FURTHER IP COMMUNICATIONS WORKS

Let me know what other diags to run or if I should upgrade to the latest 
wl tree if you think that will change the symptoms.
Things have been busy but there is a weekend coming up here shortly.

Ehud

> ------------------------------------------------------------------------
>
> _______________________________________________
> Bcm43xx-dev mailing list
> Bcm43xx-dev@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
>   

  parent reply	other threads:[~2008-05-30 15:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 12:31 suspend vs. b43 Johannes Berg
2008-05-30 14:06 ` Michael Buesch
2008-05-30 14:37   ` Johannes Berg
2008-05-30 14:42     ` Michael Buesch
2008-05-30 14:46       ` Johannes Berg
2008-05-30 15:20         ` Rafael J. Wysocki
2008-05-30 15:42           ` Johannes Berg
2008-05-30 21:19             ` Rafael J. Wysocki
2008-05-30 22:38               ` Johannes Berg
2008-05-30 22:49                 ` Rafael J. Wysocki
2008-05-30 22:54                   ` Johannes Berg
2008-05-30 23:05                     ` Rafael J. Wysocki
2008-05-30 14:49     ` Holger Schurig
2008-05-30 14:50       ` Johannes Berg
2008-05-30 15:02     ` Ehud Gavron [this message]
2008-05-30 15:23     ` Rafael J. Wysocki
2008-05-30 14:07 ` Rafael J. Wysocki
2008-05-30 14:31 ` Michael Grundmann
2008-05-30 14:40   ` Johannes Berg
2008-05-30 14:47     ` Michael Grundmann

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=4840171B.5080604@wetwork.net \
    --to=gavron@wetwork.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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