From: Darren Salt <linux@youmustbejoking.demon.co.uk>
To: Fabio Comolli <fabio.comolli@gmail.com>
Cc: Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org, rjw@sisk.pl,
linux-wireless@vger.kernel.org
Subject: Re: [Regression] - 2.6.32-rc5 hangs using rfkill on an eeePC
Date: Fri, 16 Oct 2009 22:28:27 +0100 [thread overview]
Message-ID: <50B0C1487C%linux@youmustbejoking.demon.co.uk> (raw)
In-Reply-To: <b637ec0b0910161423o2a5fdd12u926f50c2e4139bf3@mail.gmail.com>
I demand that Fabio Comolli may or may not have written...
[snip]
> I already answered my own post in the thread: the culprit is:
> eeepc-laptop: Prevent a panic when disabling RT2860 wireless when
> associated
> Funnily enough, my eeePC has an Atheros card.
We (myself and Corentin Chary) tried to stop that patch once I'd noticed the
problem – I updated the patch, tested (all was fine with the rt2860 card),
upgraded from -rc3 to -rc4, installed an Intel 3945 card, tested, sent the
patch, restored the rt2860 card to its proper place, happened to toggle
wireless, got a panic due to having failed to remember to actually apply the
patch to -rc4... at this point, I rechecked with the Intel card (this time
with a patched kernel), saw a failure (stuck process – hmm, should rfkill be
re-entrant?), reported it, went digging into rt2860sta and produced, tested
and sent the replacement patch, then tried to stop the broken patch from
going upstream.
A reversion patch has been sent by Corentin (shortly after you reported this,
though the commit message says that he's reacted to its being in rc5) and,
earlier today, I directly requested that it be reverted; so hopefully, one
way or another, -rc6 will be fine for Atheros users and anybody else affected
by this, much as -rc5 is for rt2860 users.
Oh well. So much for Linus's "no new regressions". ;-}
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| using Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + Travel less. Share transport more. PRODUCE LESS CARBON DIOXIDE.
Look! Over there!... Ha. Made you look.
prev parent reply other threads:[~2009-10-16 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 19:53 Fabio Comolli
2009-10-16 20:36 ` Fabio Comolli
2009-10-16 20:46 ` Frans Pop
2009-10-16 21:23 ` Fabio Comolli
2009-10-16 21:28 ` Darren Salt [this message]
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=50B0C1487C%linux@youmustbejoking.demon.co.uk \
--to=linux@youmustbejoking.demon.co.uk \
--cc=elendil@planet.nl \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®