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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1198331994.5964.12.camel@elara.tcw.local>
Date:	Sat, 22 Dec 2007 14:59:54 +0100
From:	Michael Schmitt <mschmitt@...xkiste.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: drive appears confused; hda lost interrupt; IRQ169: nobody
	cared

Hi Alan

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.

greetings
Michael

Am Freitag, den 21.12.2007, 13:18 +0000 schrieb Alan Cox: 
> > I changed the mainboard of this computer recently to this P4P800-SE from
> > a rubish oem SIS chipset board and I had the problems right away,
> > starting with kernel 2.6.18 but problems persist even with 2.6.23
> > (Debian kernels).
> 
> Your IRQ routing appears broken. That is usually a BIOS problem.
> 
> > So, my main concern is that there may be some sort of data corruption
> > even if I don't see them right now but as the messages seem to be very
> > serious... dunno. Any thoughts?
> 
> Check for BIOS uupdates also try playing with the various pci irq
> routing, APIC and acpi options. 
> 
> Alan

--
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/