Bug 7516
| Summary: | Promise SATA300 TX4 with WD2500KS: "no sense translation" errors | ||
|---|---|---|---|
| Product: | IO/Storage | Reporter: | Gregory Brauer (gbrauer1) |
| Component: | Serial ATA | Assignee: | Tejun Heo (htejun) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | alan, arnova, balleman-osdl, bug, bz, htejun, justin, kernelbugs, mikpelinux, protasnb, Roel.Teuwen, shurick, wschlich |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.19-rc5 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: | add more initialisation quirks to sata_promise | ||
Same problem here.
Most recent kernel where this bug did not occur:
none (happens in 2.6.19-rc5, and also all tested FC5 kernels,
including 2.6.18-1.2239.fc5smp)
Distribution:
Debian GNU/Linux 3.1/Sarge
Hardware Environment:
MSI KT6 (VIA KT600) motherboard with AMD Athlon XP
2x Promise SATA300 TX4 controller card
8x Seagate 7200.7 250Gb HDD's
Software Environment: kernel-2.6.18.3
Problem Description:
I have a system with 2 Promise TX4-300 controllers (but in the past also used
SATA150's with same problem). I also get:
Nov 24 06:25:44 rulhm3 kernel: ata10: no sense translation for status: 0x50
Nov 24 06:25:44 rulhm3 kernel: ata10: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Nov 24 06:25:44 rulhm3 kernel: ata10: status=0x50 { DriveReady SeekComplete }
Nov 25 08:10:10 rulhm3 kernel: ata7: no sense translation for status: 0x50
Nov 25 08:10:10 rulhm3 kernel: ata7: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Nov 25 08:10:10 rulhm3 kernel: ata7: status=0x50 { DriveReady SeekComplete }
I have 8 250Gb Seagate 7200.7 (SATA-1) drives using software RAID6. The errors
only seem to happen with high disk activity. This problem seems to be there
since at least 2.6.13, but I never had any disk/partition corruption, so it
seems like a harmless bug, though it would be nice if it would be fixed by now.
sata_promise just received new error handling code. It probably doesn't fix root cause of the problem but should report the problems better so that it can be diagnosed. Please give a shot at 2.6.20-rc2. (beware, -rc kernel can be unstable) bugme-daemon@bugzilla.kernel.org wrote: > sata_promise just received new error handling code. It probably doesn't fix > root cause of the problem but should report the problems better so that it can > be diagnosed. Please give a shot at 2.6.20-rc2. (beware, -rc kernel can be > unstable) Good stuff. Here are the new error messages: Greg Dec 28 23:56:22 gleep kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 28 23:56:22 gleep kernel: ata3.00: cmd c8/00:08:f8:41:92/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 28 23:56:22 gleep kernel: res 50/00:00:ff:41:92/00:00:00:00:00/e0 Emask 0x1 (device error) Dec 28 23:56:22 gleep kernel: ata3.00: configured for UDMA/133 Dec 28 23:56:22 gleep kernel: ata3: EH complete Dec 28 23:56:22 gleep kernel: SCSI device sdc: 488397168 512-byte hdwr sectors (250059 MB) Dec 28 23:56:22 gleep kernel: sdc: Write Protect is off Dec 28 23:56:22 gleep kernel: SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 28 23:56:27 gleep kernel: ata1.00: limiting speed to UDMA/100 Dec 28 23:56:27 gleep kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 Dec 28 23:56:27 gleep kernel: ata1.00: cmd c8/00:08:48:72:93/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in Dec 28 23:56:27 gleep kernel: res 50/00:00:4f:72:93/00:00:00:00:00/e0 Emask 0x1 (device error) Dec 28 23:56:27 gleep kernel: ata1: soft resetting port Dec 28 23:56:28 gleep kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Dec 28 23:56:28 gleep kernel: ata1.00: configured for UDMA/100 Dec 28 23:56:28 gleep kernel: ata1: EH complete Dec 28 23:56:28 gleep kernel: SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) Dec 28 23:56:28 gleep kernel: sda: Write Protect is off Dec 28 23:56:28 gleep kernel: SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA I had to revert back to kernel 2.6.19, because 2.6.20-rc2 was causing a lot of
disk activity (all disk leds flashing constantly, even when idle) and [ata/0]
was taking a lot of cpu causing the machine to be extremely slow.
With kernel 2.6.19 all is fine again, except for the sense translation messages
flooding syslog.
These are four WD2500KS-00MJB0 drives connected to a Promise Technology, Inc.
PDC40718 (SATA 300 TX4) (rev 02) in software raid5.
With 2.6.19 I constantly see the messages below when accessing the array
intensively :
Dec 31 12:39:01 testbox kernel: ata2: no sense translation for status: 0x50
Dec 31 12:39:01 testbox kernel: ata2: status=0x50 { DriveReady SeekComplete }
Dec 31 12:45:35 testbox kernel: ata1: no sense translation for status: 0x50
Dec 31 12:45:35 testbox kernel: ata1: status=0x50 { DriveReady SeekComplete }
With 2.6.20-rc2 these become the ones below, and the machine is unusable (even
when idle / barely accessed it seems) :
Jan 1 09:55:33 testbox kernel: SCSI device sdd: 488397168 512-byte hdwr sectors
(250059 MB)
Jan 1 09:55:33 testbox kernel: sdd: Write Protect is off
Jan 1 09:55:33 testbox kernel: SCSI device sdd: write cache: enabled, read
cache: enabled, doesn't support DPO or FUA
Jan 1 09:56:43 testbox kernel: res 50/00:00:ef:81:ad/00:00:00:00:00/ed
Emask 0x1 (device error)
Jan 1 09:56:43 testbox kernel: ata1.00: configured for UDMA/133
Jan 1 09:56:43 testbox kernel: ata1: EH complete
Jan 1 09:56:43 testbox kernel: SCSI device sda: 488397168 512-byte hdwr sectors
(250059 MB)
Jan 1 09:56:43 testbox kernel: sda: Write Protect is off
Jan 1 09:56:43 testbox kernel: SCSI device sda: write cache: enabled, read
cache: enabled, doesn't support DPO or FUA
Jan 1 09:58:12 testbox kernel: res 50/00:00:8f:fc:4c/00:00:00:00:00/eb
Emask 0x1 (device error)
Jan 1 09:58:12 testbox kernel: ata4.00: configured for UDMA/133
Jan 1 09:58:12 testbox kernel: ata4: EH complete
Just tested 2.6.20-rc6
All seems ok for a while (though the messages remain.
After a while, the messages change to something like :
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.00: cmd c8/00:68:70:5c:c9/00:00:00:00:00/eb tag 0 cdb 0x0 data 53248 in
res 50/00:00:d7:5c:c9/00:00:00:00:00/eb Emask 0x1 (device error)
ata2.00: configured for UDMA/133
ata2: EH complete
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 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
ata3.00: limiting speed to UDMA/33
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.00: cmd c8/00:50:20:11:c8/00:00:00:00:00/eb tag 0 cdb 0x0 data 40960 in
res 50/00:00:6f:11:c8/00:00:0c:00:00/eb Emask 0x1 (device error)
ata3: soft resetting port
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: configured for UDMA/33
ata3: EH complete
SCSI device sdc: 488397168 512-byte hdwr sectors (250059 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: limiting speed to UDMA/25
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.00: cmd c8/00:18:48:0e:c8/00:00:00:00:00/eb tag 0 cdb 0x0 data 12288 in
res 50/00:00:5f:0e:c8/00:00:0c:00:00/eb Emask 0x1 (device error)
ata3: soft resetting port
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: configured for UDMA/25
ata3: EH complete
SCSI device sdc: 488397168 512-byte hdwr sectors (250059 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
Note the 'limiting speed' messages.
ata/0 takes lots of cpu now and the array/machine becomes unusable.
Reverting to 2.6.19 makes everything ok again, except for the constant sense
translation messages.
The high CPU usage might actually be because of the fallback to PIO mode.
Among the tons of messages is :
ata3.00: limiting speed to PIO4
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
ata3.00: cmd c8/00:30:f0:e6:bb/00:00:00:00:00/eb tag 0 cdb 0x0 data 24576 in
res 50/00:00:1f:e7:bb/00:00:0c:00:00/eb Emask 0x1 (device error)
ata3: soft resetting port
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: configured for PIO4
ata3: EH complete
It seems to want to limit the speed more and more over time :
Jan 27 15:45:48 testbox kernel: ata1.00: limiting speed to UDMA/100
Jan 27 15:47:22 testbox kernel: ata3.00: limiting speed to UDMA/100
Jan 27 15:47:50 testbox kernel: ata3.00: limiting speed to UDMA/66
Jan 27 15:48:20 testbox kernel: ata1.00: limiting speed to UDMA/66
Jan 27 15:49:07 testbox kernel: ata3.00: limiting speed to UDMA/44
Jan 27 15:50:23 testbox kernel: ata3.00: limiting speed to UDMA/33
Jan 27 15:50:24 testbox kernel: ata3.00: limiting speed to UDMA/25
Jan 27 15:50:39 testbox kernel: ata2.00: limiting speed to UDMA/100
Jan 27 15:51:39 testbox kernel: ata1.00: limiting speed to UDMA/44
Jan 27 15:51:52 testbox kernel: ata2.00: limiting speed to UDMA/66
Jan 27 15:51:55 testbox kernel: ata2.00: limiting speed to UDMA/44
Jan 27 15:52:00 testbox kernel: ata1.00: limiting speed to UDMA/33
Jan 27 15:53:04 testbox kernel: ata2.00: limiting speed to UDMA/33
Jan 27 15:53:27 testbox kernel: ata3.00: limiting speed to UDMA/16
Jan 27 15:54:06 testbox kernel: ata2.00: limiting speed to UDMA/25
Jan 27 15:54:26 testbox kernel: ata2.00: limiting speed to UDMA/16
Jan 27 15:54:31 testbox kernel: ata4.00: limiting speed to UDMA/100
Jan 27 15:54:37 testbox kernel: ata3.00: limiting speed to PIO4
Your drive is reporting device errors without specifying why it's raising it. So, libata chooses to speed down the drive after some number of those errors. This seems more like a hardware problem to me. Please apply common hardware debugging methods. * Rewire SATA connectors and power lines one by one and see to which the error conditions are attached. * Wire harddisks to separate power supply and see what happens. * If possible, connect the harddisks to a different controller or computer and make sure they work. I have the same problem. My hardware is:
00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:0a.0 Mass storage controller: Promise Technology, Inc. PDC40718 (SATA 300
TX4) (rev 02)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
(rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
(rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
(rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 200]
(rev a3)
A sample of the messages in my log
Jan 30 23:22:33 enslaved kernel: ata2: no sense translation for status: 0x50
Jan 30 23:22:33 enslaved kernel: ata2: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Jan 30 23:22:33 enslaved kernel: ata2: status=0x50 { DriveReady SeekComplete }
I have three 500GB: 2 x ST3500641AS, 1 x ST3500630AS connected to port 1,2,3. I
have run surface scans on all the disks and they are fine. No random clicks
either. As far as I know, there is no data corruption. However, my logs do fill
up with these messages. So far there have been three instances when this has
made me have to reboot due to the system becoming unresponsive. Not too much
load on this machine. It is just a file server for a single user. Hope this gets
fixed soon.
For some reason, I cant get the driver from promise to compile on FC6. Anyone
have experience with that driver? ulsata2.ko is what it is called I believe.
1. Please try 2.6.20 and report full dmesg. 2. I'll ask Mikael Pettersson who implemented new EH on promise to take a look. Thanks. Thanx. I shall try 2.6.20. Just wanted to add that I seem to be having this problem only when the disk is mounted as rw. When mounted as ro, I havent seen this happen so far. Hope that is useful to someone. Here is a dmesg. Toward the end of the dump, you will notice the multiple mounts of ext3 fs. That is because, I use the disk as ro most of the time, but when I occasionally want to write, I remount it as rw. I am just a lil paranoid about my data integrity. Linux version 2.6.19-1.2895.fc6 (brewbuilder@hs20-bc2-2.build.redhat.com) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:28:18 EST 2007 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000002fff0000 (usable) BIOS-e820: 000000002fff0000 - 000000002fff3000 (ACPI NVS) BIOS-e820: 000000002fff3000 - 0000000030000000 (ACPI data) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) 0MB HIGHMEM available. 767MB LOWMEM available. found SMP MP-table at 000f4d10 Using x86 segment limits to approximate NX protection Entering add_active_range(0, 0, 196592) 0 entries of 256 used Zone PFN ranges: DMA 0 -> 4096 Normal 4096 -> 196592 HighMem 196592 -> 196592 early_node_map[1] active PFN ranges 0: 0 -> 196592 On node 0 totalpages: 196592 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 4064 pages, LIFO batch:0 Normal zone: 1503 pages used for memmap Normal zone: 190993 pages, LIFO batch:31 HighMem zone: 0 pages used for memmap DMI 2.3 present. Using APIC driver default ACPI: RSDP (v000 BIOSTA ) @ 0x000f6770 ACPI: RSDT (v001 BIOSTA AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x2fff3000 ACPI: FADT (v001 BIOSTA AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x2fff3040 ACPI: MADT (v001 BIOSTA AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x2fff6ec0 ACPI: DSDT (v001 BIOSTA AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000 ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:6 APIC version 16 ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 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 40000000 (gap: 30000000:cec00000) Detected 1150.149 MHz processor. Built 1 zonelists. Total pages: 195057 Kernel command line: ro root=/dev/VolGroup00/LogVol00 vga=0x305 selinux=0 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=c0808000 soft=c07e8000 PID hash table entries: 4096 (order: 12, 16384 bytes) Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 771776k/786368k available (2210k kernel code, 14036k reserved, 1135k data, 244k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffc56000 - 0xfffff000 (3748 kB) pkmap : 0xff800000 - 0xffc00000 (4096 kB) vmalloc : 0xf0800000 - 0xff7fe000 ( 239 MB) lowmem : 0xc0000000 - 0xefff0000 ( 767 MB) .init : 0xc07a6000 - 0xc07e3000 ( 244 kB) .data : 0xc0628bff - 0xc07448f4 (1135 kB) .text : 0xc0400000 - 0xc0628bff (2210 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2301.68 BogoMIPS (lpj=1150840) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: After all inits, caps: 0383f3ff c1cbfbff 00000000 00000420 00000000 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed ACPI: Core revision 20060707 CPU0: AMD Athlon(tm) stepping 02 Total of 1 processors activated (2301.68 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 Brought up 1 CPUs sizeof(vma)=84 bytes sizeof(page)=32 bytes sizeof(inode)=424 bytes sizeof(dentry)=144 bytes sizeof(ext3inode)=600 bytes sizeof(buffer_head)=56 bytes sizeof(skbuff)=172 bytes sizeof(task_struct)=1376 bytes checking if image is initramfs... it is Freeing initrd memory: 2266k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfb3f0, last bus=1 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region 4000-407f claimed by vt8235 PM PCI quirk: region 5000-500f claimed by vt8235 SMB Boot video device is 0000:01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *0, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs 21) *0, disabled. ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0, disabled. ACPI: PCI Interrupt Link [ALKD] (IRQs 23) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 11 devices 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 NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default PCI: Bridge: 0000:00:01.0 IO window: disabled. MEM window: d0000000-d7ffffff PREFETCH window: d8000000-dfffffff 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: 9, 2621440 bytes) TCP bind hash table entries: 65536 (order: 8, 1310720 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac) apm: overridden by ACPI. audit: initializing netlink socket (disabled) audit(1170481436.076:1): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring - Added public key A803A00FB8A89D68 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 vesafb: framebuffer at 0xd8000000, mapped to 0xf0880000, using 1536k, total 65536k vesafb: mode is 1024x768x8, linelength=1024, pages=4 vesafb: protected mode interface info at c000:b6f0 vesafb: pmi: set display start = c00cb735, set palette = c00cb7ba vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da vesafb: scrolling: redraw vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0 Console: switching to colour frame buffer device 128x48 fb0: VESA VGA frame buffer device ACPI: Fan [FAN] (on) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Processor [CPU0] (supports 2 throttling states) ACPI: Thermal Zone [THRM] (51 C) isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12ac Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA PM266/KM266 chipset agpgart: AGP aperture is 256M @ 0xc0000000 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller at PCI slot 0000:00:11.1 ACPI: PCI Interrupt Link [ALKA] BIOS reported IRQ 0, using IRQ 20 ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20 ACPI: PCI Interrupt 0000:00:11.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 16 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1 ide0: BM-DMA at 0xe400-0xe407, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xe408-0xe40f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: ST310014A, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: ST310014A, ATA DISK drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 128KiB hda: 20005650 sectors (10242 MB) w/2048KiB Cache, CHS=19846/16/63, UDMA(100) hda: cache flushes supported hda: hda1 hda2 hdc: max request size: 128KiB hdc: 20005650 sectors (10242 MB) w/2048KiB Cache, CHS=19846/16/63, UDMA(100) hdc: cache flushes supported hdc: hdc1 hdc2 hdc3 ide-floppy driver 0.99.newide usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,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 TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 powernow-k8: Processor cpuid 662 not supported Using IPI No-Shortcut mode ACPI: (supports S0 S1 S4 S5) Time: tsc clocksource has been installed. Time: acpi_pm clocksource has been installed. Freeing unused kernel memory: 244k freed Write protecting the kernel read-only data: 416k input: AT Translated Set 2 keyboard as /class/input/input0 logips2pp: Detected unknown logitech mouse model 62 USB Universal Host Controller Interface driver v3.0 ACPI: PCI Interrupt Link [ALKB] BIOS reported IRQ 0, using IRQ 21 ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21 ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17 uhci_hcd 0000:00:10.0: UHCI Host Controller uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:10.0: irq 17, io base 0x0000d800 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17 uhci_hcd 0000:00:10.1: UHCI Host Controller uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:10.1: irq 17, io base 0x0000dc00 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.2[C] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17 uhci_hcd 0000:00:10.2: UHCI Host Controller uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:10.2: irq 17, io base 0x0000e000 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected input: ImExPS/2 Logitech Explorer Mouse as /class/input/input1 ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 17 ehci_hcd 0000:00:10.3: EHCI Host Controller ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4 ehci_hcd 0000:00:10.3: irq 17, io mem 0xe1021000 ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 6 ports detected SCSI subsystem initialized libata version 2.00 loaded. sata_promise 0000:00:0a.0: version 1.04 ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 18 ata1: SATA max UDMA/133 cmd 0xF0836200 ctl 0xF0836238 bmdma 0x0 irq 18 ata2: SATA max UDMA/133 cmd 0xF0836280 ctl 0xF08362B8 bmdma 0x0 irq 18 ata3: SATA max UDMA/133 cmd 0xF0836300 ctl 0xF0836338 bmdma 0x0 irq 18 ata4: SATA max UDMA/133 cmd 0xF0836380 ctl 0xF08363B8 bmdma 0x0 irq 18 scsi0 : sata_promise ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 scsi1 : sata_promise ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32) ata2.00: configured for UDMA/133 scsi2 : sata_promise ata3: SATA link down (SStatus 0 SControl 300) scsi3 : sata_promise ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata4.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32) ata4.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5 SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back sda: sda1 sd 0:0:0:0: Attached scsi disk sda scsi 1:0:0:0: Direct-Access ATA ST3500630AS 3.AA PQ: 0 ANSI: 5 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: drive cache: write back 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: drive cache: write back sdb: sdb1 sd 1:0:0:0: Attached scsi disk sdb scsi 3:0:0:0: Direct-Access ATA ST3500641AS 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: drive cache: write back 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: drive cache: write back sdc: sdc1 sd 3:0:0:0: Attached scsi disk sdc device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: dm-devel@redhat.com kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] NET: Registered protocol family 23 input: PC Speaker as /class/input/input2 via-rhine.c:v1.10-LK1.4.2 Sept-11-2006 Written by Donald Becker ACPI: PCI Interrupt Link [ALKD] BIOS reported IRQ 0, using IRQ 23 ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [ALKD] -> GSI 23 (level, low) -> IRQ 19 eth0: VIA Rhine II at 0xe1022000, 00:e0:4c:86:25:9e, IRQ 19. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 1:0:0:0: Attached scsi generic sg1 type 0 sd 3:0:0:0: Attached scsi generic sg2 type 0 floppy0: no floppy controllers found lp0: using parport0 (interrupt-driven). lp0: console ready sonypi: Sony Programmable I/O Controller Driver v1.26. ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Sleep Button (CM) [SLPB] ibm_acpi: ec object not found md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. device-mapper: multipath: version 1.0.5 loaded EXT3 FS on dm-0, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on hda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Adding 1572856k swap on /dev/VolGroup00/LogVol01. Priority:-1 extents:1 across:1572856k NET: Registered protocol family 10 lo: Disabled Privacy Extensions Mobile IPv6 process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.base_reachable_time; Use net.ipv6.neigh.lo.base_reachable_time_ms instead. eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 eth0: no IPv6 routers present kjournald starting. Commit interval 5 seconds EXT3 FS on hdc2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. ata2: no sense translation for status: 0x50 ata2: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 ata2: status=0x50 { DriveReady SeekComplete } ata2: no sense translation for status: 0x50 ata2: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 ata2: status=0x50 { DriveReady SeekComplete } kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. ata2: no sense translation for status: 0x50 ata2: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 ata2: status=0x50 { DriveReady SeekComplete } kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Upgraded to 2.6.20 kernel. Not seeing these messages anymore. 2 days uptime and everything seems to me ok. Will update if I seen any messages again. Thanx. OK so I just notice the following messages in my 'tail -f /var/log/messages' window. Is it something to be worried about? I have three 500 gig drives connected to the promise card. Feb 21 09:28:16 enslaved kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0action 0x0 Feb 21 09:28:16 enslaved kernel: ata4.00: cmd c8/00:08:9f:a1:47/00:00:00:00:00/e5 tag 0 cdb 0x0 data 4096 in Feb 21 09:28:16 enslaved kernel: res 50/00:00:a6:a1:47/00:00:00:00:00/e5 Emask 0x1 (device error) Feb 21 09:28:16 enslaved kernel: ata4.00: configured for UDMA/133 Feb 21 09:28:16 enslaved kernel: ata4: EH complete Feb 21 09:28:16 enslaved kernel: SCSI device sdd: 976773168 512-byte hdwr sectors (500108 MB) Feb 21 09:28:16 enslaved kernel: sdd: Write Protect is off Feb 21 09:28:16 enslaved kernel: SCSI device sdd: write cache: enabled, read cache: enabled, doesn't support DPO or FUA Here is the entire dmesg output: Linux version 2.6.20-1.2932.fc7 (brewbuilder@hs20-bc2-3.build.redhat.com) (gcc version 4.1.2 20070214 (Red Hat 4.1.2-1)) #1 SMP Thu Feb 15 11:02:47 EST 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: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2 copy_e820_map() start: 0000000000100000 size: 000000002fef0000 end: 000000002fff0000 type: 1 copy_e820_map() type is E820_RAM copy_e820_map() start: 000000002fff0000 size: 0000000000003000 end: 000000002fff3000 type: 4 copy_e820_map() start: 000000002fff3000 size: 000000000000d000 end: 0000000030000000 type: 3 copy_e820_map() start: 00000000fec00000 size: 0000000000001000 end: 00000000fec01000 type: 2 copy_e820_map() start: 00000000fee00000 size: 0000000000001000 end: 00000000fee01000 type: 2 copy_e820_map() start: 00000000ffff0000 size: 0000000000010000 end: 0000000100000000 type: 2 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000002fff0000 (usable) BIOS-e820: 000000002fff0000 - 000000002fff3000 (ACPI NVS) BIOS-e820: 000000002fff3000 - 0000000030000000 (ACPI data) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) 0MB HIGHMEM available. 767MB LOWMEM available. found SMP MP-table at 000f4d10 Using x86 segment limits to approximate NX protection Entering add_active_range(0, 0, 196592) 0 entries of 256 used Zone PFN ranges: DMA 0 -> 4096 Normal 4096 -> 196592 HighMem 196592 -> 196592 early_node_map[1] active PFN ranges 0: 0 -> 196592 On node 0 totalpages: 196592 DMA zone: 52 pages used for memmap DMA zone: 0 pages reserved DMA zone: 4044 pages, LIFO batch:0 Normal zone: 2443 pages used for memmap Normal zone: 190053 pages, LIFO batch:31 HighMem zone: 0 pages used for memmap DMI 2.3 present. Using APIC driver default ACPI: RSDP 000F6770, 0014 (r0 BIOSTA) ACPI: RSDT 2FFF3000, 002C (r1 BIOSTA AWRDACPI 42302E31 AWRD 0) ACPI: FACP 2FFF3040, 0074 (r1 BIOSTA AWRDACPI 42302E31 AWRD 0) ACPI: DSDT 2FFF30C0, 3DDB (r1 BIOSTA AWRDACPI 1000 MSFT 100000C) ACPI: FACS 2FFF0000, 0040 ACPI: APIC 2FFF6EC0, 0054 (r1 BIOSTA AWRDACPI 42302E31 AWRD 0) ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:6 APIC version 16 ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 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 40000000 (gap: 30000000:cec00000) Detected 1150.043 MHz processor. Built 1 zonelists. Total pages: 194097 Kernel command line: ro root=/dev/VolGroup00/LogVol00 vga=0x305 selinux=0 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=c0792000 soft=c0772000 PID hash table entries: 4096 (order: 12, 16384 bytes) Console: colour dummy device 80x25 Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 30 ... MAX_LOCKDEP_KEYS: 2048 ... CLASSHASH_SIZE: 1024 ... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 16384 ... CHAINHASH_SIZE: 8192 memory used by lock dependency info: 1096 kB per task-struct memory footprint: 1200 bytes Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 765140k/786368k available (2124k kernel code, 20676k reserved, 1120k data, 244k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffc56000 - 0xfffff000 (3748 kB) pkmap : 0xff800000 - 0xffc00000 (4096 kB) vmalloc : 0xf0800000 - 0xff7fe000 ( 239 MB) lowmem : 0xc0000000 - 0xefff0000 ( 767 MB) .init : 0xc0730000 - 0xc076d000 ( 244 kB) .data : 0xc06130cf - 0xc072b474 (1120 kB) .text : 0xc0400000 - 0xc06130cf (2124 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2302.22 BogoMIPS (lpj=1151112) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: After all inits, caps: 0383f3ff c1cbfbff 00000000 00000420 00000000 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 11k freed ACPI: Core revision 20070126 CPU0: AMD Athlon(tm) stepping 02 Total of 1 processors activated (2302.22 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 Brought up 1 CPUs sizeof(vma)=84 bytes sizeof(page)=52 bytes sizeof(inode)=564 bytes sizeof(dentry)=156 bytes sizeof(ext3inode)=800 bytes sizeof(buffer_head)=56 bytes sizeof(skbuff)=176 bytes sizeof(task_struct)=2704 bytes NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfb3f0, last bus=1 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) PCI quirk: region 4000-407f claimed by vt8235 PM PCI quirk: region 5000-500f claimed by vt8235 SMB Boot video device is 0000:01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *0 ACPI: PCI Interrupt Link [ALKB] (IRQs 21) *0, disabled. ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0 ACPI: PCI Interrupt Link [ALKD] (IRQs 23) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 11 devices 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 NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default pnp: 00:00: iomem range 0xd1000-0xd3fff has been reserved pnp: 00:00: iomem range 0xf0000-0xf7fff could not be reserved pnp: 00:00: iomem range 0xf8000-0xfbfff could not be reserved pnp: 00:00: iomem range 0xfc000-0xfffff could not be reserved PCI: Bridge: 0000:00:01.0 IO window: disabled. MEM window: d0000000-d7ffffff PREFETCH window: d8000000-dfffffff 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: 65536 (order: 9, 2359296 bytes) TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) TCP: Hash tables configured (established 65536 bind 65536) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 3508k freed apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac) apm: overridden by ACPI. audit: initializing netlink socket (disabled) audit(1171747327.288:1): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring - Added public key D1867D943305748 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 vesafb: framebuffer at 0xd8000000, mapped to 0xf0880000, using 1536k, total 65536k vesafb: mode is 1024x768x8, linelength=1024, pages=4 vesafb: protected mode interface info at c000:b6f0 vesafb: pmi: set display start = c00cb735, set palette = c00cb7ba vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da vesafb: scrolling: redraw vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0 Console: switching to colour frame buffer device 128x48 fb0: VESA VGA frame buffer device ACPI: Fan [FAN] (on) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Processor [CPU0] (supports 2 throttling states) ACPI: Thermal Zone [THRM] (58 C) isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12ac Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected VIA PM266/KM266 chipset agpgart: AGP aperture is 256M @ 0xc0000000 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,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: AT Translated Set 2 keyboard as /class/input/input1 TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 powernow-k8: Processor cpuid 662 not supported Using IPI No-Shortcut mode Time: tsc clocksource has been installed. Time: acpi_pm clocksource has been installed. ACPI: (supports S0 S1 S4 S5) Freeing unused kernel memory: 244k freed Write protecting the kernel read-only data: 830k logips2pp: Detected unknown logitech mouse model 62 USB Universal Host Controller Interface driver v3.0 ACPI: PCI Interrupt Link [ALKB] BIOS reported IRQ 0, using IRQ 21 ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21 ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 16 uhci_hcd 0000:00:10.0: UHCI Host Controller uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1 uhci_hcd 0000:00:10.0: irq 16, io base 0x0000d800 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 16 uhci_hcd 0000:00:10.1: UHCI Host Controller uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:10.1: irq 16, io base 0x0000dc00 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected input: ImExPS/2 Logitech Explorer Mouse as /class/input/input2 ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 16 uhci_hcd 0000:00:10.2: UHCI Host Controller uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:10.2: irq 16, io base 0x0000e000 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [ALKB] -> GSI 21 (level, low) -> IRQ 16 ehci_hcd 0000:00:10.3: EHCI Host Controller ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4 ehci_hcd 0000:00:10.3: irq 16, io mem 0xe1021000 ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 6 ports detected SCSI subsystem initialized libata version 2.10 loaded. pata_via 0000:00:11.1: version 0.2.1 ACPI: PCI Interrupt Link [ALKA] BIOS reported IRQ 0, using IRQ 20 ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20 ACPI: PCI Interrupt 0000:00:11.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 17 ata1: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001e400 irq 14 ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001e408 irq 15 scsi0 : pata_via ata1.00: ATA-6: ST310014A, 3.09, max UDMA/100 ata1.00: 20005650 sectors, multi 16: LBA ata1.00: configured for UDMA/100 scsi1 : pata_via ata2.00: ATA-6: ST310014A, 3.09, max UDMA/100 ata2.00: 20005650 sectors, multi 16: LBA ata2.00: configured for UDMA/100 scsi 0:0:0:0: Direct-Access ATA ST310014A 3.09 PQ: 0 ANSI: 5 SCSI device sda: 20005650 512-byte hdwr sectors (10243 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: 20005650 512-byte hdwr sectors (10243 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 scsi 1:0:0:0: Direct-Access ATA ST310014A 3.09 PQ: 0 ANSI: 5 SCSI device sdb: 20005650 512-byte hdwr sectors (10243 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: 20005650 512-byte hdwr sectors (10243 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 sdb3 sd 1:0:0:0: Attached scsi disk sdb sata_promise 0000:00:0a.0: version 1.05 ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 18 (level, low) -> IRQ 18 ata3: SATA max UDMA/133 cmd 0xf083e200 ctl 0xf083e238 bmdma 0x00000000 irq 18 ata4: SATA max UDMA/133 cmd 0xf083e280 ctl 0xf083e2b8 bmdma 0x00000000 irq 18 ata5: SATA max UDMA/133 cmd 0xf083e300 ctl 0xf083e338 bmdma 0x00000000 irq 18 ata6: SATA max UDMA/133 cmd 0xf083e380 ctl 0xf083e3b8 bmdma 0x00000000 irq 18 scsi2 : sata_promise ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata3.00: ATA-7: ST3500641AS, 3.AAE, 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 3.0 Gbps (SStatus 123 SControl 300) ata4.00: ATA-7: ST3500630AS, 3.AAE, max UDMA/133 ata4.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) ata4.00: configured for UDMA/133 scsi4 : sata_promise ata5: SATA link down (SStatus 0 SControl 300) scsi5 : sata_promise ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata6.00: ATA-7: ST3500641AS, 3.AAE, max UDMA/133 ata6.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) ata6.00: configured for UDMA/133 scsi 2:0:0:0: Direct-Access ATA ST3500641AS 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 sd 2:0:0:0: Attached scsi disk sdc 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 sd 3:0:0:0: Attached scsi disk sdd scsi 5:0:0:0: Direct-Access ATA ST3500641AS 3.AA PQ: 0 ANSI: 5 SCSI device sde: 976773168 512-byte hdwr sectors (500108 MB) sde: Write Protect is off sde: Mode Sense: 00 3a 00 00 SCSI device sde: write cache: enabled, read cache: enabled, doesn't support DPO or FUA SCSI device sde: 976773168 512-byte hdwr sectors (500108 MB) sde: Write Protect is off sde: Mode Sense: 00 3a 00 00 SCSI device sde: write cache: enabled, read cache: enabled, doesn't support DPO or FUA sde: sde1 sd 5:0:0:0: Attached scsi disk sde device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] NET: Registered protocol family 23 input: PC Speaker as /class/input/input3 via-rhine.c:v1.10-LK1.4.2 Sept-11-2006 Written by Donald Becker ACPI: PCI Interrupt Link [ALKD] BIOS reported IRQ 0, using IRQ 23 ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:12.0[A] -> Link [ALKD] -> GSI 23 (level, low) -> IRQ 19 eth0: VIA Rhine II at 0xe1022000, 00:e0:4c:86:25:9e, IRQ 19. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 1:0:0:0: Attached scsi generic sg1 type 0 sd 2:0:0:0: Attached scsi generic sg2 type 0 sd 3:0:0:0: Attached scsi generic sg3 type 0 sd 5:0:0:0: Attached scsi generic sg4 type 0 floppy0: no floppy controllers found lp0: using parport0 (interrupt-driven). lp0: console ready sonypi: Sony Programmable I/O Controller Driver v1.26. No dock devices found. input: Power Button (FF) as /class/input/input4 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input5 ACPI: Power Button (CM) [PWRB] input: Sleep Button (CM) as /class/input/input6 ACPI: Sleep Button (CM) [SLPB] ibm_acpi: ec object not found md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. device-mapper: multipath: version 1.0.5 loaded EXT3 FS on dm-0, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Adding 1572856k swap on /dev/VolGroup00/LogVol01. Priority:-1 extents:1 across:1572856k NET: Registered protocol family 10 lo: Disabled Privacy Extensions Mobile IPv6 process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.lo.retrans_time; Use net.ipv6.neigh.lo.retrans_time_ms instead. eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 eth0: no IPv6 routers present kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata4.00: cmd c8/00:08:9f:a1:47/00:00:00:00:00/e5 tag 0 cdb 0x0 data 4096 in res 50/00:00:a6:a1:47/00:00:00:00:00/e5 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 I dunno. Roel's error seems identical to yours. It could be a driver problem or a hardware problem. I'll ask Mikael again. Thanks. I've just put a 2.6.20.1 vanilla-kernel on my system. Now I don't get the "no-sense in translation"-error anymore (as far as I can see know) but instead I get: Feb 24 15:01:45 rulhm3 kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 24 15:01:45 rulhm3 kernel: ata7.00: cmd 25/00:08:4f:00:4c/00:00:15:00:00/e0 tag 0 cdb 0x0 data 4096 in Feb 24 15:01:45 rulhm3 kernel: res 50/00:00:56:00:4c/00:00:00:00:00/e0 Emask 0x1 (device error) which seems related. One coincidence I noticed: my system also has a VIA chipset. Maybe there is a conflict between the VIA chipset and the Promise TX4 controllers? Created attachment 10550 [details]
add more initialisation quirks to sata_promise
(This is a duplicate of a post I sent to linux-ide a few minutes ago.)
There have been some reports of intermittent errors
with sata_promise, especially with newer disks.
My theory is that the driver isn't initialisating the
controller properly for SATAII 3Gbps transfer speeds.
It would be helpful if people seeing intermittent errors
with sata_promise could do the following:
1. Check if affected disks have jumpers for selecting
between 1.5Gbps and 3Gbps operation, and adjust the
jumpers for 1.5Gbps operation.
This is exactly what happened to me about a year ago:
I replaced an older SATA disk with a new Seagate SATAII
disk on a SATA 300 TX2plus controller, and immediately
started getting errors. Resetting the disk's jumper to
1.5Gbps operation eliminated the problems.
2. Try the patch included below, on top of a 2.6.21-rc1
or newer kernel. This patch ports all initialisation
quirks I could find in Promise's SATAII driver to
sata_promise. I've tested it and the one quirk that does
seem to actually change something is the "phy quality"
reprogramming.
(the patch should be linked on the bugzilla page with a
name like patch-sata_promise-quirks-v1-2.6.21-rc1)
If you find that this patch makes a difference, you can
then test each quirk individually simply by editing the
"#if 1" that precedes the quirk.
/Mikael
Well, at least I'm not using the promise TX4 controllers (I have 2) which SATA-2 disks. I use Seagate Barracude 7200.8 250Gb (ST3250823AS) disks, which are as far as I know SATA-1 (150).... As this machine is a production server I can't simply test things out (unfortunately)... I get the same messages with 3 Samsung drives (2x SP1614C, 1x SP2504C) on a Promise SATAII 150 TX4. Most of the time the translations pop up for the SP2504C drive which is SATA-II capable, but very sporadic they are also printed for one of the SP1614C drives. I jumpered the SP2504C drive for 1.5Gbps operation and also tried the initialisation patch with kernel 2.6.21-rc3 but it makes no difference. The warnings still occur. I experience the same with 2 SAMSUNG HD501LJ SATAII drives connected
to a SATA300 TX4 controller:
--8<--
ata1: SATA max UDMA/133 cmd 0xD0802200 ctl 0xD0802238 bmdma 0x0 irq 11
ata2: SATA max UDMA/133 cmd 0xD0802280 ctl 0xD08022B8 bmdma 0x0 irq 11
ata3: SATA max UDMA/133 cmd 0xD0802300 ctl 0xD0802338 bmdma 0x0 irq 11
ata4: SATA max UDMA/133 cmd 0xD0802380 ctl 0xD08023B8 bmdma 0x0 irq 11
scsi0 : sata_promise
ata1: SATA link down (SStatus 0 SControl 300)
scsi1 : sata_promise
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8, max UDMA7, 976773168 sectors: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
scsi2 : sata_promise
ata3: SATA link down (SStatus 0 SControl 300)
scsi3 : sata_promise
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-8, max UDMA7, 976773168 sectors: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4
sd 1:0:0:0: Attached scsi disk sda
sd 1:0:0:0: Attached scsi generic sg0 type 0
scsi 3:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
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: drive cache: write back
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: drive cache: write back
sdb: sdb1 sdb2 sdb3 sdb4
sd 3:0:0:0: Attached scsi disk sdb
sd 3:0:0:0: Attached scsi generic sg1 type 0
pata_via 0000:00:11.1: version 0.1.14
ata5: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0xCC00 irq 14
ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xCC08 irq 15
scsi4 : pata_via
ata5.00: ATAPI, max MWDMA2
ata5.01: ATAPI, max MWDMA2
ata5.00: configured for MWDMA2
ata5.01: configured for MWDMA2
scsi5 : pata_via
ATA: abnormal status 0x8 on port 0x177
scsi 4:0:0:0: CD-ROM SAMSUNG CD-ROM SC-152C C300 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 1x/52x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
sr 4:0:0:0: Attached scsi generic sg2 type 5
scsi 4:0:1:0: CD-ROM LITE-ON LTR-16102B OS0B PQ: 0 ANSI: 5
sr1: scsi3-mmc drive: 100x/40x writer cd/rw xa/form2 cdda tray
sr 4:0:1:0: Attached scsi CD-ROM sr1
sr 4:0:1:0: Attached scsi generic sg3 type 5
[...]
ata2: no sense translation for status: 0x50
ata2: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
ata2: status=0x50 { DriveReady SeekComplete }
ata4: no sense translation for status: 0x50
ata4: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
ata4: status=0x50 { DriveReady SeekComplete }
--8<--
The SATA300 TX4 package contained 4 SATA cables of which I used 2 to connect the 2 drives. After I replaced the 2 in-use cables by the other 2 ones, the kernel logged many many more errors (of the same kind). I had some foxconn SATA cables lying around, so I tried those. Not a single error message so far. Currently running... stress --io 2 --hdd 10 --hdd-bytes 10G --timeout 3600s ...to stress the disks a little :) Everything is still fine. I can't remember I did something different when connecting the 3 pairs of SATA cables in question, so I must assume those Promise SATA cables are just a pile of shi...ny stuff :) I've put the card and the three drives in an older PII board with SR440BX chipset. I connected the drives with the same cables and used the PSU as before. And I got none of these "sense translation" messages anymore. Even hdparm showed up a higher buffered disk read rate. I get the messages on an Athlon XP board with Via KT400 chipset. I will soon test a board with nforce2. Hmm, just a day after my last post, it started happening again:
--8<--
2007-03-21 20:40:35 +01:00; hannibal; kern.warning; kernel: ata2: no sense
translation for status: 0x50
2007-03-21 20:40:35 +01:00; hannibal; kern.err; kernel: ata2: translated ATA
stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
2007-03-21 20:40:35 +01:00; hannibal; kern.warning; kernel: ata2: status=0x50 {
DriveReady SeekComplete }
2007-03-21 20:41:11 +01:00; hannibal; kern.warning; kernel: ata4: no sense
translation for status: 0x50
2007-03-21 20:41:11 +01:00; hannibal; kern.err; kernel: ata4: translated ATA
stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
2007-03-21 20:41:11 +01:00; hannibal; kern.warning; kernel: ata4: status=0x50 {
DriveReady SeekComplete }
2007-03-21 21:17:39 +01:00; hannibal; kern.warning; kernel: ata2: no sense
translation for status: 0x50
2007-03-21 21:17:39 +01:00; hannibal; kern.err; kernel: ata2: translated ATA
stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
2007-03-21 21:17:39 +01:00; hannibal; kern.warning; kernel: ata2: status=0x50 {
DriveReady SeekComplete }
2007-03-21 21:36:05 +01:00; hannibal; kern.warning; kernel: ata2: no sense
translation for status: 0x50
2007-03-21 21:36:05 +01:00; hannibal; kern.err; kernel: ata2: translated ATA
stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
2007-03-21 21:36:05 +01:00; hannibal; kern.warning; kernel: ata2: status=0x50 {
DriveReady SeekComplete }
2007-03-23 03:12:28 +01:00; hannibal; kern.warning; kernel: ata4: no sense
translation for status: 0x50
2007-03-23 03:12:28 +01:00; hannibal; kern.err; kernel: ata4: translated ATA
stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
2007-03-23 03:12:28 +01:00; hannibal; kern.warning; kernel: ata4: status=0x50 {
DriveReady SeekComplete }
2007-03-25 03:11:09 +02:00; hannibal; kern.warning; kernel: ata4: no sense
translation for status: 0x50
2007-03-25 03:11:09 +02:00; hannibal; kern.err; kernel: ata4: translated ATA
stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00
2007-03-25 03:11:09 +02:00; hannibal; kern.warning; kernel: ata4: status=0x50 {
DriveReady SeekComplete }
--8<--
But still very strange that a change of the cables fixed it in the
first place.
Anyway, this is an old VIA C3 800MHz on an old Chaintech mainboard
with a VIA chipset (I hate those anyway).
This is now gonna be replaced by a Celeron D347 on a Gigabyte
mainboard with Intel 945 chipset and onboard SATA-II.
Just moved my disks + TX4 controllers (I use 2 to build an 8-disk RAID6 array)
to a new system, with a new motherboard (Intel 945 + Pentium4 CPU). I did some
testing to see whether the problem has something to do with the previous
VIA-based motherboard, but again I get:
ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata5.00: cmd c8/00:00:3f:6b:c9/00:00:00:00:00/e6 tag 0 cdb 0x0 data 131072 in
res 50/00:00:3e:6c:c9/00:00:00:00:00/e6 Emask 0x1 (device error)
ata5.00: configured for UDMA/133
ata5: EH complete
So it seems that the problem is really in the TX4 itself, and not some
compatibility issue with ie. the motherboard....
Arno, the message you posted is completely different from the "no sense translation" message(s) this bug is about. Wolfram, I also noticed this BUT this is the error instead since I use kernel 2.6.20. So where I previously got the "no sense in translation"-messages, I know get the "device error"-messages. And I'm 99.9% that it is triggered by the same issue, but just shown in another way because of the new EH in 2.6.20+.... I was previously using a via chipset based motherboard when I was experiencing these problems. I switched to an intel 440BX motherboard and I am no longer experiencing these error messages. I have been using the 440 BX motherboard for about 2 weeks now. I have head that the via chipset mobos perform really bad on DMA. Could this have been an issue? I am the original reporter, and I can confirm that on 2.6.20(-1.3207.fc5smp) that the error messages for the two problem drives on my SATA300 TX4 have now changed to: Apr 21 04:15:46 gleep kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 21 04:15:46 gleep kernel: ata3.00: cmd c8/00:08:70:1d:d4/00:00:00:00:00/eb tag 0 cdb 0x0 data 4096 in Apr 21 04:15:46 gleep kernel: res 50/00:00:77:1d:d4/00:00:7f:c1:1f/eb Emask 0x1 (device error) Apr 21 04:15:46 gleep kernel: ata3.00: configured for UDMA/133 Apr 21 04:15:46 gleep kernel: ata3: EH complete Apr 21 04:15:46 gleep kernel: SCSI device sdc: 488397168 512-byte hdwr sectors (250059 MB) Apr 21 04:15:46 gleep kernel: sdc: Write Protect is off Apr 21 04:15:46 gleep kernel: SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 22 03:11:02 gleep kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 22 03:11:02 gleep kernel: ata1.00: cmd c8/00:08:30:f2:a5/00:00:00:00:00/ed tag 0 cdb 0x0 data 4096 in Apr 22 03:11:02 gleep kernel: res 50/00:00:37:f2:a5/00:00:0f:91:a6/ed Emask 0x1 (device error) Apr 22 03:11:02 gleep kernel: ata1.00: configured for UDMA/133 Apr 22 03:11:02 gleep kernel: ata1: EH complete Apr 22 03:11:02 gleep kernel: SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) Apr 22 03:11:02 gleep kernel: sda: Write Protect is off Apr 22 03:11:02 gleep kernel: SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA These error messages appear somewhat less frequently (a few times a day instead of a few times an hour under my normal use) than the original errors appeared on the 2.6.19 kernel. I moved my Promise SATAII 150 TX4 controller with the three Samsung drives (2x SP1614C, 1x SP2504C) from a KT400 to a nForce2 based board and never saw these messages again. Furthermore hdparm gives me a "buffered disk read"-rate of 70MB/s, before I got only around 30MB/s. Cached read speed is nearly the same. I also have the feeling that the performance is much better, no big latencies on heavy I/O anymore. Hi, I have this hardware configuration : VT400 + promise 300TX2 + 2xWD2500KS, and both disks report the same message "no sense translation for status: 0x50". Since kernel 2.6.18 it is worst : each time fsck executes i get many "Buffer I/O error on device sdaX, logical block XXXX". The block numbers are completely random, each time I run fsck it reports some different blocks. If I switch back to 2.6.17, I don't have the I/O errors any more and fsck completes normally (but i still have the "no sense translation..." messages). Distribution : Debian Etch. Just after sending the previous message i plugged the "SATA/150 operation only" jumpers into both disks (as proposed in comment #15) and it solved my problem, no more error message. Thanks to Mikael. Same problems on Debian Etch:
Jul 4 22:58:46 xen kernel: ata3: port reset, p_is 8000000 is 4 pis 0 cmd 4017 tf d0 ss 123 se 80000
Jul 4 22:58:46 xen kernel: ata3: status=0x50 { DriveReady SeekComplete }
Jul 4 22:58:46 xen kernel: sdb: Current: sense key: No Sense
Jul 4 22:58:46 xen kernel: Additional sense: No additional sense information
Uname: Linux xen 2.6.17-2-xen-amd64 #1 SMP Wed Sep 13 18:35:45 CEST 2006 x86_64 GNU/Linux
3x500 Gb WD drives connected to a Tyan Tempest i5000VF S5370 mainboard using the SATA II ports on board.
Messages appear when drives (they show up for all three drives intermittently) are under load. Using DM for RAID5 with LVM2 and ext3.
Will try notching down the speed, but would rather see this fixed.
What is the status on this problem? Have you tested with latest kernel, 2.6.22 as of today? Thanks. On one of my machine's that (previously) had the problem (although note quite easy to reproduce), I installed kernel 2.6.22.1 about 2 weeks ago. The problem always occurred in the weekends, when the backups are made because then there's a a lot of read/write activity (I guess). But for 2 weekends now I haven't seen the notorious error messages in my kernel messages. So it *seems* this problem was fixed in 2.6.22. As a lot was changed in sata_promise in 2.6.22, I'm still wondering what actually fixed this issue. Note that if the problem does somehow reoccur, I'll post it ASAP here (of course). Thanks for reporting. Closing for now. Please reopen if the problem shows up again. Thanks. Arno reports the problem is still there. Reopening. NOTE: There's no immediate action to take at the moment. Mikael says 2.6.24-rc2 has related fixes. I'll set the status to NEEDINFO until Arno acks or nacks the fix. These are the errors I'm currently still getting: Nov 3 15:35:50 rulhm3 kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 Nov 3 15:35:50 rulhm3 kernel: ata8.00: (port_status 0x20080000) Nov 3 15:35:50 rulhm3 kernel: ata8.00: cmd c8/00:08:47:55:25/00:00:00:00:00/e4 tag 0 cdb 0x0 data 4096 in Nov 3 15:35:50 rulhm3 kernel: res 50/00:00:4e:55:25/00:00:00:00:00/e4 Emask 0x2 (HSM violation) Nov 10 04:45:26 rulhm3 kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 Nov 10 04:45:26 rulhm3 kernel: ata8.00: (port_status 0x20080000) Nov 10 04:45:26 rulhm3 kernel: ata8.00: cmd c8/00:08:3f:03:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in Nov 10 04:45:26 rulhm3 kernel: res 50/00:00:46:03:00/00:00:00:00:00/e0 Emask 0x2 (HSM violation) Nov 3 15:35:50 rulhm3 kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 Nov 3 15:35:50 rulhm3 kernel: ata8.00: (port_status 0x20080000) Nov 3 15:35:50 rulhm3 kernel: ata8.00: cmd c8/00:08:47:55:25/00:00:00:00:00/e4 tag 0 cdb 0x0 data 4096 in Nov 3 15:35:50 rulhm3 kernel: res 50/00:00:4e:55:25/00:00:00:00:00/e4 Emask 0x2 (HSM violation) Sep 29 03:10:40 rulhm3 kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 Sep 29 03:10:40 rulhm3 kernel: ata6.00: (port_status 0x20080000) Sep 29 03:10:40 rulhm3 kernel: ata6.00: cmd c8/00:08:2f:24:8b/00:00:00:00:00/e7 tag 0 cdb 0x0 data 4096 in Sep 29 03:10:40 rulhm3 kernel: res 50/00:00:36:24:8b/00:00:00:00:00/e7 Emask 0x2 (HSM violation) As soon as 2.6.24-final is released I will retest, to see whether it got fixed. Unfortunately I can't do this anytime sooner as this is a production server. Just before I had the chance to install/boot the new 2.6.24 kernel on my system my filesystem got corrupted. I'm about 99% sure that it is related to this problem. I do wonder whether the fixes in 2.6.24 will fix my problem as the fixes in there (as far as I can see / checked the changelog) only apply for 2nd generation TX4 controllers (with the ASIC bug). I *believe* the controllers I use are 1st generation conntrollers as they are "PDC20518/PDC40518 (SATAII 150 TX4) (rev 02)" (according to lspci). Can someone confirm whether my controllers are actually affected by this "ASIC bug" ? (In reply to comment #39) > Just before I had the chance to install/boot the new 2.6.24 kernel on my > system > my filesystem got corrupted. I'm about 99% sure that it is related to this > problem. I do wonder whether the fixes in 2.6.24 will fix my problem as the > fixes in there (as far as I can see / checked the changelog) only apply for > 2nd > generation TX4 controllers (with the ASIC bug). I *believe* the controllers I > use are 1st generation conntrollers as they are "PDC20518/PDC40518 (SATAII > 150 > TX4) (rev 02)" (according to lspci). Can someone confirm whether my > controllers > are actually affected by this "ASIC bug" ? Your controllers ARE 2nd-generation and thus are afflicted by the ASIC bug. I've just recovered my filesystem and installed vanilla kernel 2.6.24 on the affected system. Hopefully this will fix the problem. I will keep an eye on it the forthcoming weeks and let you know whether the issue is actually fixed. One final question: I also have another system with 2 other distinct TX4 controllers. An "PDC40718 (SATA 300 TX4) (rev 02)" and an "PDC20319 (FastTrak S150 TX4) (rev 02)". I don't know whether the "rev 02" means "generation 2", I assume not. Therefor could please tell me whether these are also "generation 2" controllers and thus afflicted by the ASIC-bug". (In reply to comment #41) > I've just recovered my filesystem and installed vanilla kernel 2.6.24 on the > affected system. Hopefully this will fix the problem. I will keep an eye on > it > the forthcoming weeks and let you know whether the issue is actually fixed. > > One final question: I also have another system with 2 other distinct TX4 > controllers. An "PDC40718 (SATA 300 TX4) (rev 02)" and an "PDC20319 (FastTrak > S150 TX4) (rev 02)". > > I don't know whether the "rev 02" means "generation 2", I assume not. > Therefor > could please tell me whether these are also "generation 2" controllers and > thus > afflicted by the ASIC-bug". The 40718 is 2nd-generation and afflicted, the 20319 is 1st-generation and is believed not to have the bug. Uhm, what is that "ASIC hardware bug" you're talking about?! I stumbled over this: Patch RFC: Promise SATA300 TX4 hardware bug workaround. http://lists.freebsd.org/pipermail/freebsd-hackers/2007-November/022112.html Is that it? Here's another thread from LKML where Alexander Sabourenkov was reporting a/the problem: http://lkml.org/lkml/2007/10/1/50 Ok, I sent a mail to Alexander Sabourenkov requesting some more details about the PRD/DMA issue. He responded: --8<-- The patch was merged into versions 2.6.22.19, 2.6.23.15 and 2.6.24. --8<-- My system has been running now for about 3 months, with NO further problems :-D It seems that the problem has been fixed, so this bug can be closed as far as I am concerned.... |
Most recent kernel where this bug did not occur: none (happens in 2.6.19-rc5, and also all tested FC5 kernels, including 2.6.18-1.2239.fc5smp) Distribution: Fedora Core 5 Hardware Environment: 440BX chipset motherboard Promise SATA300 TX4 controller card WD2500KS and WD2500JD hard drives Software Environment: kernel-2.6.19-rc5 Problem Description: I have a new Promise SATA300 TX4 4-port SATA controller to which I have attached two older WD2500JD hard drives and two brand new WD2500KS hard drives as a RAID-5 md array. The older drives seem to work fine, but both of the brand new hard drivestrigger the following errors every few seconds during i/o, more frequently during writes: Nov 13 22:18:03 gleep kernel: ata1: no sense translation for status: 0x50 Nov 13 22:18:03 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 13 22:18:03 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete } Nov 13 22:18:14 gleep kernel: ata3: no sense translation for status: 0x50 Nov 13 22:18:14 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 13 22:18:14 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete } Nov 13 22:18:50 gleep kernel: ata3: no sense translation for status: 0x50 Nov 13 22:18:50 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 13 22:18:50 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete } Nov 13 22:19:14 gleep kernel: ata1: no sense translation for status: 0x50 Nov 13 22:19:14 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 13 22:19:14 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete } Nov 13 22:19:25 gleep kernel: ata1: no sense translation for status: 0x50 Nov 13 22:19:25 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 13 22:19:25 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete } Nov 13 22:19:49 gleep kernel: ata3: no sense translation for status: 0x50 Nov 13 22:19:49 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 13 22:19:49 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete } Nov 13 22:20:01 gleep kernel: ata1: no sense translation for status: 0x50 Nov 13 22:20:01 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 13 22:20:01 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete } Nov 13 22:20:12 gleep kernel: ata1: no sense translation for status: 0x50 Nov 13 22:20:12 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI SK/ASC/ASCQ 0xb/00/00 Nov 13 22:20:12 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete } ata1 and ata3 are WD2500KS drives, but ata2 and ata4 are WD2500JD drives. The JD drives appear to have no problems (i.e., I have never seen any error messages for those drives.) The error messages do not *appear* to be causing any severe problems (the i/o does not appear to be interrupted), but the messages file gets large very quickly. Steps to reproduce: Attach a WD2500KS hard drive to a Promise SATA300 TX4 controller. Make a filesystem and write data to it. (I do not believe it is necessary to be using the md subsystem to get the error, but I do not have extra hardware to test with.) I originally reported this to the kernel mailing list: http://lkml.org/lkml/2006/10/25/198