[opensuse] SSD problem when running on battery
Hello, ever since I have installed a SSD instead of HDD in my HP Pavilion DV7, I have this problem: whenever I work on battery, computer slows down and eventually stops, with dmesg showing errors from disk. The same happens on friend's Dell Vostro 1015 SSD's are Patriot Pyro SE 120GB (with firmware 502ABBF0) and Transcend TS128GSSD320 128GB. Tried upgrading kernels from opensuse 12.1 default 3.1.something, to 3.2, 3.3, 3.4, 3.5 and now 3.6RC Also upgraded whole system to opensuse 12.2 (with kernel 3.4.6) ant tried fresh install of 12.2, everything was the same in all cases. Any suggestions? Best regards, Siniša Bandin These are the messages (well, a tiny part of them): Sep 13 07:26:33 susedell kernel: [ 99.712063] ata1.00: exception Emask 0x0 SAct 0x3ff SErr 0x50000 action 0x6 frozen Sep 13 07:26:33 susedell kernel: [ 99.712068] ata1: SError: { PHYRdyChg CommWake } Sep 13 07:26:33 susedell kernel: [ 99.712071] ata1.00: failed command: READ FPDMA QUEUED Sep 13 07:26:33 susedell kernel: [ 99.712076] ata1.00: cmd 60/10:00:90:1c:14/00:00:0b:00:00/40 tag 0 ncq 8192 in Sep 13 07:26:33 susedell kernel: [ 99.712076] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Sep 13 07:26:33 susedell kernel: [ 99.712079] ata1.00: status: { DRDY } Sep 13 07:26:33 susedell kernel: [ 99.712081] ata1.00: failed command: READ FPDMA QUEUED Sep 13 07:26:33 susedell kernel: [ 99.712086] ata1.00: cmd 60/48:08:80:84:ba/00:00:00:00:00/40 tag 1 ncq 36864 in Sep 13 07:26:33 susedell kernel: [ 99.712086] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Sep 13 07:26:33 susedell kernel: [ 99.712089] ata1.00: status: { DRDY } Sep 13 07:26:33 susedell kernel: [ 99.712091] ata1.00: failed command: READ FPDMA QUEUED ........................ Sep 13 07:26:33 susedell kernel: [ 99.712165] ata1.00: status: { DRDY } Sep 13 07:26:33 susedell kernel: [ 99.712169] ata1: hard resetting link Sep 13 07:26:34 susedell kernel: [ 100.017074] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 13 07:26:34 susedell kernel: [ 100.038778] ata1.00: configured for UDMA/133 Sep 13 07:26:34 susedell kernel: [ 100.039218] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039220] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039222] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039224] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039226] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039228] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039230] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039232] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039234] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039236] ata1.00: device reported invalid CHS sector 0 Sep 13 07:26:34 susedell kernel: [ 100.039244] sd 0:0:0:0: [sda] Sep 13 07:26:34 susedell kernel: [ 100.039246] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sep 13 07:26:34 susedell kernel: [ 100.039249] sd 0:0:0:0: [sda] Sep 13 07:26:34 susedell kernel: [ 100.039250] Sense Key : Aborted Command [current] [descriptor] Sep 13 07:26:34 susedell kernel: [ 100.039254] Descriptor sense data with sense descriptors (in hex): Sep 13 07:26:34 susedell kernel: [ 100.039255] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 13 07:26:34 susedell kernel: [ 100.039265] 00 00 00 00 Sep 13 07:26:34 susedell kernel: [ 100.039269] sd 0:0:0:0: [sda] Sep 13 07:26:34 susedell kernel: [ 100.039272] Add. Sense: No additional sense information Sep 13 07:26:34 susedell kernel: [ 100.039274] sd 0:0:0:0: [sda] CDB: Sep 13 07:26:34 susedell kernel: [ 100.039276] Read(10): 28 00 0b 14 1c 90 00 00 10 00 Sep 13 07:26:34 susedell kernel: [ 100.039285] end_request: I/O error, dev sda, sector 185867408 Sep 13 07:26:34 susedell kernel: [ 100.039299] sd 0:0:0:0: [sda] Sep 13 07:26:34 susedell kernel: [ 100.039301] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sep 13 07:26:34 susedell kernel: [ 100.039303] sd 0:0:0:0: [sda] Sep 13 07:26:34 susedell kernel: [ 100.039304] Sense Key : Aborted Command [current] [descriptor] ...................... Sep 13 07:27:37 susedell kernel: [ 163.031571] sd 0:0:0:0: [sda] CDB: Sep 13 07:27:37 susedell kernel: [ 163.031572] Write(10): 2a 00 01 2a 58 00 00 04 00 00 Sep 13 07:27:37 susedell kernel: [ 163.031580] end_request: I/O error, dev sda, sector 195522563 07:27:37 susedell kernel: [ 163.031572] Write(10): 2a 00 01 2a 58 00 00 04 00 00 Sep 13 07:27:37 susedell kernel: [ 163.031580] end_request: I/O error, dev sda, sector 19552256 Sep 13 07:27:37 susedell kernel: [ 163.031588] Buffer I/O error on device sda2, logical block 1920000 Sep 13 07:27:37 susedell kernel: [ 163.031596] Buffer I/O error on device sda2, logical block 1920001 Sep 13 07:27:37 susedell kernel: [ 163.031599] Buffer I/O error on device sda2, logical block 1920002 Sep 13 07:27:37 susedell kernel: [ 163.031601] Buffer I/O error on device sda2, logical block 1920003 Sep 13 07:27:37 susedell kernel: [ 163.031603] Buffer I/O error on device sda2, logical block 1920004 Sep 13 07:27:37 susedell kernel: [ 163.031605] Buffer I/O error on device sda2, logical block 1920005 Sep 13 07:27:37 susedell kernel: [ 163.031608] Buffer I/O error on device sda2, logical block 1920006 Sep 13 07:27:37 susedell kernel: [ 163.031610] Buffer I/O error on device sda2, logical block 1920007 Sep 13 07:27:37 susedell kernel: [ 163.031612] Buffer I/O error on device sda2, logical block 1920008 Sep 13 07:27:37 susedell kernel: [ 163.031614] Buffer I/O error on device sda2, logical block 1920009 Sep 13 07:27:37 susedell kernel: [ 163.031617] Buffer I/O error on device sda2, logical block 1920010 Sep 13 07:27:37 susedell kernel: [ 163.031619] Buffer I/O error on device sda2, logical block 1920011 ............. etc -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 14/09/12 10:25, Sinisa escribió:
Hello,
ever since I have installed a SSD instead of HDD in my HP Pavilion DV7, I have this problem: whenever I work on battery, computer slows down and eventually stops, with dmesg showing errors from disk. The same happens on friend's Dell Vostro 1015
SSD's are Patriot Pyro SE 120GB (with firmware 502ABBF0) and Transcend TS128GSSD320 128GB.
Ok, in order to figure this out.. you have to tell what of the two SSD drives is device "sda" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 14.09.2012 20:29, Cristian Rodríguez wrote:
El 14/09/12 10:25, Sinisa escribió:
Hello, ever since I have installed a SSD instead of HDD in my HP Pavilion DV7, I have this problem: whenever I work on battery, computer slows down and eventually stops, with dmesg showing errors from disk. The same happens on friend's Dell Vostro 1015 SSD's are Patriot Pyro SE 120GB (with firmware 502ABBF0) and Transcend TS128GSSD320 128GB.
Ok, in order to figure this out.. you have to tell what of the two SSD drives is device "sda"
Either. One is in my laptop, the oteh is in friend's. Both showing the same symptoms, only in Linux and only when running on battery. Tried with btrfs, ext4, xfs, no difference. Also tried searching the Internet, did not find anything. Btw, I am a Linux pro (well, at least I make my living from it), but this is something I just cannot understand :( Best regards, Siniša Bandin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 14/09/12 18:03, Sinisa Bandin escribió:
Btw, I am a Linux pro (well, at least I make my living from it), but this is something I just cannot understand :(
Best regards, Siniša Bandin
OK, First steps. 1. Update both drive's firmware from the manufacturer. (and peraphs BIOSes too) 2. See if you have package "laptop-mode" installed and running, if so, disable it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 14.09.2012 23:42, Cristian Rodríguez wrote:
El 14/09/12 18:03, Sinisa Bandin escribió:
Btw, I am a Linux pro (well, at least I make my living from it), but this is something I just cannot understand :( Best regards, Siniša Bandin
OK, First steps.
1. Update both drive's firmware from the manufacturer. (and peraphs BIOSes too)
Done that, even tried restoring the older versions... no change
2. See if you have package "laptop-mode" installed and running, if so, disable it.
Tried that already, same with and without laptop-mode. Currently, it is not even installed Did I mention that everything is just fine in Windows (but who wants to use that)? Best regards, Siniša Bandin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
No real answers but... BIOS power management settings for when on battery? HD power management settings (hdparm)? Tried safe mode boot? Tried a different Linux or Linux Live-CD? (To eliminate OpenSUSE) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15.09.2012 12:25, michael@actrix.gen.nz wrote:
No real answers but...
BIOS power management settings for when on battery?
It is a HP, so no real BIOS config... I can set the date and select the default boot device and thats it. On the other hand, problems happen when I am actively working, so there should be no power saving...
HD power management settings (hdparm)?
# hdparm -i /dev/sda /dev/sda: Model=Patriot Pyro SE, FwRev=502ABBF0, SerialNo=PT1208A00069307 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234441648 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 AdvancedPM=yes: unknown setting WriteCache=enabled Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7 * signifies the current active mode
Tried safe mode boot?
Yes, same. As soon as I try to read something from disk: # dd if=/dev/sda of=/dev/null # dmesg .......... [ 446.217835] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x50000 action 0x6 frozen [ 446.217849] ata1: SError: { PHYRdyChg CommWake } [ 446.217859] ata1.00: failed command: READ FPDMA QUEUED [ 446.217873] ata1.00: cmd 60/08:00:00:eb:71/00:00:00:00:00/40 tag 0 ncq 4096 in [ 446.217876] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 446.217888] ata1.00: status: { DRDY } [ 446.217895] ata1.00: failed command: READ FPDMA QUEUED [ 446.217908] ata1.00: cmd 60/e8:08:88:eb:71/00:00:00:00:00/40 tag 1 ncq 118784 in [ 446.217910] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 446.217923] ata1.00: status: { DRDY } [ 446.217929] ata1.00: failed command: READ FPDMA QUEUED [ 446.217942] ata1.00: cmd 60/20:10:e0:f0:71/00:00:00:00:00/40 tag 2 ncq 16384 in [ 446.217944] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 446.217956] ata1.00: status: { DRDY } [ 446.217967] ata1: hard resetting link [ 446.537392] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 446.559358] ata1.00: configured for UDMA/133 [ 446.559792] ata1.00: device reported invalid CHS sector 0 [ 446.559800] ata1.00: device reported invalid CHS sector 0 [ 446.559808] ata1.00: device reported invalid CHS sector 0 [ 446.559823] ata1: EH complete [ 480.261445] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x50000 action 0x6 frozen [ 480.261460] ata1: SError: { PHYRdyChg CommWake } [ 480.261469] ata1.00: failed command: READ FPDMA QUEUED [ 480.261483] ata1.00: cmd 60/00:00:58:8e:82/04:00:00:00:00/40 tag 0 ncq 524288 in [ 480.261486] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 480.261499] ata1.00: status: { DRDY } [ 480.261505] ata1.00: failed command: READ FPDMA QUEUED [ 480.261518] ata1.00: cmd 60/00:08:58:92:82/04:00:00:00:00/40 tag 1 ncq 524288 in [ 480.261521] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 480.261533] ata1.00: status: { DRDY } [ 480.261544] ata1: hard resetting link [ 480.581202] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 480.602820] ata1.00: configured for UDMA/133 [ 480.603258] ata1.00: device reported invalid CHS sector 0 [ 480.603266] ata1.00: device reported invalid CHS sector 0 [ 480.603282] ata1: EH complete ..........
Tried a different Linux or Linux Live-CD? (To eliminate OpenSUSE)
Well, only openSUSE live CD... with the same symptoms But today I found some "Gentoo System rescue CD", it said version 2.0.2, kernel 3.0.something, and could not reproduce the problem within 15 minutes (usually I can do that immediately after taking out the power cable) I will try to download some more live images and try with them... Best regards, Sinisa Bandin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 17 Sep 2012 05:42:55 Sinisa Bandin wrote:
...
HD power management settings (hdparm)?
# hdparm -i /dev/sda
/dev/sda:
Model=Patriot Pyro SE, FwRev=502ABBF0, SerialNo=PT1208A00069307 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234441648 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 AdvancedPM=yes: unknown setting WriteCache=enabled Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7
* signifies the current active mode ... I'm be tempted to try disabling/setting/adjusting AvancedPM.
Your settings above look the same as for my OCZ SSD, but it's in a power hungry desktop, so battery/power-management is not an issue for me. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Cristian Rodríguez -
michael＠actrix.gen.nz -
Sinisa -
Sinisa Bandin