lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0702081332330.24105@Phoenix.oltrelinux.com>
Date:	Thu, 8 Feb 2007 13:33:16 +0100 (CET)
From:	l.genoni@...relinux.com
To:	Robert Hancock <hancockr@...w.ca>
cc:	Alan <alan@...rguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Luigi Genoni <genoni@....it>, l.genoni@....it
Subject: Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new
 pata driver, NV CK804 ide controller.

Well, the cable is OK, of course I checked.

On Wed, 7 Feb 2007, Robert Hancock wrote:

> Date: Wed, 07 Feb 2007 22:36:58 -0600
> From: Robert Hancock <hancockr@...w.ca>
> To: Alan <alan@...rguk.ukuu.org.uk>,
>     linux-kernel <linux-kernel@...r.kernel.org>
> Cc: Luigi Genoni <genoni@....it>
> Subject: Re: [BUG?] ata disk running maximum at DMA33 with 2.6.20 and new pata
>      driver, NV CK804 ide controller.
> Resent-Date: Thu, 08 Feb 2007 05:47:22 +0100
> Resent-From: <l.genoni@....it>
> 
> Alan wrote:
>> On Wed, 7 Feb 2007 01:19:36 +0100
>> Luigi Genoni <genoni@....it> wrote:
>> 
>>> Hi,
>>> since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is
>>> initialized maximum  in DMA33 mode (and obviously performances drop 
>>> consequently), as you can see from:
>> 
>> Interesting.
>> 
>>> Willing to test any patch.
>> 
>> Firstly can you see if its consistently the case that booting 2.6.20
>> gives UDMA33 and 2.6.19 UDMA100 over a few reboots. If it is please drop
>> the 2.6.19 drivers/ata/pamd_amd into 2.6.20 and try that.
>
> As an aside to this sort of problem, shouldn't we print some kind of loud 
> message in dmesg when we force a high-UDMA-capable device down to UDMA33 due 
> to a 40-wire cable detection? In the case where it truly is a 40-wire cable 
> the user may want to know that and replace the cable, if it isn't it gives 
> more of a hint of why the drive isn't running at full speed..
>
> -- 
> Robert Hancock      Saskatoon, SK, Canada
> To email, remove "nospam" from hancockr@...pamshaw.ca
> Home Page: http://www.roberthancock.com/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ