[FIXED] Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Alan Cox wrote: > > > have the rules for testing if the driver/host/device register and report > > > that all signals are valid and stable. > > > > Yes, I had some "interesting" modifications to a lot of my /usr when I > > tried to activate UDMA4 under RH7.0 (I don't believe my hardware is > > capable of UDMA4!) > > The 2.2 kernel we ship doesnt have the ide patches either so Im not suprised > it got upset 8) OK, so in case anyone is tracking open issues, this was "pilot error". My motherboard only does ATA33 (UDMA2). It just happens to work under ATA44 (UDMA3). Since ATA44 is out of my machine's spec, and could corrupt data, the 2.4 kernel is correct to reject attempts to set UDMA3.[1] Cheers Chris [1] But if you're mad, you can still boot with idex=ata66 and force the issue. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
[FIXED] Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Alan Cox wrote: have the rules for testing if the driver/host/device register and report that all signals are valid and stable. Yes, I had some "interesting" modifications to a lot of my /usr when I tried to activate UDMA4 under RH7.0 (I don't believe my hardware is capable of UDMA4!) The 2.2 kernel we ship doesnt have the ide patches either so Im not suprised it got upset 8) OK, so in case anyone is tracking open issues, this was "pilot error". My motherboard only does ATA33 (UDMA2). It just happens to work under ATA44 (UDMA3). Since ATA44 is out of my machine's spec, and could corrupt data, the 2.4 kernel is correct to reject attempts to set UDMA3.[1] Cheers Chris [1] But if you're mad, you can still boot with idex=ata66 and force the issue. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Alan Cox wrote:
Alan... The following errors are what I am getting with your
pre-2.2.18pre15 release.
Does this mean anything. It only concerns ONE of my two physical drives.
I can take it out but it works fine with 2.2.17 ??
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> Bad CRC is a cable error. That could be misconfiguration but could also be
> crap cables
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
>
---
Your mode of life will be changed to ASCII.
Ted Gervais <[EMAIL PROTECTED]>
44.135.34.201 linux.ve1drg.ampr.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Chris Evans wrote: > ... > # IDE patch provides UDMA66 support, but is known to corrupt filesystems > # on a few systems, so is not applied by default. > Patch151: linux-2.2.16-ide-2805.patch > ... > # Dangerous IDE patch available but off by default > #%patch151 -p1 > ... Should I send RedHat an unpatch for 2.4? Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Alan Cox wrote: > The 2.2 kernel we ship doesnt have the ide patches either so Im not suprised > it got upset 8) Ah yes you're correct. I saw the patch in the kernel SRPM but didn't look far enough to see: ... # IDE patch provides UDMA66 support, but is known to corrupt filesystems # on a few systems, so is not applied by default. Patch151: linux-2.2.16-ide-2805.patch ... # Dangerous IDE patch available but off by default #%patch151 -p1 ... Still, with hdparm -d1 -X67, I can presumably get UDMA3 and good 2.2 speeds (17Mb/s, or 21Mb/s with rawio) without this patch. Cheers Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Alan Cox wrote:
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
> Bad CRC is a cable error. That could be misconfiguration but could also be
> crap cables
It went away when I enabled PIIX4 support + PIIX4 tuning support.
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
> > have the rules for testing if the driver/host/device register and report > > that all signals are valid and stable. > > Yes, I had some "interesting" modifications to a lot of my /usr when I > tried to activate UDMA4 under RH7.0 (I don't believe my hardware is > capable of UDMA4!) The 2.2 kernel we ship doesnt have the ide patches either so Im not suprised it got upset 8) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Tue, 10 Oct 2000, Andre Hedrick wrote: > Also set this option "CONFIG_IDEDMA_IVB" because you are in the > transistion period of drive manufacturing. Turned that on, applied the patch. BTW, your patch seems to make the "Speed warnings" failure _more_ likely?? Still refuses to activate UDMA3. 11.5Mb/sec vs. 17Mb/sec in 2.2. Is my hardware trying to tell me that 2.2 shouldn't be allowing me to run with UDMA3? It's rock solid and yes I've given it a pounding. Cheers Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Bad CRC is a cable error. That could be misconfiguration but could also be
crap cables
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
Also set this option "CONFIG_IDEDMA_IVB" because you are in the transistion period of drive manufacturing. On Tue, 10 Oct 2000, Chris Evans wrote: > > On Tue, 10 Oct 2000, Andre Hedrick wrote: > > > Basically you have drive that caught in the word93 rules change. > > > > However, the error you got were real and the kernel did properly respeed > > the drive to one step slower. The problem above prevented you from going > > from ATA66 to ATA44, thus you fell to ATA33. > > > > You RHS 7.0 kernel does not have all the fallback and rules testing to > > keep things running the very best and in the safest way. Also you do not > > have the rules for testing if the driver/host/device register and report > > that all signals are valid and stable. > > Yes, I had some "interesting" modifications to a lot of my /usr when I > tried to activate UDMA4 under RH7.0 (I don't believe my hardware is > capable of UDMA4!) > > > If you did not set TUNING option if the chipset has it specifically > > flagged then you will not be able to retune the chipset/drive and the IO > > will be out of sync. > > Shortly after my first post, I noticed and activated the Intel PIIX4 > support + tuning. This got rid of the nasty errors but didn't get my > 17Mb/sec. > > Trying your patch now. > > Cheers > Chris > Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Tue, 10 Oct 2000, Andre Hedrick wrote: > Basically you have drive that caught in the word93 rules change. > > However, the error you got were real and the kernel did properly respeed > the drive to one step slower. The problem above prevented you from going > from ATA66 to ATA44, thus you fell to ATA33. > > You RHS 7.0 kernel does not have all the fallback and rules testing to > keep things running the very best and in the safest way. Also you do not > have the rules for testing if the driver/host/device register and report > that all signals are valid and stable. Yes, I had some "interesting" modifications to a lot of my /usr when I tried to activate UDMA4 under RH7.0 (I don't believe my hardware is capable of UDMA4!) > If you did not set TUNING option if the chipset has it specifically > flagged then you will not be able to retune the chipset/drive and the IO > will be out of sync. Shortly after my first post, I noticed and activated the Intel PIIX4 support + tuning. This got rid of the nasty errors but didn't get my 17Mb/sec. Trying your patch now. Cheers Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
Basically you have drive that caught in the word93 rules change.
However, the error you got were real and the kernel did properly respeed
the drive to one step slower. The problem above prevented you from going
from ATA66 to ATA44, thus you fell to ATA33.
You RHS 7.0 kernel does not have all the fallback and rules testing to
keep things running the very best and in the safest way. Also you do not
have the rules for testing if the driver/host/device register and report
that all signals are valid and stable.
If you did not set TUNING option if the chipset has it specifically
flagged then you will not be able to retune the chipset/drive and the IO
will be out of sync.
At best it will reject DMA attempts, at worst this will do bad things to
data.
The stuff that 2.4 has that 2.2 does not have is following the rules and
guidelines set forth by the folks writing the rules.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
diff -urN linux-2.4.0-t10-1-pristine/drivers/ide/ide-features.c
linux-2.4.0-t10-1.smsc/drivers/ide/ide-features.c
--- linux-2.4.0-t10-1-pristine/drivers/ide/ide-features.c Thu Aug 3 16:07:42
2000
+++ linux-2.4.0-t10-1.smsc/drivers/ide/ide-features.c Tue Oct 10 00:00:38 2000
@@ -224,7 +224,8 @@
#ifndef CONFIG_IDEDMA_IVB
if ((drive->id->hw_config & 0x6000) == 0) {
#else /* !CONFIG_IDEDMA_IVB */
- if ((drive->id->hw_config & 0x2000) == 0) {
+ if (((drive->id->hw_config & 0x2000) == 0) ||
+ ((drive->id->hw_config & 0x4000) == 0)) {
#endif /* CONFIG_IDEDMA_IVB */
printk("%s: Speed warnings UDMA 3/4/5 is not functional.\n",
drive->name);
return 1;
@@ -260,7 +261,7 @@
#ifndef CONFIG_IDEDMA_IVB
(drive->id->hw_config & 0x4000) &&
#endif /* CONFIG_IDEDMA_IVB */
- (drive->id->hw_config & 0x2000)) ? 1 : 0);
+ (drive->id->hw_config & 0x6000)) ? 1 : 0);
}
/*
2.4.0test-9: IDE problems
Hi,
Finally got around to trying out 2.4.0test9. I'm going to do some VM
performance comparisons (incidentally because VM should be a carefully
measured science not random cool idea of the day which we have seen too
much of recently).
Unfortunately, I can't start fair tests yet because UDMA3 refuses to
activate in 2.4.0test-9.
I get these messages on boot
ide0: Speed warnings UDMA 3/4/5 is not functional.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda: DMA disabled
Subsequently, if I run
hdparm -d1 -X67 /dev/hda
I get told
ide0: Speed warnings UDMA 3/4/5 is not functional.
And this leaves me with
/dev/hda:
Timing buffered disk reads: 64 MB in 5.71 seconds = 11.21 MB/sec
Under the stock 2.2 RedHat 7.0 kernel, the same hdparm tuning gives me
about 17Mb/s.
Anyone got any hints? I selected the ATA option. Might this be causing the
failure?
Anyone got any hints?
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
2.4.0test-9: IDE problems
Hi,
Finally got around to trying out 2.4.0test9. I'm going to do some VM
performance comparisons (incidentally because VM should be a carefully
measured science not random cool idea of the day which we have seen too
much of recently).
Unfortunately, I can't start fair tests yet because UDMA3 refuses to
activate in 2.4.0test-9.
I get these messages on boot
ide0: Speed warnings UDMA 3/4/5 is not functional.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda: DMA disabled
Subsequently, if I run
hdparm -d1 -X67 /dev/hda
I get told
ide0: Speed warnings UDMA 3/4/5 is not functional.
And this leaves me with
/dev/hda:
Timing buffered disk reads: 64 MB in 5.71 seconds = 11.21 MB/sec
Under the stock 2.2 RedHat 7.0 kernel, the same hdparm tuning gives me
about 17Mb/s.
Anyone got any hints? I selected the ATA option. Might this be causing the
failure?
Anyone got any hints?
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
Basically you have drive that caught in the word93 rules change.
However, the error you got were real and the kernel did properly respeed
the drive to one step slower. The problem above prevented you from going
from ATA66 to ATA44, thus you fell to ATA33.
You RHS 7.0 kernel does not have all the fallback and rules testing to
keep things running the very best and in the safest way. Also you do not
have the rules for testing if the driver/host/device register and report
that all signals are valid and stable.
If you did not set TUNING option if the chipset has it specifically
flagged then you will not be able to retune the chipset/drive and the IO
will be out of sync.
At best it will reject DMA attempts, at worst this will do bad things to
data.
The stuff that 2.4 has that 2.2 does not have is following the rules and
guidelines set forth by the folks writing the rules.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
diff -urN linux-2.4.0-t10-1-pristine/drivers/ide/ide-features.c
linux-2.4.0-t10-1.smsc/drivers/ide/ide-features.c
--- linux-2.4.0-t10-1-pristine/drivers/ide/ide-features.c Thu Aug 3 16:07:42
2000
+++ linux-2.4.0-t10-1.smsc/drivers/ide/ide-features.c Tue Oct 10 00:00:38 2000
@@ -224,7 +224,8 @@
#ifndef CONFIG_IDEDMA_IVB
if ((drive-id-hw_config 0x6000) == 0) {
#else /* !CONFIG_IDEDMA_IVB */
- if ((drive-id-hw_config 0x2000) == 0) {
+ if (((drive-id-hw_config 0x2000) == 0) ||
+ ((drive-id-hw_config 0x4000) == 0)) {
#endif /* CONFIG_IDEDMA_IVB */
printk("%s: Speed warnings UDMA 3/4/5 is not functional.\n",
drive-name);
return 1;
@@ -260,7 +261,7 @@
#ifndef CONFIG_IDEDMA_IVB
(drive-id-hw_config 0x4000)
#endif /* CONFIG_IDEDMA_IVB */
- (drive-id-hw_config 0x2000)) ? 1 : 0);
+ (drive-id-hw_config 0x6000)) ? 1 : 0);
}
/*
Re: 2.4.0test-9: IDE problems
On Tue, 10 Oct 2000, Andre Hedrick wrote: Basically you have drive that caught in the word93 rules change. However, the error you got were real and the kernel did properly respeed the drive to one step slower. The problem above prevented you from going from ATA66 to ATA44, thus you fell to ATA33. You RHS 7.0 kernel does not have all the fallback and rules testing to keep things running the very best and in the safest way. Also you do not have the rules for testing if the driver/host/device register and report that all signals are valid and stable. Yes, I had some "interesting" modifications to a lot of my /usr when I tried to activate UDMA4 under RH7.0 (I don't believe my hardware is capable of UDMA4!) If you did not set TUNING option if the chipset has it specifically flagged then you will not be able to retune the chipset/drive and the IO will be out of sync. Shortly after my first post, I noticed and activated the Intel PIIX4 support + tuning. This got rid of the nasty errors but didn't get my 17Mb/sec. Trying your patch now. Cheers Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
Also set this option "CONFIG_IDEDMA_IVB" because you are in the transistion period of drive manufacturing. On Tue, 10 Oct 2000, Chris Evans wrote: On Tue, 10 Oct 2000, Andre Hedrick wrote: Basically you have drive that caught in the word93 rules change. However, the error you got were real and the kernel did properly respeed the drive to one step slower. The problem above prevented you from going from ATA66 to ATA44, thus you fell to ATA33. You RHS 7.0 kernel does not have all the fallback and rules testing to keep things running the very best and in the safest way. Also you do not have the rules for testing if the driver/host/device register and report that all signals are valid and stable. Yes, I had some "interesting" modifications to a lot of my /usr when I tried to activate UDMA4 under RH7.0 (I don't believe my hardware is capable of UDMA4!) If you did not set TUNING option if the chipset has it specifically flagged then you will not be able to retune the chipset/drive and the IO will be out of sync. Shortly after my first post, I noticed and activated the Intel PIIX4 support + tuning. This got rid of the nasty errors but didn't get my 17Mb/sec. Trying your patch now. Cheers Chris Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Bad CRC is a cable error. That could be misconfiguration but could also be
crap cables
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Tue, 10 Oct 2000, Andre Hedrick wrote: Also set this option "CONFIG_IDEDMA_IVB" because you are in the transistion period of drive manufacturing. Turned that on, applied the patch. BTW, your patch seems to make the "Speed warnings" failure _more_ likely?? Still refuses to activate UDMA3. 11.5Mb/sec vs. 17Mb/sec in 2.2. Is my hardware trying to tell me that 2.2 shouldn't be allowing me to run with UDMA3? It's rock solid and yes I've given it a pounding. Cheers Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
have the rules for testing if the driver/host/device register and report that all signals are valid and stable. Yes, I had some "interesting" modifications to a lot of my /usr when I tried to activate UDMA4 under RH7.0 (I don't believe my hardware is capable of UDMA4!) The 2.2 kernel we ship doesnt have the ide patches either so Im not suprised it got upset 8) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Alan Cox wrote:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Bad CRC is a cable error. That could be misconfiguration but could also be
crap cables
It went away when I enabled PIIX4 support + PIIX4 tuning support.
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Alan Cox wrote: The 2.2 kernel we ship doesnt have the ide patches either so Im not suprised it got upset 8) Ah yes you're correct. I saw the patch in the kernel SRPM but didn't look far enough to see: ... # IDE patch provides UDMA66 support, but is known to corrupt filesystems # on a few systems, so is not applied by default. Patch151: linux-2.2.16-ide-2805.patch ... # Dangerous IDE patch available but off by default #%patch151 -p1 ... Still, with hdparm -d1 -X67, I can presumably get UDMA3 and good 2.2 speeds (17Mb/s, or 21Mb/s with rawio) without this patch. Cheers Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.0test-9: IDE problems
On Wed, 11 Oct 2000, Chris Evans wrote: ... # IDE patch provides UDMA66 support, but is known to corrupt filesystems # on a few systems, so is not applied by default. Patch151: linux-2.2.16-ide-2805.patch ... # Dangerous IDE patch available but off by default #%patch151 -p1 ... Should I send RedHat an unpatch for 2.4? Andre Hedrick The Linux ATA/IDE guy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
