From: Joseph Garcia <jpgarcia@execpc.com>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Benjamin Herrenschmidt <bh40@calva.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: powerbook hang from post-sleep cdrom access - fix
Date: Thu, 27 Jul 2000 15:36:35 -0500 [thread overview]
Message-ID: <39809D53.76BEBBB@execpc.com> (raw)
In-Reply-To: Pine.LNX.4.10.10007272146140.2350-100000@opal.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
> > My expirience is that just reading the drive causes a problem, much like
> > userspace trying to read it. there is also the door locking feature that I
> > suppose could be done explicitly on wakeup if mounted. I dont know what else a
> > "media change" ctl entails, but it seems to do enough to get the cdrom back to
> > where it left off.
>
> OK, that seems to mean wherever we can safely send the drive a reset
> command after sleep, we should do that. Now under what conditions will a
> reset command mess up things beyond recovery? Is it possible to sleep the
> machine while the IDE drive has a request under service?
ide-pmac resets all non-mediabay (non-CD?) ide drives on wake.
(idepmac_wake_disk)
looking at the mediabay code, the media bay (at least when containing a CD)
seems to be reset. (set_media_bay is called, feature_set(reset) is called on
the bay, messages confirms call to set_media_bay with a "kernel: media bay 0
contains a CD-ROM drive" on wake). are IDE-floppies handled by the mediabay's
CD code as well?
By mutual exclusion, it would appear we already reset ide devices upon wake.
the media change call may be what we need to get the removable media to re-init
their status. I did get the following VFS message, which may cause concern.
Jul 27 12:00:01 momiji pmud[330]: system awake again
Jul 27 12:00:01 momiji pmud[330]: running /etc/power/pwrctl wakeup ac
Jul 27 12:00:01 momiji pwrctl: calling /etc/power/pwrctl-local wakeup ac
Jul 27 12:00:01 momiji kernel: VFS: busy inodes on changed media.
PMUD does a sync right before signalling to sleep, so most activity is reduced.
I think the rest tends to be handled by the kernel's sleep with interrupts
disabled, etc.
I noticed in browsing the kernel code, there is a file operation called
revalidate, which takes the same params as check_media_change. cdrom.c does not
define this. Would this be a route worth pursuing over the media change
solution?
--
Joseph P. Garcia jpgarcia@execpc.com jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate Student Employee - Systems Programmer
University of Wisconsin - Madison UW Lidar Group
An error occurred while booting. Please try again.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-27 20:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-27 7:13 powerbook hang from post-sleep cdrom access - fix Joseph Garcia
2000-07-27 7:16 ` Stephan Leemburg
2000-07-27 8:12 ` Joseph Garcia
2000-07-27 10:32 ` Benjamin Herrenschmidt
2000-07-27 17:46 ` Robert Thompson
2000-07-27 8:59 ` Michael Schmitz
2000-07-27 10:36 ` Benjamin Herrenschmidt
2000-07-27 12:12 ` Michael Schmitz
2000-07-27 13:12 ` Benjamin Herrenschmidt
2000-07-27 19:27 ` Michael Schmitz
2000-07-27 16:10 ` Joseph Garcia
2000-07-27 19:48 ` Michael Schmitz
2000-07-27 20:36 ` Joseph Garcia [this message]
2000-07-27 20:50 ` Michael Schmitz
2000-07-27 21:21 ` Benjamin Herrenschmidt
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=39809D53.76BEBBB@execpc.com \
--to=jpgarcia@execpc.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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).