All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Martin Zwickel <martin.zwickel@technotrend.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [QUESTION] hdparm -d1 on boot gives strange errors
Date: Thu, 24 Apr 2003 20:30:30 +0200	[thread overview]
Message-ID: <3EA82D46.6030604@inet6.fr> (raw)
In-Reply-To: <20030424101212.4687780c.martin.zwickel@technotrend.de>

Martin Zwickel wrote:

>Hi there!
>
>I'm running Gentoo, and on boot, a script enables DMA on all IDE-Devices.
>For my 1st disk on hdparm -d1 it waits 15secs and kernel gives strange errors.
>But for my 2nd disk it works ok.
>
>Any clues?
>

See below.

>Is it the damn SiS chipset?
>
>  
>

Maybe but drive/chipset combination is more likely. The one being out of 
spec is unknown to me.


Note :

What I don't understand is why you need the hdparm -d1 : from your boot 
log, the kernel already set DMA for you.

> hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(100)

> hdb: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63, UDMA(100)


These come after (probably when hdparm -d1 is called)

hda: dma_timer_expiry: dma status == 0x61
hda: timeout waiting for DMA
hda: timeout waiting for DMA
hda: (__ide_dma_test_irq) called while not waiting


My clue :

> WDC WD800BB-00CAA1

Hum, I have a WDC WD800BB-32CCB0 here and it is the only one that wouldn't work correctly with my SiS735-based K7S5A (sometimes values returned by the drive including its id string had one bit forced to 1 or 0, had to reboot to fix the issue).

Try a different drive...

LB.


      parent reply	other threads:[~2003-04-24 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24  8:12 [QUESTION] hdparm -d1 on boot gives strange errors Martin Zwickel
2003-04-24  8:19 ` Paul Rolland
2003-04-24 18:30 ` Lionel Bouton [this message]

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=3EA82D46.6030604@inet6.fr \
    --to=lionel.bouton@inet6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.zwickel@technotrend.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.