From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Michael Witten <mfwitten@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, stable@kernel.org,
Witold Baryluk <baryluk@smp.if.uj.edu.pl>
Subject: Re: [PATCH] mac80211: fix suspend/resume races with unregister hw
Date: Thu, 8 Sep 2011 18:26:06 +0200 [thread overview]
Message-ID: <20110908162605.GD2195@redhat.com> (raw)
In-Reply-To: <CAMOZ1BvsPok-AZVCwKnv0hWWXyV+np+nARjGRqwqsvC-du_GAw@mail.gmail.com>
On Thu, Sep 08, 2011 at 04:04:28PM +0000, Michael Witten wrote:
> On Thu, Sep 8, 2011 at 06:44, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> > On Wed, Sep 07, 2011 at 09:50:29PM -0000, Michael Witten wrote:
> >> My boot process is stalling proximate the following messages (after a period
> >> of time, some other message might show up, but the boot never progresses much
> >> further):
> >>
> >> cfg80211: World regulatory domain updated:
> >> cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> >> cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> >> cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> >> cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> >> cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> >> cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> >>
> >> I bisected to this patch, namely via the following commit:
> >>
> >> commit ecb4433550f0620f3d1471ae7099037ede30a91e
> >> Author: Stanislaw Gruszka <sgruszka@redhat.com>
> >> Date: Fri Aug 12 14:00:59 2011 +0200
> >
> > Grr, crap.
> >
> >>
> >> Now, it may be the case that my system startup's scripts are doing something
> >> funny, as the stall described above occurs after Arch Linux outputs:
> >>
> >> Waiting for UDev uevents to be processed
> >>
> >> At this point, that's all I know.
> >
> > What wireless driver are you using? If this is ipw2x00 please try
> > attached patch.
>
> I am indeed using `ipw2200', and your patch seems to fix the problem.
>
> How did you know what to do?
You are not the first person who hit this bug and did bisection :-/
Witold (CCed) did it. Can you also check if wireless network and rmmod
ipw2x00 works? I did not yet receive that information from Witold
regarding latest patch.
Thanks
Stanislaw
next prev parent reply other threads:[~2011-09-08 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 12:00 [PATCH] mac80211: fix suspend/resume races with unregister hw Stanislaw Gruszka
2011-08-25 5:06 ` Johannes Berg
2011-08-25 15:07 ` [PATCH] cfg80211: document wiphy->registered Stanislaw Gruszka
2011-08-25 16:24 ` Johannes Berg
[not found] ` <d9f6472975e34cb294831e32c8ce2346-mfwitten@gmail.com>
2011-09-08 6:44 ` [PATCH] mac80211: fix suspend/resume races with unregister hw Stanislaw Gruszka
[not found] ` <CAMOZ1BvsPok-AZVCwKnv0hWWXyV+np+nARjGRqwqsvC-du_GAw@mail.gmail.com>
2011-09-08 16:26 ` Stanislaw Gruszka [this message]
2011-09-08 16:54 ` Witold Baryluk
[not found] ` <CAMOZ1Bs_DesZoyYw6yzC8CdqR3yLgXXpBzxvsEsQ0eX4L6Vw+A@mail.gmail.com>
2011-09-08 16:57 ` Witold Baryluk
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=20110908162605.GD2195@redhat.com \
--to=sgruszka@redhat.com \
--cc=baryluk@smp.if.uj.edu.pl \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mfwitten@gmail.com \
--cc=stable@kernel.org \
/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).