Re: Two problems with system sleep

["Rafael J. Wysocki" <rjw@sisk.pl>]

On Wednesday 17 February 2010, Alan Stern wrote:
> On Tue, 16 Feb 2010, Rafael J. Wysocki wrote:
> 
> > > > Is the problem reproducible with init=/bin/bash vga=0?
> > > 
> > > Yes.  I tried booting with no initramfs and with "init=/bin/bash
> > > vga=0".  Just as before the suspended machine didn't do anything when I
> > > pressed keys on the keyboard, and pressing the power button caused it
> > > to come back up totally unresponsive with the screen blank and the
> > > CapsLock and ScrollLock lights blinking.
> > 
> > Hmm.  What about X86_CHECK_BIOS_CORRUPTION and friends?
> 
> CONFIG_X86_CHECK_BIOS_CORRUPTION was not set.  I created a new kernel 
> with:
> 
> CONFIG_X86_CHECK_BIOS_CORRUPTION=y
> CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
> CONFIG_X86_RESERVE_LOW_64K=y
> 
> And then I booted with "memory_corruption_check=1 vga=0 init=/bin/bash" 
> on the command line just to be sure.  There was a log message saying 
> that low memory would be checked every 60 seconds, but no error 
> messages appeared after waiting for a few minutes.
> 
> The behavior during resume was unchanged.
> 
> > Perhaps the BIOS steps onto the early wakeup code.
> 
> The difficulty is that I have no way to find out what's going on.  The
> serial port isn't working (or nothing gets sent to it, or both) and the
> system hangs before the video output gets enabled.

You can try to put no_console_suspend into the kernel command line, but I doubt
it'll help with the serial resume.

Anyway, we need to check if control gets back to acpi_suspend_enter().

BTW, does anything change if you put acpi_sleep=sci_force_enable into the
kernel command line?

Rafael