resume from suspend to Ram only works once - I/O error the second time (Samsung X20 and IBM T40p - feisty)

[Christopher Hübner]

The first resume after suspend to ram works fine, but after the second resume there seems to be no disk available. On the console I get the error message: scsi 0:0:0:0: rejecting I/O to dead device.

Here's a part of my /var/log/messages file which shows the first successful try and the failing second one:

Apr 24 22:30:36 localhost gnome-power-manager: (nixblicker) Rechner wird in Bereitschaft versetzt da Bereitschaftstaste wurde gedrückt
Apr 24 22:30:45 localhost kernel: [ 3084.772000] ADDRCONF(NETDEV_UP): eth1: link is not ready
Apr 24 22:30:49 localhost kernel: [ 3088.964000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
Apr 24 22:30:49 localhost kernel: [ 3089.120000] ACPI: PCI interrupt for device 0000:02:09.2 disabled
Apr 24 22:30:49 localhost kernel: [ 3089.208000] ACPI: PCI interrupt for device 0000:02:05.0 disabled
Apr 24 22:30:49 localhost kernel: [ 3089.288000] ACPI: PCI interrupt for device 0000:02:07.0 disabled
Apr 24 22:31:03 localhost kernel: [ 3091.672000] Stopping tasks ... done.
Apr 24 22:31:03 localhost kernel: [ 3092.932000] Suspending console(s)
Apr 24 22:31:03 localhost kernel: [ 3094.824000] ohci1394 does not fully support suspend and resume yet
Apr 24 22:31:03 localhost kernel: [ 3094.844000] ACPI: PCI interrupt for device 0000:00:1f.1 disabled
Apr 24 22:31:03 localhost kernel: [ 3094.844000] ACPI: PCI interrupt for device 0000:00:1e.2 disabled
Apr 24 22:31:03 localhost kernel: [ 3094.844000] ACPI: PCI interrupt for device 0000:00:1d.7 disabled
Apr 24 22:31:03 localhost kernel: [ 3094.860000] ACPI: PCI interrupt for device 0000:00:1d.3 disabled
Apr 24 22:31:03 localhost kernel: [ 3094.860000] ACPI: PCI interrupt for device 0000:00:1d.2 disabled
Apr 24 22:31:03 localhost kernel: [ 3094.860000] ACPI: PCI interrupt for device 0000:00:1d.1 disabled
Apr 24 22:31:03 localhost kernel: [ 3094.860000] ACPI: PCI interrupt for device 0000:00:1d.0 disabled
Apr 24 22:31:03 localhost kernel: [ 3098.876000] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
Apr 24 22:31:03 localhost kernel: [ 3098.876000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 19
Apr 24 22:31:03 localhost kernel: [ 3098.876000] usb usb1: root hub lost power or was reset
Apr 24 22:31:03 localhost kernel: [ 3098.876000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 20
Apr 24 22:31:03 localhost kernel: [ 3098.876000] usb usb2: root hub lost power or was reset
Apr 24 22:31:03 localhost kernel: [ 3098.876000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 21
Apr 24 22:31:03 localhost kernel: [ 3098.876000] usb usb3: root hub lost power or was reset
Apr 24 22:31:03 localhost kernel: [ 3098.876000] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 17
Apr 24 22:31:03 localhost kernel: [ 3098.876000] usb usb4: root hub lost power or was reset
Apr 24 22:31:03 localhost kernel: [ 3098.892000] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 19
Apr 24 22:31:03 localhost kernel: [ 3098.892000] ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 17 (level, low) -> IRQ 16
Apr 24 22:31:03 localhost kernel: [ 3099.896000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 21
Apr 24 22:31:03 localhost kernel: [ 3099.964000] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[16] MMIO=[b8003000-b80037ff] Max Packet=[2048] IR/IT contexts=[4/4]
Apr 24 22:31:03 localhost kernel: [ 3099.972000] pnp: Device 00:08 does not support activation.
Apr 24 22:31:03 localhost kernel: [ 3099.972000] pnp: Device 00:09 does not support activation.
Apr 24 22:31:03 localhost kernel: [ 3100.720000] Restarting tasks ... done.
Apr 24 22:31:03 localhost kernel: [ 3101.240000] ata1.00: ata_hpa_resize 1: sectors = 155490289, hpa_sectors = 156301488
Apr 24 22:31:03 localhost kernel: [ 3101.240000] ata1.00: Host Protected Area detected.
Apr 24 22:31:03 localhost kernel: [ 3101.240000] current size : 155490289 sectors (79611 MB)
Apr 24 22:31:03 localhost kernel: [ 3101.240000] native size : 156301488 sectors (80026 MB)
Apr 24 22:31:03 localhost kernel: [ 3101.248000] ata1.00: Native size increased to 156301488 sectors
Apr 24 22:31:03 localhost kernel: [ 3101.252000] ata1.00: limited to UDMA/33 due to 40-wire cable
Apr 24 22:31:03 localhost kernel: [ 3101.264000] ata1.00: ata_hpa_resize 1: sectors = 156301488, hpa_sectors = 156301488
Apr 24 22:31:03 localhost kernel: [ 3101.264000] ata1.00: configured for UDMA/33
Apr 24 22:31:03 localhost kernel: [ 3101.428000] ata1.01: configured for UDMA/33
Apr 24 22:31:03 localhost kernel: [ 3101.428000] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Apr 24 22:31:03 localhost kernel: [ 3101.528000] sda: Write Protect is off
Apr 24 22:31:03 localhost kernel: [ 3101.528000] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 24 22:31:03 localhost kernel: [ 3101.528000] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Apr 24 22:31:03 localhost kernel: [ 3101.528000] sda: Write Protect is off
Apr 24 22:31:03 localhost kernel: [ 3101.552000] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 24 22:31:03 localhost kernel: [ 3101.988000] sdhci: Secure Digital Host Controller Interface driver
Apr 24 22:31:03 localhost kernel: [ 3101.988000] sdhci: Copyright(c) Pierre Ossman
Apr 24 22:31:03 localhost kernel: [ 3101.992000] sdhci: SDHCI controller found at 0000:02:09.2 [1180:0822] (rev 17)
Apr 24 22:31:03 localhost kernel: [ 3101.992000] ACPI: PCI Interrupt 0000:02:09.2[C] -> GSI 18 (level, low) -> IRQ 21
Apr 24 22:31:03 localhost kernel: [ 3101.992000] mmc0: SDHCI at 0xb8003800 irq 21 DMA
Apr 24 22:31:03 localhost kernel: [ 3102.140000] b44.c:v1.01 (Jun 16, 2006)
Apr 24 22:31:03 localhost kernel: [ 3102.140000] ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 22 (level, low) -> IRQ 22
Apr 24 22:31:03 localhost kernel: [ 3102.144000] eth0: Broadcom 4400 10/100BaseT Ethernet 00:13:77:03:9f:41
Apr 24 22:31:03 localhost kernel: [ 3102.272000] ieee80211: 802.11 data/management/control stack, git-1.1.13
Apr 24 22:31:03 localhost kernel: [ 3102.272000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <email address hidden>
Apr 24 22:31:04 localhost kernel: [ 3102.500000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmprq
Apr 24 22:31:04 localhost kernel: [ 3102.500000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
Apr 24 22:31:04 localhost kernel: [ 3102.504000] ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 20 (level, low) -> IRQ 18
Apr 24 22:31:04 localhost kernel: [ 3102.504000] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Apr 24 22:31:04 localhost kernel: [ 3102.800000] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
Apr 24 22:31:09 localhost gnome-power-manager: (nixblicker) DBUS timed out, but recovering
Apr 24 22:31:09 localhost gnome-power-manager: (nixblicker) Rechner wird aufgeweckt
Apr 24 22:31:10 localhost kernel: [ 3109.204000] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level, low) -> IRQ 18
Apr 24 22:31:11 localhost kernel: [ 3109.964000] input: Power Button (FF) as /class/input/input7
Apr 24 22:31:11 localhost kernel: [ 3109.964000] ACPI: Power Button (FF) [PWRF]
Apr 24 22:31:11 localhost kernel: [ 3109.964000] input: Lid Switch as /class/input/input8
Apr 24 22:31:11 localhost kernel: [ 3109.964000] ACPI: Lid Switch [LID0]
Apr 24 22:31:11 localhost kernel: [ 3109.964000] input: Power Button (CM) as /class/input/input9
Apr 24 22:31:11 localhost kernel: [ 3109.964000] ACPI: Power Button (CM) [PWRB]
Apr 24 22:31:11 localhost kernel: [ 3109.964000] input: Sleep Button (CM) as /class/input/input10
Apr 24 22:31:11 localhost kernel: [ 3109.964000] ACPI: Sleep Button (CM) [SLPB]
Apr 24 22:31:12 localhost kernel: [ 3111.060000] ACPI: Transitioning device [FAN1] to D3
Apr 24 22:31:12 localhost kernel: [ 3111.060000] ACPI: Transitioning device [FAN1] to D3
Apr 24 22:31:12 localhost kernel: [ 3111.060000] ACPI: Fan [FAN1] (off)
Apr 24 22:31:12 localhost kernel: [ 3111.096000] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3])
Apr 24 22:31:12 localhost kernel: [ 3111.096000] ACPI: Processor [CPU0] (supports 2 throttling states)
Apr 24 22:31:12 localhost kernel: [ 3111.104000] ACPI: Thermal Zone [THRM] (50 C)
Apr 24 22:31:12 localhost kernel: [ 3111.176000] ACPI: AC Adapter [ADP1] (off-line)
Apr 24 22:31:12 localhost kernel: [ 3111.212000] ACPI: Battery Slot [BAT1] (battery present)
Apr 24 22:31:13 localhost kernel: [ 3111.420000] ADDRCONF(NETDEV_UP): eth1: link is not ready
Apr 24 22:31:13 localhost kernel: [ 3111.588000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 24 22:31:13 localhost kernel: [ 3111.880000] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Apr 24 22:31:13 localhost kernel: [ 3111.940000] VFS: busy inodes on changed media.
Apr 24 22:31:13 localhost kernel: [ 3111.948000] VFS: busy inodes on changed media.
Apr 24 22:32:07 localhost gnome-power-manager: (nixblicker) Rechner wird in Bereitschaft versetzt da Bereitschaftstaste wurde gedrückt
Apr 24 22:32:09 localhost kernel: [ 3167.484000] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
Apr 24 22:32:09 localhost kernel: [ 3167.552000] ACPI: PCI interrupt for device 0000:02:09.2 disabled
Apr 24 22:32:09 localhost kernel: [ 3167.608000] ACPI: PCI interrupt for device 0000:02:05.0 disabled
Apr 24 22:32:09 localhost kernel: [ 3167.664000] ACPI: PCI interrupt for device 0000:02:07.0 disabled
Apr 24 22:34:15 localhost syslogd 1.4.1#20ubuntu4: restart.

[Christopher Hübner (huebnerc)]

With the old kernel 2.6.17-11-386 suspend works without problems.

[Christopher Hübner (huebnerc)]

With the old kernel 2.6.17-11-386 suspend works without problems.

[Konrad Hofer (konrad.hofer)]

Hi,

I have a Samsung X20 and I get the same error.

konrad

[Torsten Spindler (tspindler)]

I can reproduce this problem on an IBM Thinkpad T40p. Following the kernel suspend debugging procedure described at https://wiki.ubuntu.com/DebuggingKernelSuspend the only entry in dmesg is
[ 6.344073] ACPI: (supports S0 S3 S4 S5)
[ 6.344126] Magic number: 0:798:917
[ 6.344128] hash matches drivers/base/power/resume.c:46
See the attached dmesg.txt for full details.

[Torsten Spindler (tspindler)]

$ cat /proc/version_signature
Ubuntu 2.6.20-15.27-generic

[Torsten Spindler (tspindler)]

With the kernel option acpi_sleep=s3_bios the boot stops with the attached image. The line
ata1.00: revalidation failed (errno=-19)
may point to the problem.

[Torsten Spindler (tspindler)]

I tried the suspend/resume cycle with the older 2.6.20-14 kernel and it works fine there.

[gmayer (gunther-mayer)]

I'm on a Samsung Q35 and I can confirm this bug :-(

Of course there's nothing in my syslog because it can't write to disk in the first place...

[Brett Clippingdale (brett-clippingdale)]

this seems like a duplicate of bug# 106410:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/106410

[Brett Clippingdale (brett-clippingdale)]

After more research, this seems like a duplicate of an even earlier bug, bug# 99267:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/99267

[Chris (poser)]

Hi all,

(Copied from my post to bug 109403)

System:
- Thinkpad T41p (2373-GEU)
- ATI FireGL T2 (128 MB)
- Ubuntu Feisty with fresh-from-ATI fglrx module 8.36.5 and XGL/Beryl
- uname -a output: "Linux chibacityblues 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux"
- fglrxinfo output:
    display: :0.0 screen: 0
    OpenGL vendor string: ATI Technologies Inc.
    OpenGL renderer string: ATI MOBILITY FIRE GL T2/T2e
    OpenGL version string: 2.0.6458 (8.36.5)
- dmesg debugging output as per (https://wiki.ubuntu.com/DebuggingKernelSuspend)
    [ 5.605629] ACPI: (supports S0 S3 S4 S5)
    [ 5.605678] Magic number: 0:798:685
    [ 5.605681] hash matches drivers/base/power/resume.c:46
- dmesg debugging output from previous run
    [ 9.020266] ACPI: (supports S0 S3 S4 S5)
    [ 9.020314] Magic number: 0:901:786
    [ 9.020446] hash matches device ptyq8
- lspci -vvnn output attached above

Symptoms:
- Resume after suspend results in a blank screen. The Sleep light blinks continually (I think; this symptom is intermittent, actually...). Switching consoles reveals SCSI "dead I/O device" errors. Switching back to tty7 doesn't help.
- Hibernate works fine

Details:
- I experienced the same behavior with the official Apt version of fglrx
- I experienced the same behavior before switching over to this XGL/Beryl nonsense
- I've tried all combinations of the SAVE_VBE_STATE, POST_VIDEO, USE_DPMS, and DOUBLE_CONSOLE_SWITCH options in /etc/default/acpi-support
- I have "fglrx" in my /etc/default/acpi-support MODULES_WHITELIST
- I have tried with and without the "pci=noacpi" option in /boot/grub/menu.lst. I have no idea what that does. Monkey see; monkey do. :)
- I do not have an explicit "resume" line in /boot/grub/menu.lst; It seems to figure things out for itself
- I stop powernowd before suspend and start it after resume (using /etc/acpi/suspend.d/10-thinkpad-standby-led.sh and /etc/acpi/resume.d/90-thinkpad-unstandby-led.sh)
- In response to Torsten's question, I do have "00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01) (prog-if 8a [Master SecP PriP])" in my lspci -vvnn
- I _also_ have the SCSI "dead I/O device" errors. Switching to tty8 during a failed resume reveals this error message.
- Also, while using the debugging method to suspend/resume, I was able to restore my session on tty7, but had no access to the drive (placeholder icons, just like Sebastian...)
- Root partition is /dev/sda3. It is a non-SATA (and, of course, non-SCSI) 60 GB 7200 rpm IDE drive that was identified as SCSI during a clean Feisty installation. (Is this typical, now?)

Thanks all,
-Chris

(posted under bug 109403 as well)

[James Muscat (james-muscat)]

I have the same issue on a ThinkPad T41. Suspend-to-disk works fine, suspend-to-RAM has "rejecting dead device" errors on resume. I can't even get mine suspend/resuming once though...

ACPI: (supports S0 S3 S4 S5)
Magic number: 7:905:185
hash matches device 0000:02:01.0

lspci | grep 02:01.0 points to the ethernet controller (Intel 82540EP Gigabit Ethernet Controller (Mobile) rev 03)

Using 2.6.20-15-generic kernel.

[Chris (poser)]

Hi again,

Just to clarify, I never managed a successful suspend/resume either (though it sounds like the original poster did). I have the same Ethernet controller, though I have yet to see it show up as the "hash matches" culprit. If I start a 'tail -f /var/log/syslog', then suspend using the '/etc/acpi/sleep.sh force', I can see a fair bit of additional information in the terminal when it "resumes" (even though it no longer has a hard drive...). Doing this revealed...

ata1.00: n_sectors mismatch 117210240 != 110302575
ata1.00: revalidation failed (errno=-19)
ata1.00: limiting speed UDMA/100:PIO3
ata1: failed to recover some devices, retrying in 5 secs

...and, 5 secs later...

ata1: soft resetting port
ata1.00: n_sectors mismatch 117210240 != 110302575
ata1.00: revalidation failed (errno=-19)
ata1.00: disabled
sd 0:0:0:0: rejecting I/O to offline devices
sd 0:0:0:0: SCSI error: return code=0x00010000
end-request: I/O error, dev sda, sector 47716685

I will repost to bug 109403 as well

Thanks,
-Chris

[Felix Hagemann (flixh)]

Hi,
I can confirm this bug on my Samsung X20. Resuming from suspend-to-ram works the
first time, while the second time X comes up but freezes completely after approx. 20s.
In the first 2-3s after X comes up again I am able to run commands (i.e. start top in a
Konsole session) but then every attempt to run something ends with an error message
like "bash: /bin/ls: No such file or directory" and some seconds later the system freezes
and can only be restarted by power-cycling.

As bugs 106410 and 99267 mainly seem to be related to USB not coming up after resume
I doubt that this bug is a duplicate of those.

The system:
Kubuntu Freisty upgraded from Edgy. suspend worked fine with Edgy.
$ uname -a
Linux silver 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

This:

$ lspci -vv | grep 00:1f.1
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])

might indicate that the problem here is similar to (or the same as) bug 109403.

The syslog does not contain anything concernig the crash, probably because it cannot be
written to disk.

I hope somebody has an idea how to fix this,
Felix

[ralle but (rbutenuth)]

Hi,

I can confirm this bug on an Samsung X11. It's the same behaviour as Felix described.

lspci -vv | grep 00:1f.1 says:

00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) (prog-if 8a [Master SecP PriP])

uname -a says:
Linux ralf-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Yours, Ralf

[ralle but (rbutenuth)]

Upgrading to Kernel 2.6.20-16 fixed the problem for me.

Yours, Ralf

[Christopher Hübner (huebnerc)]

The new Kernel 2.6.20-16 fixed the problem for me too.

[Chris (poser)]

Me too. (Thinkpad t41p)

[Torsten Spindler (tspindler)]

Fix released according to bug reporter in 2.6.20-16.

[Konrad Hofer (konrad.hofer)]

ralle but wrote:
> Upgrading to Kernel 2.6.20-16 fixed the problem for me.
>
> Yours, Ralf
>
Yes, also for me!!

Good work!

thanks.

cheers, konrad

[Christopher Hübner (huebnerc)]

With the latest security fix, the problem reappeared. :-(

[ralle but (rbutenuth)]

I can confirm this. On my machine (Samsung X11 T2300) the problem also reappeared with upgrade to linux-image-2.6.20-16-generic_2.6.20-16.29_i386.deb

[Christopher Hübner (huebnerc)]

Is anybody able to change the status from "Fix Released" to something more accurate? Seems that the fix has been thrown away with the latest security fixes. And the importance should be changed too. Or am I the only one who thinks, that this should not only be on the wishlist? "Medium" would be adequaete, as especially notebooks use suspend modes very often.

[Torsten Spindler (tspindler)]

On the above mentioned T40p the problem reappears with the 2.6.20-16.29-generic as well.

[Amit Kucheria (amitk)]

Could somebody confirm if this bug still exists with 2.6.22 (Gutsy Tribe 1 CD)?

[Torsten Spindler (tspindler)]

The bug does not occur with gutsy tribe 1 anymore, suspend to ram and resume works fine there.

[Torsten Spindler (tspindler)]

The bug seems to be related on using the ata_piix module instead of piix. The use of the module for the ICH4-M controller did change in recent kernel upgrades.

[ralle but (rbutenuth)]

Thanks Torsten.

It would be great if you can be more specific on how a work-around for Feisty works:

Do you suggest to use the module piix instead of ata_piix (both modules are in /lib/modules/2.6.20-16-generic/kernel/drivers on my system). And if yes: How can i tell the system to load the other module, and do i have to change other things to?

Or do you suggest updating to kernel 2.6.22. If yes: How can this be done on Feisty.

Yours, Ralle

[gmayer (gunther-mayer)]

I can confirm that the last security update made the problem reappear on my Samsung Q35 too :-(

I'm now running linux-generic 2.6.20.16.28.1, the previous 2.6.20.16 worked fine. Anyone know how to downgrade?

[Konrad Hofer (konrad.hofer)]

The same is true for my Samsung X20. Any news on this?

[Konrad Hofer (konrad.hofer)]

Ok, this is what I did on my Samsung X20 (found http://ubuntuforums.org/showthread.php?t=472650&highlight=suspend+samsung)

Add piix module to initial ram disk:

   sudo vi /etc/initramfs-tools/modules

add piix at the bottom

Save

Update the initrd image:

   sudo update-initramfs -u

Next check if if you have any sdaX devices in /etc/fstab, change them to hdaX.
I have none, using UUID.

Reboot and Enjoy like I do!!!

[ashikase (ashikase)]

Switching to the piix module fixed the problem for my Panasonic Let's Note R4.

(thanks konrad)

[Konrad Hofer (konrad.hofer)]

Anyone experienced this kind of problems with the latest security kernel
updates? kernel 2.6.20-16.31

thanks

konrad

ashikase wrote:
> Switching to the piix module fixed the problem for my Panasonic Let's
> Note R4.
>
> (thanks konrad)
>

[c_t (chefturner)]

For me, unfortunately, the problem is still there in kernel 2.6.20-16.31 (Samsung X20 WVC1730) ... Only replacing ata_piix with piix-module works at the moment (thanks by the way).

Christoph

[Vaxius (thegeeker)]

Running Ubuntu 7.04 with kernel 2.6.20-16.31 on HP Pavilion dv2116wm has same "rejecting I/O to dead device" error for sda after trying konrad's fix. (fstab is using UUID).

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.