Firmware on SATA PMP Sil3726 - Sil3124
Hello, I've got a couple of older PMP's with Sil3726. I wonder if it's possible from Linux to check which firmware version it is on the Sil3726 and on the Sil3124? Is it possible to upgrade the firmware/bios on Sil3726 and Sil3124 from Linux? Best Regards, /LM - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Problems with "frozen drives" on sil3124 + sil3726
Hi Tejun et. al.
I'm running a server with Linux 2.6.18.1+Debian's Xen-patches and the
sata+pmp-patches from
http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.18.1-20061020.tar.bz2
Unfortunately I can't upgrade to anything newer than 2.6.18 since there
is no Xen Dom0-patches that I'm aware of to anything newer.
I have successfully for a long time together, but a couple of weeks ago
my motherboard gave in, and I installed a new one (along with new
processor/memory).
I'm running the very same kernel, the same sil3124-controller and the
same sil3726-PMP-board. The only difference is that instead of a
Supermicro P4SC8 w/ Intel P4 (and PCI-X slot of 66MHz) I'm currently
using Supermicro PDSME+ w/ E6600 (and PCI-X slot of 133MHz)
The sil3124-controller is an Addonics ADS3GX4R5-E.
The problem is that with the new motherboard I'm getting a lot of
libata-EH messages indicating that one of the disks are "frozen". The
messages comes a couple times per hour, but with different disks as the
"source" of the freeze. It happened with the old motherboard aswell, but
only once or twice a month.
Oct 12 09:44:58 cleopatra kernel: ata2.02: exception Emask 0x0 SAct 0x2 SErr
0x0 action 0x2 frozen
Oct 12 09:44:58 cleopatra kernel: ata2.02: tag 1 cmd 0x60 Emask 0x4 stat 0x40
err 0x0 (timeout)
Oct 12 09:44:58 cleopatra kernel: ata2.15: hard resetting port
Oct 12 09:45:00 cleopatra kernel: ata2.15: SATA link up 3.0 Gbps (SStatus 123
SControl 300)
Oct 12 09:45:00 cleopatra kernel: ata2.00: hard resetting port
Oct 12 09:45:00 cleopatra kernel: ata2.00: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Oct 12 09:45:01 cleopatra kernel: ata2.01: hard resetting port
Oct 12 09:45:03 cleopatra kernel: ata2.01: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Oct 12 09:45:03 cleopatra kernel: ata2.02: hard resetting port
Oct 12 09:45:04 cleopatra kernel: ata2.02: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Oct 12 09:45:04 cleopatra kernel: ata2.03: hard resetting port
Oct 12 09:45:04 cleopatra kernel: ata2.03: SATA link up 3.0 Gbps (SStatus 123
SControl 300)
Oct 12 09:45:04 cleopatra kernel: ata2.04: hard resetting port
Oct 12 09:45:04 cleopatra kernel: ata2.04: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Oct 12 09:45:04 cleopatra kernel: ata2.00: configured for UDMA/100
Oct 12 09:45:04 cleopatra kernel: ata2.01: configured for UDMA/100
Oct 12 09:45:04 cleopatra kernel: ata2.02: configured for UDMA/100
Oct 12 09:45:04 cleopatra kernel: ata2.03: configured for UDMA/100
Oct 12 09:45:04 cleopatra kernel: ata2.04: configured for UDMA/100
Oct 12 09:45:04 cleopatra kernel: ata2: EH complete
If I leave going, it slows down the speed of the disks remarkable.
Oct 18 06:45:59 cleopatra kernel: ata2.04: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x2 frozen
Oct 18 06:45:59 cleopatra kernel: ata2.04: tag 3 cmd 0xea Emask 0x4 stat 0x40
err 0x0 (timeout)
Oct 18 06:45:59 cleopatra kernel: ata2.15: hard resetting port
Oct 18 06:46:01 cleopatra kernel: ata2.15: SATA link up 3.0 Gbps (SStatus 123
SControl 300)
Oct 18 06:46:02 cleopatra kernel: ata2.00: hard resetting port
Oct 18 06:46:02 cleopatra kernel: ata2.00: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Oct 18 06:46:02 cleopatra kernel: ata2.01: hard resetting port
Oct 18 06:46:03 cleopatra kernel: ata2.01: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Oct 18 06:46:03 cleopatra kernel: ata2.02: hard resetting port
Oct 18 06:46:03 cleopatra kernel: ata2.02: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Oct 18 06:46:03 cleopatra kernel: ata2.03: hard resetting port
Oct 18 06:46:04 cleopatra kernel: ata2.03: SATA link up 3.0 Gbps (SStatus 123
SControl 300)
Oct 18 06:46:04 cleopatra kernel: ata2.04: hard resetting port
Oct 18 06:46:05 cleopatra kernel: ata2.04: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Oct 18 06:46:05 cleopatra kernel: ata2.00: configured for UDMA/33
Oct 18 06:46:05 cleopatra kernel: ata2.01: configured for UDMA/66
Oct 18 06:46:05 cleopatra kernel: ata2.02: configured for PIO4
Oct 18 06:46:05 cleopatra kernel: ata2.03: configured for UDMA/100
Oct 18 06:46:05 cleopatra kernel: ata2.04: configured for UDMA/100
Oct 18 06:46:05 cleopatra kernel: ata2: EH complete
I've tried to see a pattern of the disks (who all are in the same raid5
md), but some of the disks seems to affected more often but I can't find
a pattern.
$ sudo zgrep frozen /var/log/kern.log.?.gz | awk '{ print $6 }' | sort |
uniq -c
55 ata1.00:
170 ata1.01:
3 ata1.02:
72 ata1.03:
137 ata1.04:
220 ata2.00:
107 ata2.01:
152 ata2.02:
129 ata2.03:
103 ata2.04:
I've attached the dmesg after a reboot of the server.
If there is anymore information needed to track this problem down, or if
I should open a case in the kernel bugzilla, please let me know.
Best Regards,
/LM
Linux version 2.6.18-4-xen-686 (Debian 2.6.18.dfsg.1-12etch2.0.satapmp) ([EMAIL
PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #3 S
Problem with size after growing a device on 3ware-9500
Hi, I don't know really which subsystem this, so I'm sending this to the linux-ide list. Please direct me to a more appropriate place if this is not correct. I'm using a 3ware 9500 with Linux 2.6.18.1. I've grown the HW raid5-array and here is where the problem begins. After the card had expanded the array, I used "blockdev --rereadpt /dev/sdn" to get the kernel to recognize the now larger device. The last step was to do a "pvresize /dev/sdn". The problem is that pvresize still thought that the device was at the original size. From the lvm mailinglist I found out that pvresize used the same mechanism as "blockdev" (ioctl BLKGETSIZE64) to get the size of the disks, so I tested this and found that blockdev also reported the device to have the wrong size. So, if I do: # cat /sys/block/sdn/size 5859250176 and # blockdev --getsize64 /dev/sdn 2499946741760 # blockdev --getss /dev/sdn 512 # expr 2499946741760 / 512 4882708480 Apparently /sys/block/sdk/size is updated with the new size, but whatever "ioctl BLKGETSIZE64" is querying is not. If I reboot, everything works correctly. Shouldn't it be possible to extend the size of a disk without rebooting? Best Regards, /LM - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems w/ Sil3124 + Port Multiplier
Tejun Heo wrote: Lars Michael Jogbäck wrote: I think the disk attached to port 0 might be bad. Please report the result of 'smartctl -d ata -a /dev/sdX' where sdX is the device attached to the failing port. SMART Error Log Version: 1 No Errors Logged I was hoping to see some error logs but no. Hardware_ECC_Recovered count seems high (385707184) but I dunno whether the value is normal or not. Different manufacturers use different norms in counting them. If you have other disks of the same model, you can compare the values and see whether if it's unusually high. I think that is normal for that kind of disk. This is another disk but the same model (this one is attached to a 3ware 9500-controller) and it shows the same. smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD501LJ Serial Number:S0VVJ1NP300014 Firmware Version: CR100-10 User Capacity:500,107,862,016 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x52 Local Time is:Thu May 3 12:36:32 2007 CEST ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (8852) seconds. Offline data collection capabilities:(0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 151) minutes. SMART Attributes Data Structure revision number: 16 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 100 100 051Pre-fail Always - 3 3 Spin_Up_Time0x0007 100 100 015Pre-fail Always - 7104 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 7 5 Reallocated_Sector_Ct 0x0033 253 253 010Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 253 253 015Pre-fail Offline - 0 9 Power_On_Hours 0x0032 253 253 000Old_age Always - 97 10 Spin_Retry_Count0x0033 253 253 051Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 253 253 000Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 7 187 Unknown_Attribute 0x0032 253 253 000Old_age Always - 0 188 Unknown_Attribute 0x0032 253 253 000Old_age Always - 0 190 Unknown_Attribute 0x0022 068 067 000Old_age Always - 32 194 Temperature_Celsius 0x0022 142 139 000Old_age Always - 32 195 Hardware_ECC_Recovered 0x001a 100 100 000Old_age Always - 455228167 196 Reallocated_Event_Count 0x0032 253 253 000Old_age Always - 0 197 Current_Pending_Sector 0x0012 253 253 000Old_age Always - 0 198 Offline_Uncorrectable 0x0030 253 253 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x003e
Re: Problems w/ Sil3124 + Port Multiplier
Tejun Heo wrote: Lars Michael Jogbäck wrote: I have a system with a Sil3124 controller and two Sil3726 port multipliers. I'm running 2.6.18.1 with the patches from http://home-tj.org/wiki/index.php/Libata-tj-stable since I was not able to get the port multipler to work at all with 2.6.21 (perhaps the support for PMP is not fully integrated there). One of my Sil3726 is freezing my system approx one time per hour when the disks are under load. ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata5.00: tag 0 cmd 0xea Emask 0x4 stat 0x40 err 0x0 (timeout) Hmmm... that's FLUSH_CACHE timing out. Is there a way that I can generate a FLUSH_CACHE event manually somehow? I suspect that the root-cause of the problem could be drive-related. All the disks on the other Sil3726 are WD4000KD's and the disks attached to this one is 3xWD4000KD and 1xWD4000KS and 1xSamsung HD501LJ. Is there a way of test this? I think the disk attached to port 0 might be bad. Please report the result of 'smartctl -d ata -a /dev/sdX' where sdX is the device attached to the failing port. smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD501LJ Serial Number:S0VVJ1NP39 Firmware Version: CR100-10 User Capacity:500,107,862,016 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x52 Local Time is:Wed May 2 15:26:35 2007 CEST ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (8887) seconds. Offline data collection capabilities:(0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 152) minutes. SMART Attributes Data Structure revision number: 16 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 100 100 051Pre-fail Always - 2 3 Spin_Up_Time0x0007 100 100 015Pre-fail Always - 7232 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 3 5 Reallocated_Sector_Ct 0x0033 253 253 010Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 253 253 015Pre-fail Offline - 0 9 Power_On_Hours 0x0032 253 253 000Old_age Always - 49 10 Spin_Retry_Count0x0033 253 253 051Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 253 253 000Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 3 187 Unknown_Attribute 0x0032 253 253 000Old_age Always - 0 188 Unknown_Attribute 0x0032 253 253 000Old_age Always - 0 190 Unknown_Attribute 0x0022 070 069 000Old_age Always - 30 194 Temperature_Celsius 0x0022 148 145 000Old_age Always - 30 195 Hardware_ECC_Recovered 0x001a
Problems w/ Sil3124 + Port Multiplier
Hi, I have a system with a Sil3124 controller and two Sil3726 port multipliers. I'm running 2.6.18.1 with the patches from http://home-tj.org/wiki/index.php/Libata-tj-stable since I was not able to get the port multipler to work at all with 2.6.21 (perhaps the support for PMP is not fully integrated there). One of my Sil3726 is freezing my system approx one time per hour when the disks are under load. ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata5.00: tag 0 cmd 0xea Emask 0x4 stat 0x40 err 0x0 (timeout) ata5.15: hard resetting port ata5.15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5.00: hard resetting port ata5.00: SATA link up 3.0 Gbps (SStatus 113 SControl 300) ata5.01: hard resetting port ata5.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata5.02: hard resetting port ata5.02: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata5.03: hard resetting port ata5.03: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata5.04: hard resetting port ata5.04: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata5.00: configured for UDMA/100 ata5.01: configured for UDMA/100 ata5.02: configured for UDMA/100 ata5.03: configured for UDMA/100 ata5.04: configured for UDMA/100 ata5: EH complete I suspect that the root-cause of the problem could be drive-related. All the disks on the other Sil3726 are WD4000KD's and the disks attached to this one is 3xWD4000KD and 1xWD4000KS and 1xSamsung HD501LJ. Is there a way of test this? Is there an updated patch-set for port multipliers in a later kernel than 2.6.18.1? Regards, /LM - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
