[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I can confirm this bug on my Dell Vostro 1710 running Jaunty
(2.6.28-11-{generic,server}).
It occurs only once on every boot, when GDM starts (and thus does its
prefetch), provoking a ~30s blank screen with heavy disk activity before the
login screen.
[ 80.040094] ata1.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6
frozen
[ 80.040106] ata1.00: cmd 60/88:00:25:76:72/00:00:08:00:00/40 tag 0 ncq 69632
in
[ 80.040107] res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 80.040112] ata1.00: status: { DRDY }
[ 80.040118] ata1.00: cmd 60/08:08:7d:63:d4/00:00:07:00:00/40 tag 1 ncq 4096
in
[ 80.040120] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040124] ata1.00: status: { DRDY }
[ 80.040130] ata1.00: cmd 60/08:10:8d:cb:81/00:00:07:00:00/40 tag 2 ncq 4096
in
[ 80.040132] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040136] ata1.00: status: { DRDY }
[ 80.040142] ata1.00: cmd 61/08:18:b5:64:f8/00:00:07:00:00/40 tag 3 ncq 4096
out
[ 80.040144] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040147] ata1.00: status: { DRDY }
[ 80.040153] ata1.00: cmd 61/08:20:45:e1:f8/00:00:07:00:00/40 tag 4 ncq 4096
out
[ 80.040155] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040159] ata1.00: status: { DRDY }
[ 80.040165] ata1.00: cmd 61/08:28:ad:d4:f9/00:00:07:00:00/40 tag 5 ncq 4096
out
[ 80.040167] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040171] ata1.00: status: { DRDY }
[ 80.040177] ata1.00: cmd 61/08:30:c5:58:fc/00:00:07:00:00/40 tag 6 ncq 4096
out
[ 80.040178] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040188] ata1.00: status: { DRDY }
[ 80.040191] ata1.00: cmd 61/18:38:4d:e1:f8/00:00:07:00:00/40 tag 7 ncq 12288
out
[ 80.040192] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040193] ata1.00: status: { DRDY }
[ 80.040196] ata1.00: cmd 61/10:40:25:fa:f6/00:00:07:00:00/40 tag 8 ncq 8192
out
[ 80.040197] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040199] ata1.00: status: { DRDY }
[ 80.040201] ata1.00: cmd 61/10:48:45:fa:f6/00:00:07:00:00/40 tag 9 ncq 8192
out
[ 80.040202] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040204] ata1.00: status: { DRDY }
[ 80.040207] ata1.00: cmd 61/08:50:5d:fa:f6/00:00:07:00:00/40 tag 10 ncq 4096
out
[ 80.040208] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040210] ata1.00: status: { DRDY }
[ 80.040212] ata1.00: cmd 61/08:58:6d:fa:f6/00:00:07:00:00/40 tag 11 ncq 4096
out
[ 80.040213] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040215] ata1.00: status: { DRDY }
[ 80.040218] ata1.00: cmd 61/08:60:85:fa:f6/00:00:07:00:00/40 tag 12 ncq 4096
out
[ 80.040218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040220] ata1.00: status: { DRDY }
[ 80.040223] ata1.00: cmd 61/28:68:dd:20:f7/00:00:07:00:00/40 tag 13 ncq
20480 out
[ 80.040224] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040226] ata1.00: status: { DRDY }
[ 80.040228] ata1.00: cmd 61/08:70:0d:21:f7/00:00:07:00:00/40 tag 14 ncq 4096
out
[ 80.040229] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040231] ata1.00: status: { DRDY }
[ 80.040234] ata1.00: cmd 61/08:78:fd:44:d3/00:00:07:00:00/40 tag 15 ncq 4096
out
[ 80.040235] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040236] ata1.00: status: { DRDY }
[ 80.040239] ata1.00: cmd 61/08:80:6d:1d:f8/00:00:07:00:00/40 tag 16 ncq 4096
out
[ 80.040240] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040242] ata1.00: status: { DRDY }
[ 80.040244] ata1.00: cmd 61/08:88:75:21:f8/00:00:07:00:00/40 tag 17 ncq 4096
out
[ 80.040245] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040247] ata1.00: status: { DRDY }
[ 80.040250] ata1.00: cmd 61/08:90:c5:b5:f8/00:00:07:00:00/40 tag 18 ncq 4096
out
[ 80.040251] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040252] ata1.00: status: { DRDY }
[ 80.040255] ata1.00: cmd 61/08:98:dd:21:f9/00:00:07:00:00/40 tag 19 ncq 4096
out
[ 80.040256] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040258] ata1.00: status: { DRDY }
[ 80.040260] ata1.00: cmd 61/10:a0:ed:f1:fa/00:00:07:00:00/40 tag 20 ncq 8192
out
[ 80.040261] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040263] ata1.00: status: { DRDY }
[ 80.040266] ata1.00: cmd 61/08:a8:bd:64:f8/00:00:07:00:00/40 tag 21 ncq 4096
out
[ 80.040266] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040268] ata1.00: status: { DRDY }
[ 80.040271] ata1.00
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
There seem to be multiple issues mixed into one report. The initial report shows problems on generic write commands without any NCQ. The ICH6 controller used seems to use the same PCI ID for both piix and ahci modes (according to the Jaunty code). The second one fails on DMA read/writes with NCQ involved (so might have a controller in ahci mode). @José, could you try to compare the behavior against the a recent mainline kernel https://wiki.ubuntu.com/KernelMainlineBuilds. Also, please supply "sudo lspci -vvvnnxxx" and the full dmesg from the boot. @Cedric, could you please open another bug report (with ubuntu-bug linux, so it gets automatic information attached). And if possible also compare the results with a recent mainline kernel. Maybe experiment with "libata.force=noncq" @ShinobiTeno, this is also a different controller. Have you tried to limit DMA speed with "libata.force=udma/66" to see whether this changes things? @Joachim, this definitely sounds like a different problem. Could you please open another report with "ubuntu-bug linux"? Thanks. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Just want to add the link to https://wiki.ubuntu.com/KernelTeam/Netconsole which I will also try myself since I might have the same problem (reported in bug 397096). -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I'll add a 'me too' to this one. Patched up jaunty sysytem used as a Mythtv box. System was fine with a 250GB Seagate Bara which failed. I replaced it with a new 1Tb seagate bara and now get these errors under heavy read load. 2.6.30 doesn't help - I got several errors while the Nvidia installer was running. Just moving through the recordings menu in Mythtv will trigger it - really any thing that generate high disk activity seems to. disk - ST31000528AS 00:1f.2 IDE interface [0101]: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller [8086:2651] (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Giga-byte Technology Device [1458:2651] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
** Summary changed:
- ata timeout exception with linux 2.6.28-11
+ ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
** Description changed:
Binary package hint: linux-image-2.6.28-11-generic
package: linux-image-2.6.28-11
release: Jaunty Beta
latest version tested: 2.6.28-11.38
Trying to boot the new 2.6.28-11 kernel on Jaunty Beta results in many
ata timeout errors (like the one copied below) that make the system
unusable. Sounds much more serious than
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343919, and
different, in as much as it is not an ext4 fs that I am aware of, it is
not an nvidia disk controller, and these errors are many more than ~10,
and trivially easy to reproduce (it happens every time, from the first
disk-reads onward)
dmesg error message:
[ 75.816051] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 75.816135] ata1.00: cmd ca/00:10:50:27:1e/00:00:00:00:00/e9 tag 0 dma
8192 out
[ 75.816137] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 75.816275] ata1.00: status: { DRDY }
[ 75.816337] ata1: hard resetting link
[ 76.804036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 76.806704] ata1.00: configured for UDMA/100
[ 76.806715] ata1: EH complete
- Note that booting 2.6.27 does not produce any disk error. smartctl
- reports no disk health problems, either.
+ Note that booting 2.6.27 does not produce any disk error. smartctl reports no
disk health problems, either.
+ [update] the bug is present in previouos versions too, and it only appears
when using the ahci dirver for libata (see lspci -vv output below).
lspci -vv for IDE controllers:
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Sony Corporation Device 81b9
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR-
Kernel driver in use: ata_piix
Kernel modules: ahci, ata_piix
--
ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
https://bugs.launchpad.net/bugs/352197
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I updated the bug desc and title to reflect new findings. The issue is definitely located in the AHCI driver, as per my previous comments, and it affects all kernels tested (2.6.27-* and 2.6.28-* on intrepid, jaunty beta, jaunty release and debian lenny up to now). The workaround i used works for 2.6.27 kernels, as ahci is loaded as a module and can be blacklisted in /etc/modprobe.d/blacklist. Unfortunately, 2.6.28 kernels in ubuntu (haven't tested with debian again) do not load ahci (or any libata driver, for that matter) as modules, but are now built-in into the kernel, so my workaround is useless. Any help on how to disable ahci when it's built in (ie, force the kernel to use ata_piix anyway) would be greatly appreciated. note that i do not have any intention of recompiling the kernel :) If you need more information, please let me know. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem here: ~$ uname -a Linux Mihai 2.6.28-12-server #43-Ubuntu SMP Fri May 1 20:28:32 UTC 2009 i686 GNU/Linux Luckily..if I boot the computer with a cd in the drive..then everything works... Otherwise no luck in reading anything. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem: Xubuntu 9.04, Asus A6Rp laptop, CoreDuoT2060, Hitachi HTS541080G9AT00 uname: 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux Hitachi > is a PATA drive< , lspci -vv reports: 00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80) (prog-if 8a [Master SecP PriP]) Subsystem: ASUSTeK Computer Inc. Device 1397 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Add: disk has undergone 48h load and performed long SMART test. SMART table shows no errors or bad/transfered sectors whatsoever. lspci -vv: http://nopaste.info/0dc0f76223.html dmesg : http://nopaste.info/3d69c55172.html hdparm -iI /dev/sda: http://nopaste.info/2667d93861.html smartctl --all /dev/sda: http://nopaste.info/1f78922cd0.html ** Attachment added: "lspci.txt" http://launchpadlibrarian.net/26872602/lspci.txt -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I had the same problem (SATA disk freezing), and I solved it by tunning the pdflush parameters ... https://bugs.launchpad.net/ubuntu/+bug/270794/comments/12 -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I have the same problem on an IDE DVD writer, it occurs when inserting some writable medium (doesnt occur with CD-ROM or DVD-ROM). After that, it is impossible to eject disk with "eject" command nor with device button. It could be related as the syslog is the same. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Another "me, too" for this bug. Ubuntu 9.04 64bit - SATA AHCI mode - ext4 fs WD Velociraptor (ext4fs: /, Swap, /Data) WD Caviar Black 1TB (ext4fs: /home) WD 640GB (ext4fs: /Backup) I recently built a new system using an EVGA 760 Classified MB, i7 920cpu, 12GB triple ch DDR3 and 300GB Velociraptor. I installed the OS after setting the BIOS to SATA AHCI mode (needed hot swapping capabilities). Everything worked fine for about 1 month until last night. I was doing a very large (200GB+) grsync backup of my /home partition to my WD640GB backup drive. At some point in the backup the system froze. No combination of keyboard tricks (ctl+alt+backspace, or alt+print screen+REISUB) would restart X or reboot the OS. I had to resort to killing power. On reboot, the one of my BIOS screens reported "Port 00:" during what I will call the AHCI check. The Velociraptor system drive would not boot. When, I went back into the BIOS setup, I saw that the BIOS did not even see the Velociraptor. I assumed the crash and hard power down had corrputed some critical system files. I removed the Velociraptor boot drive and replaced it with a WinXP 64 boot drive (also set for AHCI mode) and was able to boot up a Windows system with no problem. I then tested the Velociraptor with SpinRite 6 and its a good drive. I decided to try and reboot the Ubuntu system by changing the BIOS SATA setting to "IDE" mode. This worked. Ubuntu was able to start after it found a few errors on the / partition, corrected them, and finished booting. Ubuntu 9.04/64 now seems to be working fine in "IDE" mode. After reading through this thread, it seems that I have been bitten by this AHCI bug when I was doing the very large rsync file backup; although, I have to add that this wasn't the first time, I did such a large backup on this new system without problems. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Just want to add the link to https://wiki.ubuntu.com/KernelTeam/Netconsole which I will also try myself since I might have the same problem (reported in bug 397096). -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I'll add a 'me too' to this one. Patched up jaunty sysytem used as a Mythtv box. System was fine with a 250GB Seagate Bara which failed. I replaced it with a new 1Tb seagate bara and now get these errors under heavy read load. 2.6.30 doesn't help - I got several errors while the Nvidia installer was running. Just moving through the recordings menu in Mythtv will trigger it - really any thing that generate high disk activity seems to. disk - ST31000528AS 00:1f.2 IDE interface [0101]: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller [8086:2651] (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Giga-byte Technology Device [1458:2651] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I can confirm this bug on my Dell Vostro 1710 running Jaunty
(2.6.28-11-{generic,server}).
It occurs only once on every boot, when GDM starts (and thus does its
prefetch), provoking a ~30s blank screen with heavy disk activity before the
login screen.
[ 80.040094] ata1.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6
frozen
[ 80.040106] ata1.00: cmd 60/88:00:25:76:72/00:00:08:00:00/40 tag 0 ncq 69632
in
[ 80.040107] res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 80.040112] ata1.00: status: { DRDY }
[ 80.040118] ata1.00: cmd 60/08:08:7d:63:d4/00:00:07:00:00/40 tag 1 ncq 4096
in
[ 80.040120] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040124] ata1.00: status: { DRDY }
[ 80.040130] ata1.00: cmd 60/08:10:8d:cb:81/00:00:07:00:00/40 tag 2 ncq 4096
in
[ 80.040132] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040136] ata1.00: status: { DRDY }
[ 80.040142] ata1.00: cmd 61/08:18:b5:64:f8/00:00:07:00:00/40 tag 3 ncq 4096
out
[ 80.040144] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040147] ata1.00: status: { DRDY }
[ 80.040153] ata1.00: cmd 61/08:20:45:e1:f8/00:00:07:00:00/40 tag 4 ncq 4096
out
[ 80.040155] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040159] ata1.00: status: { DRDY }
[ 80.040165] ata1.00: cmd 61/08:28:ad:d4:f9/00:00:07:00:00/40 tag 5 ncq 4096
out
[ 80.040167] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040171] ata1.00: status: { DRDY }
[ 80.040177] ata1.00: cmd 61/08:30:c5:58:fc/00:00:07:00:00/40 tag 6 ncq 4096
out
[ 80.040178] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040188] ata1.00: status: { DRDY }
[ 80.040191] ata1.00: cmd 61/18:38:4d:e1:f8/00:00:07:00:00/40 tag 7 ncq 12288
out
[ 80.040192] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040193] ata1.00: status: { DRDY }
[ 80.040196] ata1.00: cmd 61/10:40:25:fa:f6/00:00:07:00:00/40 tag 8 ncq 8192
out
[ 80.040197] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040199] ata1.00: status: { DRDY }
[ 80.040201] ata1.00: cmd 61/10:48:45:fa:f6/00:00:07:00:00/40 tag 9 ncq 8192
out
[ 80.040202] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040204] ata1.00: status: { DRDY }
[ 80.040207] ata1.00: cmd 61/08:50:5d:fa:f6/00:00:07:00:00/40 tag 10 ncq 4096
out
[ 80.040208] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040210] ata1.00: status: { DRDY }
[ 80.040212] ata1.00: cmd 61/08:58:6d:fa:f6/00:00:07:00:00/40 tag 11 ncq 4096
out
[ 80.040213] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040215] ata1.00: status: { DRDY }
[ 80.040218] ata1.00: cmd 61/08:60:85:fa:f6/00:00:07:00:00/40 tag 12 ncq 4096
out
[ 80.040218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040220] ata1.00: status: { DRDY }
[ 80.040223] ata1.00: cmd 61/28:68:dd:20:f7/00:00:07:00:00/40 tag 13 ncq
20480 out
[ 80.040224] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040226] ata1.00: status: { DRDY }
[ 80.040228] ata1.00: cmd 61/08:70:0d:21:f7/00:00:07:00:00/40 tag 14 ncq 4096
out
[ 80.040229] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040231] ata1.00: status: { DRDY }
[ 80.040234] ata1.00: cmd 61/08:78:fd:44:d3/00:00:07:00:00/40 tag 15 ncq 4096
out
[ 80.040235] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040236] ata1.00: status: { DRDY }
[ 80.040239] ata1.00: cmd 61/08:80:6d:1d:f8/00:00:07:00:00/40 tag 16 ncq 4096
out
[ 80.040240] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040242] ata1.00: status: { DRDY }
[ 80.040244] ata1.00: cmd 61/08:88:75:21:f8/00:00:07:00:00/40 tag 17 ncq 4096
out
[ 80.040245] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040247] ata1.00: status: { DRDY }
[ 80.040250] ata1.00: cmd 61/08:90:c5:b5:f8/00:00:07:00:00/40 tag 18 ncq 4096
out
[ 80.040251] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040252] ata1.00: status: { DRDY }
[ 80.040255] ata1.00: cmd 61/08:98:dd:21:f9/00:00:07:00:00/40 tag 19 ncq 4096
out
[ 80.040256] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040258] ata1.00: status: { DRDY }
[ 80.040260] ata1.00: cmd 61/10:a0:ed:f1:fa/00:00:07:00:00/40 tag 20 ncq 8192
out
[ 80.040261] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040263] ata1.00: status: { DRDY }
[ 80.040266] ata1.00: cmd 61/08:a8:bd:64:f8/00:00:07:00:00/40 tag 21 ncq 4096
out
[ 80.040266] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040268] ata1.00: status: { DRDY }
[ 80.040271] ata1.00
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
There seem to be multiple issues mixed into one report. The initial report shows problems on generic write commands without any NCQ. The ICH6 controller used seems to use the same PCI ID for both piix and ahci modes (according to the Jaunty code). The second one fails on DMA read/writes with NCQ involved (so might have a controller in ahci mode). @José, could you try to compare the behavior against the a recent mainline kernel https://wiki.ubuntu.com/KernelMainlineBuilds. Also, please supply "sudo lspci -vvvnnxxx" and the full dmesg from the boot. @Cedric, could you please open another bug report (with ubuntu-bug linux, so it gets automatic information attached). And if possible also compare the results with a recent mainline kernel. Maybe experiment with "libata.force=noncq" @ShinobiTeno, this is also a different controller. Have you tried to limit DMA speed with "libata.force=udma/66" to see whether this changes things? @Joachim, this definitely sounds like a different problem. Could you please open another report with "ubuntu-bug linux"? Thanks. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem here: ~$ uname -a Linux Mihai 2.6.28-12-server #43-Ubuntu SMP Fri May 1 20:28:32 UTC 2009 i686 GNU/Linux Luckily..if I boot the computer with a cd in the drive..then everything works... Otherwise no luck in reading anything. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem: Xubuntu 9.04, Asus A6Rp laptop, CoreDuoT2060, Hitachi HTS541080G9AT00 uname: 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux Hitachi > is a PATA drive< , lspci -vv reports: 00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80) (prog-if 8a [Master SecP PriP]) Subsystem: ASUSTeK Computer Inc. Device 1397 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Add: disk has undergone 48h load and performed long SMART test. SMART table shows no errors or bad/transfered sectors whatsoever. lspci -vv: http://nopaste.info/0dc0f76223.html dmesg : http://nopaste.info/3d69c55172.html hdparm -iI /dev/sda: http://nopaste.info/2667d93861.html smartctl --all /dev/sda: http://nopaste.info/1f78922cd0.html ** Attachment added: "lspci.txt" http://launchpadlibrarian.net/26872602/lspci.txt -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
** Summary changed:
- ata timeout exception with linux 2.6.28-11
+ ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
** Description changed:
Binary package hint: linux-image-2.6.28-11-generic
package: linux-image-2.6.28-11
release: Jaunty Beta
latest version tested: 2.6.28-11.38
Trying to boot the new 2.6.28-11 kernel on Jaunty Beta results in many
ata timeout errors (like the one copied below) that make the system
unusable. Sounds much more serious than
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343919, and
different, in as much as it is not an ext4 fs that I am aware of, it is
not an nvidia disk controller, and these errors are many more than ~10,
and trivially easy to reproduce (it happens every time, from the first
disk-reads onward)
dmesg error message:
[ 75.816051] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 75.816135] ata1.00: cmd ca/00:10:50:27:1e/00:00:00:00:00/e9 tag 0 dma
8192 out
[ 75.816137] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 75.816275] ata1.00: status: { DRDY }
[ 75.816337] ata1: hard resetting link
[ 76.804036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 76.806704] ata1.00: configured for UDMA/100
[ 76.806715] ata1: EH complete
- Note that booting 2.6.27 does not produce any disk error. smartctl
- reports no disk health problems, either.
+ Note that booting 2.6.27 does not produce any disk error. smartctl reports no
disk health problems, either.
+ [update] the bug is present in previouos versions too, and it only appears
when using the ahci dirver for libata (see lspci -vv output below).
lspci -vv for IDE controllers:
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Sony Corporation Device 81b9
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR-
Kernel driver in use: ata_piix
Kernel modules: ahci, ata_piix
--
ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
https://bugs.launchpad.net/bugs/352197
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I updated the bug desc and title to reflect new findings. The issue is definitely located in the AHCI driver, as per my previous comments, and it affects all kernels tested (2.6.27-* and 2.6.28-* on intrepid, jaunty beta, jaunty release and debian lenny up to now). The workaround i used works for 2.6.27 kernels, as ahci is loaded as a module and can be blacklisted in /etc/modprobe.d/blacklist. Unfortunately, 2.6.28 kernels in ubuntu (haven't tested with debian again) do not load ahci (or any libata driver, for that matter) as modules, but are now built-in into the kernel, so my workaround is useless. Any help on how to disable ahci when it's built in (ie, force the kernel to use ata_piix anyway) would be greatly appreciated. note that i do not have any intention of recompiling the kernel :) If you need more information, please let me know. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem here: ~$ uname -a Linux Mihai 2.6.28-12-server #43-Ubuntu SMP Fri May 1 20:28:32 UTC 2009 i686 GNU/Linux Luckily..if I boot the computer with a cd in the drive..then everything works... Otherwise no luck in reading anything. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Just want to add the link to https://wiki.ubuntu.com/KernelTeam/Netconsole which I will also try myself since I might have the same problem (reported in bug 397096). -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
There seem to be multiple issues mixed into one report. The initial report shows problems on generic write commands without any NCQ. The ICH6 controller used seems to use the same PCI ID for both piix and ahci modes (according to the Jaunty code). The second one fails on DMA read/writes with NCQ involved (so might have a controller in ahci mode). @José, could you try to compare the behavior against the a recent mainline kernel https://wiki.ubuntu.com/KernelMainlineBuilds. Also, please supply "sudo lspci -vvvnnxxx" and the full dmesg from the boot. @Cedric, could you please open another bug report (with ubuntu-bug linux, so it gets automatic information attached). And if possible also compare the results with a recent mainline kernel. Maybe experiment with "libata.force=noncq" @ShinobiTeno, this is also a different controller. Have you tried to limit DMA speed with "libata.force=udma/66" to see whether this changes things? @Joachim, this definitely sounds like a different problem. Could you please open another report with "ubuntu-bug linux"? Thanks. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I can confirm this bug on my Dell Vostro 1710 running Jaunty
(2.6.28-11-{generic,server}).
It occurs only once on every boot, when GDM starts (and thus does its
prefetch), provoking a ~30s blank screen with heavy disk activity before the
login screen.
[ 80.040094] ata1.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6
frozen
[ 80.040106] ata1.00: cmd 60/88:00:25:76:72/00:00:08:00:00/40 tag 0 ncq 69632
in
[ 80.040107] res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 80.040112] ata1.00: status: { DRDY }
[ 80.040118] ata1.00: cmd 60/08:08:7d:63:d4/00:00:07:00:00/40 tag 1 ncq 4096
in
[ 80.040120] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040124] ata1.00: status: { DRDY }
[ 80.040130] ata1.00: cmd 60/08:10:8d:cb:81/00:00:07:00:00/40 tag 2 ncq 4096
in
[ 80.040132] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040136] ata1.00: status: { DRDY }
[ 80.040142] ata1.00: cmd 61/08:18:b5:64:f8/00:00:07:00:00/40 tag 3 ncq 4096
out
[ 80.040144] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040147] ata1.00: status: { DRDY }
[ 80.040153] ata1.00: cmd 61/08:20:45:e1:f8/00:00:07:00:00/40 tag 4 ncq 4096
out
[ 80.040155] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040159] ata1.00: status: { DRDY }
[ 80.040165] ata1.00: cmd 61/08:28:ad:d4:f9/00:00:07:00:00/40 tag 5 ncq 4096
out
[ 80.040167] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040171] ata1.00: status: { DRDY }
[ 80.040177] ata1.00: cmd 61/08:30:c5:58:fc/00:00:07:00:00/40 tag 6 ncq 4096
out
[ 80.040178] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040188] ata1.00: status: { DRDY }
[ 80.040191] ata1.00: cmd 61/18:38:4d:e1:f8/00:00:07:00:00/40 tag 7 ncq 12288
out
[ 80.040192] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040193] ata1.00: status: { DRDY }
[ 80.040196] ata1.00: cmd 61/10:40:25:fa:f6/00:00:07:00:00/40 tag 8 ncq 8192
out
[ 80.040197] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040199] ata1.00: status: { DRDY }
[ 80.040201] ata1.00: cmd 61/10:48:45:fa:f6/00:00:07:00:00/40 tag 9 ncq 8192
out
[ 80.040202] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040204] ata1.00: status: { DRDY }
[ 80.040207] ata1.00: cmd 61/08:50:5d:fa:f6/00:00:07:00:00/40 tag 10 ncq 4096
out
[ 80.040208] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040210] ata1.00: status: { DRDY }
[ 80.040212] ata1.00: cmd 61/08:58:6d:fa:f6/00:00:07:00:00/40 tag 11 ncq 4096
out
[ 80.040213] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040215] ata1.00: status: { DRDY }
[ 80.040218] ata1.00: cmd 61/08:60:85:fa:f6/00:00:07:00:00/40 tag 12 ncq 4096
out
[ 80.040218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040220] ata1.00: status: { DRDY }
[ 80.040223] ata1.00: cmd 61/28:68:dd:20:f7/00:00:07:00:00/40 tag 13 ncq
20480 out
[ 80.040224] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040226] ata1.00: status: { DRDY }
[ 80.040228] ata1.00: cmd 61/08:70:0d:21:f7/00:00:07:00:00/40 tag 14 ncq 4096
out
[ 80.040229] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040231] ata1.00: status: { DRDY }
[ 80.040234] ata1.00: cmd 61/08:78:fd:44:d3/00:00:07:00:00/40 tag 15 ncq 4096
out
[ 80.040235] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040236] ata1.00: status: { DRDY }
[ 80.040239] ata1.00: cmd 61/08:80:6d:1d:f8/00:00:07:00:00/40 tag 16 ncq 4096
out
[ 80.040240] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040242] ata1.00: status: { DRDY }
[ 80.040244] ata1.00: cmd 61/08:88:75:21:f8/00:00:07:00:00/40 tag 17 ncq 4096
out
[ 80.040245] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040247] ata1.00: status: { DRDY }
[ 80.040250] ata1.00: cmd 61/08:90:c5:b5:f8/00:00:07:00:00/40 tag 18 ncq 4096
out
[ 80.040251] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040252] ata1.00: status: { DRDY }
[ 80.040255] ata1.00: cmd 61/08:98:dd:21:f9/00:00:07:00:00/40 tag 19 ncq 4096
out
[ 80.040256] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040258] ata1.00: status: { DRDY }
[ 80.040260] ata1.00: cmd 61/10:a0:ed:f1:fa/00:00:07:00:00/40 tag 20 ncq 8192
out
[ 80.040261] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040263] ata1.00: status: { DRDY }
[ 80.040266] ata1.00: cmd 61/08:a8:bd:64:f8/00:00:07:00:00/40 tag 21 ncq 4096
out
[ 80.040266] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040268] ata1.00: status: { DRDY }
[ 80.040271] ata1.00
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
** Summary changed:
- ata timeout exception with linux 2.6.28-11
+ ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
** Description changed:
Binary package hint: linux-image-2.6.28-11-generic
package: linux-image-2.6.28-11
release: Jaunty Beta
latest version tested: 2.6.28-11.38
Trying to boot the new 2.6.28-11 kernel on Jaunty Beta results in many
ata timeout errors (like the one copied below) that make the system
unusable. Sounds much more serious than
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343919, and
different, in as much as it is not an ext4 fs that I am aware of, it is
not an nvidia disk controller, and these errors are many more than ~10,
and trivially easy to reproduce (it happens every time, from the first
disk-reads onward)
dmesg error message:
[ 75.816051] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 75.816135] ata1.00: cmd ca/00:10:50:27:1e/00:00:00:00:00/e9 tag 0 dma
8192 out
[ 75.816137] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 75.816275] ata1.00: status: { DRDY }
[ 75.816337] ata1: hard resetting link
[ 76.804036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 76.806704] ata1.00: configured for UDMA/100
[ 76.806715] ata1: EH complete
- Note that booting 2.6.27 does not produce any disk error. smartctl
- reports no disk health problems, either.
+ Note that booting 2.6.27 does not produce any disk error. smartctl reports no
disk health problems, either.
+ [update] the bug is present in previouos versions too, and it only appears
when using the ahci dirver for libata (see lspci -vv output below).
lspci -vv for IDE controllers:
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Sony Corporation Device 81b9
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR-
Kernel driver in use: ata_piix
Kernel modules: ahci, ata_piix
--
ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
https://bugs.launchpad.net/bugs/352197
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I updated the bug desc and title to reflect new findings. The issue is definitely located in the AHCI driver, as per my previous comments, and it affects all kernels tested (2.6.27-* and 2.6.28-* on intrepid, jaunty beta, jaunty release and debian lenny up to now). The workaround i used works for 2.6.27 kernels, as ahci is loaded as a module and can be blacklisted in /etc/modprobe.d/blacklist. Unfortunately, 2.6.28 kernels in ubuntu (haven't tested with debian again) do not load ahci (or any libata driver, for that matter) as modules, but are now built-in into the kernel, so my workaround is useless. Any help on how to disable ahci when it's built in (ie, force the kernel to use ata_piix anyway) would be greatly appreciated. note that i do not have any intention of recompiling the kernel :) If you need more information, please let me know. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I'll add a 'me too' to this one. Patched up jaunty sysytem used as a Mythtv box. System was fine with a 250GB Seagate Bara which failed. I replaced it with a new 1Tb seagate bara and now get these errors under heavy read load. 2.6.30 doesn't help - I got several errors while the Nvidia installer was running. Just moving through the recordings menu in Mythtv will trigger it - really any thing that generate high disk activity seems to. disk - ST31000528AS 00:1f.2 IDE interface [0101]: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller [8086:2651] (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Giga-byte Technology Device [1458:2651] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem: Xubuntu 9.04, Asus A6Rp laptop, CoreDuoT2060, Hitachi HTS541080G9AT00 uname: 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux Hitachi > is a PATA drive< , lspci -vv reports: 00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80) (prog-if 8a [Master SecP PriP]) Subsystem: ASUSTeK Computer Inc. Device 1397 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Add: disk has undergone 48h load and performed long SMART test. SMART table shows no errors or bad/transfered sectors whatsoever. lspci -vv: http://nopaste.info/0dc0f76223.html dmesg : http://nopaste.info/3d69c55172.html hdparm -iI /dev/sda: http://nopaste.info/2667d93861.html smartctl --all /dev/sda: http://nopaste.info/1f78922cd0.html ** Attachment added: "lspci.txt" http://launchpadlibrarian.net/26872602/lspci.txt -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I had the same problem (SATA disk freezing), and I solved it by tunning the pdflush parameters ... https://bugs.launchpad.net/ubuntu/+bug/270794/comments/12 -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I have the same problem on an IDE DVD writer, it occurs when inserting some writable medium (doesnt occur with CD-ROM or DVD-ROM). After that, it is impossible to eject disk with "eject" command nor with device button. It could be related as the syslog is the same. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Another "me, too" for this bug. Ubuntu 9.04 64bit - SATA AHCI mode - ext4 fs WD Velociraptor (ext4fs: /, Swap, /Data) WD Caviar Black 1TB (ext4fs: /home) WD 640GB (ext4fs: /Backup) I recently built a new system using an EVGA 760 Classified MB, i7 920cpu, 12GB triple ch DDR3 and 300GB Velociraptor. I installed the OS after setting the BIOS to SATA AHCI mode (needed hot swapping capabilities). Everything worked fine for about 1 month until last night. I was doing a very large (200GB+) grsync backup of my /home partition to my WD640GB backup drive. At some point in the backup the system froze. No combination of keyboard tricks (ctl+alt+backspace, or alt+print screen+REISUB) would restart X or reboot the OS. I had to resort to killing power. On reboot, the one of my BIOS screens reported "Port 00:" during what I will call the AHCI check. The Velociraptor system drive would not boot. When, I went back into the BIOS setup, I saw that the BIOS did not even see the Velociraptor. I assumed the crash and hard power down had corrputed some critical system files. I removed the Velociraptor boot drive and replaced it with a WinXP 64 boot drive (also set for AHCI mode) and was able to boot up a Windows system with no problem. I then tested the Velociraptor with SpinRite 6 and its a good drive. I decided to try and reboot the Ubuntu system by changing the BIOS SATA setting to "IDE" mode. This worked. Ubuntu was able to start after it found a few errors on the / partition, corrected them, and finished booting. Ubuntu 9.04/64 now seems to be working fine in "IDE" mode. After reading through this thread, it seems that I have been bitten by this AHCI bug when I was doing the very large rsync file backup; although, I have to add that this wasn't the first time, I did such a large backup on this new system without problems. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Just want to add the link to https://wiki.ubuntu.com/KernelTeam/Netconsole which I will also try myself since I might have the same problem (reported in bug 397096). -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I'll add a 'me too' to this one. Patched up jaunty sysytem used as a Mythtv box. System was fine with a 250GB Seagate Bara which failed. I replaced it with a new 1Tb seagate bara and now get these errors under heavy read load. 2.6.30 doesn't help - I got several errors while the Nvidia installer was running. Just moving through the recordings menu in Mythtv will trigger it - really any thing that generate high disk activity seems to. disk - ST31000528AS 00:1f.2 IDE interface [0101]: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller [8086:2651] (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Giga-byte Technology Device [1458:2651] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Another "me, too" for this bug. Ubuntu 9.04 64bit - SATA AHCI mode - ext4 fs WD Velociraptor (ext4fs: /, Swap, /Data) WD Caviar Black 1TB (ext4fs: /home) WD 640GB (ext4fs: /Backup) I recently built a new system using an EVGA 760 Classified MB, i7 920cpu, 12GB triple ch DDR3 and 300GB Velociraptor. I installed the OS after setting the BIOS to SATA AHCI mode (needed hot swapping capabilities). Everything worked fine for about 1 month until last night. I was doing a very large (200GB+) grsync backup of my /home partition to my WD640GB backup drive. At some point in the backup the system froze. No combination of keyboard tricks (ctl+alt+backspace, or alt+print screen+REISUB) would restart X or reboot the OS. I had to resort to killing power. On reboot, the one of my BIOS screens reported "Port 00:" during what I will call the AHCI check. The Velociraptor system drive would not boot. When, I went back into the BIOS setup, I saw that the BIOS did not even see the Velociraptor. I assumed the crash and hard power down had corrputed some critical system files. I removed the Velociraptor boot drive and replaced it with a WinXP 64 boot drive (also set for AHCI mode) and was able to boot up a Windows system with no problem. I then tested the Velociraptor with SpinRite 6 and its a good drive. I decided to try and reboot the Ubuntu system by changing the BIOS SATA setting to "IDE" mode. This worked. Ubuntu was able to start after it found a few errors on the / partition, corrected them, and finished booting. Ubuntu 9.04/64 now seems to be working fine in "IDE" mode. After reading through this thread, it seems that I have been bitten by this AHCI bug when I was doing the very large rsync file backup; although, I have to add that this wasn't the first time, I did such a large backup on this new system without problems. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
** Summary changed:
- ata timeout exception with linux 2.6.28-11
+ ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
** Description changed:
Binary package hint: linux-image-2.6.28-11-generic
package: linux-image-2.6.28-11
release: Jaunty Beta
latest version tested: 2.6.28-11.38
Trying to boot the new 2.6.28-11 kernel on Jaunty Beta results in many
ata timeout errors (like the one copied below) that make the system
unusable. Sounds much more serious than
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343919, and
different, in as much as it is not an ext4 fs that I am aware of, it is
not an nvidia disk controller, and these errors are many more than ~10,
and trivially easy to reproduce (it happens every time, from the first
disk-reads onward)
dmesg error message:
[ 75.816051] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 75.816135] ata1.00: cmd ca/00:10:50:27:1e/00:00:00:00:00/e9 tag 0 dma
8192 out
[ 75.816137] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 75.816275] ata1.00: status: { DRDY }
[ 75.816337] ata1: hard resetting link
[ 76.804036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 76.806704] ata1.00: configured for UDMA/100
[ 76.806715] ata1: EH complete
- Note that booting 2.6.27 does not produce any disk error. smartctl
- reports no disk health problems, either.
+ Note that booting 2.6.27 does not produce any disk error. smartctl reports no
disk health problems, either.
+ [update] the bug is present in previouos versions too, and it only appears
when using the ahci dirver for libata (see lspci -vv output below).
lspci -vv for IDE controllers:
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Sony Corporation Device 81b9
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR-
Kernel driver in use: ata_piix
Kernel modules: ahci, ata_piix
--
ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
https://bugs.launchpad.net/bugs/352197
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I updated the bug desc and title to reflect new findings. The issue is definitely located in the AHCI driver, as per my previous comments, and it affects all kernels tested (2.6.27-* and 2.6.28-* on intrepid, jaunty beta, jaunty release and debian lenny up to now). The workaround i used works for 2.6.27 kernels, as ahci is loaded as a module and can be blacklisted in /etc/modprobe.d/blacklist. Unfortunately, 2.6.28 kernels in ubuntu (haven't tested with debian again) do not load ahci (or any libata driver, for that matter) as modules, but are now built-in into the kernel, so my workaround is useless. Any help on how to disable ahci when it's built in (ie, force the kernel to use ata_piix anyway) would be greatly appreciated. note that i do not have any intention of recompiling the kernel :) If you need more information, please let me know. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I can confirm this bug on my Dell Vostro 1710 running Jaunty
(2.6.28-11-{generic,server}).
It occurs only once on every boot, when GDM starts (and thus does its
prefetch), provoking a ~30s blank screen with heavy disk activity before the
login screen.
[ 80.040094] ata1.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6
frozen
[ 80.040106] ata1.00: cmd 60/88:00:25:76:72/00:00:08:00:00/40 tag 0 ncq 69632
in
[ 80.040107] res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 80.040112] ata1.00: status: { DRDY }
[ 80.040118] ata1.00: cmd 60/08:08:7d:63:d4/00:00:07:00:00/40 tag 1 ncq 4096
in
[ 80.040120] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040124] ata1.00: status: { DRDY }
[ 80.040130] ata1.00: cmd 60/08:10:8d:cb:81/00:00:07:00:00/40 tag 2 ncq 4096
in
[ 80.040132] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040136] ata1.00: status: { DRDY }
[ 80.040142] ata1.00: cmd 61/08:18:b5:64:f8/00:00:07:00:00/40 tag 3 ncq 4096
out
[ 80.040144] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040147] ata1.00: status: { DRDY }
[ 80.040153] ata1.00: cmd 61/08:20:45:e1:f8/00:00:07:00:00/40 tag 4 ncq 4096
out
[ 80.040155] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040159] ata1.00: status: { DRDY }
[ 80.040165] ata1.00: cmd 61/08:28:ad:d4:f9/00:00:07:00:00/40 tag 5 ncq 4096
out
[ 80.040167] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040171] ata1.00: status: { DRDY }
[ 80.040177] ata1.00: cmd 61/08:30:c5:58:fc/00:00:07:00:00/40 tag 6 ncq 4096
out
[ 80.040178] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040188] ata1.00: status: { DRDY }
[ 80.040191] ata1.00: cmd 61/18:38:4d:e1:f8/00:00:07:00:00/40 tag 7 ncq 12288
out
[ 80.040192] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040193] ata1.00: status: { DRDY }
[ 80.040196] ata1.00: cmd 61/10:40:25:fa:f6/00:00:07:00:00/40 tag 8 ncq 8192
out
[ 80.040197] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040199] ata1.00: status: { DRDY }
[ 80.040201] ata1.00: cmd 61/10:48:45:fa:f6/00:00:07:00:00/40 tag 9 ncq 8192
out
[ 80.040202] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040204] ata1.00: status: { DRDY }
[ 80.040207] ata1.00: cmd 61/08:50:5d:fa:f6/00:00:07:00:00/40 tag 10 ncq 4096
out
[ 80.040208] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040210] ata1.00: status: { DRDY }
[ 80.040212] ata1.00: cmd 61/08:58:6d:fa:f6/00:00:07:00:00/40 tag 11 ncq 4096
out
[ 80.040213] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040215] ata1.00: status: { DRDY }
[ 80.040218] ata1.00: cmd 61/08:60:85:fa:f6/00:00:07:00:00/40 tag 12 ncq 4096
out
[ 80.040218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040220] ata1.00: status: { DRDY }
[ 80.040223] ata1.00: cmd 61/28:68:dd:20:f7/00:00:07:00:00/40 tag 13 ncq
20480 out
[ 80.040224] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040226] ata1.00: status: { DRDY }
[ 80.040228] ata1.00: cmd 61/08:70:0d:21:f7/00:00:07:00:00/40 tag 14 ncq 4096
out
[ 80.040229] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040231] ata1.00: status: { DRDY }
[ 80.040234] ata1.00: cmd 61/08:78:fd:44:d3/00:00:07:00:00/40 tag 15 ncq 4096
out
[ 80.040235] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040236] ata1.00: status: { DRDY }
[ 80.040239] ata1.00: cmd 61/08:80:6d:1d:f8/00:00:07:00:00/40 tag 16 ncq 4096
out
[ 80.040240] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040242] ata1.00: status: { DRDY }
[ 80.040244] ata1.00: cmd 61/08:88:75:21:f8/00:00:07:00:00/40 tag 17 ncq 4096
out
[ 80.040245] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040247] ata1.00: status: { DRDY }
[ 80.040250] ata1.00: cmd 61/08:90:c5:b5:f8/00:00:07:00:00/40 tag 18 ncq 4096
out
[ 80.040251] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040252] ata1.00: status: { DRDY }
[ 80.040255] ata1.00: cmd 61/08:98:dd:21:f9/00:00:07:00:00/40 tag 19 ncq 4096
out
[ 80.040256] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040258] ata1.00: status: { DRDY }
[ 80.040260] ata1.00: cmd 61/10:a0:ed:f1:fa/00:00:07:00:00/40 tag 20 ncq 8192
out
[ 80.040261] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040263] ata1.00: status: { DRDY }
[ 80.040266] ata1.00: cmd 61/08:a8:bd:64:f8/00:00:07:00:00/40 tag 21 ncq 4096
out
[ 80.040266] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040268] ata1.00: status: { DRDY }
[ 80.040271] ata1.00
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
There seem to be multiple issues mixed into one report. The initial report shows problems on generic write commands without any NCQ. The ICH6 controller used seems to use the same PCI ID for both piix and ahci modes (according to the Jaunty code). The second one fails on DMA read/writes with NCQ involved (so might have a controller in ahci mode). @José, could you try to compare the behavior against the a recent mainline kernel https://wiki.ubuntu.com/KernelMainlineBuilds. Also, please supply "sudo lspci -vvvnnxxx" and the full dmesg from the boot. @Cedric, could you please open another bug report (with ubuntu-bug linux, so it gets automatic information attached). And if possible also compare the results with a recent mainline kernel. Maybe experiment with "libata.force=noncq" @ShinobiTeno, this is also a different controller. Have you tried to limit DMA speed with "libata.force=udma/66" to see whether this changes things? @Joachim, this definitely sounds like a different problem. Could you please open another report with "ubuntu-bug linux"? Thanks. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem here: ~$ uname -a Linux Mihai 2.6.28-12-server #43-Ubuntu SMP Fri May 1 20:28:32 UTC 2009 i686 GNU/Linux Luckily..if I boot the computer with a cd in the drive..then everything works... Otherwise no luck in reading anything. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem: Xubuntu 9.04, Asus A6Rp laptop, CoreDuoT2060, Hitachi HTS541080G9AT00 uname: 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux Hitachi > is a PATA drive< , lspci -vv reports: 00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80) (prog-if 8a [Master SecP PriP]) Subsystem: ASUSTeK Computer Inc. Device 1397 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Add: disk has undergone 48h load and performed long SMART test. SMART table shows no errors or bad/transfered sectors whatsoever. lspci -vv: http://nopaste.info/0dc0f76223.html dmesg : http://nopaste.info/3d69c55172.html hdparm -iI /dev/sda: http://nopaste.info/2667d93861.html smartctl --all /dev/sda: http://nopaste.info/1f78922cd0.html ** Attachment added: "lspci.txt" http://launchpadlibrarian.net/26872602/lspci.txt -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I had the same problem (SATA disk freezing), and I solved it by tunning the pdflush parameters ... https://bugs.launchpad.net/ubuntu/+bug/270794/comments/12 -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I have the same problem on an IDE DVD writer, it occurs when inserting some writable medium (doesnt occur with CD-ROM or DVD-ROM). After that, it is impossible to eject disk with "eject" command nor with device button. It could be related as the syslog is the same. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I can confirm this bug on my Dell Vostro 1710 running Jaunty
(2.6.28-11-{generic,server}).
It occurs only once on every boot, when GDM starts (and thus does its
prefetch), provoking a ~30s blank screen with heavy disk activity before the
login screen.
[ 80.040094] ata1.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6
frozen
[ 80.040106] ata1.00: cmd 60/88:00:25:76:72/00:00:08:00:00/40 tag 0 ncq 69632
in
[ 80.040107] res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 80.040112] ata1.00: status: { DRDY }
[ 80.040118] ata1.00: cmd 60/08:08:7d:63:d4/00:00:07:00:00/40 tag 1 ncq 4096
in
[ 80.040120] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040124] ata1.00: status: { DRDY }
[ 80.040130] ata1.00: cmd 60/08:10:8d:cb:81/00:00:07:00:00/40 tag 2 ncq 4096
in
[ 80.040132] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040136] ata1.00: status: { DRDY }
[ 80.040142] ata1.00: cmd 61/08:18:b5:64:f8/00:00:07:00:00/40 tag 3 ncq 4096
out
[ 80.040144] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040147] ata1.00: status: { DRDY }
[ 80.040153] ata1.00: cmd 61/08:20:45:e1:f8/00:00:07:00:00/40 tag 4 ncq 4096
out
[ 80.040155] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040159] ata1.00: status: { DRDY }
[ 80.040165] ata1.00: cmd 61/08:28:ad:d4:f9/00:00:07:00:00/40 tag 5 ncq 4096
out
[ 80.040167] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040171] ata1.00: status: { DRDY }
[ 80.040177] ata1.00: cmd 61/08:30:c5:58:fc/00:00:07:00:00/40 tag 6 ncq 4096
out
[ 80.040178] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040188] ata1.00: status: { DRDY }
[ 80.040191] ata1.00: cmd 61/18:38:4d:e1:f8/00:00:07:00:00/40 tag 7 ncq 12288
out
[ 80.040192] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040193] ata1.00: status: { DRDY }
[ 80.040196] ata1.00: cmd 61/10:40:25:fa:f6/00:00:07:00:00/40 tag 8 ncq 8192
out
[ 80.040197] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040199] ata1.00: status: { DRDY }
[ 80.040201] ata1.00: cmd 61/10:48:45:fa:f6/00:00:07:00:00/40 tag 9 ncq 8192
out
[ 80.040202] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040204] ata1.00: status: { DRDY }
[ 80.040207] ata1.00: cmd 61/08:50:5d:fa:f6/00:00:07:00:00/40 tag 10 ncq 4096
out
[ 80.040208] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040210] ata1.00: status: { DRDY }
[ 80.040212] ata1.00: cmd 61/08:58:6d:fa:f6/00:00:07:00:00/40 tag 11 ncq 4096
out
[ 80.040213] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040215] ata1.00: status: { DRDY }
[ 80.040218] ata1.00: cmd 61/08:60:85:fa:f6/00:00:07:00:00/40 tag 12 ncq 4096
out
[ 80.040218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040220] ata1.00: status: { DRDY }
[ 80.040223] ata1.00: cmd 61/28:68:dd:20:f7/00:00:07:00:00/40 tag 13 ncq
20480 out
[ 80.040224] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040226] ata1.00: status: { DRDY }
[ 80.040228] ata1.00: cmd 61/08:70:0d:21:f7/00:00:07:00:00/40 tag 14 ncq 4096
out
[ 80.040229] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040231] ata1.00: status: { DRDY }
[ 80.040234] ata1.00: cmd 61/08:78:fd:44:d3/00:00:07:00:00/40 tag 15 ncq 4096
out
[ 80.040235] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040236] ata1.00: status: { DRDY }
[ 80.040239] ata1.00: cmd 61/08:80:6d:1d:f8/00:00:07:00:00/40 tag 16 ncq 4096
out
[ 80.040240] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040242] ata1.00: status: { DRDY }
[ 80.040244] ata1.00: cmd 61/08:88:75:21:f8/00:00:07:00:00/40 tag 17 ncq 4096
out
[ 80.040245] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040247] ata1.00: status: { DRDY }
[ 80.040250] ata1.00: cmd 61/08:90:c5:b5:f8/00:00:07:00:00/40 tag 18 ncq 4096
out
[ 80.040251] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040252] ata1.00: status: { DRDY }
[ 80.040255] ata1.00: cmd 61/08:98:dd:21:f9/00:00:07:00:00/40 tag 19 ncq 4096
out
[ 80.040256] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040258] ata1.00: status: { DRDY }
[ 80.040260] ata1.00: cmd 61/10:a0:ed:f1:fa/00:00:07:00:00/40 tag 20 ncq 8192
out
[ 80.040261] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040263] ata1.00: status: { DRDY }
[ 80.040266] ata1.00: cmd 61/08:a8:bd:64:f8/00:00:07:00:00/40 tag 21 ncq 4096
out
[ 80.040266] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040268] ata1.00: status: { DRDY }
[ 80.040271] ata1.00
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Just want to add the link to https://wiki.ubuntu.com/KernelTeam/Netconsole which I will also try myself since I might have the same problem (reported in bug 397096). -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I'll add a 'me too' to this one. Patched up jaunty sysytem used as a Mythtv box. System was fine with a 250GB Seagate Bara which failed. I replaced it with a new 1Tb seagate bara and now get these errors under heavy read load. 2.6.30 doesn't help - I got several errors while the Nvidia installer was running. Just moving through the recordings menu in Mythtv will trigger it - really any thing that generate high disk activity seems to. disk - ST31000528AS 00:1f.2 IDE interface [0101]: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller [8086:2651] (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Giga-byte Technology Device [1458:2651] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
There seem to be multiple issues mixed into one report. The initial report shows problems on generic write commands without any NCQ. The ICH6 controller used seems to use the same PCI ID for both piix and ahci modes (according to the Jaunty code). The second one fails on DMA read/writes with NCQ involved (so might have a controller in ahci mode). @José, could you try to compare the behavior against the a recent mainline kernel https://wiki.ubuntu.com/KernelMainlineBuilds. Also, please supply "sudo lspci -vvvnnxxx" and the full dmesg from the boot. @Cedric, could you please open another bug report (with ubuntu-bug linux, so it gets automatic information attached). And if possible also compare the results with a recent mainline kernel. Maybe experiment with "libata.force=noncq" @ShinobiTeno, this is also a different controller. Have you tried to limit DMA speed with "libata.force=udma/66" to see whether this changes things? @Joachim, this definitely sounds like a different problem. Could you please open another report with "ubuntu-bug linux"? Thanks. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Another "me, too" for this bug. Ubuntu 9.04 64bit - SATA AHCI mode - ext4 fs WD Velociraptor (ext4fs: /, Swap, /Data) WD Caviar Black 1TB (ext4fs: /home) WD 640GB (ext4fs: /Backup) I recently built a new system using an EVGA 760 Classified MB, i7 920cpu, 12GB triple ch DDR3 and 300GB Velociraptor. I installed the OS after setting the BIOS to SATA AHCI mode (needed hot swapping capabilities). Everything worked fine for about 1 month until last night. I was doing a very large (200GB+) grsync backup of my /home partition to my WD640GB backup drive. At some point in the backup the system froze. No combination of keyboard tricks (ctl+alt+backspace, or alt+print screen+REISUB) would restart X or reboot the OS. I had to resort to killing power. On reboot, the one of my BIOS screens reported "Port 00:" during what I will call the AHCI check. The Velociraptor system drive would not boot. When, I went back into the BIOS setup, I saw that the BIOS did not even see the Velociraptor. I assumed the crash and hard power down had corrputed some critical system files. I removed the Velociraptor boot drive and replaced it with a WinXP 64 boot drive (also set for AHCI mode) and was able to boot up a Windows system with no problem. I then tested the Velociraptor with SpinRite 6 and its a good drive. I decided to try and reboot the Ubuntu system by changing the BIOS SATA setting to "IDE" mode. This worked. Ubuntu was able to start after it found a few errors on the / partition, corrected them, and finished booting. Ubuntu 9.04/64 now seems to be working fine in "IDE" mode. After reading through this thread, it seems that I have been bitten by this AHCI bug when I was doing the very large rsync file backup; although, I have to add that this wasn't the first time, I did such a large backup on this new system without problems. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I had the same problem (SATA disk freezing), and I solved it by tunning the pdflush parameters ... https://bugs.launchpad.net/ubuntu/+bug/270794/comments/12 -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I have the same problem on an IDE DVD writer, it occurs when inserting some writable medium (doesnt occur with CD-ROM or DVD-ROM). After that, it is impossible to eject disk with "eject" command nor with device button. It could be related as the syslog is the same. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem here: ~$ uname -a Linux Mihai 2.6.28-12-server #43-Ubuntu SMP Fri May 1 20:28:32 UTC 2009 i686 GNU/Linux Luckily..if I boot the computer with a cd in the drive..then everything works... Otherwise no luck in reading anything. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem: Xubuntu 9.04, Asus A6Rp laptop, CoreDuoT2060, Hitachi HTS541080G9AT00 uname: 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux Hitachi > is a PATA drive< , lspci -vv reports: 00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80) (prog-if 8a [Master SecP PriP]) Subsystem: ASUSTeK Computer Inc. Device 1397 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Add: disk has undergone 48h load and performed long SMART test. SMART table shows no errors or bad/transfered sectors whatsoever. lspci -vv: http://nopaste.info/0dc0f76223.html dmesg : http://nopaste.info/3d69c55172.html hdparm -iI /dev/sda: http://nopaste.info/2667d93861.html smartctl --all /dev/sda: http://nopaste.info/1f78922cd0.html ** Attachment added: "lspci.txt" http://launchpadlibrarian.net/26872602/lspci.txt -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
** Summary changed:
- ata timeout exception with linux 2.6.28-11
+ ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
** Description changed:
Binary package hint: linux-image-2.6.28-11-generic
package: linux-image-2.6.28-11
release: Jaunty Beta
latest version tested: 2.6.28-11.38
Trying to boot the new 2.6.28-11 kernel on Jaunty Beta results in many
ata timeout errors (like the one copied below) that make the system
unusable. Sounds much more serious than
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343919, and
different, in as much as it is not an ext4 fs that I am aware of, it is
not an nvidia disk controller, and these errors are many more than ~10,
and trivially easy to reproduce (it happens every time, from the first
disk-reads onward)
dmesg error message:
[ 75.816051] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 75.816135] ata1.00: cmd ca/00:10:50:27:1e/00:00:00:00:00/e9 tag 0 dma
8192 out
[ 75.816137] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 75.816275] ata1.00: status: { DRDY }
[ 75.816337] ata1: hard resetting link
[ 76.804036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 76.806704] ata1.00: configured for UDMA/100
[ 76.806715] ata1: EH complete
- Note that booting 2.6.27 does not produce any disk error. smartctl
- reports no disk health problems, either.
+ Note that booting 2.6.27 does not produce any disk error. smartctl reports no
disk health problems, either.
+ [update] the bug is present in previouos versions too, and it only appears
when using the ahci dirver for libata (see lspci -vv output below).
lspci -vv for IDE controllers:
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Sony Corporation Device 81b9
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR-
Kernel driver in use: ata_piix
Kernel modules: ahci, ata_piix
--
ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
https://bugs.launchpad.net/bugs/352197
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I updated the bug desc and title to reflect new findings. The issue is definitely located in the AHCI driver, as per my previous comments, and it affects all kernels tested (2.6.27-* and 2.6.28-* on intrepid, jaunty beta, jaunty release and debian lenny up to now). The workaround i used works for 2.6.27 kernels, as ahci is loaded as a module and can be blacklisted in /etc/modprobe.d/blacklist. Unfortunately, 2.6.28 kernels in ubuntu (haven't tested with debian again) do not load ahci (or any libata driver, for that matter) as modules, but are now built-in into the kernel, so my workaround is useless. Any help on how to disable ahci when it's built in (ie, force the kernel to use ata_piix anyway) would be greatly appreciated. note that i do not have any intention of recompiling the kernel :) If you need more information, please let me know. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Another "me, too" for this bug. Ubuntu 9.04 64bit - SATA AHCI mode - ext4 fs WD Velociraptor (ext4fs: /, Swap, /Data) WD Caviar Black 1TB (ext4fs: /home) WD 640GB (ext4fs: /Backup) I recently built a new system using an EVGA 760 Classified MB, i7 920cpu, 12GB triple ch DDR3 and 300GB Velociraptor. I installed the OS after setting the BIOS to SATA AHCI mode (needed hot swapping capabilities). Everything worked fine for about 1 month until last night. I was doing a very large (200GB+) grsync backup of my /home partition to my WD640GB backup drive. At some point in the backup the system froze. No combination of keyboard tricks (ctl+alt+backspace, or alt+print screen+REISUB) would restart X or reboot the OS. I had to resort to killing power. On reboot, the one of my BIOS screens reported "Port 00:" during what I will call the AHCI check. The Velociraptor system drive would not boot. When, I went back into the BIOS setup, I saw that the BIOS did not even see the Velociraptor. I assumed the crash and hard power down had corrputed some critical system files. I removed the Velociraptor boot drive and replaced it with a WinXP 64 boot drive (also set for AHCI mode) and was able to boot up a Windows system with no problem. I then tested the Velociraptor with SpinRite 6 and its a good drive. I decided to try and reboot the Ubuntu system by changing the BIOS SATA setting to "IDE" mode. This worked. Ubuntu was able to start after it found a few errors on the / partition, corrected them, and finished booting. Ubuntu 9.04/64 now seems to be working fine in "IDE" mode. After reading through this thread, it seems that I have been bitten by this AHCI bug when I was doing the very large rsync file backup; although, I have to add that this wasn't the first time, I did such a large backup on this new system without problems. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I had the same problem (SATA disk freezing), and I solved it by tunning the pdflush parameters ... https://bugs.launchpad.net/ubuntu/+bug/270794/comments/12 -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I have the same problem on an IDE DVD writer, it occurs when inserting some writable medium (doesnt occur with CD-ROM or DVD-ROM). After that, it is impossible to eject disk with "eject" command nor with device button. It could be related as the syslog is the same. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
** Summary changed:
- ata timeout exception with linux 2.6.28-11
+ ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
** Description changed:
Binary package hint: linux-image-2.6.28-11-generic
package: linux-image-2.6.28-11
release: Jaunty Beta
latest version tested: 2.6.28-11.38
Trying to boot the new 2.6.28-11 kernel on Jaunty Beta results in many
ata timeout errors (like the one copied below) that make the system
unusable. Sounds much more serious than
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343919, and
different, in as much as it is not an ext4 fs that I am aware of, it is
not an nvidia disk controller, and these errors are many more than ~10,
and trivially easy to reproduce (it happens every time, from the first
disk-reads onward)
dmesg error message:
[ 75.816051] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[ 75.816135] ata1.00: cmd ca/00:10:50:27:1e/00:00:00:00:00/e9 tag 0 dma
8192 out
[ 75.816137] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 75.816275] ata1.00: status: { DRDY }
[ 75.816337] ata1: hard resetting link
[ 76.804036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 76.806704] ata1.00: configured for UDMA/100
[ 76.806715] ata1: EH complete
- Note that booting 2.6.27 does not produce any disk error. smartctl
- reports no disk health problems, either.
+ Note that booting 2.6.27 does not produce any disk error. smartctl reports no
disk health problems, either.
+ [update] the bug is present in previouos versions too, and it only appears
when using the ahci dirver for libata (see lspci -vv output below).
lspci -vv for IDE controllers:
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
IDE Controller (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: Sony Corporation Device 81b9
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- TAbort-
SERR-
Kernel driver in use: ata_piix
Kernel modules: ahci, ata_piix
--
ata timeout exception with ahci libata driver (was with 2.6.28-11, but i
confirmed it affewcts previous kernels too)
https://bugs.launchpad.net/bugs/352197
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I updated the bug desc and title to reflect new findings. The issue is definitely located in the AHCI driver, as per my previous comments, and it affects all kernels tested (2.6.27-* and 2.6.28-* on intrepid, jaunty beta, jaunty release and debian lenny up to now). The workaround i used works for 2.6.27 kernels, as ahci is loaded as a module and can be blacklisted in /etc/modprobe.d/blacklist. Unfortunately, 2.6.28 kernels in ubuntu (haven't tested with debian again) do not load ahci (or any libata driver, for that matter) as modules, but are now built-in into the kernel, so my workaround is useless. Any help on how to disable ahci when it's built in (ie, force the kernel to use ata_piix anyway) would be greatly appreciated. note that i do not have any intention of recompiling the kernel :) If you need more information, please let me know. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
There seem to be multiple issues mixed into one report. The initial report shows problems on generic write commands without any NCQ. The ICH6 controller used seems to use the same PCI ID for both piix and ahci modes (according to the Jaunty code). The second one fails on DMA read/writes with NCQ involved (so might have a controller in ahci mode). @José, could you try to compare the behavior against the a recent mainline kernel https://wiki.ubuntu.com/KernelMainlineBuilds. Also, please supply "sudo lspci -vvvnnxxx" and the full dmesg from the boot. @Cedric, could you please open another bug report (with ubuntu-bug linux, so it gets automatic information attached). And if possible also compare the results with a recent mainline kernel. Maybe experiment with "libata.force=noncq" @ShinobiTeno, this is also a different controller. Have you tried to limit DMA speed with "libata.force=udma/66" to see whether this changes things? @Joachim, this definitely sounds like a different problem. Could you please open another report with "ubuntu-bug linux"? Thanks. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem here: ~$ uname -a Linux Mihai 2.6.28-12-server #43-Ubuntu SMP Fri May 1 20:28:32 UTC 2009 i686 GNU/Linux Luckily..if I boot the computer with a cd in the drive..then everything works... Otherwise no luck in reading anything. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Same problem: Xubuntu 9.04, Asus A6Rp laptop, CoreDuoT2060, Hitachi HTS541080G9AT00 uname: 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux Hitachi > is a PATA drive< , lspci -vv reports: 00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80) (prog-if 8a [Master SecP PriP]) Subsystem: ASUSTeK Computer Inc. Device 1397 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Add: disk has undergone 48h load and performed long SMART test. SMART table shows no errors or bad/transfered sectors whatsoever. lspci -vv: http://nopaste.info/0dc0f76223.html dmesg : http://nopaste.info/3d69c55172.html hdparm -iI /dev/sda: http://nopaste.info/2667d93861.html smartctl --all /dev/sda: http://nopaste.info/1f78922cd0.html ** Attachment added: "lspci.txt" http://launchpadlibrarian.net/26872602/lspci.txt -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I had the same problem (SATA disk freezing), and I solved it by tunning the pdflush parameters ... https://bugs.launchpad.net/ubuntu/+bug/270794/comments/12 -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I have the same problem on an IDE DVD writer, it occurs when inserting some writable medium (doesnt occur with CD-ROM or DVD-ROM). After that, it is impossible to eject disk with "eject" command nor with device button. It could be related as the syslog is the same. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I can confirm this bug on my Dell Vostro 1710 running Jaunty
(2.6.28-11-{generic,server}).
It occurs only once on every boot, when GDM starts (and thus does its
prefetch), provoking a ~30s blank screen with heavy disk activity before the
login screen.
[ 80.040094] ata1.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6
frozen
[ 80.040106] ata1.00: cmd 60/88:00:25:76:72/00:00:08:00:00/40 tag 0 ncq 69632
in
[ 80.040107] res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 80.040112] ata1.00: status: { DRDY }
[ 80.040118] ata1.00: cmd 60/08:08:7d:63:d4/00:00:07:00:00/40 tag 1 ncq 4096
in
[ 80.040120] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040124] ata1.00: status: { DRDY }
[ 80.040130] ata1.00: cmd 60/08:10:8d:cb:81/00:00:07:00:00/40 tag 2 ncq 4096
in
[ 80.040132] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040136] ata1.00: status: { DRDY }
[ 80.040142] ata1.00: cmd 61/08:18:b5:64:f8/00:00:07:00:00/40 tag 3 ncq 4096
out
[ 80.040144] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040147] ata1.00: status: { DRDY }
[ 80.040153] ata1.00: cmd 61/08:20:45:e1:f8/00:00:07:00:00/40 tag 4 ncq 4096
out
[ 80.040155] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040159] ata1.00: status: { DRDY }
[ 80.040165] ata1.00: cmd 61/08:28:ad:d4:f9/00:00:07:00:00/40 tag 5 ncq 4096
out
[ 80.040167] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040171] ata1.00: status: { DRDY }
[ 80.040177] ata1.00: cmd 61/08:30:c5:58:fc/00:00:07:00:00/40 tag 6 ncq 4096
out
[ 80.040178] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040188] ata1.00: status: { DRDY }
[ 80.040191] ata1.00: cmd 61/18:38:4d:e1:f8/00:00:07:00:00/40 tag 7 ncq 12288
out
[ 80.040192] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040193] ata1.00: status: { DRDY }
[ 80.040196] ata1.00: cmd 61/10:40:25:fa:f6/00:00:07:00:00/40 tag 8 ncq 8192
out
[ 80.040197] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040199] ata1.00: status: { DRDY }
[ 80.040201] ata1.00: cmd 61/10:48:45:fa:f6/00:00:07:00:00/40 tag 9 ncq 8192
out
[ 80.040202] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040204] ata1.00: status: { DRDY }
[ 80.040207] ata1.00: cmd 61/08:50:5d:fa:f6/00:00:07:00:00/40 tag 10 ncq 4096
out
[ 80.040208] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040210] ata1.00: status: { DRDY }
[ 80.040212] ata1.00: cmd 61/08:58:6d:fa:f6/00:00:07:00:00/40 tag 11 ncq 4096
out
[ 80.040213] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040215] ata1.00: status: { DRDY }
[ 80.040218] ata1.00: cmd 61/08:60:85:fa:f6/00:00:07:00:00/40 tag 12 ncq 4096
out
[ 80.040218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040220] ata1.00: status: { DRDY }
[ 80.040223] ata1.00: cmd 61/28:68:dd:20:f7/00:00:07:00:00/40 tag 13 ncq
20480 out
[ 80.040224] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040226] ata1.00: status: { DRDY }
[ 80.040228] ata1.00: cmd 61/08:70:0d:21:f7/00:00:07:00:00/40 tag 14 ncq 4096
out
[ 80.040229] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040231] ata1.00: status: { DRDY }
[ 80.040234] ata1.00: cmd 61/08:78:fd:44:d3/00:00:07:00:00/40 tag 15 ncq 4096
out
[ 80.040235] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040236] ata1.00: status: { DRDY }
[ 80.040239] ata1.00: cmd 61/08:80:6d:1d:f8/00:00:07:00:00/40 tag 16 ncq 4096
out
[ 80.040240] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040242] ata1.00: status: { DRDY }
[ 80.040244] ata1.00: cmd 61/08:88:75:21:f8/00:00:07:00:00/40 tag 17 ncq 4096
out
[ 80.040245] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040247] ata1.00: status: { DRDY }
[ 80.040250] ata1.00: cmd 61/08:90:c5:b5:f8/00:00:07:00:00/40 tag 18 ncq 4096
out
[ 80.040251] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040252] ata1.00: status: { DRDY }
[ 80.040255] ata1.00: cmd 61/08:98:dd:21:f9/00:00:07:00:00/40 tag 19 ncq 4096
out
[ 80.040256] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040258] ata1.00: status: { DRDY }
[ 80.040260] ata1.00: cmd 61/10:a0:ed:f1:fa/00:00:07:00:00/40 tag 20 ncq 8192
out
[ 80.040261] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040263] ata1.00: status: { DRDY }
[ 80.040266] ata1.00: cmd 61/08:a8:bd:64:f8/00:00:07:00:00/40 tag 21 ncq 4096
out
[ 80.040266] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 80.040268] ata1.00: status: { DRDY }
[ 80.040271] ata1.00
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Just want to add the link to https://wiki.ubuntu.com/KernelTeam/Netconsole which I will also try myself since I might have the same problem (reported in bug 397096). -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
I'll add a 'me too' to this one. Patched up jaunty sysytem used as a Mythtv box. System was fine with a 250GB Seagate Bara which failed. I replaced it with a new 1Tb seagate bara and now get these errors under heavy read load. 2.6.30 doesn't help - I got several errors while the Nvidia installer was running. Just moving through the recordings menu in Mythtv will trigger it - really any thing that generate high disk activity seems to. disk - ST31000528AS 00:1f.2 IDE interface [0101]: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller [8086:2651] (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Giga-byte Technology Device [1458:2651] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
Another "me, too" for this bug. Ubuntu 9.04 64bit - SATA AHCI mode - ext4 fs WD Velociraptor (ext4fs: /, Swap, /Data) WD Caviar Black 1TB (ext4fs: /home) WD 640GB (ext4fs: /Backup) I recently built a new system using an EVGA 760 Classified MB, i7 920cpu, 12GB triple ch DDR3 and 300GB Velociraptor. I installed the OS after setting the BIOS to SATA AHCI mode (needed hot swapping capabilities). Everything worked fine for about 1 month until last night. I was doing a very large (200GB+) grsync backup of my /home partition to my WD640GB backup drive. At some point in the backup the system froze. No combination of keyboard tricks (ctl+alt+backspace, or alt+print screen+REISUB) would restart X or reboot the OS. I had to resort to killing power. On reboot, the one of my BIOS screens reported "Port 00:" during what I will call the AHCI check. The Velociraptor system drive would not boot. When, I went back into the BIOS setup, I saw that the BIOS did not even see the Velociraptor. I assumed the crash and hard power down had corrputed some critical system files. I removed the Velociraptor boot drive and replaced it with a WinXP 64 boot drive (also set for AHCI mode) and was able to boot up a Windows system with no problem. I then tested the Velociraptor with SpinRite 6 and its a good drive. I decided to try and reboot the Ubuntu system by changing the BIOS SATA setting to "IDE" mode. This worked. Ubuntu was able to start after it found a few errors on the / partition, corrected them, and finished booting. Ubuntu 9.04/64 now seems to be working fine in "IDE" mode. After reading through this thread, it seems that I have been bitten by this AHCI bug when I was doing the very large rsync file backup; although, I have to add that this wasn't the first time, I did such a large backup on this new system without problems. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
@stefan, I have already tested the behaviour with the mainline kernels closest to 2.6.27-14 and 2.6.28-11. I have not tested any version after 2.6.28-11. In all this cases, using the ahci module produces the timeouts, but ata_piix works fine. If only i could tell the 2.6.28 kernels to use ata_piix instead of ahci, i'd take the bug as solved through a workaround. If you tell me how i can recover the complete dmesg log from the boot sequence, i'd be happy to provide one. actually, i'd love it if you could explain how can i recover the complete boot mesages that tipically go to tty8 after boot, as the ata timeouts are also printed there and it allows to see at which point in the boot sequence the disk starts to hang. In any case, i'm losing all hope with this bug, and i am still not sure if its not hardware related, but i have tested with smart tools and in windows and the drive seems to behave. thanks for your interest. -- entia non sunt multiplicanda praeter necessitatem -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
> closest to 2.6.27-14 and 2.6.28-11. I have not tested any version > after 2.6.28-11. In all this cases, using the ahci module produces the A mainline kernel farther away (2.6.30) would be of interest as it could show whether this is an issue upstream. > timeouts, but ata_piix works fine. If only i could tell the 2.6.28 > kernels to use ata_piix instead of ahci, i'd take the bug as solved > through a workaround. It looks a bit strange as your lspci looks like ahci and ata_piix are loaded but only ata_piix shows up as being the driver. Reading the code for the ahci driver they have a comment in there that in both modes ahci and ide the controller reports the same ids. So they do a test to see whether to use ahci mode or not. I'd like to check with the lspci command mentioned above and the dmesg what this decision might be. Actually, do you have the ability to change the controller mode in the BIOS or is that hidden? > If you tell me how i can recover the complete dmesg log from the boot > sequence, i'd be happy to provide one. actually, i'd love it if you I would try whether it is possible to save a dmesg on a USB stick, if that is possible. But thats probably prevented by the problems with the disk and the system trying to log the login. Depending on whether you got a second computer, netconsole might be an option. > sure if its not hardware related, but i have tested with smart tools > and in windows and the drive seems to behave. Windows normally would not use the ahci mode by default. And as you say, you have no problems when blacklisting the ahci module. The question would be whether the ahci driver for some reason believes the controller is in ahci mode while it isn't. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
@stefan, I have already tested the behaviour with the mainline kernels closest to 2.6.27-14 and 2.6.28-11. I have not tested any version after 2.6.28-11. In all this cases, using the ahci module produces the timeouts, but ata_piix works fine. If only i could tell the 2.6.28 kernels to use ata_piix instead of ahci, i'd take the bug as solved through a workaround. If you tell me how i can recover the complete dmesg log from the boot sequence, i'd be happy to provide one. actually, i'd love it if you could explain how can i recover the complete boot mesages that tipically go to tty8 after boot, as the ata timeouts are also printed there and it allows to see at which point in the boot sequence the disk starts to hang. In any case, i'm losing all hope with this bug, and i am still not sure if its not hardware related, but i have tested with smart tools and in windows and the drive seems to behave. thanks for your interest. -- entia non sunt multiplicanda praeter necessitatem -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
> closest to 2.6.27-14 and 2.6.28-11. I have not tested any version > after 2.6.28-11. In all this cases, using the ahci module produces the A mainline kernel farther away (2.6.30) would be of interest as it could show whether this is an issue upstream. > timeouts, but ata_piix works fine. If only i could tell the 2.6.28 > kernels to use ata_piix instead of ahci, i'd take the bug as solved > through a workaround. It looks a bit strange as your lspci looks like ahci and ata_piix are loaded but only ata_piix shows up as being the driver. Reading the code for the ahci driver they have a comment in there that in both modes ahci and ide the controller reports the same ids. So they do a test to see whether to use ahci mode or not. I'd like to check with the lspci command mentioned above and the dmesg what this decision might be. Actually, do you have the ability to change the controller mode in the BIOS or is that hidden? > If you tell me how i can recover the complete dmesg log from the boot > sequence, i'd be happy to provide one. actually, i'd love it if you I would try whether it is possible to save a dmesg on a USB stick, if that is possible. But thats probably prevented by the problems with the disk and the system trying to log the login. Depending on whether you got a second computer, netconsole might be an option. > sure if its not hardware related, but i have tested with smart tools > and in windows and the drive seems to behave. Windows normally would not use the ahci mode by default. And as you say, you have no problems when blacklisting the ahci module. The question would be whether the ahci driver for some reason believes the controller is in ahci mode while it isn't. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
@stefan, I have already tested the behaviour with the mainline kernels closest to 2.6.27-14 and 2.6.28-11. I have not tested any version after 2.6.28-11. In all this cases, using the ahci module produces the timeouts, but ata_piix works fine. If only i could tell the 2.6.28 kernels to use ata_piix instead of ahci, i'd take the bug as solved through a workaround. If you tell me how i can recover the complete dmesg log from the boot sequence, i'd be happy to provide one. actually, i'd love it if you could explain how can i recover the complete boot mesages that tipically go to tty8 after boot, as the ata timeouts are also printed there and it allows to see at which point in the boot sequence the disk starts to hang. In any case, i'm losing all hope with this bug, and i am still not sure if its not hardware related, but i have tested with smart tools and in windows and the drive seems to behave. thanks for your interest. -- entia non sunt multiplicanda praeter necessitatem -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
> closest to 2.6.27-14 and 2.6.28-11. I have not tested any version > after 2.6.28-11. In all this cases, using the ahci module produces the A mainline kernel farther away (2.6.30) would be of interest as it could show whether this is an issue upstream. > timeouts, but ata_piix works fine. If only i could tell the 2.6.28 > kernels to use ata_piix instead of ahci, i'd take the bug as solved > through a workaround. It looks a bit strange as your lspci looks like ahci and ata_piix are loaded but only ata_piix shows up as being the driver. Reading the code for the ahci driver they have a comment in there that in both modes ahci and ide the controller reports the same ids. So they do a test to see whether to use ahci mode or not. I'd like to check with the lspci command mentioned above and the dmesg what this decision might be. Actually, do you have the ability to change the controller mode in the BIOS or is that hidden? > If you tell me how i can recover the complete dmesg log from the boot > sequence, i'd be happy to provide one. actually, i'd love it if you I would try whether it is possible to save a dmesg on a USB stick, if that is possible. But thats probably prevented by the problems with the disk and the system trying to log the login. Depending on whether you got a second computer, netconsole might be an option. > sure if its not hardware related, but i have tested with smart tools > and in windows and the drive seems to behave. Windows normally would not use the ahci mode by default. And as you say, you have no problems when blacklisting the ahci module. The question would be whether the ahci driver for some reason believes the controller is in ahci mode while it isn't. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
@stefan, I have already tested the behaviour with the mainline kernels closest to 2.6.27-14 and 2.6.28-11. I have not tested any version after 2.6.28-11. In all this cases, using the ahci module produces the timeouts, but ata_piix works fine. If only i could tell the 2.6.28 kernels to use ata_piix instead of ahci, i'd take the bug as solved through a workaround. If you tell me how i can recover the complete dmesg log from the boot sequence, i'd be happy to provide one. actually, i'd love it if you could explain how can i recover the complete boot mesages that tipically go to tty8 after boot, as the ata timeouts are also printed there and it allows to see at which point in the boot sequence the disk starts to hang. In any case, i'm losing all hope with this bug, and i am still not sure if its not hardware related, but i have tested with smart tools and in windows and the drive seems to behave. thanks for your interest. -- entia non sunt multiplicanda praeter necessitatem -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
> closest to 2.6.27-14 and 2.6.28-11. I have not tested any version > after 2.6.28-11. In all this cases, using the ahci module produces the A mainline kernel farther away (2.6.30) would be of interest as it could show whether this is an issue upstream. > timeouts, but ata_piix works fine. If only i could tell the 2.6.28 > kernels to use ata_piix instead of ahci, i'd take the bug as solved > through a workaround. It looks a bit strange as your lspci looks like ahci and ata_piix are loaded but only ata_piix shows up as being the driver. Reading the code for the ahci driver they have a comment in there that in both modes ahci and ide the controller reports the same ids. So they do a test to see whether to use ahci mode or not. I'd like to check with the lspci command mentioned above and the dmesg what this decision might be. Actually, do you have the ability to change the controller mode in the BIOS or is that hidden? > If you tell me how i can recover the complete dmesg log from the boot > sequence, i'd be happy to provide one. actually, i'd love it if you I would try whether it is possible to save a dmesg on a USB stick, if that is possible. But thats probably prevented by the problems with the disk and the system trying to log the login. Depending on whether you got a second computer, netconsole might be an option. > sure if its not hardware related, but i have tested with smart tools > and in windows and the drive seems to behave. Windows normally would not use the ahci mode by default. And as you say, you have no problems when blacklisting the ahci module. The question would be whether the ahci driver for some reason believes the controller is in ahci mode while it isn't. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
@stefan, I have already tested the behaviour with the mainline kernels closest to 2.6.27-14 and 2.6.28-11. I have not tested any version after 2.6.28-11. In all this cases, using the ahci module produces the timeouts, but ata_piix works fine. If only i could tell the 2.6.28 kernels to use ata_piix instead of ahci, i'd take the bug as solved through a workaround. If you tell me how i can recover the complete dmesg log from the boot sequence, i'd be happy to provide one. actually, i'd love it if you could explain how can i recover the complete boot mesages that tipically go to tty8 after boot, as the ata timeouts are also printed there and it allows to see at which point in the boot sequence the disk starts to hang. In any case, i'm losing all hope with this bug, and i am still not sure if its not hardware related, but i have tested with smart tools and in windows and the drive seems to behave. thanks for your interest. -- entia non sunt multiplicanda praeter necessitatem -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
> closest to 2.6.27-14 and 2.6.28-11. I have not tested any version > after 2.6.28-11. In all this cases, using the ahci module produces the A mainline kernel farther away (2.6.30) would be of interest as it could show whether this is an issue upstream. > timeouts, but ata_piix works fine. If only i could tell the 2.6.28 > kernels to use ata_piix instead of ahci, i'd take the bug as solved > through a workaround. It looks a bit strange as your lspci looks like ahci and ata_piix are loaded but only ata_piix shows up as being the driver. Reading the code for the ahci driver they have a comment in there that in both modes ahci and ide the controller reports the same ids. So they do a test to see whether to use ahci mode or not. I'd like to check with the lspci command mentioned above and the dmesg what this decision might be. Actually, do you have the ability to change the controller mode in the BIOS or is that hidden? > If you tell me how i can recover the complete dmesg log from the boot > sequence, i'd be happy to provide one. actually, i'd love it if you I would try whether it is possible to save a dmesg on a USB stick, if that is possible. But thats probably prevented by the problems with the disk and the system trying to log the login. Depending on whether you got a second computer, netconsole might be an option. > sure if its not hardware related, but i have tested with smart tools > and in windows and the drive seems to behave. Windows normally would not use the ahci mode by default. And as you say, you have no problems when blacklisting the ahci module. The question would be whether the ahci driver for some reason believes the controller is in ahci mode while it isn't. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
@stefan, I have already tested the behaviour with the mainline kernels closest to 2.6.27-14 and 2.6.28-11. I have not tested any version after 2.6.28-11. In all this cases, using the ahci module produces the timeouts, but ata_piix works fine. If only i could tell the 2.6.28 kernels to use ata_piix instead of ahci, i'd take the bug as solved through a workaround. If you tell me how i can recover the complete dmesg log from the boot sequence, i'd be happy to provide one. actually, i'd love it if you could explain how can i recover the complete boot mesages that tipically go to tty8 after boot, as the ata timeouts are also printed there and it allows to see at which point in the boot sequence the disk starts to hang. In any case, i'm losing all hope with this bug, and i am still not sure if its not hardware related, but i have tested with smart tools and in windows and the drive seems to behave. thanks for your interest. -- entia non sunt multiplicanda praeter necessitatem -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 352197] Re: ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too)
> closest to 2.6.27-14 and 2.6.28-11. I have not tested any version > after 2.6.28-11. In all this cases, using the ahci module produces the A mainline kernel farther away (2.6.30) would be of interest as it could show whether this is an issue upstream. > timeouts, but ata_piix works fine. If only i could tell the 2.6.28 > kernels to use ata_piix instead of ahci, i'd take the bug as solved > through a workaround. It looks a bit strange as your lspci looks like ahci and ata_piix are loaded but only ata_piix shows up as being the driver. Reading the code for the ahci driver they have a comment in there that in both modes ahci and ide the controller reports the same ids. So they do a test to see whether to use ahci mode or not. I'd like to check with the lspci command mentioned above and the dmesg what this decision might be. Actually, do you have the ability to change the controller mode in the BIOS or is that hidden? > If you tell me how i can recover the complete dmesg log from the boot > sequence, i'd be happy to provide one. actually, i'd love it if you I would try whether it is possible to save a dmesg on a USB stick, if that is possible. But thats probably prevented by the problems with the disk and the system trying to log the login. Depending on whether you got a second computer, netconsole might be an option. > sure if its not hardware related, but i have tested with smart tools > and in windows and the drive seems to behave. Windows normally would not use the ahci mode by default. And as you say, you have no problems when blacklisting the ahci module. The question would be whether the ahci driver for some reason believes the controller is in ahci mode while it isn't. -- ata timeout exception with ahci libata driver (was with 2.6.28-11, but i confirmed it affewcts previous kernels too) https://bugs.launchpad.net/bugs/352197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
