|
Bugzilla – Full Text Bug Listing |
| Summary: | Suspend To Disk, RAM and Standby are not working (go to screensaver instead) | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | J. Vasconcelos <jfvasconcelos> |
| Component: | Kernel | Assignee: | Pavel Machek <pavel> |
| Status: | RESOLVED WONTFIX | QA Contact: | Siegfried Olschner <siegfried.olschner> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Alpha 3plus | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | /var/log/messages | ||
|
Description
J. Vasconcelos
2005-12-11 17:56:39 UTC
Seems to be a kernel issue, CCing Pavel. this looks like a usb device. Check for device 1-4 (which device it is) and detach it before suspend or unload its driver. Needs to be fixed anyway. Don't have any USB plugged in (not even the mouse). I don't know how to see which is the device 1-4 but I do know this:
1) If booted without my LAN cable,i.e. without LAN access, the suspend to disk works OK.
2) If booted with my LAN cable plugged in, the suspend to disk fails (as reported above).
So I guess it's the network card. Furthermore, browsing the net sometimes fails ("Unknown host bugzilla.novell.com", for instance) and have to hit reload to load the site.
Rebooted some more times with both LAN plugged and unplugged. Can figure out a pattern because the suspend to disk now works ok. The bug is there, somewhere, but it doesn't seem systematic! I'm attaching the /var/log/messages file tail in the case for a successful "Suspend To Disk" with USB mouse and LAN cable plugged in. The USB mouse takes some time to be reactivated after KDE prompts up (have to use touchpad for a while). Created attachment 60245 [details]
/var/log/messages
(In reply to comment #0) > Another minor issue: the scroll lock key led is always switched on. If > numlock/capslock is activated, the numlock/capslock led goes on (as it should) > and the scroll lock led goes off. If the numlock/capslock is deactivated, > scroll lock led goes on again. I experience the same with an installation of Alpha4 on an IBM ThinkPad T30 (2366-97G, to be exact). This issue should be forked to another bug, though. SuSE had some very stupid init scripts that do setleds +scrolllock or something like that. Make sure that is not biting you. I'm afraid that we need reproducible failure for suspend-to-disk. Debugging suspend-to-ram should be done on mainline. This seems to be a hardware problem and not a usability issue. Who could be responsible for this and where can we sort this? J.: please only report one issue for every bug. So please make a new bug for the numlock issue. Please try to find a a way to reproduce the suspend bug. It is probably me being responsible, but I need better info for debugging it. I.e. reproducible way to reproduce. Without that it is CLOSED/WONTFIX. Hi I'll install Suse 10.1 alpha4 as soon as I have time (small bandwidth and lots of work). Working with Suse 10.1 alpha3 for now. While the suspend to disk seems to works most of the times, the suspend to ram doesn't work at all (wakeup fails and the computer hangs). What files can I send to help debug? Cheers. Pavel: Assigning this to you... to #11: Try finding out what device 1-4 is. Also see my comment #7. Reporter indicated that he has no time just now (in private mail), so I'm closing it. If s-t-disk problems remain in beta1 (or later) kernels, please just file another bug report. |