Public bug reported:
Hi,
I can reproduce this bug on various kernels/systems (including Debian
stable, Debian testing and Kubuntu 7.10) and I am a bit unsure, if this
is a SATA driver, a dm-crypt devicemapper or a LVM problem.
After initial booting and with complete (non-network) based installation
of Kubuntu 7.10 drive access works normal. After a few minutes, the
system freezes up completely, showing heaps of SATA errors in the
logfile (see below). After a few extra rounds producing errors, the
drive then reactivates and works normal for as long as I have been using
the system (a few hours). As I said before, this behavior is
reproducible over several kernel versions and Distributions. I am using
a LVM over dm-crypt installation with the following layout:
SCSI1 (0,0,0) #1 primary 67.1 GB ntfs
#2 primary 510 MB ext2 /boot
#3 primary 182.4 GB crypto (sda3_crypt)
Encrypted Volume (sda3_crypt) 182.4 GB Linux device mapper
#1 182.4 GB lvm
LVM VG disk1, LV home 107.4 GB Linux device mapper
#1 107.4 GB ext2 /home
LVM VG disk1, LV swap 2.1 GB Linux device mapper
#1 2.1GB swap swap
LVM VG disk1, LV system 72.9 GB Linux device mapper
#1 72.9 GB ext2 /
Error messages as reported by dmesg:
[ 0.000000] Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc version
4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2))
... cont.
[ 22.606745] ata1: SATA max UDMA/133 cmd 0xf8860480 ctl 0xf88604a0 bmdma
0x0001d400 irq 18
[ 22.606748] ata2: SATA max UDMA/133 cmd 0xf8860580 ctl 0xf88605a0 bmdma
0x0001d408 irq 18
[ 23.071589] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 23.116317] ata1.00: ATA-7: ST3250620NS, 3.AEG, max UDMA/133
[ 23.116319] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32)
[ 23.182879] ata1.00: configured for UDMA/133
[ 23.491089] ata2: SATA link down (SStatus 0 SControl 300)
[ 23.491170] scsi 0:0:0:0: Direct-Access ATA ST3250620NS 3.AE
PQ: 0 ANSI: 5
[ 23.491177] ata1: bounce limit 0xFFFFFFFFFFFFFFFF, segment boundary
0xFFFFFFFF, hw segs 61
... cont.
[ 23.499267] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
[ 23.499277] sd 0:0:0:0: [sda] Write Protect is off
[ 23.499279] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 23.499289] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 23.499322] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
[ 23.499328] sd 0:0:0:0: [sda] Write Protect is off
[ 23.499329] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 23.499337] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 23.499341] sda: sda1 sda2 sda3
[ 23.514090] sd 0:0:0:0: [sda] Attached SCSI disk
[ 23.517291] sd 0:0:0:0: Attached scsi generic sg0 type 0
... cont.
[ 113.972000] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl
0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0
[ 113.972000] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x2
[ 113.972000] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x2
[ 113.972000] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x2
[ 113.972000] ata1: CPB 4: ctl_flags 0x1f, resp_flags 0x2
[ 113.972000] ata1: timeout waiting for ADMA IDLE, stat=0x400
[ 113.972000] ata1: timeout waiting for ADMA LEGACY, stat=0x400
[ 113.972000] ata1.00: exception Emask 0x0 SAct 0x1e SErr 0x200000 action 0x2
frozen
[ 113.972000] ata1.00: cmd 61/00:08:b5:d1:28/02:00:17:00:00/40 tag 1 cdb 0x0
data 262144 out
[ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 113.972000] ata1.00: cmd 61/78:10:b5:d3:28/01:00:17:00:00/40 tag 2 cdb 0x0
data 192512 out
[ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 113.972000] ata1.00: cmd 61/08:18:a5:45:27/00:00:17:00:00/40 tag 3 cdb 0x0
data 4096 out
[ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 113.972000] ata1.00: cmd 60/10:20:15:4e:b9/00:00:1a:00:00/40 tag 4 cdb 0x0
data 8192 in
[ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 114.284000] ata1: soft resetting port
[ 114.440000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 114.572000] ata1.00: configured for UDMA/133
[ 114.576000] ata1: EH complete
[ 114.576000] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
[ 114.576000] sd 0:0:0:0: [sda] Write Protect is off
[ 114.576000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 114.576000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
... cont.
[ 233.248000] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl
0x1501000 status 0x400 next cpb count 0x4 next cpb idx 0x0
[ 233.248000] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x0
[ 233.248000] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0
[ 233.248000] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x0
[ 233.248000] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x0
[ 233.248000] ata1: CPB 4: ctl_flags 0x1f, resp_flags 0x0
[ 233.248000] ata1: timeout waiting for ADMA IDLE, stat=0x400
[ 233.248000] ata1: timeout waiting for ADMA LEGACY, stat=0x400
[ 233.248000] ata1.00: NCQ disabled due to excessive errors
[ 233.248000] ata1.00: exception Emask 0x0 SAct 0x1f SErr 0x0 action 0x2 frozen
[ 233.248000] ata1.00: cmd 60/08:00:25:4a:df/00:00:1a:00:00/40 tag 0 cdb 0x0
data 4096 in
[ 233.248000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 233.248000] ata1.00: cmd 60/10:08:15:4e:b9/00:00:1a:00:00/40 tag 1 cdb 0x0
data 8192 in
[ 233.248000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 233.248000] ata1.00: cmd 61/08:10:a5:45:27/00:00:17:00:00/40 tag 2 cdb 0x0
data 4096 out
[ 233.248000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 233.248000] ata1.00: cmd 61/78:18:b5:d3:28/01:00:17:00:00/40 tag 3 cdb 0x0
data 192512 out
[ 233.248000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 233.248000] ata1.00: cmd 61/00:20:b5:d1:28/02:00:17:00:00/40 tag 4 cdb 0x0
data 262144 out
[ 233.248000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
(timeout)
[ 233.560000] ata1: soft resetting port
[ 233.716000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 233.828000] ata1.00: configured for UDMA/133
[ 233.828000] ata1: EH complete
[ 233.896000] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
[ 233.904000] sd 0:0:0:0: [sda] Write Protect is off
[ 233.904000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 233.920000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
>From there (s)ata runs without further problems.
Steps to reproduce: Install any kernel > 2.6.18 and use a SATA disk with
LVM over dm-crypt as documented above. Make use of disk. Voila.
Please advise what I can do to help narrow down/solve the problem. If it
was me, I'd say this bug is "critical", since I do not know if the drive
access works correctly and thus whether data storage is reliable.
Thank you for your support!
Cheers
Jens
** Affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
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
