On Tuesday 16 February 2010, Alan Stern wrote:
> On Sun, 14 Feb 2010, Rafael J. Wysocki wrote:
>
> > On Sunday 14 February 2010, Alan Stern wrote:
> > > On Sat, 13 Feb 2010, Rafael J. Wysocki wrote:
> > >
> > > > > The bigger problem is that with a normal sleep ("echo none >pm_test"),
> > > > > the system doesn't wake up. Pressing a key or a mouse button does
> > > > > nothing. Pressing the power button causes the machine to start up
> > > > > again, but the screen remains blank and there's no response to network
> > > > > pings.
> > > > >
> > > > > This was with more or less standard 2.6.33-rc6 (Greg KH's patch set was
> > > > > applied but none of your PM patches). The motherboard is an Intel
> > > > > ICH5 with a 32-bit CPU. Any ideas on ways to approach this?
> > > >
> > > > That depends on the graphics adapter. Is it Intel or AMD?
> > >
> > > $ lspci -s 2.0
> > > 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
> >
> > Well, that is supposed to work. Do you have KMS turned on?
>
> It's hard to tell. CONFIG_DRM and CONFIG_DRM_HELPER were both set to M
> and the i915 driver was loaded, which pulled both of them in as well.
> But lsmod showed that i915's usage count was 0 and there were no kernel
> messages about the framebuffer device; the only relevant messages were:
>
> [ 41.814441] [drm] Initialized drm 1.1.0 20060810
> [ 41.869690] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [ 41.869705] pci 0000:00:02.0: setting latency timer to 64
> [ 41.883076] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
>
> Also, the console remained in the BIOS's original 80x25 video mode.
> Since I wasn't running X11 during the test, KMS shouldn't have made any
> difference, right?
>
> > > Do you need any more information than that?
> >
> > 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?
Perhaps the BIOS steps onto the early wakeup code.
Rafael
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm
