linux-kernel - Re: drive appears confused; hda lost interrupt; IRQ169: nobody cared

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-id: <alpine.LFD.1.10.0806241728070.3014@localhost.localdomain>
Date:	Tue, 24 Jun 2008 17:32:58 -0400 (EDT)
From:	Len Brown <lenb@...nel.org>
To:	Michael Schmitt <mschmitt@...xkiste.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: drive appears confused; hda lost interrupt; IRQ169: nobody cared


> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/