Bug 669892 - Slow SATA-Device after resuming from suspend mode
Summary: Slow SATA-Device after resuming from suspend mode
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-15 15:18 UTC by smobbl_bobbl
Modified: 2012-08-16 18:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 18:48:20 UTC
Type: ---


Attachments (Terms of Use)
content of dmesg; starts at the beginning to suspend, ends with final resume operation (15.25 KB, text/plain)
2011-01-15 15:27 UTC, smobbl_bobbl
no flags Details

Description smobbl_bobbl 2011-01-15 15:18:27 UTC
http://forums.fedoraforum.org/showthread.php?p=1425227

Description of problem:

Since ever, i face the problem, that i cannot continue using my computer properly after i suspended it to ram and wake it up again.

    * Fedora 14, 64-bit, most recent and stable kernel
    * mainly KDE
    * Motherboard: Gigabyte P55A-UD4
    * Hard Drives
         1. SAMSUNG HD501LJ
         2. SAMSUNG SP1213N

I can figure out, that everything works fine, but with a severe delay.
Having a look at my led, signifying hard drive activity, it flases once a second for approx 10ms. frequency is very constant.


so i performed several checks:

firstly, hdparm -i, there is no difference before and after sleeping mode:
Code:

[root@bobbl-pc bobbl]# hdparm -i /dev/sda

/dev/sda:

 Model=SAMSUNG HD501LJ, FwRev=CR100-13, SerialNo=S0MUJDWQ560307
 Config={ Fixed }
 RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
 BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
 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=no WriteCache=enabled
 Drive conforms to: unknown:  ATA/ATAPI-3,4,5,6,7

 * signifies the current active mode

secondly, the drive speeds:

SATA-device:
Code:

[root@bobbl-pc bobbl]# hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:   15220 MB in  2.00 seconds = 7621.57 MB/sec
 Timing buffered disk reads:  228 MB in  3.02 seconds =  75.52 MB/sec

after resuming:
Code:

[root@bobbl-pc bobbl]# hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:     2 MB in  4.10 seconds = 499.54 kB/sec
 Timing buffered disk reads:    4 MB in  4.30 seconds = 952.62 kB/sec


IDE-device: (speed is equivalent, before suspending and after resuming)
Code:

[root@bobbl-pc bobbl]# hdparm -Tt /dev/sdb

/dev/sdb:
 Timing cached reads:   17582 MB in  2.00 seconds = 8806.94 MB/sec
 Timing buffered disk reads:  168 MB in  3.00 seconds =  55.93 MB/sec

kindly assist me in solving this problem!
thank you in anticipation! 

Version-Release number of selected component (if applicable):


How reproducible:
configuring a system with similiar hardware components, suspending system to RAM


Steps to Reproduce:
1.implied by description
  
Actual results:


Expected results:

-----------------------------------------------

Additional info:

[bobbl@bobbl-pc ~]$ lspci -nnk 
[...]
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI [8086:d131] (rev 11)
        Subsystem: Giga-byte Technology Device [1458:5000]
[...]
00:1f.2 IDE interface [0101]: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller [8086:3b20] (rev 05)
        Subsystem: Giga-byte Technology Device [1458:b002]
        Kernel driver in use: ata_piix
        Kernel modules: ata_generic, pata_acpi
[...]
04:00.0 SATA controller [0106]: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller [197b:2363] (rev 03)
        Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:b000]
        Kernel driver in use: ahci
04:00.1 IDE interface [0101]: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller [197b:2363] (rev 03)
        Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:b000]
        Kernel driver in use: pata_jmicron
        Kernel modules: ata_generic, pata_acpi, pata_jmicron
05:00.0 IDE interface [0101]: Marvell Technology Group Ltd. Device [1b4b:91a3] (rev 11)
        Subsystem: Giga-byte Technology Device [1458:b000]
        Kernel modules: ata_generic, pata_acpi


if you have any open questions, i'd like to resolve them!

Comment 1 smobbl_bobbl 2011-01-15 15:27:53 UTC
Created attachment 473650 [details]
content of dmesg; starts at the beginning to suspend, ends with final resume operation

Comment 2 Sergio Basto 2011-07-14 16:24:12 UTC
My issue is fixed on kernel 2.6.38.8-35 , I think is was : 

* Wed Jul 06 2011 Chuck Ebbert <cebbert> 2.6.38.8-35 - Revert
SCSI/block patches from 2.6.38.6 that caused more problems.

Please, try it and report it .

Comment 3 Fedora End Of Life 2012-08-16 18:48:23 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.