Hardy - nvidia mcp51 ata controller: slow access to SATA and PATA drives

Bug #220349 reported by Dane Mutters
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released

Bug Description

Binary package hint: linux-source

I have a MSI P7N-SLI Platinum motherboard. It has an nVidia MCP51 IDE controller, according to `lspci`. This controller, according to google (and the solution I found) is actually 2 controllers: nVidia 430 (MCP) and JMicron JMB363. See this for more details: http://www.nvnews.net/reviews/msi_p7n_platinum/index.shtml

-extremely slow optical disk burning
-it takes forever to copy, delete, or create large files
-tracker is REALLY slow, to the point of being practically useless.

I am using Hardy Heron Beta, fully updated, as of April 21, 2008, AMD64 edition, on an Intel Core 2 Duo processor. I have several drives attached directly to the 2 PATA controllers on the motherboard:

-primary master: 250GB HD
-primary slave: 18X DVDRW drive
-sec. master: removable HD bay (various older HDs)
-sec. slave: 16X DVDRW drive

I have 1 SATA drive connected to the motherboard at SATA channel 2: a 320GB drive.

I also have installed a Promise Ultra133 TX2 PATA controller card with 2 PATA channels. Only channel 1 has connected drives:

-master: 40GB hard drive
-slave: 80GB hard drive

The larger drives (250 PATA and 320 SATA) are pretty new; the rest are not, but all drives pass `badblocks -c 4096 -svnb 4096 /dev/xxx` with no errors.

Here's the workaround I manged to find:

-compile my own kernel based on `apt-get source linux-source-2.6.24`, using the "old debian method" from the WIKI. Attached are the old (NOT working) config from /boot/, and the new (working) config that I made using `make menuconfig` in the kernel source directory. Note that the sound drivers were, for some reason not set up properly in the original .config (as far as I could tell), but oddly enough, worked out-of-the-box.

-blacklist the module, "ata_generic" in /etc/modprobe.d/blacklist. (Added "blacklist ata_generic" to the last line.)

Please let me know if you need some more info, and I'll do my best to give it to you.

Thanks for all your work!


Revision history for this message
Dane Mutters (dmutters) wrote :
Revision history for this message
Dane Mutters (dmutters) wrote :

original .config from /boot/

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

Hi dmutters,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 220349

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Dane Mutters (dmutters) wrote :

It's been working so well that I had forgotten all about this bug! Mark as closed/fixed.

Revision history for this message
Dane Mutters (dmutters) wrote :

This has been fixed in Jaunty on my machine.

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

Other bug subscribers