public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolly <wwolly@gmx.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: IDE DMA hard lock at boot time (KT266A chpiset)
Date: Sun, 24 Feb 2002 03:06:01 +0100	[thread overview]
Message-ID: <200202240206.DAA19045@enigma.deepspace.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0202231740270.23868-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.33.0202231740270.23868-100000@coffee.psychology.mcmaster.ca>

Hi Mark,

Thank you very much for your quick responses to my problem. 

Due to your help I was now able to solve both problems. 

Now everything works great (including UDMA and the ethernet NIC 
and ACPI)
[however, the rtl8139 still refuses to work, but I can use the eepro100]. 

The three core things were: 
- switch off apic stuff
- you may enable ACPI but you must _disable_ ide power down 
  in the BIOS (seems to be a bug somewhere)
- This message is normal and can be ignored: 
  PCI: No IRQ known for interrupt pin A of device 00:11.1. Please try using 
    pci=biosirq.

Regards,
Wolly

[Sorry; everyone who did not CC me did not reach me because I seem 
to be `mysteriously' unsubscribed from lkml since Feb 01 when my 
mail box ran out of space...]

> maybe I wasn't clear on this: your problem seems to be irq-routing
> or irq lossage.  others have reported the same thing, and have fixed
> it by turning off the (spurious UP apic usage), turning off apics
> in bios, etc.

       reply	other threads:[~2002-02-24  2:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0202231740270.23868-100000@coffee.psychology.mcmaster.ca>
2002-02-24  2:06 ` Wolly [this message]
2002-02-23 18:12 IDE DMA hard lock at boot time (KT266A chpiset) Wolly
2002-02-22 19:28 ` Jose Luis Domingo Lopez

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=200202240206.DAA19045@enigma.deepspace.net \
    --to=wwolly@gmx.net \
    --cc=hahn@physics.mcmaster.ca \
    --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