FS#5920 - Suspend2ram broken again with 2.6.19

Attached to Project: Arch Linux
Opened by Dawid Wróbel (cromo) - Saturday, 02 December 2006, 17:40 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 22 March 2007, 12:49 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To James Rayner (iphitus)
Architecture All
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

This is getting radiculous, to be honest. Suspend2ram worked fine with .16, stopped with .17. .18 fixed it, .19 broke it again. I simply can't belive it. The testing unit is Dell Precision M20 laptop which exactly the sam as Precision M20, except for the different dedicated GPU, that is not the problem here anyway (I tested suspending under console only). After resuming, no reaction at all, the system is dead, disk spin up, LCD backlight works, but pressing caps lock doesn't. Dead. Exactly the same way as it was dead with .17.
I guess the issue is libata again, since the system comes with SATA drive and AFIR that was the reason for the problems with .17.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Thursday, 22 March 2007, 13:54 GMT
Reason for closing:  None
Comment by Dawid Wróbel (cromo) - Saturday, 02 December 2006, 17:43 GMT
Errr: "The testing unit is Dell Precision M20 laptop which is exactly the same as Latitude D610"
Comment by Pierre Schmitz (Pierre) - Wednesday, 06 December 2006, 09:47 GMT
I can cofrim this problem with a Toshiba L10. Suspend2Disk still works. But 2.6.18 did not work for me, too. (but as I remeber 2.6.16 did). I am using an integrated graphic from Intel (i855)

Strange: On my desktop with nvidia-driver this works perfectly.
Comment by Tobias Powalowski (tpowa) - Wednesday, 14 February 2007, 23:43 GMT
status on .20 series?
Comment by Dawid Wróbel (cromo) - Thursday, 15 February 2007, 01:15 GMT
What I noticed with .20 is that s3 works fine with x.org radeon driver, but has exactly same problems with fglrx as with .19. I noticed that by accident when the fglrx package was initially broken for .20 and I had to use radeon - I was happy to notice s3 works. Then after fglrx package got fixed I got disappointed again with fglrx. The conclusion that I would not expect is that it is fglrx that breaks s3 even though everything seamed it is not graphic's fault.
Comment by Tobias Powalowski (tpowa) - Thursday, 15 February 2007, 06:19 GMT
probably a bug in binary driver, thats not a kernel fault assigning to fglrx maintainer now.
bug can be probably only fixed upstream by amd/ati
Comment by Pierre Schmitz (Pierre) - Thursday, 15 February 2007, 06:25 GMT
Suspend2Ram works fine for me when using kernel 2.6.20 from testing.
Comment by Dawid Wróbel (cromo) - Friday, 09 March 2007, 11:54 GMT
The most recent fglrx package has fixed the problem. I think this bug report can be closed now.
Comment by Roman Kyrylych (Romashka) - Thursday, 22 March 2007, 12:50 GMT
Dawid Wróbel (cromo):
2.6.20-beyond2 from testing breaks S3 again, although the stock 2.6.20.3-2 still works fine. 2.6.19-beyond2 worked fine, too. Note this is with fglrx, I am not sure what about x.org radeon driver but for me it doesn't seem related since the aforementioned kernels work fine with the same fglrx driver.
Comment by Dawid Wróbel (cromo) - Thursday, 22 March 2007, 13:20 GMT
I've already filed a bug report on iphitus's beyond bugzilla.

Loading...