From: Bob Gill <gillb4@telusplanet.net>
To: Alex Riesen <fork0@users.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: hdc: lost interrupt ide-cd: cmd 0x3 timed out ...
Date: Fri, 07 May 2004 13:41:58 -0600 [thread overview]
Message-ID: <1083958918.4734.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20040507110756.GA4647@linux-ari.internal>
OK, great! Adding acpi=noirq to the kernel line made the lost interrupt
problem go away, and getting rid of rhgb on the same line made the
problems I had with nvidia drivers killing the system at the login
prompt (white screen, no kbd response) go away.
One goes in, one goes out! ;)
Thanks,
Bob
On Fri, 2004-05-07 at 05:07, Alex Riesen wrote:
> >> zero IDE changes in bk6 -> bk8 but a lot of ACPI / IRQ related
>
> it's bk8 which broke sis961 (or revealed it native brokenness)
>
> > OK. My APIC is a SiS961.
>
> I have the same problem (and the same chipset).
> Passing acpi=noirq helps to work it around.
>
next prev parent reply other threads:[~2004-05-07 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 23:07 hdc: lost interrupt ide-cd: cmd 0x3 timed out with 2.6.6-rc3-bk8 Bob Gill
2004-05-07 11:07 ` hdc: lost interrupt ide-cd: cmd 0x3 timed out Alex Riesen
2004-05-07 19:41 ` Bob Gill [this message]
[not found] <A6974D8E5F98D511BB910002A50A6647615FAE21@hdsmsx403.hd.intel.com>
2004-05-09 2:56 ` Len Brown
2004-05-09 9:31 ` Alex Riesen
[not found] ` <1084135217.4430.141.camel@localhost.localdomain>
2004-05-10 2:16 ` Len Brown
2004-05-10 7:17 ` Alex Riesen
2004-05-10 8:08 ` Alex Riesen
[not found] <A6974D8E5F98D511BB910002A50A6647615FAF0B@hdsmsx403.hd.intel.com>
2004-05-10 3:27 ` Len Brown
2004-05-10 11:18 ` Alex Riesen
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=1083958918.4734.8.camel@localhost.localdomain \
--to=gillb4@telusplanet.net \
--cc=fork0@users.sourceforge.net \
--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