FS#16562 - [kernel26] Can't suspend or hibernate using 2.6.31

Attached to Project: Arch Linux
Opened by - (sqrt) - Saturday, 10 October 2009, 20:06 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 23 January 2010, 16:28 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
When I try to hibernate or suspend using pm-hibernate or pm-suspent my MSi WiND netbook, the black screeinks and than I fall back to KDE. There was nothing like that on 2.6.30 kernel.
Additional info:
Kernel 2.6.31.3-1
pm-utils 1.2.5-1
I attach pm-suspend.log after few tries to suspend.
   pm-suspend.log (5.3 KiB)
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 23 January 2010, 16:28 GMT
Reason for closing:  Upstream
Additional comments about closing:  No response in ~3 months. Please reopen if necessary, with a link to upstream report.
Comment by Nicholas Moore (diamondice00085) - Sunday, 18 October 2009, 21:20 GMT
I too am having this issue with hibernating after the 2.6.31 kernel upgrade. The following error appears in my pm-suspend.log

/usr/lib/pm-utils/pm-functions: line 275: echo: write error: Device or resource busy
   pm-suspend.log (6 KiB)
Comment by Not Important (pholie) - Wednesday, 28 October 2009, 21:57 GMT
Wed Oct 28 22:52:27 CET 2009: performing suspend
/usr/lib/pm-utils/pm-functions: line 259: echo: write error: Device or resource busy


$ uname -r
2.6.31-bfs211-bfs
Comment by Not Important (pholie) - Thursday, 29 October 2009, 09:20 GMT
with 2.6.31-bfs it suspends again but after resuming keyboard didn't work
Comment by Not Important (pholie) - Thursday, 29 October 2009, 09:21 GMT
more precise 2.6.31-304.5
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 09 November 2009, 01:31 GMT
  • Field changed: Category (Packages: Core → Upstream Bugs)
Please report to upstream if not already reported. This is the best way to resolve this type of issues. Thanks.

Loading...