linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Savola <pekkas@netcore.fi>
To: <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.19pre14 VP3 + Quantum: dma on hangs
Date: Mon, 26 Feb 2001 21:43:15 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.31.0102262135550.2005-100000@netcore.fi> (raw)
In-Reply-To: <Pine.LNX.4.31.0102241544320.1149-100000@netcore.fi>

On Sat, 24 Feb 2001, Pekka Savola wrote:

There was a suggestion to try the IDE patch.  With it, the same kind of
freezing happens immediately after 'hdparm -d 1'.

With the patch, the kernel message at bootup is like:

hda: QUANTUM FIREBALLP AS20.5, 19595MB w/1902kB Cache, CHS=2498/255/63
hdc: QUANTUM FIREBALLP AS20.5, 19595MB w/1902kB Cache, CHS=39813/16/63
hdd: IBM-DTTA-350840, 8063MB w/467kB Cache, CHS=16383/16/63, UDMA(33)
hdb: ATAPI 4X CD-ROM drive, 256kB Cache

So, it'd appear Fireballs don't get UDMA enabled for some reason.

In the patch there are a few shit-listed drives:
---
const char *quirk_drives[] = {
       "QUANTUM FIREBALLlct08 08",
       "QUANTUM FIREBALLP KA6.4",
       "QUANTUM FIREBALLP LM20.4",
       "QUANTUM FIREBALLP LM20.5",
        NULL
};
---

However, this is FIREBALLP AS20.5, not LM20.5.

Any idea why DMA doesn't get on ?


> Hello all,
>
> Using 2.2.19pre14 with:
>  * software raid
>  * raid1 readbalancing
>  * i2c
>  * lm_sensors
>  * ipsec
>
> My drives are as follows:
>
> hda: QUANTUM FIREBALLP AS20.5, 19595MB w/1902kB Cache, CHS=2498/255/63
> hdc: QUANTUM FIREBALLP AS20.5, 19595MB w/1902kB Cache, CHS=39813/16/63
> hdd: IBM-DTTA-350840, 8063MB w/467kB Cache, CHS=16383/16/63
> hdb: ATAPI 4X CD-ROM drive, 256kB Cache
>
> [ Bios sees: HDA & HDC : udma5, HDD: udma2 ]
>
> And the mainboard related stuff in lspci:
>
> 00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
> 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo VP] (rev 47)
> 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
> 00:07.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 02)
> 00:07.3 Bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 10)
>
> Now, if I turn on dma on hdd, and run hdparm benchmark, everything works
> fine.
>
> If I turn on dma with hdparm on hda or hdc, next disk activity will freeze
> the system completely.  No keyboard interaction, not anything.  Only reset
> helps.
>
> Also, if I disable UDMA in bios completely on hda and hdc, hdparm will
> work, but the speed is awful (only ~6 MB/s) even if DMA is enabled.
>
> The most relevant kernel settings are, I think:
>
> CONFIG_BLK_DEV_IDEDMA=y
> # CONFIG_BLK_DEV_OFFBOARD is not set
> CONFIG_IDEDMA_AUTO=y
> # CONFIG_BLK_DEV_OPTI621 is not set
> # CONFIG_BLK_DEV_ALI15X3 is not set
> # CONFIG_BLK_DEV_TRM290 is not set
> # CONFIG_BLK_DEV_NS87415 is not set
> CONFIG_BLK_DEV_VIA82C586=y
> # CONFIG_BLK_DEV_CMD646 is not set
> # CONFIG_BLK_DEV_CS5530 is not set
> # CONFIG_IDE_CHIPSETS is not set
>
> Any ideas?
>
> Please Cc:
>

-- 
Pekka Savola                  "Tell me of difficulties surmounted,
Netcore Oy                    not those you stumble over and fall"
Systems. Networks. Security.   -- Robert Jordan: A Crown of Swords


      reply	other threads:[~2001-02-26 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-24 14:31 2.2.19pre14 VP3 + Quantum: dma on hangs Pekka Savola
2001-02-26 19:43 ` Pekka Savola [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=Pine.LNX.4.31.0102262135550.2005-100000@netcore.fi \
    --to=pekkas@netcore.fi \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).