Re: 2.6.10-rc3-mm1: swsusp

[Pavel Machek <pavel@ucw.cz>]

Hi!

> I must say I'm really impressed with the progress that swsusp made since I 
> tried it last time (close to 2.6.10-rc1 as I recall).  Now I've been using it 
> for a couple of days on 2.6.10-rc3-mm1 and It's never refused to suspend the 
> machine because of the lack of (contiguous) memory which happened very often 
> before, and it seems to be much faster.  Using it my notebook has
> reached 

Hmmm, unfortunately I did not changes in that area. Perhaps memory
managment was fixed/improved?

> Still, unfortunately, today it crashed on suspend and I wasn't able to get any 
> useful information related to the crash, because swsusp apparently does not 
> send some of its messages to the serial console.  In particular, anything 
> from within the critical section is not printed there and that's why I think 
> (I'm not sure though) that the crash occured in the critical section.  Could 
> you tell me please if it's possible to make all of the swsusp messages appear 
> on the serial console and, if so, how to do this (I've already tried "dmesg 
> -n 8" and "echo 9 > /proc/sysrq-trigger" but none of them helps)?

Using regular vga console and digital camera seems to be popular way
to get dumps. I'm not sure why swsusp critical section interferes with
serial, perhaps serial console support has to "know" about serial
console and not suspend it during suspend() call?

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!