From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: linux-kernel@vger.kernel.org, corentincj@iksaif.net,
acpi4asus-user@lists.sourceforge.net
Subject: Re: EeePC card reader activated after suspend to ram
Date: Tue, 17 Feb 2009 14:30:23 +0000 [thread overview]
Message-ID: <499AC9FF.8040605@tuffmail.co.uk> (raw)
In-Reply-To: <20090217135857.GA2854@silver.sucs.org>
Sitsofe Wheeler wrote:
> Hi,
>
> I've found that there is a particular circumstance when the card reader
> in my EeePC 900 will always be activated on resume even though before
> the suspend to ram it was switched off.
>
> The steps to reproduce are as follows:
>
> 1. Ensure the card reader is enabled before Linux boots (e.g. if Linux
> is already running do (as root)
> echo 1 > /sys/devices/platform/eeepc/cardr
> and then reboot).
> 2. In the freshly booted kernel issue (as root)
> echo 0 > /sys/devices/platform/eeepc/cardr
> 3. Initiate suspend to RAM e.g.:
> echo mem > /sys/power/state
> 4. Press a key to resume.
>
> Notice that the logs will contain something similar to the following:
>
> kernel: [ 841.435629] Restarting tasks ... done.
> kernel: [ 907.576216] usb 1-5: new high speed USB device using ehci_hcd and address 3
> kernel: [ 907.699381] usb 1-5: configuration #1 chosen from 1 choice
> kernel: [ 907.707460] scsi3 : SCSI emulation for USB Mass Storage devices
>
> Doing
> cat /sys/devices/platform/eeepc/cardr
> returns 0. Issuing
> echo 0 > /sys/devices/platform/eeepc/cardr
> even though the card reader is supposedly off will result in it being
> disabled until after the next suspend to ram/resume.
>
> Reproduced with a clean 2.6.29rc5 and the heavily Xandros patched
> Xandros 2.6.21 kernel that the Eee ships with.
>
> Does anyone have any ideas about this one?
>
It happens on my 701 too. The driver doesn't explicitly cache the
"cardr" value, so I'd blame the BIOS.
You could work around it. Add a hack somewhere that does the equivalent of
x=`cat /sys/devices/platform/eeepc/cardr`
echo $x > /sys/devices/platform/eeepc/cardr
But it is a tradeoff. This is a largely unused feature. You've found one
pretty harmless bug in the hardware... there's the risk that there's
another hardware bug which would then be easier to trigger, and cause
bigger problems. It'd be much better if Asus could fix the BIOS :-).
Alan
prev parent reply other threads:[~2009-02-17 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 13:58 EeePC card reader activated after suspend to ram Sitsofe Wheeler
2009-02-17 14:30 ` Alan Jenkins [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=499AC9FF.8040605@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentincj@iksaif.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.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.