Bug 6714
Summary: | Suspend-to-RAM w/SATA slight regression from 2.6.16.20 to 2.6.17 | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Øyvind Stegard (oyvind) |
Component: | Serial ATA | Assignee: | Tejun Heo (htejun) |
Status: | REJECTED UNREPRODUCIBLE | ||
Severity: | normal | CC: | bunk, htejun |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.17 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
2.6.17 kernel boot log
kernel config lspci -vv |
Description
Øyvind Stegard
2006-06-19 06:33:52 UTC
Created attachment 8340 [details]
2.6.17 kernel boot log
Created attachment 8341 [details]
kernel config
Created attachment 8342 [details]
lspci -vv
I haven't experienced the problem since applying the patch mentioned in the description of this bugzilla-report. Re: Comment #14: I take that back, it still happens occasionally. The latest incident was with 2.6.17.7. So I guess that patch really doesn't do any good. Sorry, the previous comment should be Re: Comment #4. libata recently received overhaul in suspend/resume department. Can you try libata-tj patch[1] against 2.6.17.4 or 2.6.18-rc3? [1] http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17.4-20060710.tar.bz2 Do you have a patch against 2.6.17.7 (latest stable) ? I could try it and report back, but it's a little cumbersome for me to downgrade to 2.6.17.4 right now, since I'm at work. I tried the patch against 2.6.17.7, and I suspect some parts of it are already in 2.6.17.7 (patch detects previously applied stuff). Sorry, not yet. I'll make an updated version but can't say when. Is the problem still there in 2.6.18-mmX kernel? Since this bug was reported, I've switched to using the standard Ubuntu Dapper distro kernel (2.6.15-based), switched distro _and_ I've switched hardware (new laptop). But, for the sake of this bug report, I will try 2.6.18-mm2 (using the the config attached here) on my old laptop. I am, however, not able to re-create the old sitation completely because of different suspend/resume scripts, etc (Ubuntu's suspend/resume scripts are quite sophisticated compared to what I used earlier on Fedora Core). Note that the 2.6.15-based Dapper kernel does *not* exhibit the SATA problem on resume on my old laptop (the hardware used when this bug was first reported). I've not invested any time in finding out what patches they might have for SATA-suspend, etc, etc (it just works nicely:). I think this bug should be closed now and a new one opened if need be. I have no means of reproducing it any more (updated all my installations to Ubuntu Edgy). However, Edgy has a 2.6.17-based kernel, and I have never had troubles suspending any of my SATA-laptops. So I think it can safely be closed. |