Re: Inspiron 8200 + FC3 + suspend/resume
- I have exactly the same problem in Mandriva LE2005, with kernel
2.6.11. Hardware is inspiron 8200 with ATI radeon mobility 9000. Boot
with acpi=off, suspend from console with apm -s.
It works perfectly in Mandrake 10.0 (kernel 2.6.3) with the same
settings. The only difference I can see in the logs is the following:
May 22 00:08:51 ignatius cardmgr: executing: 'modprobe -r
May 22 00:08:51 ignatius cardmgr: + FATAL: Module orinoco_cs is
May 22 00:08:51 ignatius cardmgr: modprobe exited with status 1
May 22 00:08:51 ignatius cardmgr: exiting
--- In firstname.lastname@example.org, "Dave Kristol"
> --- In email@example.com, "Dave Kristol"
> <dmk-yahoo@k...> wrote:
> > [Replying to my own post.]
> > I've been trying to simplify the problem. I've cut X and the
> > driver out of the picture by trying to suspend/resume *just* fromthe
> > shell level, and even that does not work. Suspend seems to work:
> > machine does shut down. But when I resume, the disk light comeson
> > for a long time. I seem to be able to do a little bit from theshell,
> > then the system locks up (on the first access to disk?).disk.
> I'm now lurching in another direction. The behavior I see is
> consistent with a system that, after resume, cannot access its
> When the system resumes, I don't get a shell prompt immediately if II
> hit newline, only if I hit Ctrl-C, as though I'm breaking out of a
> shell script. I can poke around a little with shell commands until
> do something that, presumably, requires access to the disk. I canthe
> look at files whose blocks are in the buffer cache. Once I go to
> disk, though, the system locks up.disk
> Question: How can I tell whether the disk controller is alive after
> resume (especially if I can't write anything to the disk!)? The
> sounds like it spins up after resume.tamper
> N.B. I've looked at the HDPARM_AT_RESUME stuff in
> /etc/sysconfig/apmd. I don't think it's appropriate for me to
> with those. First, suspend/resume had been working under RH9.
> Second, I did an hdparm after resuming, and the values looked right.
> Thanks for any help.
> Dave Kristol