From: Matthias Langer <mlangc@gmx.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dma_intr: status=0x51
Date: Sat, 08 Oct 2005 16:31:58 +0200 [thread overview]
Message-ID: <4347D85E.6060204@gmx.at> (raw)
In-Reply-To: <4347C0BD.1070107@gmx.at>
Matthias Langer wrote:
> Hemmann, Volker Armin wrote:
>
>> On Saturday 08 October 2005 04:15, Matthias Langer wrote:
>>
>>
>>> I just bought myself a new harddrive. While everything seems to work
>>> fine so far, I recognized these messages from dmesg:
>>>
>>> hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>>> hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
>>>
>>> I'm using vanilla-sources-2.6.12.5.
>>>
>>> Here are some other parts from dmesg, which are included to describe
>>> the
>>> relevant hardware in detail:
>>>
>>> SiI680: IDE controller at PCI slot 0000:00:09.0
>>> ....
>>> SiI680: chipset revision 1
>>> SiI680: BASE CLOCK == 133
>>> SiI680: 100% native mode on irq 10
>>> ide0: MMIO-DMA , BIOS settings: hda:pio, hdb:pio
>>> ide1: MMIO-DMA , BIOS settings: hdc:pio, hdd:pio
>>> ...
>>> Probing IDE interface ide1...
>>> hdc: _NEC DVD_RW ND-3540A, ATAPI CD/DVD-ROM drive
>>> hdd: Maxtor 6L250R0, ATA DISK drive
>>> hdd: max request size: 64KiB
>>> hdd: 490234752 sectors (251000 MB) w/16384KiB Cache, CHS=30515/255/63,
>>> UDMA(133)
>>> hdd: cache flushes supported
>>>
>>> Finally, this is what i get from hdparm -i /dev/hdd:
>>>
>>> Model=Maxtor 6L250R0, FwRev=BAH41G10, SerialNo=L59CY5SH
>>> Config={ Fixed }
>>> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
>>> BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=16
>>> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
>>> IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
>>> PIO modes: pio0 pio1 pio2 pio3 pio4
>>> DMA modes: mdma0 mdma1 mdma2
>>> UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6
>>> AdvancedPM=yes: disabled (255) WriteCache=enabled
>>> Drive conforms to: (null):
>>>
>>> Maybe someone can give me a hint what might be wrong with my
>>> configuration.
>>>
>>
>>
>> first off all, you should never mix ata and atapi devices (harddisks
>> and opticals) on one channel. That is known for making problems.
>>
>> Your error message could be have two origins: your cable is defective
>> or not properly seated (easy to check), or your harddisk is on its
>> way to the great vendor in the sky.
>> Get a different cable. Connect the drive with this new cable. ONLY
>> connect the drive, not the burner. Does the error still occurs? Bring
>> back the harddisk, where you bought it.
>>
>>
> Well, I tried to connect the drive to another cable with success.
> However, with this cable, which seemed to be an older one, the drive
> was restricted to UDMA(33).
>
> My theory about these messages now is the following:
> The HD I'm talking about is not directly connected to the ide-cable,
> but via a rather old 'HD-Box'. Thus I have:
>
> Controller->Modern IDE-Cable->HD-Box->Old IDE-Cable->HD.
>
> I think that the 'Old IDE-Cable' part is causing the troubles. However
> I can't verify that without rearranging a bulk of ide-drives.
> I'll buy myself a new box and tell you about the results.
Well, it was as I expected. After switching to an UDMA(133) compatible
mobile rack the error messages are gone.
>
> Thanks for your hints, Matthias
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-08 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 2:15 [gentoo-user] dma_intr: status=0x51 Matthias Langer
2005-10-08 3:46 ` Hemmann, Volker Armin
2005-10-08 12:51 ` Matthias Langer
2005-10-08 14:31 ` Matthias Langer [this message]
2005-10-10 18:30 ` [gentoo-user] " James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4347D85E.6060204@gmx.at \
--to=mlangc@gmx.at \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox