Bug 10004 - Smartd causes HSM violations on ata_piix
Summary: Smartd causes HSM violations on ata_piix
Status: REJECTED INVALID
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Serial ATA (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Tejun Heo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-16 10:52 UTC by Slava Gorbunov
Modified: 2008-02-20 18:18 UTC (History)
0 users

See Also:
Kernel Version: 2.6.24.1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Slava Gorbunov 2008-02-16 10:52:42 UTC
Latest working kernel version:
Earliest failing kernel version:
Distribution: Gentoo
Hardware Environment: IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02)
Software Environment: smartmontools-5.36
Problem Description:

When smartd starts and initializes device parameters, HSM violation errors are reported. The smartd is configured in the following way:

/dev/sda -d ata -a -o on -R 194 -m root -M daily
(the same parameters for sdb).

When smartd starts, the following is reported to the syslog:

Feb 16 21:39:01 fpfe smartd[10704]: smartd version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Feb 16 21:39:01 fpfe smartd[10704]: Home page is http://smartmontools.sourceforge.net/
Feb 16 21:39:01 fpfe smartd[10704]: Opened configuration file /etc/smartd.conf
Feb 16 21:39:01 fpfe smartd[10704]: Configuration file /etc/smartd.conf parsed.
Feb 16 21:39:01 fpfe smartd[10704]: Device: /dev/sda, opened
Feb 16 21:39:01 fpfe smartd[10704]: Device: /dev/sda, found in smartd database.
Feb 16 21:39:02 fpfe ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:02 fpfe ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 pio 126976 in
Feb 16 21:39:02 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
Feb 16 21:39:02 fpfe ata1.00: status: { DRDY }
Feb 16 21:39:02 fpfe ata1: soft resetting link
Feb 16 21:39:02 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:02 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:02 fpfe ata1: EH complete
Feb 16 21:39:02 fpfe ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:02 fpfe ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 pio 126976 in
Feb 16 21:39:02 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
Feb 16 21:39:02 fpfe ata1.00: status: { DRDY }
Feb 16 21:39:02 fpfe ata1: soft resetting link
Feb 16 21:39:02 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:02 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:02 fpfe ata1: EH complete
Feb 16 21:39:02 fpfe ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:02 fpfe ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 pio 126976 in
Feb 16 21:39:02 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
Feb 16 21:39:02 fpfe ata1.00: status: { DRDY }
Feb 16 21:39:02 fpfe ata1: soft resetting link
Feb 16 21:39:02 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:02 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:02 fpfe ata1: EH complete
Feb 16 21:39:02 fpfe ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:02 fpfe ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 pio 126976 in
Feb 16 21:39:02 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
Feb 16 21:39:02 fpfe ata1.00: status: { DRDY }
Feb 16 21:39:02 fpfe ata1: soft resetting link
Feb 16 21:39:02 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:02 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:02 fpfe ata1: EH complete
Feb 16 21:39:02 fpfe ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:02 fpfe ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 pio 126976 in
Feb 16 21:39:02 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
Feb 16 21:39:02 fpfe ata1.00: status: { DRDY }
Feb 16 21:39:02 fpfe ata1: soft resetting link
Feb 16 21:39:03 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:03 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:03 fpfe ata1: EH complete
Feb 16 21:39:03 fpfe ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:03 fpfe ata1.00: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/00 tag 0 pio 126976 in
Feb 16 21:39:03 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation)
Feb 16 21:39:03 fpfe ata1.00: status: { DRDY }
Feb 16 21:39:03 fpfe ata1: soft resetting link
Feb 16 21:39:03 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:03 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:03 fpfe ata1: EH complete
Feb 16 21:39:03 fpfe sd 0:0:0:0: [sda] 117302879 512-byte hardware sectors (60059 MB)
Feb 16 21:39:03 fpfe sd 0:0:0:0: [sda] Write Protect is off
Feb 16 21:39:03 fpfe sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 16 21:39:03 fpfe sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 16 21:39:03 fpfe sd 0:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
Feb 16 21:39:03 fpfe sd 0:0:1:0: [sdb] Write Protect is off
Feb 16 21:39:03 fpfe sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
Feb 16 21:39:03 fpfe sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 16 21:39:03 fpfe sd 0:0:0:0: [sda] 117302879 512-byte hardware sectors (60059 MB)
Feb 16 21:39:03 fpfe sd 0:0:0:0: [sda] Write Protect is off
Feb 16 21:39:03 fpfe sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 16 21:39:03 fpfe sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 16 21:39:03 fpfe sd 0:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
Feb 16 21:39:03 fpfe sd 0:0:1:0: [sdb] Write Protect is off
Feb 16 21:39:03 fpfe sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
Feb 16 21:39:03 fpfe sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 16 21:39:03 fpfe smartd[10704]: Device: /dev/sda, enable SMART Automatic Offline Testing failed.
Feb 16 21:39:03 fpfe smartd[10704]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
Feb 16 21:39:03 fpfe smartd[10704]: Device: /dev/sdb, opened
Feb 16 21:39:03 fpfe smartd[10704]: Device: /dev/sdb, not found in smartd database.
Feb 16 21:39:03 fpfe ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:03 fpfe ata1.01: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/10 tag 0 pio 126976 in
Feb 16 21:39:03 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/b0 Emask 0x202 (HSM violation)
Feb 16 21:39:03 fpfe ata1.01: status: { DRDY }
Feb 16 21:39:03 fpfe ata1: soft resetting link
Feb 16 21:39:04 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:04 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:04 fpfe ata1: EH complete
Feb 16 21:39:04 fpfe ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:04 fpfe ata1.01: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/10 tag 0 pio 126976 in
Feb 16 21:39:04 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/b0 Emask 0x202 (HSM violation)
Feb 16 21:39:04 fpfe ata1.01: status: { DRDY }
Feb 16 21:39:04 fpfe ata1: soft resetting link
Feb 16 21:39:04 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:04 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:04 fpfe ata1: EH complete
Feb 16 21:39:04 fpfe sd 0:0:0:0: [sda] 117302879 512-byte hardware sectors (60059 MB)
Feb 16 21:39:04 fpfe ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:04 fpfe ata1.01: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/10 tag 0 pio 126976 in
Feb 16 21:39:04 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/b0 Emask 0x202 (HSM violation)
Feb 16 21:39:04 fpfe ata1.01: status: { DRDY }
Feb 16 21:39:04 fpfe ata1: soft resetting link
Feb 16 21:39:04 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:04 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:04 fpfe ata1: EH complete
Feb 16 21:39:04 fpfe sd 0:0:0:0: [sda] Write Protect is off
Feb 16 21:39:04 fpfe sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 16 21:39:04 fpfe ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:04 fpfe ata1.01: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/10 tag 0 pio 126976 in
Feb 16 21:39:04 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/b0 Emask 0x202 (HSM violation)
Feb 16 21:39:04 fpfe ata1.01: status: { DRDY }
Feb 16 21:39:04 fpfe ata1: soft resetting link
Feb 16 21:39:04 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:04 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:04 fpfe ata1: EH complete
Feb 16 21:39:05 fpfe ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:05 fpfe ata1.01: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/10 tag 0 pio 126976 in
Feb 16 21:39:05 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/b0 Emask 0x202 (HSM violation)
Feb 16 21:39:05 fpfe ata1.01: status: { DRDY }
Feb 16 21:39:05 fpfe ata1: soft resetting link
Feb 16 21:39:05 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:05 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:05 fpfe ata1: EH complete
Feb 16 21:39:05 fpfe sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 16 21:39:05 fpfe ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Feb 16 21:39:05 fpfe ata1.01: cmd b0/db:f8:00:4f:c2/00:00:00:00:00/10 tag 0 pio 126976 in
Feb 16 21:39:05 fpfe res 50/00:f8:00:4f:c2/00:00:00:00:00/b0 Emask 0x202 (HSM violation)
Feb 16 21:39:05 fpfe ata1.01: status: { DRDY }
Feb 16 21:39:05 fpfe ata1: soft resetting link
Feb 16 21:39:05 fpfe ata1.00: configured for UDMA/100
Feb 16 21:39:05 fpfe ata1.01: configured for UDMA/100
Feb 16 21:39:05 fpfe ata1: EH complete
Feb 16 21:39:05 fpfe sd 0:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
Feb 16 21:39:05 fpfe sd 0:0:1:0: [sdb] Write Protect is off
Feb 16 21:39:05 fpfe sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
Feb 16 21:39:05 fpfe sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 16 21:39:05 fpfe sd 0:0:0:0: [sda] 117302879 512-byte hardware sectors (60059 MB)
Feb 16 21:39:05 fpfe sd 0:0:0:0: [sda] Write Protect is off
Feb 16 21:39:05 fpfe sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb 16 21:39:05 fpfe sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 16 21:39:05 fpfe sd 0:0:1:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
Feb 16 21:39:05 fpfe sd 0:0:1:0: [sdb] Write Protect is off
Feb 16 21:39:05 fpfe sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
Feb 16 21:39:05 fpfe sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 16 21:39:05 fpfe smartd[10704]: Device: /dev/sdb, enable SMART Automatic Offline Testing failed.
Feb 16 21:39:05 fpfe smartd[10704]: Device: /dev/sdb, is SMART capable. Adding to "monitor" list.
Feb 16 21:39:05 fpfe smartd[10704]: Monitoring 2 ATA and 0 SCSI devices
Feb 16 21:39:06 fpfe smartd[10706]: smartd has fork()ed into background mode. New PID=10706.
Feb 16 21:39:06 fpfe smartd[10706]: file /var/run/smartd.pid written containing PID 10706

Steps to reproduce:
Configure the kernel to use libata driver ata_piix for IDE, compile and boot it, then start smartd.
Comment 1 Bartlomiej Zolnierkiewicz 2008-02-16 11:09:03 UTC
this is libata problem - reassigning
Comment 2 Jim Paris 2008-02-16 16:14:13 UTC
Libata is fine, this is a smartmontools bug fixed in CVS:
http://marc.info/?l=linux-ide&m=118288925701541&w=2
Comment 3 Tejun Heo 2008-02-20 18:18:22 UTC
Rejecting as INVALID.

Note You need to log in before you can comment on or make changes to this bug.