[KLUG Members] IBM T30/SUSE 10.0 Suspend to RAM Problems

[Peter Bart]

On Sun, 2006-11-19 at 14:04 -0800, Chester Wisniewski wrote:
> You can do a lspci from a shell to determine what those devices are.
> 
> Chet
> 
> 
> Peter Bart wrote:
> > Hello Everyone,
> > 	I'm trying to clean up some things on my install before I move on to
> > the next install, for which I now have permission. I've been working my
> > way through the logs, slowly but successfully because I have to look
> > thing up. One of the things I'm trying to deal with is I've never gotten
> > suspend to disk to work properly. It's set in Yast to work and when I
> > suspend a popup box shows up telling me it's stopping services but then
> > the display stays on with several error messages. Over several minutes
> > the screen goes from black with the messages to almost white which
> > obscures the text. The indicator lights show that it has suspended. I
> > can also resume. I found the text displayed in /var/log/messages:
> >
> >
> > Nov 18 21:59:28 plumber kernel: ACPI: PCI interrupt for device
> > 0000:00:1d.0 disabled
> > Nov 18 21:59:40 plumber syslog-ng[4435]: Changing permissions on special file /dev/xconsole
> > Nov 18 21:59:40 plumber syslog-ng[4435]: Changing permissions on special file /dev/tty10
> > Nov 18 21:59:40 plumber kernel: Stopping tasks: =========================================

> =========================================================================================

> ============================================|
> > Nov 18 21:59:40 plumber kernel: ACPI: PCI interrupt for device 0000:02:08.0 disabled
> > Nov 18 21:59:40 plumber kernel: wlan0: Orinoco-PCI entering sleep mode (state=3)
> > Nov 18 21:59:40 plumber kernel: ACPI: PCI interrupt for device 0000:02:00.1 disabled
> > Nov 18 21:59:40 plumber kernel: ACPI: PCI interrupt for device 0000:02:00.0 disabled
> > Nov 18 21:59:40 plumber kernel: ACPI: PCI interrupt for device 0000:00:1f.5 disabled
> >
> > 	A few lines above this I see the following:
> >
> > Nov 18 21:59:28 plumber kernel: ACPI: PCI interrupt for device 0000:00:1d.1 disabled
> >
> > 	And a few more lines up:
> >
> > Nov 18 21:59:28 plumber kernel: ACPI: PCI interrupt for device 0000:00:1d.2 disabled
> >
> > 	Some more lines up from that:
> >
> > Nov 18 21:59:22 plumber kernel: ACPI: PCI interrupt for device 0000:00:1f.6 disabled
> >
> > 	I've searched the web for a similar problem, read man pages until my eyes bled,

>  looked through the SUSE help center, looked through the K control center and Yast all 

> for naught. I can't even seem to find out what those devices are! I didn't post the 

> entire message log file for obvious reasons. I can replicate it easy enough.What am I missing here?
> >
> > Regards,
> >
> >
> >   
> 
> _______________________________________________
> Members mailing list
> Members at kalamazoolinux.org
> 

Chester,
	Thanks for the command. I think it might be a dead end though. I
compared the suspend to disk and ram logs and they appear identical.
>From the entries into the log to the order in which they appear. The
only difference seems to be the display shuts off when I suspend to
disk. Sometimes the sound card has a hard time coming back from suspend
to ram but that's after. Even if the display is still on my laptop
appears to suspend to ram successfully. There is a difference between
the two, suspend to disk appears to wake up some of the suspended
devices; sorry it goes by very quickly; and it also wakes up the orinoco
pci. Then it writes data to swap and then the hadr drive shuts down.
What confuses me is not just the screen staying on but why something to
do with wifi needs to wake up to write to swap. I think i get why data
would be written to swap for suspend to disk but not for suspend to ram,
the way the data is stored is different. I might be confused about that
though. What is interesting is that suspend to ram worked beautifully on
the same laptop, same distro but using gnome then. I use KDE now.

Regards,
-- 
Peter Bart <peter at petertheplumber.net>
http://petertheplumber.net