linux-kernel - Re: irq 16: 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]

Date:	Tue, 23 Apr 2013 16:10:22 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Borislav Petkov <bp@...en8.de>
cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Takashi Iwai <tiwai@...e.de>, x86-ml <x86@...nel.org>,
	lkml <linux-kernel@...r.kernel.org>, Len Brown <lenb@...nel.org>
Subject: Re: irq 16: nobody cared

On Mon, 22 Apr 2013, Borislav Petkov wrote:
> [ 1449.134864] ACPI: Preparing to enter system sleep state S5
> [ 1449.141054] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored

and right after that the spurious interrupt happens. I asked Boris to
boot with acpi_osi=Linux on the command line and the issue went
away, though now it complains right before shutdown about:

[  123.142377] do_IRQ: 2.179 No irq handler for vector (irq -1)

I wouldn't be surprised if that vector 179 was previously used for
irq16.

Without acpi_osi=Linux the BIOS manages to put the hardware into a
state which causes an interrupt to be sent from thin air.

We should have an annual "Brain Is Obviously Superfluous" award.
This one would be high up on the nomination list.

Yours grumpy

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