From: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
To: thunder7-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: Possible quick fix for ACPI routing problem on Nforce2
Date: Sun, 13 Jul 2003 20:35:17 +0100 [thread overview]
Message-ID: <200307132035.17596.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030713053913.GB1284-4cpIIuwL6H0O5nXqB3HebLNAH6kLmebB@public.gmane.org>
> No joy on VIA KT400 chipset (bugzilla #678): ide0 get's IRQ 17, during
> boot multiple oopses occur, starting with 'IRQ 17: nobody cared' right
> after probing hda. Eventually it crashes hard, after probing hde.
I think this is related to the same problem. I've looked at your DSDT dump. It
doesn't have the same style of IRQ definitions that mine has... It defines
most of your IRQs as being connected to specific global system interrupt
numbers (p165, ACPI v2.0b) (Mine has all interrupts directed at link
devices).
However, IRQ 17 will be set up as a PCI-standard IRQ... So its _probably_ that
the first IDE device is expecting a different signalling standard to that
which it is getting... If you were able to get to a command prompt you'd
probably see /proc/interrupts showing millions of spurious IRQs like I did.
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
next prev parent reply other threads:[~2003-07-13 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200307122352.45704.adq_dvb@lidskialf.net>
[not found] ` <200307122352.45704.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-13 1:18 ` Possible quick fix for ACPI routing problem on Nforce2 Andrew de Quincey
[not found] ` <200307130218.44398.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-13 5:39 ` Jurriaan
[not found] ` <20030713053913.GB1284-4cpIIuwL6H0O5nXqB3HebLNAH6kLmebB@public.gmane.org>
2003-07-13 16:52 ` Andrew de Quincey
2003-07-13 19:35 ` Andrew de Quincey [this message]
2003-07-13 23:51 ` Andrew de Quincey
[not found] ` <200307140051.29231.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-14 1:08 ` Located the problem with the VIA KT400 board Andrew de Quincey
[not found] ` <200307140208.07975.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-14 15:32 ` hgfelger-9nAOAgdJVo4b1SvskN2V4Q
[not found] ` <Pine.LNX.4.33.0307141730001.1166-100000-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2003-07-14 15:53 ` Andrew de Quincey
2003-07-13 9:19 ` Re: Possible quick fix for ACPI routing problem on Nforce2 liste-9nAOAgdJVo4b1SvskN2V4Q
[not found] ` <Pine.LNX.4.33.0307131118210.561-100000-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2003-07-13 13:11 ` Andrew de Quincey
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=200307132035.17596.adq_dvb@lidskialf.net \
--to=adq_dvb-fmpxvn3awwjajazl26g0sa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=thunder7-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.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