Regression Sata hard disk unable to mount after upgrade 2.6.27 generic kernel

[Marcos]

Description: Ubuntu intrepid (development branch)
Release: 8.10

After Intrepid beta clean installation every thing worked fine. I made the last updates. From kernel 2.6.27-4-generic to 2.6.27-6-generic now I can't boot because my second serial ata hard disk ( Maxtor 6V250F0) fails to mount in /media/sdb1 on start up.

After remove this sdb from fstab I could start.

But If I want to mount this device I have the same kernel error and I cant access to this harddisk.

The kernel log is:

ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 7 17:49:59 deflagmator kernel: [ 86.604091] ata4.00: cmd ca/00:08:fc:86:bb/00:00:00:00:00/e0 tag 0 dma 4096 out
Oct 7 17:49:59 deflagmator kernel: [ 86.604094] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 7 17:49:59 deflagmator kernel: [ 86.604101] ata4.00: status: { DRDY }
Oct 7 17:49:59 deflagmator kernel: [ 86.604113] ata4: hard resetting link
Oct 7 17:50:00 deflagmator kernel: [ 87.080072] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 7 17:50:00 deflagmator kernel: [ 87.105231] ata4.00: configured for UDMA/133
Oct 7 17:50:00 deflagmator kernel: [ 87.105262] ata4: EH complete

I tried to change the jumper to 1,5 GB instead to 3GB and every works fine.

I think is an error in this last update.
THIS COULD HELP . Yesterday I tried debian lenny. (clean installation) after the upgrade with last kernel available I also have the same problem.

Maybe is an incompatibility with this Maxtor hard disk.

[Robert Hrovat (robi-hipnos)]

Same here. It started with 2.6.27-5. It kicks me in busybox. Attached is a photo of errors with *-5.

[Robert Hrovat (robi-hipnos)]

Attaching better photo with boot process. Nothing new with latest updates as of today.

[Vwracer69 (vwracer)]

i had the same problem, try changing your bios from "AHCI" to "IDE". worked for me.

[Robert Hrovat (robi-hipnos)]

I don't think this is a good solution when kernels before *-5 works just fine. It's linux we're talking about, not windows where you have to hack bios or use floppy just to install it :-)

[Vwracer69 (vwracer)]

I was just trying to help. that solution worked for me. might also help people look in the right direction when trying to find a solution for this so called bug.

[Robert Hrovat (robi-hipnos)]

I know, but since my BIOS - and many others - doesn't have this option. This option comes with newer motherboards as a workaround for floppyless windows install.

Your solution might be a workaround but I still think this is a bug. I'm using same machine with ubuntu for more than 2 years and all kernels before *-5 worked fine.

[douham (dougg)]

i had a problem where could'nt boot into 27-6 until I changed my bios from IDE to AHCI (Vwracer, i had the same problem, try changing your bios from "AHCI" to "IDE". worked for me.)
Is it possible that if the drives on any particular machine are not set spot on, 27-6 is quite sensitive.

[Marcos (deflagmator)]

I'm also sure that this is a bug. My machine with the same hardware worked perfect for 2 years with all past Ubuntu versions. Only this last 2.6.27-6 kernel can't use this hard disk.
I normally use this hard disk as secondary SATA drive. If I use only this hard disk as primary SATA drive the system still has the problem. It's not a problem to use one or two hard disk.
I think this can help. If I change the jumper in the hard disk from 3GB/s to 1,5GB/s the system runs perfectly. As I tell before the problem is also present in last Debian Lenny kernel.

[Marcos (deflagmator)]

Latest upgrade to kernel 2.6.27-7-generic still the same. :-)

[Robert Hrovat (robi-hipnos)]

Yep. I can confirm it too. It's quite annoying and now even last sucessfull boot does not work. It exits with message "no file found", so I have to select *-4 entry below.

[Marcos (deflagmator)]

I found this Bug #285892 seems the same problem

[Robert Hrovat (robi-hipnos)]

I guess this one will not be fixed in intrepid. So we, who use that particular nvidia chipset won't be able to use intrepid???

[Jason Bodycott (jbodycott)]

exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

I have the same problem on my computer (for me this is NOT with an nForce chipset but rather a Highpoint 37x RAID controller and a VIA chipset and with IDE HDDs instead of SATA) and this makes 2.6.27-5+ unusable.

Binaries for 2.6.27-4 don't seem to be around anymore so I'm stuck using 2.6.24-21 (I have no desire to recompile from source with a perfectly good laptop). If anyone knows of a repository with that around, I'd be happy to verify 2.6.27-4.

Hardware errors are ruled out as older kernels work perfect and Windows runs just fine on the same box. I really hope we can get this one fixed before Jaunty.

[Jason Bodycott (jbodycott)]

Per Leann's comment on another thread with a vaguely similar issue, I'm trying the proposed 2.6.27-11 kernel right now from the intrepid-proposed repository. So far I'm 15 minutes uptime and I've survived checking my email, browsing the web and a full disk ls -laR (which generally killed the system in the past), not to mention this post ;) I'll keep updated but thus far 2.6.27-11 looks promising.

Note: The bug with the update comment was one I stumbled across troubleshooting an unrelated RT kernel issue here - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/236335

[Jason Bodycott (jbodycott)]

Sadly, 2.6.27-11 met the same fate today after several days of use and is now actually worse. I consistently fail to boot and don't even make it past the splash screen anymore. Back to 2.6.24-21 (where I write this) which is rock solid.

[Jaime R. Garza (garzaj)]

I have the same problem using Intrepid on amd64, but only with one of my disks, I have three disks, all in the same system, two work perfectly well and one cannot be mounted. They are all resierfs, so I checked the disk with "fsck.resierfs /dev/sdc1" and it takes toooo long but finally says is fine. The problem is that I get:

Jan 21 17:29:59 deflagmator kernel: [ 86.604101] ata4.00: status: { DRDY }
Jan 21 17:29:59 deflagmator kernel: [ 86.604113] ata4: hard resetting link
Jan 21 17:30:00 deflagmator kernel: [ 87.080072] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 21 17:30:00 deflagmator kernel: [ 87.105231] ata4.00: configured for UDMA/33
Jan 21 17:30:00 deflagmator kernel: [ 87.105262] ata4: EH complete

This problem has nothing to do with the chipset as many implied, I changed cables, moved all three disks around and only one disk failed, the problem is the Harddisk:

Maxtor DiamondMax 10
Model:6V250F0
250GB SATA 3.0Gb HDD

My other two disks are also SATA, one Seagate Baracuda 500GB and one Hitachi 164GB, both work perfectly well on the same system.

I noticed using Hardy, this problem will come, but only with soft restart. If I turned the computer completely off, this problem didn't happen on Hardy.

Cheers!

[Kow (kow)]

Still occurring with 2.6.28.3 kernel. This bug looks to survive into jaunty... :(

[ 6921.701044] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 6921.701055] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 6921.701056] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 6921.701060] ata2.00: status: { DRDY }
[ 6926.750018] ata2: link is slow to respond, please be patient (ready=0)
[ 6931.340029] ata2: soft resetting link
[ 6931.518620] ata2.00: configured for UDMA/100
[ 6931.518654] ata2: EH complete
[ 6931.525401] end_request: I/O error, dev sda, sector 42465893
[ 6931.525489] Aborting journal on device sda2:8.
[ 6931.533627] journal commit I/O error
[ 6932.090234] sd 1:0:0:0: [sda] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
[ 6932.090994] sd 1:0:0:0: [sda] Write Protect is off
[ 6932.090997] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 6932.101519] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 6932.312973] ext4_abort called.
[ 6932.312979] EXT4-fs error (device sda2): ext4_journal_start_sb: Detected aborted journal
[ 6932.312983] Remounting filesystem read-only
[ 6932.385750] EXT4-fs error (device sda2) in ext4_reserve_inode_write: Journal has aborted

The ext4 portion is ext4 doing exactly what it should be in the event of a catastrophic error... unmounting and remounting ro.

[Francisco (franjesus)]

I have the same problem (sort of) with intrepid, kernel 2.6.27-11-generic. It freezes for about 10 seconds, then does a hardreset and goes on without any further problem. I was worried that it might be a hardware problem, so I even changed the hard drive. The problem still persists.

For what is worth, my hdd controller is not nVidia:

00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)

[ 67.804085] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 67.804102] ata1.00: cmd c8/00:80:d9:dd:3e/00:00:00:00:00/e5 tag 0 dma 65536 in
[ 67.804105] res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 67.804110] ata1.00: status: { DRDY }
[ 72.844046] ata1: link is slow to respond, please be patient (ready=0)
[ 77.828050] ata1: device not ready (errno=-16), forcing hardreset
[ 77.828066] ata1: soft resetting link
[ 78.010230] ata1.00: configured for UDMA/133
[ 78.010246] ata1: EH complete
[ 78.033587] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
[ 78.033628] sd 0:0:0:0: [sda] Write Protect is off
[ 78.033634] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 78.033689] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[Lukasz Wisniewski (vishna)]

same problem here, ubuntu 8.10 (Linux 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux) this is a really annoying bug, freezes access to disk for half a minute, causing for example music stoping to play, preventing launching new applications... though for instance i am able to switch between windows or scroll the already opened web page in the firefox - this MUST be fixed before 9.04

[ 1501.742285] ata1.00: limiting speed to PIO4
[ 1501.742293] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 1501.742298] ata1.00: BMDMA stat 0x64
[ 1501.742306] ata1.00: cmd ca/00:08:0f:1f:5e/00:00:00:00:00/e0 tag 0 dma 4096 out
[ 1501.742308] res 58/00:08:0f:1f:5e/00:00:00:00:00/e0 Emask 0x2 (HSM violation)
[ 1501.742312] ata1.00: status: { DRDY DRQ }
[ 1501.742346] ata1: soft resetting link
[ 1502.024662] ata1.00: configured for PIO4
[ 1502.024686] ata1: EH complete
[ 1502.029996] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1502.036702] sd 0:0:0:0: [sda] 78140160 512-byte hardware sectors (40008 MB)
[ 1502.083210] sd 0:0:0:0: [sda] Write Protect is off
[ 1502.083220] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1502.089234] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[Covi (j.a.cobo)]

Same problem (think from Gutsy): multierrors on system disk and corrupt GRUB with Windows.
With LiveCD -no writing on disk- only an startup notice:
[ 4.304263] Driver 'sd' needs updating - please use bus_type methods
[ 4.304389] sd 2:0:0:0: [sda] 78165360 512-byte hardware sectors (40021 MB)
[ 4.304408] sd 2:0:0:0: [sda] Write Protect is off
[ 4.304436] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4.304501] sd 2:0:0:0: [sda] 78165360 512-byte hardware sectors (40021 MB)
[ 4.304514] sd 2:0:0:0: [sda] Write Protect is off
[ 4.304539] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4.304543] sda:<4>Driver 'sr' needs updating - please use bus_type methods
[ 4.318120] sda1 sda2 < sda5 sda6 >
[ 4.360453] sd 2:0:0:0: [sda] Attached SCSI disk

---
2.6.27-7-generic
AMD Athloon x64 3200+
A8VX
Seagate 40G (another SeaGgate 80G with problems too).

...I hope Jaunty can be fix this finally :(

[Annika (annika-kremer)]

I'm getting the same problem with a Samsung Spinpoint 160 GB SATA harddisk on Kubuntu 8.10, 64 Bit edition. Sometimes it's just a small lag, sometimes my computer completely freezes when I come across this. Exact error log looks like this:

Mar 10 19:06:01 shadowfax kernel: [14205.249536] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Mar 10 19:06:01 shadowfax kernel: [14205.249549] ata1.01: cmd a0/00:00:00:04:00/00:00:00:00:00/b0 tag 0 pio 16388 in
Mar 10 19:06:01 shadowfax kernel: [14205.249550] cdb 43 00 05 00 00 00 00 00 04 00 00 00 00 00 00 00
Mar 10 19:06:01 shadowfax kernel: [14205.249551] res 40/00:02:00:ec:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
Mar 10 19:06:01 shadowfax kernel: [14205.249554] ata1.01: status: { DRDY }
Mar 10 19:06:02 shadowfax kernel: [14206.425032] ata1: soft resetting link
Mar 10 19:06:02 shadowfax kernel: [14206.617383] ata1.01: configured for UDMA/33
Mar 10 19:06:02 shadowfax kernel: [14206.617411] ata1: EH complete

[Lukasz Wisniewski (vishna)]

installing linux-rt kernel solved my problem, the latest available version is 2.6.27-3 so less then -5 where problems start.

This is only a workaround (suggested here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/236335/comments/1) yet a good one since I don't have the IDE option in my BIOS.

[Gonzhauser (gonzhauser)]

This crashed my Ubuntu (Jaunty)! :(

First there were hangs of 5 seconds, yesterday I was unable to boot with grub.
Windows works fine on the same disk.

[Annika (annika-kremer)]

I don't seem to have this problem under Jaunty. Thought it was fixed, but reading the last posting, that doesn't appear to be the case. Therefore I assume that the reason I don't have problems is simply that I did a clean reinstall instead of a dist-upgrade and got lucky. Apparently, the occurence of this bug is really completely random, since the hardware is of course completely the same as before.

[kernel-janitor (kernel-janitor)]

Hi Marcos,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/karmic .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 279693

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[James Howison (james-howison)]

I believe I have a related issue. I installed server from Jaunty alternative CD, creating two partitions on each of two disks (one swap, one everything else), I then built a RAID1 arrangement. Right from the start I saw similar errors on /dev/sda, if the RAID is working then that disk is eventually faulted out of both /dev/md devices. If I pull the other disk (/dev/sdb) then the RAID tries to continue but this same error occurs and the file system mounts r/o.

The most recent error I saw is in the attachment, it starts with:

Sep 9 20:24:33 conway2 kernel: [23146.732090] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 9 20:24:34 conway2 kernel: [23146.732185] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Sep 9 20:24:34 conway2 kernel: [23146.732188] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 9 20:24:34 conway2 kernel: [23146.732319] ata1.00: status: { DRDY }
Sep 9 20:24:34 conway2 kernel: [23146.732371] ata1: hard resetting link
Sep 9 20:24:34 conway2 kernel: [23152.652048] ata1: link is slow to respond, please be patient (ready=-19)
Sep 9 20:24:34 conway2 kernel: [23156.740061] ata1: SRST failed (errno=-16)
Sep 9 20:24:34 conway2 kernel: [23156.740130] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep 9 20:24:34 conway2 kernel: [23161.740077] ata1.00: qc timeout (cmd 0xec)
Sep 9 20:24:34 conway2 kernel: [23161.740087] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x5)
Sep 9 20:24:34 conway2 kernel: [23161.740092] ata1.00: revalidation failed (errno=-5)

smartmon gives me:

jhowison@conway2:~$ sudo smartctl -a /dev/sda
[sudo] password for jhowison:
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

If I reboot, then the disk comes up ok, and the RAID begins to resync. At some point, usually a few hours later (there's almost no activity on this just installed server) it will die in the same way.

dmesg output for ata1 shows:

[ 1.831368] sata_nv 0000:00:05.0: version 3.5
[ 1.831696] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
[ 1.831706] sata_nv 0000:00:05.0: PCI INT A -> Link[LSA0] -> GSI 23 (level, l
ow) -> IRQ 23[ 1.831709] sata_nv 0000:00:05.0: Using SWNCQ mode
[ 1.831775] sata_nv 0000:00:05.0: setting latency timer to 64[ 1.831931] scsi0 : sata_nv
[ 1.832009] scsi1 : sata_nv
[ 1.832117] ata1: SATA max UDMA/133 cmd 0xd480 ctl 0xd400 bmdma 0xcc00 irq 23
[ 1.832120] ata2: SATA max UDMA/133 cmd 0xd080 ctl 0xd000 bmdma 0xcc08 irq 23[ 2.712051] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.746186] ata1.00: ATA-8: ST31000528AS, CC34, max UDMA/133[ 2.746189] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 2.802201] ata1.00: configured for UDMA/133

...

[ 3.770300] scsi 0:0:0:0: Direct-Access ATA ST31000528AS CC34 PQ
: 0 ANSI: 5
[ 3.770375] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/
931 GiB)[ 3.770388] sd 0:0:0:0: [sda] Write...

[giorgio_fornara (giorgio-fornara)]

I have same freezes when access to disk.
All operations needings acces to disk are temporary freezed.
karmic 9.10
Linux 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009.

Dec 21 15:10:12 my2912071352 kernel: [24380.365200] ata1.01: qc timeout (cmd 0xa0)
Dec 21 15:10:12 my2912071352 kernel: [24380.365222] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 21 15:10:12 my2912071352 kernel: [24380.365243] ata1.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0
Dec 21 15:10:12 my2912071352 kernel: [24380.365246] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dec 21 15:10:12 my2912071352 kernel: [24380.365249] res 51/20:03:00:00:00/00:00:00:00:00/b0 Emask 0x5 (timeout)
Dec 21 15:10:12 my2912071352 kernel: [24380.365256] ata1.01: status: { DRDY ERR }
Dec 21 15:10:17 my2912071352 kernel: [24385.408044] ata1: link is slow to respond, please be patient (ready=0)
Dec 21 15:10:22 my2912071352 kernel: [24390.393048] ata1: device not ready (errno=-16), forcing hardreset
Dec 21 15:10:22 my2912071352 kernel: [24390.393064] ata1: soft resetting link
Dec 21 15:10:22 my2912071352 kernel: [24390.656494] ata1.00: configured for UDMA/100
Dec 21 15:10:22 my2912071352 kernel: [24390.695598] ata1.01: configured for PIO0
Dec 21 15:10:22 my2912071352 kernel: [24390.704463] ata1: EH complete

[giorgio_fornara (giorgio-fornara)]

I installed linux-rt kernel, the bug still remains.
2.6.31-17-generic

[giorgio_fornara (giorgio-fornara)]

I confirm also with linux-rt the bug still remains.
The frequency is less than with -generic, but still appears.
syslog below.

Dec 22 19:55:07 my2912071352 kernel: [ 752.997361] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 22 19:55:07 my2912071352 kernel: [ 752.997385] ata1.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0
Dec 22 19:55:07 my2912071352 kernel: [ 752.997388] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dec 22 19:55:07 my2912071352 kernel: [ 752.997391] res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
Dec 22 19:55:07 my2912071352 kernel: [ 752.997398] ata1.01: status: { DRDY }
Dec 22 19:55:12 my2912071352 kernel: [ 758.047278] ata1: link is slow to respond, please be patient (ready=0)
Dec 22 19:55:17 my2912071352 kernel: [ 763.045278] ata1: device not ready (errno=-16), forcing hardreset
Dec 22 19:55:17 my2912071352 kernel: [ 763.045294] ata1: soft resetting link
Dec 22 19:55:17 my2912071352 kernel: [ 763.295740] ata1.00: configured for UDMA/100
Dec 22 19:55:17 my2912071352 kernel: [ 763.336566] ata1.01: configured for UDMA/33
Dec 22 19:55:17 my2912071352 kernel: [ 763.339693] ata1: EH complete

[giorgio_fornara (giorgio-fornara)]

with today's last update the laptop is not more experiencing HD freezes,
maybe a temporary good combination between kernel and other modules.
Anyway NO kernel update as occoured since last bugs, only other modules updates.
hope still stable...

[giorgio_fornara (giorgio-fornara)]

freezes continues....
a very stupid possible solution is to leave a CD in the CD reader: seems to works, no freezes occurs after.
I saw this idea on another post on the same issue.
but why? does this information doesn't give any clues to developers?

[giorgio_fornara (giorgio-fornara)]

upgraded to Linux version 2.6.31-20-generic.
Freezes ATA continues.
Workaround with "inserted CD" continues.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]