Re: [opensuse] SSD problem when running on battery
Just to add to my previous post: on the same machines, Windows 7 works as expected when on battery (that is the same as when on AC). Best regards, Siniša Bandin On 14.09.2012 15:25, Sinisa wrote:
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
Sinisa Bandin wrote:
Just to add to my previous post:
on the same machines, Windows 7 works as expected when on battery (that is the same as when on AC).
Best regards,
Siniša Bandin
On 14.09.2012 15:25, Sinisa wrote:
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
I'm afraid I can't help but since nobody else has jumped in, I'd suggest you might try the opensse-kernel list or the linux-ide@vger.kernel.org list. You're perhaps more likely to find somebody who has seen the problem or has the expertise and time to diagnose the problem. I guess you have searched for kernel/driver bugs? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Dave Howorth
-
Sinisa Bandin