* Re: sata_promise ata exceptions (2.6.20.6)
@ 2007-04-09 21:33 Mikael Pettersson
2007-04-09 22:02 ` Phil Dibowitz
0 siblings, 1 reply; 20+ messages in thread
From: Mikael Pettersson @ 2007-04-09 21:33 UTC (permalink / raw)
To: phil; +Cc: linux-ide
On Mon, 9 Apr 2007 13:26:54 -0700, Phil Dibowitz wrote:
>On Mon, Apr 09, 2007 at 12:18:09PM +0200, Mikael Pettersson wrote:
>> I've seen reports of issues like these with second-generation
>> Promise SATA chips and SATAII (3Gbps) drives, but this is the
>> first time I've seen any issues with a first-generation chip.
>>
>> 1. Please try 2.6.21-rc6 plus the following two patches:
>> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6
>> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6
>>
>> This probably won't eliminate the errors, but should improve
>> the level of detail in the error messages.
>
>It doesn't appear to have changed much. After a reboot, I have:
>
>ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 frozen
>ata1.00: (port_status 0x20200000)
>ata1.00: cmd c8/00:90:f2:fb:a6/00:00:00:00:00/e0 tag 0 cdb 0x0 data 73728 in
> res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
...
>Any other info I can provide?
The error decodes as:
port_status 0x20200000: Drive Error during Packet Command Cycle
(the drive signalled an error to the controller)
SErr 0x380100: CRC error, Disparity error, 10B-to-8B decoding error,
non-recoverable transient data integrity error.
My conclusion is that the link between the controller and the drive
is corrupting messages. This is almost certainly a hardware problem,
and could be a broken motherboard (you wrote that you hadn't used
the mobo's Promise chip before), bad cables, bad drives, a bad power
supply, or electrical interference.
/Mikael
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-09 21:33 sata_promise ata exceptions (2.6.20.6) Mikael Pettersson
@ 2007-04-09 22:02 ` Phil Dibowitz
2007-04-09 22:42 ` Greg Freemyer
0 siblings, 1 reply; 20+ messages in thread
From: Phil Dibowitz @ 2007-04-09 22:02 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-ide
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
On Mon, Apr 09, 2007 at 11:33:55PM +0200, Mikael Pettersson wrote:
> The error decodes as:
> port_status 0x20200000: Drive Error during Packet Command Cycle
> (the drive signalled an error to the controller)
>
> SErr 0x380100: CRC error, Disparity error, 10B-to-8B decoding error,
> non-recoverable transient data integrity error.
>
> My conclusion is that the link between the controller and the drive
> is corrupting messages. This is almost certainly a hardware problem,
> and could be a broken motherboard (you wrote that you hadn't used
> the mobo's Promise chip before), bad cables, bad drives, a bad power
> supply, or electrical interference.
Mikael,
Thanks for the quick response. I appreciate your help. I guess I'm buying a
SATA PCI card!
Looks like my choice of reasonably-priced known-brands is Highpoint and
Promise (specifically a Highpoint ROCKETRAID1520 or a Promise SATA300 TX4) -
are one of these brands better from a Linux compatibility or hardware-bug
standpoint?
Thanks again.
--
Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-09 22:02 ` Phil Dibowitz
@ 2007-04-09 22:42 ` Greg Freemyer
0 siblings, 0 replies; 20+ messages in thread
From: Greg Freemyer @ 2007-04-09 22:42 UTC (permalink / raw)
To: Phil Dibowitz; +Cc: Mikael Pettersson, linux-ide
On 4/9/07, Phil Dibowitz <phil@ipom.com> wrote:
> Mikael,
>
> Thanks for the quick response. I appreciate your help. I guess I'm buying a
> SATA PCI card!
>
> Looks like my choice of reasonably-priced known-brands is Highpoint and
> Promise (specifically a Highpoint ROCKETRAID1520 or a Promise SATA300 TX4) -
> are one of these brands better from a Linux compatibility or hardware-bug
> standpoint?
>
Quoting an old e-mail from Tejun Heo:
===
I primarily work on sil controllers and ICH7R piix/ahci because I have
access to the hardware and docs. So, those tend to get new features
first and get a lot of testing.
If you're planning on using Port Multiplier, sil3124/32 would be the
best bet ATM.
===
Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
@ 2007-04-16 7:42 Mikael Pettersson
0 siblings, 0 replies; 20+ messages in thread
From: Mikael Pettersson @ 2007-04-16 7:42 UTC (permalink / raw)
To: Tomi.Orava, phil; +Cc: linux-ide, mikpe
On Sun, 15 Apr 2007 23:55:31 -0700, Phil Dibowitz wrote:
> Given that the last one was a hardware issue, I bought a new controller.
> Despite my bad luck, given my price-range promise still seemed to be the =
> one
> with the most good reports, so I went with that. I was going to go with a=
>
> sil, but I couldn't find one..
>
> Anyway, things are MUCH better now... but about once a week, I get:
>
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (port_status 0x00001000)
> ata2.00: cmd c8/00:80:9a:71:d0/00:00:00:00:00/ea tag 0 cdb 0x0 data 65536=
> in
> res 40/00:00:06:4f:c2/00:00:00:00:00/00 Emask 0x24 (host bus err=
> or)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/133
> ata2: EH complete
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't suppo=
> rt
> DPO or FUA
>
>
> It's the same port_status and Emask/SAct/SErr/action each time... only th=
> e
> cmd/res and data change (obviously those would change)...
>
> Can anyone tell me what that means?
port_status 0x00001000 is "host bus timeout", which the manual
defines as the host bus being busy for more than 256 clock cycles
during an ATA I/O transfer.
I have no idea what would cause this error, and I've never
seen it myself.
As long as libata recovers and doesn't downgrade your transfer
speed it shouldn't pose too much of a problem.
/Mikael
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
@ 2007-04-14 9:27 Mikael Pettersson
2007-04-14 12:46 ` Tomi Orava
0 siblings, 1 reply; 20+ messages in thread
From: Mikael Pettersson @ 2007-04-14 9:27 UTC (permalink / raw)
To: Tomi.Orava; +Cc: linux-ide
On Sat, 14 Apr 2007 10:13:12 +0300 (EEST), Tomi Orava wrote:
>I'm currently running with FC6 2990 kernel, which is based on
>2.6.21-rc3-git10 and contains also your 1.5Gbps limit patch and Promise
>Sata300TX4 port enumeration patch (does anybody know what might be the
>reason that port enumeration patch has not been accepted in to main line
>?).
Because that patch hasn't been submitted to linux-ide,
Jeff, or me?
I've seen fairly old discussions about the enumeration
order issue on 4-port cards, but no patches.
/Mikael
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-14 9:27 Mikael Pettersson
@ 2007-04-14 12:46 ` Tomi Orava
0 siblings, 0 replies; 20+ messages in thread
From: Tomi Orava @ 2007-04-14 12:46 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-ide
> On Sat, 14 Apr 2007 10:13:12 +0300 (EEST), Tomi Orava wrote:
>>I'm currently running with FC6 2990 kernel, which is based on
>>2.6.21-rc3-git10 and contains also your 1.5Gbps limit patch and Promise
>>Sata300TX4 port enumeration patch (does anybody know what might be the
>>reason that port enumeration patch has not been accepted in to main line
>>?).
>
> Because that patch hasn't been submitted to linux-ide,
> Jeff, or me?
Hmm, I quess it was submitted only to kernel mailing-list.
> I've seen fairly old discussions about the enumeration
> order issue on 4-port cards, but no patches.
It seems that original patch was written by Milan Kupcevic:
http://lkml.org/lkml/2006/2/24/316
I updated the patch for the more current kernel versions (obvious changes):
--- linux-2.6.20.i686/drivers/ata/sata_promise.c 2007-04-13
16:34:26.000000000 +0300
+++ linux-2.6.20.i686/drivers/ata/sata_promise.c.mod 2007-04-13
16:39:29.000000000 +0300
@@ -928,8 +928,13 @@
/* Fall through */
case board_20319:
probe_ent->n_ports = 4;
- pdc_ata_setup_port(&probe_ent->port[2], base + 0x300, base
+ 0x600);
- pdc_ata_setup_port(&probe_ent->port[3], base + 0x380, base
+ 0x700);
+ // pdc_ata_setup_port(&probe_ent->port[2], base + 0x300,
base + 0x600);
+ // pdc_ata_setup_port(&probe_ent->port[3], base + 0x380,
base + 0x700);
+
+ pdc_ata_setup_port(&probe_ent->port[0], base + 0x380,
base + 0x700);
+ pdc_ata_setup_port(&probe_ent->port[1], base + 0x280,
base + 0x500);
+ pdc_ata_setup_port(&probe_ent->port[2], base + 0x200,
base + 0x400);
+ pdc_ata_setup_port(&probe_ent->port[3], base + 0x300,
base + 0x600);
break;
case board_2057x:
hp->flags |= PDC_FLAG_GEN_II;
--------------------------------------------------------------------
And the above patch seems to work properly on my machine.
00:0e.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA
300 TX4) (rev 02)
Subsystem: Promise Technology, Inc. PDC40718 (SATA 300 TX4)
Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 16
I/O ports at ec00 [size=128]
I/O ports at e000 [size=256]
Memory at fe900000 (32-bit, non-prefetchable) [size=4K]
Memory at fe800000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at fe600000 [disabled] [size=32K]
Capabilities: [60] Power Management version 2
Regards,
Tomi Orava
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
@ 2007-04-13 21:21 Mikael Pettersson
2007-04-14 7:13 ` Tomi Orava
2007-04-19 10:55 ` Tomi Orava
0 siblings, 2 replies; 20+ messages in thread
From: Mikael Pettersson @ 2007-04-13 21:21 UTC (permalink / raw)
To: Tomi.Orava, linux-ide
On Fri, 13 Apr 2007 21:36:41 +0300 (EEST), Tomi Orava wrote:
> Related to my previous tests, it seems that after I changed the order of the
> hard-disks connected to Promise Sata300TX4 the errors followed both of the
> 7200.10 disks. I swapped the power supply and the SATA-cables at the same
> time
> and still get the following kind of errors (and only with 7200.10, _never_
> with
> the older 7200.7 disks):
Thanks. This tells us that it's not a power or cabling issue, but some
kind of interface or programming incompatibility with the 7200.10 disks.
My theory is that either TBG clocking (which drives the SATA interfaces)
or SET FEATURE snooping (which adjusts internal parameters for different
PIO/(U)DMA modes) is borked for SATAII/3Gbps. I hope to have time to
investigate that soon. If you can limit transfer speeds to 1.5Gpbs then
that may provide a workaround for now.
/Mikael
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-13 21:21 Mikael Pettersson
@ 2007-04-14 7:13 ` Tomi Orava
2007-04-19 10:55 ` Tomi Orava
1 sibling, 0 replies; 20+ messages in thread
From: Tomi Orava @ 2007-04-14 7:13 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-ide
Hi,
> Thanks. This tells us that it's not a power or cabling issue, but some
> kind of interface or programming incompatibility with the 7200.10 disks.
>
> My theory is that either TBG clocking (which drives the SATA interfaces)
> or SET FEATURE snooping (which adjusts internal parameters for different
> PIO/(U)DMA modes) is borked for SATAII/3Gbps. I hope to have time to
> investigate that soon. If you can limit transfer speeds to 1.5Gpbs then
> that may provide a workaround for now.
Somehow I think you are on the righ track based on my own test results ie.
the 1.5Gbps limiter doesn't seem to change anything.
I've used your following patch and still get the errors:
--- drivers/ata/sata_promise.c 2007-03-12 16:25:09.000000000 +0200
+++ drivers/ata/sata_promise.c.mod 2007-03-12 16:28:26.000000000 +0200
@@ -349,6 +349,18 @@
writel(tmp, mmio + 0x014);
}
+ /* hack SControl to limit speed to 1.5Gbps */
+ if ((hp->flags & PDC_FLAG_GEN_II) && sata_scr_valid(ap)) {
+ void __iomem *mmio = (void __iomem *) ap->ioaddr.scr_addr;
+ unsigned int tmp1, tmp2;
+
+ tmp1 = readl(mmio + 0x008);
+ tmp2 = (tmp1 & 0xffffff00) | 0x00000011;
+ writel(tmp2, mmio + 0x008);
+ readl(mmio + 0x008); /* flush */
+ printk("%s(port %u): adjusted SControl from 0x%08x to
0x%08x\n", __FUNCTION__, ap->port_no, tmp1, tmp2);
+ }
+
return 0;
}
and it did not change anything in my case. In the beginning I had the
1,5Gbps jumpers connected but I've now been running without the jumpers
(but with the 1,5Gbps sw limit patch) and still get the same errors
I've been wondering if I should boot with the Promise's own driver in
order to see if I can get some configuration to run properly with FC6
system & my current hardware.
I'm currently running with FC6 2990 kernel, which is based on
2.6.21-rc3-git10 and contains also your 1.5Gbps limit patch and Promise
Sata300TX4 port enumeration patch (does anybody know what might be the
reason that port enumeration patch has not been accepted in to main line
?). The reason why I'm not running with 2.6.21-rc6-git1 is that the
EH-subsystem seems to drop the speed o the problematic 7200.10 disks to
the UDMA-33 as a result of the above errors ---> not acceptable for the
moment.
The dmesg shows the following with the FC6 2990 patched kernel:
Linux version 2.6.20-1.2990.alderan (root@alderan.ncircle.nullnet.fi) (gcc
version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 Fri Apr 13 16:57:48 EEST
2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end:
000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end:
00000000000a0000 type: 2
copy_e820_map() start: 00000000000e4000 size: 000000000001c000 end:
0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000007fe40000 end:
000000007ff40000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000007ff40000 size: 0000000000010000 end:
000000007ff50000 type: 3
copy_e820_map() start: 000000007ff50000 size: 00000000000b0000 end:
0000000080000000 type: 4
copy_e820_map() start: 00000000ff7c0000 size: 0000000000840000 end:
0000000100000000 type: 2
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007ff40000 (usable)
BIOS-e820: 000000007ff40000 - 000000007ff50000 (ACPI data)
BIOS-e820: 000000007ff50000 - 0000000080000000 (ACPI NVS)
BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved)
1151MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000ff780
Using x86 segment limits to approximate NX protection
Entering add_active_range(0, 0, 524096) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229376
HighMem 229376 -> 524096
early_node_map[1] active PFN ranges
0: 0 -> 524096
On node 0 totalpages: 524096
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 1760 pages used for memmap
Normal zone: 223520 pages, LIFO batch:31
HighMem zone: 2302 pages used for memmap
HighMem zone: 292418 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP 000F9190, 0014 (r0 ACPIAM)
ACPI: RSDT 7FF40000, 0030 (r1 A M I OEMRSDT 1000602 MSFT 97)
ACPI: FACP 7FF40200, 0081 (r2 A M I OEMFACP 1000602 MSFT 97)
ACPI: DSDT 7FF40350, 373D (r1 A0008 A0008705 705 INTL 2002026)
ACPI: FACS 7FF50000, 0040
ACPI: APIC 7FF40300, 004A (r1 A M I OEMAPIC 1000602 MSFT 97)
ACPI: OEMB 7FF50040, 003F (r1 A M I OEMBIOS 1000602 MSFT 97)
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:10 APIC version 16
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 88000000 (gap: 80000000:7f7c0000)
Built 1 zonelists. Total pages: 520002
Kernel command line: ro root=/dev/md0 selinux=1 single
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c04d4000 soft=c04d3000
PID hash table entries: 4096 (order: 12, 16384 bytes)
Detected 2083.234 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 2071100k/2096384k available (2675k kernel code, 24076k reserved,
987k data, 228k init, 1178880k highmem)
virtual kernel memory layout:
fixmap : 0xfffaa000 - 0xfffff000 ( 340 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB)
lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
.init : 0xc0495000 - 0xc04ce000 ( 228 kB)
.data : 0xc039cd31 - 0xc0493bd4 ( 987 kB)
.text : 0xc0100000 - 0xc039cd31 (2675 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4169.09 BogoMIPS
(lpj=2084548)
Security Framework v1.0.0 initialized
SELinux: Initializing.
SELinux: Starting in permissive mode
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Failure registering Root Plug module with the kernel
selinux_register_security: There is already a secondary security module
registered.
Failure registering Root Plug module with primary security module.
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: After all inits, caps: 0383f3ff c1c3fbff 00000000 00000420 00000000
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) 2800+ stepping 00
Checking 'hlt' instruction... OK.
ACPI: Core revision 20070126
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
0000:00:0f.1: cannot adjust BAR0 (not I/O)
0000:00:0f.1: cannot adjust BAR1 (not I/O)
0000:00:0f.1: cannot adjust BAR2 (not I/O)
0000:00:0f.1: cannot adjust BAR3 (not I/O)
PCI: enabled onboard AC97/MC97 devices
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs *3 4 5 7 10 11 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *10 11 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 7 10 11 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 14 15) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
SCSI subsystem initialized
libata version 2.20 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
report
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
pnp: 00:08: iomem range 0xfec80000-0xfec800ff has been reserved
pnp: 00:08: iomem range 0xfec00000-0xfec00fff has been reserved
pnp: 00:08: iomem range 0xfee00000-0xfee00fff has been reserved
Time: tsc clocksource has been installed.
pnp: 00:08: iomem range 0xfff80000-0xffffffff has been reserved
pnp: 00:09: ioport range 0x480-0x487 has been reserved
pnp: 00:09: ioport range 0xc00-0xc7f has been reserved
pnp: 00:0b: iomem range 0x0-0x9ffff could not be reserved
pnp: 00:0b: iomem range 0xc0000-0xdffff could not be reserved
pnp: 00:0b: iomem range 0xe0000-0xfffff could not be reserved
pnp: 00:0b: iomem range 0x100000-0x7fffffff could not be reserved
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: fb700000-fd8fffff
PREFETCH window: 8ff00000-afefffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 2504k freed
Machine check exception polling timer started.
audit: initializing netlink socket (disabled)
audit(1176490841.453:1): initialized
highmem bounce pool size: 64 pages
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux: Registering netfilter hooks
ksign: Installing public key data
Loading keyring
- Added public key 8EAA7157971B15B5
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PCI: Bypassing VIA 8237 APIC De-Assert Message
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
input: Sleep Button (CM) as /class/input/input2
ACPI: Sleep Button (CM) [SLPB]
Real Time Clock Driver v1.12ac
Non-volatile memory driver v1.2
Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60
sec (nowayout= 1)
Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is
60 seconds).
Hangcheck: Using get_cycles().
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
netconsole: not configured, aborting
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SCSI Media Changer driver v0.25
sata_promise 0000:00:0e.0: version 2.00
ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 17 (level, low) -> IRQ 16
pdc_port_start(port 0): adjusted SControl from 0x00000000 to 0x00000011
ata1: SATA max UDMA/133 cmd 0xf880a380 ctl 0xf880a3b8 bmdma 0x00000000 irq 16
pdc_port_start(port 1): adjusted SControl from 0x00000000 to 0x00000011
ata2: SATA max UDMA/133 cmd 0xf880a280 ctl 0xf880a2b8 bmdma 0x00000000 irq 16
pdc_port_start(port 2): adjusted SControl from 0x00000000 to 0x00000011
ata3: SATA max UDMA/133 cmd 0xf880a200 ctl 0xf880a238 bmdma 0x00000000 irq 16
pdc_port_start(port 3): adjusted SControl from 0x00000000 to 0x00000011
ata4: SATA max UDMA/133 cmd 0xf880a300 ctl 0xf880a338 bmdma 0x00000000 irq 16
scsi0 : sata_promise
Switched to high resolution mode on CPU 0
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: ATA-6: ST3200822AS, 3.01, max UDMA/133
ata1.00: 390721968 sectors, multi 0: LBA48
ata1.00: configured for UDMA/133
scsi1 : sata_promise
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.00: ATA-6: ST3200822AS, 3.01, max UDMA/133
ata2.00: 390721968 sectors, multi 0: LBA48
ata2.00: configured for UDMA/133
scsi2 : sata_promise
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata3.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
scsi3 : sata_promise
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata4.00: ATA-7: ST3500630AS, 3.AAK, max UDMA/133
ata4.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA ST3200822AS 3.01 PQ: 0 ANSI: 5
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sda: sda1 sda2
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access ATA ST3200822AS 3.01 PQ: 0 ANSI: 5
SCSI device sdb: 390721968 512-byte hdwr sectors (200050 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
SCSI device sdb: 390721968 512-byte hdwr sectors (200050 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdb: sdb1 sdb2
sd 1:0:0:0: Attached scsi disk sdb
sd 1:0:0:0: Attached scsi generic sg1 type 0
scsi 2:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdc: sdc1 sdc2
sd 2:0:0:0: Attached scsi disk sdc
sd 2:0:0:0: Attached scsi generic sg2 type 0
scsi 3:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5
SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdd: sdd1 sdd2
sd 3:0:0:0: Attached scsi disk sdd
sd 3:0:0:0: Attached scsi generic sg3 type 0
sata_via 0000:00:0f.0: version 2.1
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 17
sata_via 0000:00:0f.0: routed to hard irq line 10
ata5: SATA max UDMA/133 cmd 0x0001efa0 ctl 0x0001ef7e bmdma 0x0001ee90 irq 17
ata6: SATA max UDMA/133 cmd 0x0001ef68 ctl 0x0001ef66 bmdma 0x0001ee98 irq 17
scsi4 : sata_via
ata5: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
ATA: abnormal status 0x7F on port 0x0001efa7
scsi5 : sata_via
ata6: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
ATA: abnormal status 0x7F on port 0x0001ef6f
pata_via 0000:00:0f.1: version 0.2.1
ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 17
ata7: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001fc00 irq 14
ata8: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001fc08 irq 15
scsi6 : pata_via
ata7.00: ATAPI, max UDMA/66
ata7.00: configured for UDMA/66
scsi7 : pata_via
ATA: abnormal status 0x8 on port 0x00010177
scsi 6:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-4160B A306 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 6:0:0:0: Attached scsi CD-ROM sr0
sr 6:0:0:0: Attached scsi generic sg4 type 5
ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 18
ehci_hcd 0000:00:10.4: EHCI Host Controller
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.4: irq 18, io mem 0xfe700000
ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 18, io base 0x0000eea0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 18, io base 0x0000eec0
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 18, io base 0x0000ef80
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 18
uhci_hcd 0000:00:10.3: UHCI Host Controller
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:10.3: irq 18, io base 0x0000ef40
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usb 2-1: new full speed USB device using uhci_hcd and address 2
usb 2-1: configuration #1 chosen from 1 choice
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
usb 2-1.4: new low speed USB device using uhci_hcd and address 3
usb 2-1.4: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: PC Speaker as /class/input/input3
input: AT Translated Set 2 keyboard as /class/input/input4
I2O subsystem v1.325
i2o: max drivers = 8
I2O Configuration OSM v1.323
I2O Bus Adapter OSM v1.317
I2O Block Device OSM v1.325
I2O SCSI Peripheral OSM v1.316
I2O ProcFS OSM v1.316
i2c /dev entries driver
md: raid1 personality registered for level 1
raid6: int32x1 726 MB/s
raid6: int32x2 890 MB/s
raid6: int32x4 703 MB/s
raid6: int32x8 757 MB/s
raid6: mmxx1 1699 MB/s
raid6: mmxx2 2589 MB/s
raid6: sse1x1 1585 MB/s
raid6: sse1x2 2691 MB/s
raid6: using algorithm sse1x2 (2691 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 5928.000 MB/sec
raid5: using function: pIII_sse (5928.000 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised:
dm-devel@redhat.com
Bluetooth: HCI USB driver ver 2.9
usbcore: registered new interface driver hci_usb
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Regards,
Tomi Orava
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-13 21:21 Mikael Pettersson
2007-04-14 7:13 ` Tomi Orava
@ 2007-04-19 10:55 ` Tomi Orava
1 sibling, 0 replies; 20+ messages in thread
From: Tomi Orava @ 2007-04-19 10:55 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-ide
Hi,
> My theory is that either TBG clocking (which drives the SATA interfaces)
> or SET FEATURE snooping (which adjusts internal parameters for different
> PIO/(U)DMA modes) is borked for SATAII/3Gbps. I hope to have time to
> investigate that soon. If you can limit transfer speeds to 1.5Gpbs then
> that may provide a workaround for now.
For your information, a friend of mine has the exact same SATA-card &
hard-disk combination (Promise Sata300TX4 + 2*Seagate 7200.10) with Intel
P4 & 875P chipset and gets similar error messages every once in a while
when there is above average disk I/O in the system (for example
raid-recheck).
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: cmd 25/00:00:bf:0f:87/00:04:05:00:00/e0 tag 0 cdb 0x0 data 524288 in
res 50/00:00:be:13:87/00:00:05:00:00/e0 Emask 0x1 (device error)
So at least it doesn't seem like my hard-disks or SATA-card are
faulty/broken.
Regards,
Tomi Orava
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
@ 2007-04-09 10:18 Mikael Pettersson
2007-04-09 16:01 ` Phil Dibowitz
` (2 more replies)
0 siblings, 3 replies; 20+ messages in thread
From: Mikael Pettersson @ 2007-04-09 10:18 UTC (permalink / raw)
To: linux-ide, phil
On Sat, 07 Apr 2007 16:41:04 -0700, Phil Dibowitz wrote:
>I've recently moved to a Promise Sata controller with two SATA drives in a
>RAID1 mirror. But I get lots of ata exceptions and the kernel eventually
>slows down my drive to UDMA/33.
>
>It usually happens on ata1 (sda), but sometimes it'll kick in on ata2 (sdb).
>I can definitely cause this to happen more by increasing load on the disks.
>But even low load (checking email) causes this. Full hardware and software
>specs are below, but first, the errors:
>
>ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x180100 action 0x2
>ata1.00: cmd c8/00:d0:8a:31:ae/00:00:00:00:00/e0 tag 0 cdb 0x0 data 106496 in
> res 51/0c:0f:4b:32:ae/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
>ata1: soft resetting port
>ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>ata1.00: configured for UDMA/133
>ata1: EH complete
>SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
>sda: Write Protect is off
>sda: Mode Sense: 00 3a 00 00
>SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
>DPO or FUA
...
>Kernel: 2.6.20.6 (PREEMT & SMP)
>SATA Controller:
> 02:04.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak
> 378/SATA 378) (rev 02)
> Subsystem: ASUSTeK Computer Inc. K8V Deluxe/PC-DL Deluxe motherboard
> Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 16
> I/O ports at df00 [size=64]
> I/O ports at dfa0 [size=16]
> I/O ports at dc00 [size=128]
> Memory at feafe000 (32-bit, non-prefetchable) [size=4K]
> Memory at feac0000 (32-bit, non-prefetchable) [size=128K]
> Capabilities: [60] Power Management version 2
>Drives:
> 2 x Western Digital WD1600JS-00N
I've seen reports of issues like these with second-generation
Promise SATA chips and SATAII (3Gbps) drives, but this is the
first time I've seen any issues with a first-generation chip.
1. Please try 2.6.21-rc6 plus the following two patches:
http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6
http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6
This probably won't eliminate the errors, but should improve
the level of detail in the error messages.
2. Try with a better power supply and verify that cooling is OK.
Also verify that the SATA data and power cables are firmly attached.
We've seen several reports of mysterious issues that eventually
were traced to insufficient power supplies or poorly seated
PCI cards (but in your case the chip is integrated on the mobo).
/Mikael
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-09 10:18 Mikael Pettersson
@ 2007-04-09 16:01 ` Phil Dibowitz
2007-04-09 20:26 ` Phil Dibowitz
2007-04-10 12:49 ` Tomi Orava
2 siblings, 0 replies; 20+ messages in thread
From: Phil Dibowitz @ 2007-04-09 16:01 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-ide
[-- Attachment #1: Type: text/plain, Size: 2021 bytes --]
Mikael Pettersson wrote:
> I've seen reports of issues like these with second-generation
> Promise SATA chips and SATAII (3Gbps) drives, but this is the
> first time I've seen any issues with a first-generation chip.
>
> 1. Please try 2.6.21-rc6 plus the following two patches:
> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6
> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6
>
> This probably won't eliminate the errors, but should improve
> the level of detail in the error messages.
I'll do this tonight and send updated logs, thanks.
> 2. Try with a better power supply and verify that cooling is OK.
> Also verify that the SATA data and power cables are firmly attached.
My power supply is well over-sized for my machine (Antec 480W), so that
shouldn't be a problem. I double checked all my SATA data and power cables.
I also tried switching from SATA-power to PATA-power cables (my drives
support both) to see if that made a difference (it didn't). I've reseated my
cables, switched cable order, etc. to see if I had a bad cable, but no
evidence I do.
> We've seen several reports of mysterious issues that eventually
> were traced to insufficient power supplies or poorly seated
> PCI cards (but in your case the chip is integrated on the mobo).
Understandable. I saw several reports like that on the list, and hence tried
the above.
Thanks for your time, I'll get you updated logs tonight.
--
Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-09 10:18 Mikael Pettersson
2007-04-09 16:01 ` Phil Dibowitz
@ 2007-04-09 20:26 ` Phil Dibowitz
2007-04-10 12:49 ` Tomi Orava
2 siblings, 0 replies; 20+ messages in thread
From: Phil Dibowitz @ 2007-04-09 20:26 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-ide
[-- Attachment #1: Type: text/plain, Size: 3074 bytes --]
On Mon, Apr 09, 2007 at 12:18:09PM +0200, Mikael Pettersson wrote:
> I've seen reports of issues like these with second-generation
> Promise SATA chips and SATAII (3Gbps) drives, but this is the
> first time I've seen any issues with a first-generation chip.
>
> 1. Please try 2.6.21-rc6 plus the following two patches:
> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6
> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6
>
> This probably won't eliminate the errors, but should improve
> the level of detail in the error messages.
It doesn't appear to have changed much. After a reboot, I have:
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 frozen
ata1.00: (port_status 0x20200000)
ata1.00: cmd c8/00:90:f2:fb:a6/00:00:00:00:00/e0 tag 0 cdb 0x0 data 73728 in
res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 frozen
ata1.00: (port_status 0x20200000)
ata1.00: cmd c8/00:88:1a:f5:a6/00:00:00:00:00/e0 tag 0 cdb 0x0 data 69632 in
res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: limiting speed to UDMA/100:PIO4
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2 frozen
ata1.00: (port_status 0x20200000)
ata1.00: cmd c8/00:80:7a:b8:a9/00:00:00:00:00/e0 tag 0 cdb 0x0 data 65536 in
res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
Any other info I can provide?
--
Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-09 10:18 Mikael Pettersson
2007-04-09 16:01 ` Phil Dibowitz
2007-04-09 20:26 ` Phil Dibowitz
@ 2007-04-10 12:49 ` Tomi Orava
2007-04-13 18:36 ` Tomi Orava
2007-04-16 6:55 ` Phil Dibowitz
2 siblings, 2 replies; 20+ messages in thread
From: Tomi Orava @ 2007-04-10 12:49 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-ide, phil
Hi,
I just ran a test with the 2.6.21-rc6-git1 + your patches below
and got the following errors (bottom of the mail). Do you have
any idea what they might be trying to tell ?
My configuration contains Promise Sata300TX4-pci card:
00:0e.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA
300 TX4) (rev 02)
Subsystem: Promise Technology, Inc. PDC40718 (SATA 300 TX4)
Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 16
I/O ports at ec00 [size=128]
I/O ports at e000 [size=256]
Memory at fe900000 (32-bit, non-prefetchable) [size=4K]
Memory at fe800000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at fe600000 [disabled] [size=32K]
Capabilities: [60] Power Management version 2
Asus A7V880 / AMD Athlon XP 2.8MHz
Antec truepower II 550W power supply
2 * Seagate 7200.7 disks 200GB (no errors with these two)
2 * Seagate 7200.10 disks 500GB (these ones generate all the errors)
(jumpered into 3.0Gbs mode)
> I've seen reports of issues like these with second-generation
> Promise SATA chips and SATAII (3Gbps) drives, but this is the
> first time I've seen any issues with a first-generation chip.
>
> 1. Please try 2.6.21-rc6 plus the following two patches:
> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6
> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6
>
> This probably won't eliminate the errors, but should improve
> the level of detail in the error messages.
>
> 2. Try with a better power supply and verify that cooling is OK.
> Also verify that the SATA data and power cables are firmly attached.
>
> We've seen several reports of mysterious issues that eventually
> were traced to insufficient power supplies or poorly seated
> PCI cards (but in your case the chip is integrated on the mobo).
On my system, cooling is OK. The power supply however has been
changed twice because previous Antec supplies have died under stress :(
Regards,
Tomi Orava
-----------------------------------------------------------------------
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (port_status 0x20080000)
ata2.00: cmd c8/00:68:27:ea:7c/00:00:00:00:00/e7 tag 0 cdb 0x0 data 53248 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout)
ata2: soft resetting port
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: configured for UDMA/133
ata2: EH complete
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (port_status 0x20080000)
ata2.00: cmd c8/00:a8:5f:95:87/00:00:00:00:00/e7 tag 0 cdb 0x0 data 86016 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout)
ata2: soft resetting port
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: configured for UDMA/133
ata2: EH complete
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (port_status 0x20080000)
ata2.00: cmd c8/00:00:3f:6f:b3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout)
ata2: soft resetting port
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: configured for UDMA/133
ata2: EH complete
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata2.00: limiting speed to UDMA/100:PIO4
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (port_status 0x20080000)
ata2.00: cmd 25/00:00:2f:2b:b3/00:02:07:00:00/e0 tag 0 cdb 0x0 data 262144 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout)
ata2: soft resetting port
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: configured for UDMA/100
ata2: EH complete
SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
-----------------------------------------------------------
--
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-10 12:49 ` Tomi Orava
@ 2007-04-13 18:36 ` Tomi Orava
2007-04-16 6:55 ` Phil Dibowitz
1 sibling, 0 replies; 20+ messages in thread
From: Tomi Orava @ 2007-04-13 18:36 UTC (permalink / raw)
To: linux-ide
Related to my previous tests, it seems that after I changed the order of the
hard-disks connected to Promise Sata300TX4 the errors followed both of the
7200.10 disks. I swapped the power supply and the SATA-cables at the same
time
and still get the following kind of errors (and only with 7200.10, _never_
with
the older 7200.7 disks):
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: cmd c8/00:08:77:7a:68/00:00:00:00:00/e7 tag 0 cdb 0x0 data 4096 in
res 50/00:00:7e:7a:68/00:00:00:00:00/e7 Emask 0x1 (device error)
ata3.00: configured for UDMA/133
ata3: EH complete
SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata3.00: cmd c8/00:08:57:bb:6a/00:00:00:00:00/e7 tag 0 cdb 0x0 data 4096 in
res 50/00:00:5e:bb:6a/00:00:00:00:00/e7 Emask 0x1 (device error)
ata3.00: configured for UDMA/133
ata3: EH complete
SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: cmd c8/00:20:2f:86:90/00:00:00:00:00/ea tag 0 cdb 0x0 data 16384 in
res 50/00:00:4e:86:90/00:00:00:00:00/ea Emask 0x1 (device error)
ata4.00: configured for UDMA/133
ata4: EH complete
SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: cmd c8/00:50:e7:f3:98/00:00:00:00:00/ea tag 0 cdb 0x0 data 40960 in
res 50/00:00:36:f4:98/00:00:00:00:00/ea Emask 0x1 (device error)
ata4.00: configured for UDMA/133
ata4: EH complete
SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB)
sdd: Write Protect is off
sdd: Mode Sense: 00 3a 00 00
SCSI device sdd: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata4.00: cmd c8/00:48:57:c8:9e/00:00:00:00:00/ea tag 0 cdb 0x0 data 36864 in
res 50/00:00:9e:c8:9e/00:00:00:00:00/ea Emask 0x1 (device error)
ata4.00: configured for UDMA/133
ata4: EH complete
The problems seem to be generated from simple ATA-READ commands:
ATA_CMD_READ = 0xC8,
ATA_CMD_READ_EXT = 0x25,
but I have absolutely no idea what is causing them ... The both disks
have nothing special in their SMART-records:
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 104 100 006 Pre-fail Always
- 6873586
3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always
- 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always
- 11
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always
- 0
7 Seek_Error_Rate 0x000f 076 061 030 Pre-fail Always
- 44625875
9 Power_On_Hours 0x0032 099 099 000 Old_age Always
- 1236
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always
- 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always
- 11
187 Unknown_Attribute 0x0032 100 100 000 Old_age Always
- 0
189 Unknown_Attribute 0x003a 100 100 000 Old_age Always
- 0
190 Unknown_Attribute 0x0022 063 060 045 Old_age Always
- 639631397
194 Temperature_Celsius 0x0022 037 040 000 Old_age Always
- 37 (Lifetime Min/Max 0/27)
195 Hardware_ECC_Recovered 0x001a 076 054 000 Old_age Always
- 194225
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
- 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline
- 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
- 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline
- 0
202 TA_Increase_Count 0x0032 100 253 000 Old_age Always
- 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 1181
-
# 2 Extended offline Completed without error 00% 231
-
Any good ideas from where to search for the solution to this error messages ?
Regards,
Tomi Orava
> I just ran a test with the 2.6.21-rc6-git1 + your patches below
> and got the following errors (bottom of the mail). Do you have
> any idea what they might be trying to tell ?
>
> My configuration contains Promise Sata300TX4-pci card:
>
> 00:0e.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA
> 300 TX4) (rev 02)
> Subsystem: Promise Technology, Inc. PDC40718 (SATA 300 TX4)
> Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 16
> I/O ports at ec00 [size=128]
> I/O ports at e000 [size=256]
> Memory at fe900000 (32-bit, non-prefetchable) [size=4K]
> Memory at fe800000 (32-bit, non-prefetchable) [size=128K]
> Expansion ROM at fe600000 [disabled] [size=32K]
> Capabilities: [60] Power Management version 2
>
> Asus A7V880 / AMD Athlon XP 2.8MHz
> Antec truepower II 550W power supply
> 2 * Seagate 7200.7 disks 200GB (no errors with these two)
> 2 * Seagate 7200.10 disks 500GB (these ones generate all the errors)
> (jumpered into 3.0Gbs mode)
>
>
>> I've seen reports of issues like these with second-generation
>> Promise SATA chips and SATAII (3Gbps) drives, but this is the
>> first time I've seen any issues with a first-generation chip.
>>
>> 1. Please try 2.6.21-rc6 plus the following two patches:
>> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-1-separate-sata-pata-ops-2.6.21-rc6
>> http://user.it.uu.se/~mikpe/linux/patches/2.6/patch-sata_promise-2-error_intr-2.6.21-rc6
>>
>> This probably won't eliminate the errors, but should improve
>> the level of detail in the error messages.
>>
>> 2. Try with a better power supply and verify that cooling is OK.
>> Also verify that the SATA data and power cables are firmly attached.
>>
>> We've seen several reports of mysterious issues that eventually
>> were traced to insufficient power supplies or poorly seated
>> PCI cards (but in your case the chip is integrated on the mobo).
>
> On my system, cooling is OK. The power supply however has been
> changed twice because previous Antec supplies have died under stress :(
>
> Regards,
> Tomi Orava
>
> -----------------------------------------------------------------------
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (port_status 0x20080000)
> ata2.00: cmd c8/00:68:27:ea:7c/00:00:00:00:00/e7 tag 0 cdb 0x0 data 53248
> in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/133
> ata2: EH complete
> SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (port_status 0x20080000)
> ata2.00: cmd c8/00:a8:5f:95:87/00:00:00:00:00/e7 tag 0 cdb 0x0 data 86016
> in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/133
> ata2: EH complete
> SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (port_status 0x20080000)
> ata2.00: cmd c8/00:00:3f:6f:b3/00:00:00:00:00/e7 tag 0 cdb 0x0 data 131072
> in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/133
> ata2: EH complete
> SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> ata2.00: limiting speed to UDMA/100:PIO4
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (port_status 0x20080000)
> ata2.00: cmd 25/00:00:2f:2b:b3/00:02:07:00:00/e0 tag 0 cdb 0x0 data 262144
> in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x6 (timeout)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/100
> ata2: EH complete
> SCSI device sdb: 976773168 512-byte hdwr sectors (500108 MB)
> sdb: Write Protect is off
> sdb: Mode Sense: 00 3a 00 00
> SCSI device sdb: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-10 12:49 ` Tomi Orava
2007-04-13 18:36 ` Tomi Orava
@ 2007-04-16 6:55 ` Phil Dibowitz
2007-04-16 7:02 ` Tomi Orava
1 sibling, 1 reply; 20+ messages in thread
From: Phil Dibowitz @ 2007-04-16 6:55 UTC (permalink / raw)
To: Tomi Orava; +Cc: Mikael Pettersson, linux-ide
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
Given that the last one was a hardware issue, I bought a new controller.
Despite my bad luck, given my price-range promise still seemed to be the one
with the most good reports, so I went with that. I was going to go with a
sil, but I couldn't find one..
Anyway, things are MUCH better now... but about once a week, I get:
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (port_status 0x00001000)
ata2.00: cmd c8/00:80:9a:71:d0/00:00:00:00:00/ea tag 0 cdb 0x0 data 65536 in
res 40/00:00:06:4f:c2/00:00:00:00:00/00 Emask 0x24 (host bus error)
ata2: soft resetting port
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: configured for UDMA/133
ata2: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
It's the same port_status and Emask/SAct/SErr/action each time... only the
cmd/res and data change (obviously those would change)...
Can anyone tell me what that means?
--
Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-16 6:55 ` Phil Dibowitz
@ 2007-04-16 7:02 ` Tomi Orava
2007-04-16 7:47 ` Phil Dibowitz
0 siblings, 1 reply; 20+ messages in thread
From: Tomi Orava @ 2007-04-16 7:02 UTC (permalink / raw)
To: Phil Dibowitz; +Cc: Mikael Pettersson, linux-ide
Hi,
> Given that the last one was a hardware issue, I bought a new controller.
> Despite my bad luck, given my price-range promise still seemed to be the
> one
> with the most good reports, so I went with that. I was going to go with a
> sil, but I couldn't find one..
Unfortunately, I don't have a solution/fix for you, but out of curiosity,
what hard-disks you have problems with ? Also what is the exact model
of your SATA-controller ?
> Anyway, things are MUCH better now... but about once a week, I get:
>
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (port_status 0x00001000)
> ata2.00: cmd c8/00:80:9a:71:d0/00:00:00:00:00/ea tag 0 cdb 0x0 data 65536
> in
> res 40/00:00:06:4f:c2/00:00:00:00:00/00 Emask 0x24 (host bus
> error)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/133
> ata2: EH complete
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't
> support
> DPO or FUA
Regards,
Tomi Orava
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-16 7:02 ` Tomi Orava
@ 2007-04-16 7:47 ` Phil Dibowitz
0 siblings, 0 replies; 20+ messages in thread
From: Phil Dibowitz @ 2007-04-16 7:47 UTC (permalink / raw)
To: Tomi Orava; +Cc: Mikael Pettersson, linux-ide
[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]
Tomi Orava wrote:
> Hi,
>
>> Given that the last one was a hardware issue, I bought a new controller.
>> Despite my bad luck, given my price-range promise still seemed to be the
>> one
>> with the most good reports, so I went with that. I was going to go with a
>> sil, but I couldn't find one..
>
> Unfortunately, I don't have a solution/fix for you, but out of curiosity,
> what hard-disks you have problems with ? Also what is the exact model
> of your SATA-controller ?
Whoops, forgot that bit. Sorry!
02:0c.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA 300
TX4) (rev 02)
Subsystem: Promise Technology, Inc. PDC40718 (SATA 300 TX4)
Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 17
I/O ports at d480 [size=128]
I/O ports at d000 [size=256]
Memory at feafd000 (32-bit, non-prefetchable) [size=4K]
Memory at fea80000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at 50020000 [disabled] [size=32K]
Capabilities: [60] Power Management version 2
My disks are WD WD1600JS 160GB drives (2 of them in linux software RAID 1).
--
Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* sata_promise ata exceptions (2.6.20.6)
@ 2007-04-07 23:41 Phil Dibowitz
2007-04-08 10:43 ` Ansgar Knappheide
0 siblings, 1 reply; 20+ messages in thread
From: Phil Dibowitz @ 2007-04-07 23:41 UTC (permalink / raw)
To: linux-ide
[-- Attachment #1: Type: text/plain, Size: 4385 bytes --]
I've recently moved to a Promise Sata controller with two SATA drives in a
RAID1 mirror. But I get lots of ata exceptions and the kernel eventually
slows down my drive to UDMA/33.
It usually happens on ata1 (sda), but sometimes it'll kick in on ata2 (sdb).
I can definitely cause this to happen more by increasing load on the disks.
But even low load (checking email) causes this. Full hardware and software
specs are below, but first, the errors:
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x180100 action 0x2
ata1.00: cmd c8/00:d0:8a:31:ae/00:00:00:00:00/e0 tag 0 cdb 0x0 data 106496 in
res 51/0c:0f:4b:32:ae/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2
ata1.00: cmd c8/00:a0:12:fa:bc/00:00:00:00:00/e0 tag 0 cdb 0x0 data 81920 in
res 51/0c:1f:93:fa:bc/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: limiting speed to UDMA/100
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2
ata1.00: cmd c8/00:48:2a:27:ac/00:00:00:00:00/e0 tag 0 cdb 0x0 data 36864 in
res 51/0c:27:4b:27:ac/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
ata1.00: limiting speed to UDMA/66
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x180100 action 0x2
ata1.00: cmd c8/00:f8:6a:7a:ae/00:00:00:00:00/e0 tag 0 cdb 0x0 data 126976 in
res 51/0c:97:cb:7a:ae/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/66
ata1: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
Kernel: 2.6.20.6 (PREEMT & SMP)
SATA Controller:
02:04.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak
378/SATA 378) (rev 02)
Subsystem: ASUSTeK Computer Inc. K8V Deluxe/PC-DL Deluxe motherboard
Flags: bus master, 66MHz, medium devsel, latency 96, IRQ 16
I/O ports at df00 [size=64]
I/O ports at dfa0 [size=16]
I/O ports at dc00 [size=128]
Memory at feafe000 (32-bit, non-prefetchable) [size=4K]
Memory at feac0000 (32-bit, non-prefetchable) [size=128K]
Capabilities: [60] Power Management version 2
Drives:
2 x Western Digital WD1600JS-00N
Other Setup Details:
3 software RAID1 mirrors (md0, 1, 2 made up of sd{a,b}1 - 3 respectively)
md3 is an LVM physical group with 2 volumes in it. In other words:
/dev/md0 = /boot
/dev/md1 = swap
/dev/md2 = LVM:
/dev/vg00/root = /
/dev/vg00/home = /home
The sata controller isn't brand new, but it's never been used and is
relatively new. The sata drives and cables are fresh out of the box. Any
help would be greatly appreciated.
--
Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: sata_promise ata exceptions (2.6.20.6)
2007-04-07 23:41 Phil Dibowitz
@ 2007-04-08 10:43 ` Ansgar Knappheide
2007-04-09 6:13 ` Phil Dibowitz
0 siblings, 1 reply; 20+ messages in thread
From: Ansgar Knappheide @ 2007-04-08 10:43 UTC (permalink / raw)
To: Phil Dibowitz; +Cc: linux-ide
Phil Dibowitz schrieb:
> ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x180100 action 0x2
> ata1.00: cmd c8/00:d0:8a:31:ae/00:00:00:00:00/e0 tag 0 cdb 0x0 data 106496 in
> res 51/0c:0f:4b:32:ae/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> ata1: soft resetting port
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2
> ata1.00: cmd c8/00:a0:12:fa:bc/00:00:00:00:00/e0 tag 0 cdb 0x0 data 81920 in
> res 51/0c:1f:93:fa:bc/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> ata1: soft resetting port
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/133
> ata1: EH complete
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> ata1.00: limiting speed to UDMA/100
> ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x380100 action 0x2
> ata1.00: cmd c8/00:48:2a:27:ac/00:00:00:00:00/e0 tag 0 cdb 0x0 data 36864 in
> res 51/0c:27:4b:27:ac/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> ata1: soft resetting port
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/100
> ata1: EH complete
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> ata1.00: limiting speed to UDMA/66
> ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x180100 action 0x2
> ata1.00: cmd c8/00:f8:6a:7a:ae/00:00:00:00:00/e0 tag 0 cdb 0x0 data 126976 in
> res 51/0c:97:cb:7a:ae/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> ata1: soft resetting port
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/66
> ata1: EH complete
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: Write Protect is off
> sda: Mode Sense: 00 3a 00 00
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
>
>
I got similar errors since kernel 2.6.20-xx and the LBA48/EH fix between
2.6.21-rc5-git10 and 2.6.21-rc5-git13 seems to fix it. I'm no developer,
but you should perhaps try kernel 2.6.21-rc5-git13 or later.
Greetings
Ansgar Knappheide
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2007-04-19 10:55 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-04-09 21:33 sata_promise ata exceptions (2.6.20.6) Mikael Pettersson
2007-04-09 22:02 ` Phil Dibowitz
2007-04-09 22:42 ` Greg Freemyer
-- strict thread matches above, loose matches on Subject: below --
2007-04-16 7:42 Mikael Pettersson
2007-04-14 9:27 Mikael Pettersson
2007-04-14 12:46 ` Tomi Orava
2007-04-13 21:21 Mikael Pettersson
2007-04-14 7:13 ` Tomi Orava
2007-04-19 10:55 ` Tomi Orava
2007-04-09 10:18 Mikael Pettersson
2007-04-09 16:01 ` Phil Dibowitz
2007-04-09 20:26 ` Phil Dibowitz
2007-04-10 12:49 ` Tomi Orava
2007-04-13 18:36 ` Tomi Orava
2007-04-16 6:55 ` Phil Dibowitz
2007-04-16 7:02 ` Tomi Orava
2007-04-16 7:47 ` Phil Dibowitz
2007-04-07 23:41 Phil Dibowitz
2007-04-08 10:43 ` Ansgar Knappheide
2007-04-09 6:13 ` Phil Dibowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).