Bug 9102
Summary: | (sata_promise) HSM violation exceptions in combination with network load | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Sebastian Witt (se.witt) |
Component: | Serial ATA | Assignee: | Mikael Pettersson (mikpelinux) |
Status: | REJECTED DOCUMENTED | ||
Severity: | normal | CC: | htejun, jgarzik |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.23-rc8 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | Kernel log |
Description
Sebastian Witt
2007-09-30 07:39:15 UTC
Created attachment 13000 [details]
Kernel log
cc'd Mikael Pettersson for sata_promise. Tested different PCI slots, no change. Also disabling PCI posted write/delayed transaction in the BIOS setup did not help (only decreasing performance). If you can, please try putting the Promise card + disks and the NICs in another machine with a different (preferably newer/better) chipset. I've seen Promise SATA cards trigger the error you mentioned all by itself on some machines, while the same card/cable/disk combination works better in other machines. At this point, I strongly suspect chipset/PCI interaction issues, though I don't know what they might be or if they can be worked around in the driver. I put the cards in a nForce3 based board for testing, so far no messages. By the way, on the VIA based board all PCI devices were on bus 0 (chipset architecture?), on the nForce3 board the PCI slots (external PCI bus) are bus 2. After approx. 20 hours one message showed up: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 ata1.00: port_status 0x20280000 ata1.00: cmd c8/00:10:27:c9:d1/00:00:00:00:00/e1 tag 0 cdb 0x0 data 8192 in res 51/40:0b:2d:c9:d1/00:00:00:00:00/e1 Emask 0xb (HSM violation) ata1: soft resetting port ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: configured for UDMA/133 ata1: EH complete sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA However I can't trigger them intentionally with disk & network load as on the other board. Because I didn't got this message the last weeks after changing the mainboard, it's fixed for me. A hardware erratum in Promise 2nd-generation controllers, like the 300 TX4 mentioned in this bug report, was fixed in kernel 2.6.24-rc2. So if you see any new errors from sata_promise, please first try a 2.6.24-rc2 or newer kernel, and please report whether the newer driver solved the problem. |