linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wes Janzen <superchkn@sbcglobal.net>
To: John Goerzen <jgoerzen@complete.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Promise IDE controller crashes 2.4.22
Date: Fri, 28 Nov 2003 13:36:57 -0600	[thread overview]
Message-ID: <3FC7A3D9.3070500@sbcglobal.net> (raw)
In-Reply-To: <slrnbsche8.2ir.jgoerzen@christoph.complete.org>

Hi,

I'd suspect some sort of PCI problem, especially since you're running a 
K6.  What chipset is your motherboard based on?

I'm running a K6-2 400 on an FIC PA2013 with two PDC20269 controllers 
and my primary drive is a 6Y060L0.  I've had no problem with writes in 
DMA mode locking the system in 2.4.22 or any of the test kernels.  I 
have a 92048D8 that doesn't like UDMA-2 writes, but that won't hang the 
system; it just causes Linux to continually reset the interface until 
the kernel finally disables DMA on the drive.  Oddly, UDMA-1 works fine 
but this is a drive to controller hardware issue and not the drivers 
fault. 

Anyway, since the kernel seems to handle a DMA write gone bad, that 
leads me to believe that this issue is caused by the increased data 
flowing over the PCI bus when using DMA vs using PIO.  I'm not an expert 
though, maybe someone else has an opinion on this?

You might try putting the card in another slot too.  My cards are 
installed in slots 1 & 2 with 2 other PCI cards and an ISA device.  This 
particular motherboard seems to handle a full complement of expansion 
cards without problem, but I remember hearing nightmares about such a 
configuration back when these things were new.

-Wes-

John Goerzen wrote:

>Hi,
>
>I have a Promise 20269-based UDMA 133 IDE controller.  If I have DMA
>enabled on this controller, then when it is seeing heavy write activity,
>the system freezes.  No messages on the console, ctrl-alt-del does
>nothing, magic sysrq does nothing.
>
>Reads do not appear to cause this problem, and the problem also
>disappears if I disable DMA on the drive connected to the controller by
>using hdparm.
>
>System information:
>Linux pi 2.4.22 #3 Sat Oct 25 15:45:50 CDT 2003 i586 GNU/Linux
>AMD K6 400MHz processor
>
>lspci:
>00:08.0 Unknown mass storage controller: Promise Technology, Inc. 20269
>(rev 02)
>
>Drive: Maxtor 6Y160P0 150GB UDMA 133
>
>I have, in my .config:
>
>CONFIG_BLK_DEV_PDC202XX_NEW=y
>CONFIG_BLK_DEV_PDC202XX=y
>
>Thanks for any insight.
>
>-- John Goerzen
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>


  reply	other threads:[~2003-11-28 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 18:43 Promise IDE controller crashes 2.4.22 John Goerzen
2003-11-28 19:36 ` Wes Janzen [this message]
2003-11-29  1:23   ` John Goerzen
2003-11-29  9:12     ` Wes Janzen
     [not found] ` <200311281400.55500.bzolnier@elka.pw.edu.pl>
     [not found]   ` <20031129015230.GA3124@complete.org>
2003-11-29 14:23     ` Bartlomiej Zolnierkiewicz

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=3FC7A3D9.3070500@sbcglobal.net \
    --to=superchkn@sbcglobal.net \
    --cc=jgoerzen@complete.org \
    --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).