Bug 344691 - kernel-2.6.23.1-23.fc8 fails to resume
Summary: kernel-2.6.23.1-23.fc8 fails to resume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-21 18:55 UTC by Osma Ahvenlampi
Modified: 2007-12-04 17:36 UTC (History)
1 user (show)

Fixed In Version: 2.6.23.8-63.fc8
Clone Of:
Environment:
Last Closed: 2007-12-04 17:36:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
lspci -v -nn output (8.65 KB, text/plain)
2007-10-21 18:55 UTC, Osma Ahvenlampi
no flags Details

Description Osma Ahvenlampi 2007-10-21 18:55:56 UTC
Description of problem:

laptop hard disk inaccessible after a suspend-to-ram-resume cycle. kernel prints
"journal commit I/O error" and "sd 0:0:0:0: [sda] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK" (or something to that
effect, I had to write it down).

Version-Release number of selected component (if applicable):

kernel-2.6.23.1-23.fc8 known-bad, kernel-2.6.22.4-65.fc7 known-good. Sorry,
that's a wide window, I know.

How reproducible:

Every time.

Steps to Reproduce:
1. pm-suspend (or trigger the same by gnome-power-manager)
2. Resume
3. try to write to disk (or read outside of cache, I think)

Comment 1 Osma Ahvenlampi 2007-10-21 18:55:56 UTC
Created attachment 233651 [details]
lspci -v -nn output

Comment 2 Will Woods 2007-10-21 21:58:27 UTC
What kind of laptop? 

Comment 3 Osma Ahvenlampi 2007-10-22 06:50:02 UTC
Acer TravelMate 6292, Core 2 Duo, Santa Rosa chipset. The attachment has the
hardware details. I've been suspending and resuming this quite (but not 100%)
reliably through gnome-power-manager and hal since I got it this summer under
the F7 kernels. What instability I've had with it has been related to X and the
Intel driver, but these days that's quite good as well. I believe this is the
first kernel-related issue I've seen with the machine.

Comment 4 Osma Ahvenlampi 2007-10-23 19:40:12 UTC
Tighter window -- the last F7 update kernel kernel-2.6.22.9-91.fc7 works, and
the  first F8 test kernel kernel-2.6.23-0.164.rc5.fc8 does not.

Comment 5 Osma Ahvenlampi 2007-10-25 12:55:25 UTC
I found kernel-2.6.23.1-10.fc7 from koji. This kernel works. 
On the other hand, kernel-2.6.23.1-30.fc8 does not. I hope these are close
enough to each other to see the difference...

Comment 6 Osma Ahvenlampi 2007-11-04 16:47:35 UTC
Still continue to have the problem with kernel-2.6.23.1-42.fc8. Certainly seems
to be some systematic difference between F7 and F8 kernel profiles.

Comment 7 Chuck Ebbert 2007-11-05 20:49:33 UTC
Which kernel: i686 or x86_64?


Comment 8 Osma Ahvenlampi 2007-11-06 07:04:04 UTC
Oh, sorry, neglected to mention that. i686.

Comment 9 Osma Ahvenlampi 2007-12-02 15:20:28 UTC
kernel-2.6.23.8-63.fc8.i686 from updates-testing works


Note You need to log in before you can comment on or make changes to this bug.