mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabio Comolli <fabio.comolli@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Darren Salt <linux@youmustbejoking.demon.co.uk>,
	Len Brown <lenb@kernel.org>
Subject: Re: [Regression] - 2.6.32-rc5 hangs using rfkill on an eeePC
Date: Fri, 16 Oct 2009 22:36:34 +0200	[thread overview]
Message-ID: <b637ec0b0910161336j7848b46eh4fcf69e450161afb@mail.gmail.com> (raw)
In-Reply-To: <b637ec0b0910161253y60eb6b4fl3e49e5b9129d81ac@mail.gmail.com>

Actually it was pretty easy to find the culprit, as thereare only two
eeepc-related commit between -rc4 and -rc5 and one is about the
camera.

Reverting:

[PATCH] eeepc-laptop: Prevent a panic when disabling RT2860 wireless
when associated

fixes the problem.

Commit-id is b56ab33d68638e6aafdbfc694025e8354a628f49

Regards,
Fabio


On Fri, Oct 16, 2009 at 9:53 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
> Hi all.
> Pressing rfkill button on my eeePC 900 to disable wireless hangs the system.
>
> In console I can see (warning: what follows is copied by hand):
>
> acpid: client 148[6:100] has disconnected
> ACPI group/action not found: hotkey / ATKD
> unregister netdevice: waiting for wlan0 to become free; usage count=1
>
> (last line repeats forever). Hard reset is needed.
>
> With any previous kernel version (I'm running -rc4 right now) everything works:
>
> ACPI group/action undefined: hotkey / ATKD
> ath5k 0000:01:00.0: PCI INT A disabled
>
> (there's no acpid line)
>
>
> Regards,
> Fabio
>

  reply	other threads:[~2009-10-16 20:44 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 [this message]
2009-10-16 20:46 ` Frans Pop
2009-10-16 21:23   ` Fabio Comolli
2009-10-16 21:28     ` Darren Salt

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=b637ec0b0910161336j7848b46eh4fcf69e450161afb@mail.gmail.com \
    --to=fabio.comolli@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@youmustbejoking.demon.co.uk \
    --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®