The problem *is* related to NCQ, however, I believe it is *not* the drive. I am running into the same problems on a different machine with a SAMSUNG SP2504C SATA drive.
--- snip --- [ 0.000000] Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:05:12 GMT 2007 (Ubuntu 2.6.22-14.46-generic) ... [ 4.936000] sata_nv 0000:00:08.0: version 3.4 [ 4.936000] sata_nv 0000:00:08.0: Using ADMA mode ... [ 800.196000] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 800.196000] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 800.196000] ata1.00: exception Emask 0x0 SAct 0x7ffff SErr 0x200000 action 0x2 frozen [ 800.196000] ata1.00: cmd 61/00:00:1c:03:3c/04:00:1b:00:00/40 tag 0 cdb 0x0 data 524288 out [ 800.196000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 800.196000] ata1.00: cmd 61/00:08:1c:ff:3b/02:00:1b:00:00/40 tag 1 cdb 0x0 data 262144 out [ 800.196000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 800.196000] ata1.00: cmd 61/00:10:1c:01:3c/02:00:1b:00:00/40 tag 2 cdb 0x0 data 262144 out ... [ 918.972000] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 918.972000] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 918.972000] ata1.00: NCQ disabled due to excessive errors [ 918.972000] ata1.00: exception Emask 0x0 SAct 0x1fffff SErr 0x0 action 0x2 frozen [ 918.972000] ata1.00: cmd 60/08:00:f4:75:14/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 in [ 918.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 918.972000] ata1.00: cmd 61/08:08:bc:1e:fe/00:00:1a:00:00/40 tag 1 cdb 0x0 data 4096 out [ 918.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 918.972000] ata1.00: cmd 61/40:10:ac:1d:4a/00:00:1a:00:00/40 tag 2 cdb 0x0 data 32768 out [ 918.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ... [ 919.284000] ata1: soft resetting port [ 919.440000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 919.960000] ata1.00: configured for UDMA/133 [ 919.960000] ata1: EH complete [ 920.056000] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) [ 920.056000] sd 0:0:0:0: [sda] Write Protect is off [ 920.056000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 920.056000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... and the drive is working again. The common denominator here is: both machines use the NForce4 chipset, both use the sata_nv driver and both are trying to use LVM over dm-crypt. I am of course not sure, but it is possible that there might be a bug combining sata_nv, NCQ and LVM mapped devices. I wish someone else would look into this issue. The drive does make funky noises during the error phase, but I am not sure if that is healthy at all. Cheers Jens -- SATA drive freezes when using LVM over dm-crypt https://bugs.launchpad.net/bugs/156669 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
