> 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
>
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
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 <[EMAIL PROTECTED]>
To: Alan <[EMAIL PROTECTED]>,
linux-kernel
Cc: Luigi Genoni <[EMAIL PROTECTED]>
Subject: Re: [BUG?] ata disk running maximum
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 [EMAIL PROTECTED]
To: Alan [EMAIL PROTECTED],
linux-kernel linux-kernel@vger.kernel.org
Cc: Luigi Genoni [EMAIL PROTECTED]
Subject: Re: [BUG?]
Alan wrote:
On Wed, 7 Feb 2007 01:19:36 +0100
Luigi Genoni <[EMAIL PROTECTED]> 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
I did the test you asked and yes, it is consistently booting at DMA33 with
2.6.20 and DMA100 with 2.6.19.3 (20 reboots, 10 2.6.20 and 10 2.6.19 in
sparse order).
I am compiling a 2.6.20 kernel with older pata_amd.c driver and will let
you know. seeing the diff I do exspect it to compile
On Wed, 7 Feb 2007 01:19:36 +0100
Luigi Genoni <[EMAIL PROTECTED]> 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
I boot 2.6.20 also on a pentium4 with intel 82801EB/ER (ICH5/ICH5R) IDE
Controller and the same pata disk.
On this controller the disk runs in DMA100 as it should, so I'm prone to
think it is a pata_amd.c driver trouble. Should try downgrading this
driver from version 0.2.7 to version 0.2.4?
On Wed, 7 Feb 2007 01:19:36 +0100
Luigi Genoni [EMAIL PROTECTED] 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
I did the test you asked and yes, it is consistently booting at DMA33 with
2.6.20 and DMA100 with 2.6.19.3 (20 reboots, 10 2.6.20 and 10 2.6.19 in
sparse order).
I am compiling a 2.6.20 kernel with older pata_amd.c driver and will let
you know. seeing the diff I do exspect it to compile
Alan wrote:
On Wed, 7 Feb 2007 01:19:36 +0100
Luigi Genoni [EMAIL PROTECTED] 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
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:
pata_amd :00:06.0: version 0.2.7
PCI: Setting latency timer of device :00:06.0 to 64
ata5: PATA max
Hi,
since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is
initialized maximum in DMA33 mode, as you can see from:
pata_amd :00:06.0: version 0.2.7
PCI: Setting latency timer of device :00:06.0 to 64
ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
Hi,
since upgrading to kernel 2.6.20 my pata disk, using new pata driver, is
initialized maximum in DMA33 mode, as you can see from:
pata_amd :00:06.0: version 0.2.7
PCI: Setting latency timer of device :00:06.0 to 64
ata5: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
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:
pata_amd :00:06.0: version 0.2.7
PCI: Setting latency timer of device :00:06.0 to 64
ata5: PATA max
15 matches
Mail list logo
