All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux acpi <linux-acpi@vger.kernel.org>,
	Matthew Garrett <mjg@redhat.com>
Subject: Re: eeepc-laptop: Use standard interfaces
Date: Sat, 11 Oct 2008 14:47:32 +0100	[thread overview]
Message-ID: <48F0AE74.30303@tuffmail.co.uk> (raw)

I've tested this change in the acpi-test tree.  I welcome the input
events - I now get a nice on-screen display for the volume hotkeys. 
However, there's a regression which is probably related to the rfkill code.

My wireless interface dies on suspend:

[  367.430008] Restarting tasks ... done.
[  368.683300] ath5k phy0: failed to wakeup the MAC Chip
[  368.683300] ath5k phy0: unable to reset hardware: -5
[  369.933290] evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting
output to 64 bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html
[  371.619966] ath5k phy0: failed to wakeup the MAC Chip
[  371.619966] ath5k phy0: unable to reset hardware: -5

I can still reproduce it if I stop the "hal" and "dbus" services and use
s2ram to suspend.

I guess the rfkill subsystem automatically trips the switch to save
power in suspend.  And I don't have resume scripts with the pci hotplug
magic workaround.  So, do you still think it would be appropriate to
merge this rfkill code before the pci hotplug magic is implemented
in-kernel?

Regards
Alan

             reply	other threads:[~2008-10-11 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 13:47 Alan Jenkins [this message]
2008-10-11 13:55 ` eeepc-laptop: Use standard interfaces Matthew Garrett

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=48F0AE74.30303@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg@redhat.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.