linux-kernel - Re: [PATCH 3/3] [2.6.25-rc5] Warn user about a BIOS bug in recent asus boards

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] [day] [month] [year] [list]

Date:	Mon, 31 Mar 2008 07:55:10 +0200
From:	Németh Márton <nm127@...email.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
CC:	"Zhang, Rui" <rui.zhang@...el.com>, Len Brown <lenb@...nel.org>,
	trenn@...e.de, linux-acpi <linux-acpi@...r.kernel.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] [2.6.25-rc5] Warn user about a BIOS bug in recent
 asus boards

Yinghai Lu wrote:
> 2008/3/13 Németh Márton <nm127@...email.hu>:
>>  [    0.715787] ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 16
> ...
>>  [   25.037202] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> ...
>>  [   86.320860] irq 16: nobody cared (try booting with the "irqpoll" option)
>>  [   86.320860] Pid: 0, comm: swapper Not tainted 2.6.25-rc5 #1
>>  [   86.320860]  [<c01578f7>] __report_bad_irq+0x27/0x90
>>  [   86.320860]  [<c0157b96>] note_interrupt+0x236/0x270
>>  [   86.320860]  [<c0156fa3>] ? handle_IRQ_event+0x53/0x60
>>  [   86.320860]  [<c015823a>] handle_fasteoi_irq+0x7a/0xd0
>>  [   86.320860]  [<c0106174>] do_IRQ+0x44/0xa0
>>  [   86.320860]  [<c0104c66>] common_interrupt+0x2e/0x34
>>  [   86.320860]  [<c0119039>] ? finish_task_switch+0x59/0xc0
>>  [   86.320860]  [<c0118fe0>] ? finish_task_switch+0x0/0xc0
>>  [   86.320860]  [<c03080d6>] schedule+0x2b6/0x470
>>  [   86.320860]  [<f892fdae>] ? acpi_processor_idle+0x0/0x436 [processor]
>>  [   86.320860]  [<c0102b65>] cpu_idle+0xb5/0xd0
>>  [   86.320860]  [<c030343c>] rest_init+0x5c/0x60
>>  [   86.320860]  =======================
>>  [   86.320860] handlers:
>>  [   86.320860] [<f8915830>] (yenta_interrupt+0x0/0xe0 [yenta_socket])
>>  [   86.320860] [<f8afd3f0>] (via_driver_irq_handler+0x0/0x1c0 [via])
>>  [   86.320860] Disabling IRQ #16
> 
> wonder if other device is using IRQ #16 too.
> 
> can you boot with pci=routeirq to check that?

Yes, in my system the yenta module uses the IRQ #16 also:

Yenta: ISA IRQ mask 0x0aa8, PCI irq 16

However, the "nobody cared" message is triggered by the "via" X11 driver.
There is a workaround to get rid of it: I switched to "openChrome" X11
driver ( http://www.openchrome.org/ ).

See also http://lkml.org/lkml/2008/3/16/10 and
http://bugzilla.kernel.org/show_bug.cgi?id=6790 .

Regards,

	Márton Németh
--
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/