From: Len Brown <lenb@kernel.org>
To: Michael Schmitt <mschmitt@unixkiste.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: drive appears confused; hda lost interrupt; IRQ169: nobody cared
Date: Tue, 24 Jun 2008 17:32:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806241728070.3014@localhost.localdomain> (raw)
In-Reply-To: <1198331994.5964.12.camel@elara.tcw.local>
> thanks for the input! This BIOS seems to be current, there are just two
> beta BIOS available and as in the changelog there is nothing IRQ related
> written (there is almost nothing in it) I don't think I want to flash
> one of them, but here are the various options I tried:
>
> noapic > the one and the same thing, but this time (as classic PIC is
> used) nobody cared about IRQ 11.
>
> acpi=noirq > the same, this time IRQ 185
>
> pci=routeirq > the same as right above
>
> pci=nobios > without irqpoll hda DMA expire, IRQ lost, with irqpoll IRQ
> 169 again
>
> pci=noacpi > the same as two and three above
>
> irqfixup (instead of irqpoll) > hda DMA timer expire, IRQ lost
>
> I may have missed some options to try out, do you suggest some else?
> I've read kernel-parameters.txt and tried to find reasonable options...
> But what I don't get... how tragic are those "irq N nobody cared" and
> "drive appears confused" messages as I don't see a negative impact? And
> at the end, what do they mean? If an IRQ is disabled I thought the
> device behind it would not work anymore... but...
> Maybe I will give the two beta BIOS a try nevertheless.
Start by running a recent kernel, such as 2.6.25 or 2.6.26-rc.
when we hit the "nobody cared", we basically mask that IRQ forever.
If any devices on that IRQ needs interrupts, that would starve them
to death from that moment forward (unless you boot with irqpoll)
The fact that (at least some of) the devices on the disabled IRQ
still work means that they're secretly getting
an IRQ from someplace else, and you should be able to find
that place by watching /proc/interrupts.
-Len
prev parent reply other threads:[~2008-06-24 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 11:50 Michael Schmitt
2007-12-21 13:18 ` Alan Cox
2007-12-22 13:59 ` Michael Schmitt
2008-06-24 21:32 ` Len Brown [this message]
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=alpine.LFD.1.10.0806241728070.3014@localhost.localdomain \
--to=lenb@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmitt@unixkiste.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
all inboxes | Powered by JetHome®