From: Randy.Dunlap [mailto:email@example.com]
> > I'm gonna go try the 2.4.7 from RH's "Roswell" beta now.
> OK, thanks for testing that.
2.4.7 has the apm=on bug and won't suspend either... I'm beginning to
suspect that something else is afoot, but I might as well try 2.4.2...
Funny, with 2.4.2, "apm=on" seems to work as expected, and the first time I
tried "apm --suspend", the screen blanked but nothing else appeared to
happen. When I hit a key, the suspend command appeared to still be running.
I switched to a different vc and did a "ps ax", it looked like it was stuck
in the middle of trying to unmount an smbfs filesystem.
Next time I booted up, I umounted the smbfs system and did an "apm
--suspend" that appears to have shut everything down... And when I hit the
power button, it comes up again, albeit with an incredibly dim screen (a
common problem on this Dell Latitude C600).
So, from the point of view of my laptop, something important seems to have
changed between 2.4.2 and 2.4.7.
> I suspect that it's something like a single driver change (not apm,
> but PM-support in a driver). How many I/O-device drivers do you
> use? Would it be difficult to try to isolate which one may be
How would I find out what driver(s) might be vetoing my suspend request?
Here's the complete list of modules which might typically be loaded at boot:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 30 2001 - 21:00:59 EST