suspend-devices-not-cpu [was Re: [PATCH 2/2] Fix console handling during suspend/resume]

[Pavel Machek <pavel@suse.cz>]

Hi!

> > > It's _not_ supposed to be PC-compatible. It just happens to be close 
> > > enough that we can ignore the differences.
> > 
> > Aha, okay. So it basically needs special config to work, and
> > complaining that it does not boot noapic is not helpful.
...
> So it's not a "legacy PC", but it's certainly "standard Intel chipsets 
> with ACPI". So the same image _should_ really work.

Okay, first example of non-legacy PC :-).

> > Actually s2ram used to work for quite long time...
> 
> I know. On _some_ machines. So far, I don't think I've actually ever hit 
> a machine where it "just worked". Every single time there's some module 
> that needs to be unloaded for it to boot, or it needs to use fbcon, or it 
> needs some other magic.
> 
> I'd really like for it to "just work", and having more people who can try 
> to debug why it doesn't work for them is probably the best way to get 
> there. I know from personal experience that at least _one_ reason why 
> people didn't even bother debugging it was that there simply wasn't 
> anythign to debug. There was just a dead brick.
> 
> It's that "it's just a dead brick" part I want to fix. I want to turn that 
> into "it's a dead brick that I can look inside".

Yes, RTC is a pretty clever hack that should not break anything. I
also used leds on port 80, hardware debugger, and beeps to get same
results.

Actually... I played around with idea "enter low-power mode without
hardware help".. it could be very useful for driver testing.

I imagine something that would suspend all the devices, but instead of
powering cpu down at the end, it would just enter low power mode. That
way, we can rule BIOS interactions etc. Would such patch be
acceptable?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html