public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Fago <cfago@tconl.com>
To: jacob@chaos2.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.9: PDC20267 not working
Date: Sun, 09 Sep 2001 23:09:13 -0500	[thread overview]
Message-ID: <3B9C3CE9.D33DEE5@tconl.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0109091843220.31509-100000@inbetween.blorf.net>

Jacob Luna Lundberg wrote:
> 
> On Sun, 9 Sep 2001, Joe Fago wrote:
> 
> > System hangs on boot:
> 
> > PDC20267: IDE controller on PCI bus 00 dev 40
> 
> > This is the only device attached to the controller. Any suggestions?
> 
> I have seen this before.  I have a system that will do it every time right
> now, in fact.  You can try setting interrupts to edge-triggered in your
> BIOS if it has such an option; this usually ``fixes'' the problem for me.
> Of course, it will mean you can't share PCI interrupts, if I understand it
> correctly.  However, I'm not sure what's going on and nobody has commented
> on it thus far that I know of.  :(
> 
> -Jacob
> 
> -
> 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/

Thanks, that worked -- well the opposite worked. I had to set mine to 
triggered by `level' rather than `edge'. But I never would have suspected
it if you hadn't brought it up.

Thanks Again,
Joe

  parent reply	other threads:[~2001-09-10  4:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10  1:26 2.4.9: PDC20267 not working Joe Fago
2001-09-10  1:46 ` Jacob Luna Lundberg
2001-09-10  3:30   ` David Grant
2001-09-10  4:26     ` Joe Fago
2001-09-10  4:09   ` Joe Fago [this message]
2001-09-10  8:32 ` Rok Papež

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=3B9C3CE9.D33DEE5@tconl.com \
    --to=cfago@tconl.com \
    --cc=jacob@chaos2.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