DriveStatusError BadCRC

DriveStatusError BadCRC

[sampei02]

I bought new Maxtor HD 80 GB but Fedora Core 3 gives  this message about
1 hour after boot stage (This one occurs in a variable time):


hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
.
.
.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide0: reset: success
Kernel panic - not syncing: mm/mmap.c:534: spin_lock(mm/rmap.c:cb80cf08)


already locked by /0. (Not tainted)

[c0120445] panic+0x42/0x1c0
[c015e1e1] vma_prio_tree_insert+017/0x2a
[c01656d3] vma_adjust+0x322/0x556
[c0166f30] split_vma+0xdd/0xf5
[c0167c70] mprotect_fixup+0xf1/0x1ca
[c0167edb] sys_mprotect+0192/0x253
[c010392d] syscall_call+0x7/0xb

I already used 80-wire cable and my Maxtor HD plugs are seated properly.
I'm using Kernel 2.6.12-1.1372 on Fedora Core 3
HD is 80 GB Maxtor ATA/133

With hdparm command I can see hda is set in "udma5".
How can I solve it ?

__________________________________________________________________
TISCALI ADSL 1.25 MEGA
Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone Telecom
a partire da 19,95 Euro/mese.
Attivala entro il 31 agosto, il primo MESE è GRATIS! CLICCA QUI.
http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/

Re: DriveStatusError BadCRC

[Tyler]

I would suggest using the smartmontools to read the SMART registers on 
the drive, it sounds like your drive is bad.  The other way to verify if 
the drive is bad or not, is to simply put it in another computer and try 
running it there, and see if it has the same problems.  Process of 
elimination.

Tyler.

sampei02@tiscali.it wrote:

>I bought new Maxtor HD 80 GB but Fedora Core 3 gives  this message about
>1 hour after boot stage (This one occurs in a variable time):
>
>
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
>ide: failed opcode was: unknown
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
>ide: failed opcode was: unknown
>.
>.
>.
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
>ide: failed opcode was: unknown
>ide0: reset: success
>Kernel panic - not syncing: mm/mmap.c:534: spin_lock(mm/rmap.c:cb80cf08)
>
>
>already locked by /0. (Not tainted)
>
>[c0120445] panic+0x42/0x1c0
>[c015e1e1] vma_prio_tree_insert+017/0x2a
>[c01656d3] vma_adjust+0x322/0x556
>[c0166f30] split_vma+0xdd/0xf5
>[c0167c70] mprotect_fixup+0xf1/0x1ca
>[c0167edb] sys_mprotect+0192/0x253
>[c010392d] syscall_call+0x7/0xb
>
>I already used 80-wire cable and my Maxtor HD plugs are seated properly.
>I'm using Kernel 2.6.12-1.1372 on Fedora Core 3
>HD is 80 GB Maxtor ATA/133
>
>With hdparm command I can see hda is set in "udma5".
>How can I solve it ?
>
>__________________________________________________________________
>TISCALI ADSL 1.25 MEGA
>Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone Telecom
>a partire da 19,95 Euro/mese.
>Attivala entro il 31 agosto, il primo MESE è GRATIS! CLICCA QUI.
>http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>

Re: DriveStatusError BadCRC

[Eric D. Mudama]

51/84 indicates the crc failed on the incoming write data from your
system.  These failures should be very rare (on PATA), but the bummer
is they don't have anything to do with bad blocks on the media or
degrading heads...

What is the temperature like inside your case?  What host adapter are
you using?  How many drives in the system?



On 8/7/05, sampei02@tiscali.it <sampei02@tiscali.it> wrote:
> I bought new Maxtor HD 80 GB but Fedora Core 3 gives  this message about
> 1 hour after boot stage (This one occurs in a variable time):
> 
> 
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
> ide: failed opcode was: unknown
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
> ide: failed opcode was: unknown
> .
> .
> .
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: Error=0x84 { DriveStatusError BadCRC }
> ide: failed opcode was: unknown
> ide0: reset: success
> Kernel panic - not syncing: mm/mmap.c:534: spin_lock(mm/rmap.c:cb80cf08)
> 
> 
> already locked by /0. (Not tainted)
> 
> [c0120445] panic+0x42/0x1c0
> [c015e1e1] vma_prio_tree_insert+017/0x2a
> [c01656d3] vma_adjust+0x322/0x556
> [c0166f30] split_vma+0xdd/0xf5
> [c0167c70] mprotect_fixup+0xf1/0x1ca
> [c0167edb] sys_mprotect+0192/0x253
> [c010392d] syscall_call+0x7/0xb
> 
> I already used 80-wire cable and my Maxtor HD plugs are seated properly.
> I'm using Kernel 2.6.12-1.1372 on Fedora Core 3
> HD is 80 GB Maxtor ATA/133
> 
> With hdparm command I can see hda is set in "udma5".
> How can I solve it ?
> 
> __________________________________________________________________
> TISCALI ADSL 1.25 MEGA
> Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone Telecom
> a partire da 19,95 Euro/mese.
> Attivala entro il 31 agosto, il primo MESE è GRATIS! CLICCA QUI.
> http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: DriveStatusError BadCRC

[Erik Slagter]

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

On Sun, 2005-08-07 at 08:38 -0600, Eric D. Mudama wrote:
> 51/84 indicates the crc failed on the incoming write data from your
> system.  These failures should be very rare (on PATA), but the bummer
> is they don't have anything to do with bad blocks on the media or
> degrading heads...
> 
> What is the temperature like inside your case?  What host adapter are
> you using?  How many drives in the system?

I'd suggest trying another cable... And also a lower UDMA setting.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

SOLVED: DriveStatusError BadCRC

[sampei02]

I replaced 80 wire flat cable with another 40 wire cable.
In this way I have no errors but now UDMA mode is set to 2 value.
I'm sure that MOTHERBOARD supports UDMA ATA/33/66/100 BUS IDE ports.
What do you think ?


>-- Messaggio Originale --
>Subject: Re: DriveStatusError BadCRC
>From:	Erik Slagter <erik@slagter.name>
>To:	linux-ide@vger.kernel.org
>Date:	Mon, 08 Aug 2005 11:54:17 +0200
>
>
>On Sun, 2005-08-07 at 08:38 -0600, Eric D. Mudama wrote:
>> 51/84 indicates the crc failed on the incoming write data from your
>> system.  These failures should be very rare (on PATA), but the bummer
>> is they don't have anything to do with bad blocks on the media or
>> degrading heads...
>> 
>> What is the temperature like inside your case?  What host adapter are
>> you using?  How many drives in the system?
>
>I'd suggest trying another cable... And also a lower UDMA setting.
>
>Allegato: signature.asc
>


__________________________________________________________________
TISCALI ADSL 1.25 MEGA
Solo con Tiscali Adsl navighi senza limiti e telefoni senza canone Telecom
a partire da 19,95 Euro/mese.
Attivala entro il 31 agosto, il primo MESE è GRATIS! CLICCA QUI.
http://abbonati.tiscali.it/adsl/sa/1e25flat_tc/

Re: SOLVED: DriveStatusError BadCRC

[Tejun Heo]

sampei02@tiscali.it wrote:
> I replaced 80 wire flat cable with another 40 wire cable.
> In this way I have no errors but now UDMA mode is set to 2 value.
> I'm sure that MOTHERBOARD supports UDMA ATA/33/66/100 BUS IDE ports.
> What do you think ?

  [sticking nose in...]

  In that case, it could be one of...

  #1 faulty cable, try another 80c cable
  #2 only one device gets attached to the cable but it's using the 
middle connector.  You need to use the connector at the end of cable 
when you connect only one device.  (I think it became a requirement w/ 
newer transfer modes.  No? still recommendation?)
  #3 faulty IDE controller (or faulty traces from the controller to cable)
  #4 faulty drive

  My bet is on #1 or #2.

-- 
tejun