sata disk speed negotiation with heavy disk activity

Bug #187146 reported by Andre Medeiros
6
Affects Status Importance Assigned to Milestone
Linux
Invalid
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.22

Every time my disk gets under heavy load, It gets really slow, where sometimes you can take up to 25 min to copy 700mb.

Here's what I get in dmesg:

-------
Jan 29 19:22:51 zeus kernel: [88872.317250] ata7.00: exception Emask 0x10 SAct 0x0 SErr 0x780100 action 0x2
Jan 29 19:22:51 zeus kernel: [88872.317255] ata7.00: (irq_stat 0x08000000)
Jan 29 19:22:51 zeus kernel: [88872.317258] ata7.00: cmd 25/00:58:a8:85:ea/00:00:14:00:00/e0 tag 0 cdb 0x0 data 45056 in
Jan 29 19:22:51 zeus kernel: [88872.317259] res 50/00:00:a7:85:ea/8c:00:14:00:00/e0 Emask 0x10 (ATA bus error)
Jan 29 19:22:51 zeus kernel: [88872.627717] ata7: soft resetting port
Jan 29 19:22:51 zeus kernel: [88872.799468] ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 29 19:22:51 zeus kernel: [88872.821938] ata7.00: configured for UDMA/33
Jan 29 19:22:51 zeus kernel: [88872.821945] ata7: EH complete
Jan 29 19:22:51 zeus kernel: [88872.822272] sd 7:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
Jan 29 19:22:51 zeus kernel: [88872.822487] sd 7:0:0:0: [sdc] Write Protect is off
Jan 29 19:22:51 zeus kernel: [88872.822490] sd 7:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Jan 29 19:22:51 zeus kernel: [88872.822829] sd 7:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
-------

As far as I could tell, this has to do with http://bugzilla.kernel.org/show_bug.cgi?id=8889 and was fixed in .23

Tags: cft-2.6.27
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Andre,

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel (2.6.24). From your comments I would then assume this should be resolved with the Hardy kernel. It would be helpful if you could test the latest Hardy Alpha release: http://www.ubuntu.com/testing . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. We'll keep this report open against the actively developed kernel bug against 2.6.22 this will be closed. Thanks.

Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.22:
status: New → Won't Fix
Changed in linux:
status: New → Invalid
Revision history for this message
kiev1 (sys-sys-admin) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.