From: "Németh Márton" <nm127@freemail.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: "Zhang, Rui" <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
trenn@suse.de, linux-acpi <linux-acpi@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] [2.6.25-rc5] Warn user about a BIOS bug in recent asus boards
Date: Mon, 31 Mar 2008 07:55:10 +0200 [thread overview]
Message-ID: <47F07CBE.5000900@freemail.hu> (raw)
In-Reply-To: <86802c440803291743i596678cem4f8ff727f208d2d3@mail.gmail.com>
Yinghai Lu wrote:
> 2008/3/13 Németh Márton <nm127@freemail.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-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Németh Márton" <nm127@freemail.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: "Zhang, Rui" <rui.zhang@intel.com>, Len Brown <lenb@kernel.org>,
trenn@suse.de, linux-acpi <linux-acpi@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] [2.6.25-rc5] Warn user about a BIOS bug in recent asus boards
Date: Mon, 31 Mar 2008 07:55:10 +0200 [thread overview]
Message-ID: <47F07CBE.5000900@freemail.hu> (raw)
In-Reply-To: <86802c440803291743i596678cem4f8ff727f208d2d3@mail.gmail.com>
Yinghai Lu wrote:
> 2008/3/13 Németh Márton <nm127@freemail.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
next prev parent reply other threads:[~2008-03-31 5:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 0:06 [PATCH 3/3] [2.6.25-rc5] Warn user about a BIOS bug in recent asus boards Thomas Renninger
2008-03-12 4:10 ` Len Brown
2008-03-12 5:40 ` Len Brown
2008-03-12 5:44 ` Zhang, Rui
2008-03-12 7:12 ` Zhang, Rui
2008-03-13 7:03 ` Zhang, Rui
2008-03-13 21:15 ` Németh Márton
2008-03-30 0:43 ` Yinghai Lu
2008-03-30 0:43 ` Yinghai Lu
2008-03-31 5:55 ` Németh Márton [this message]
2008-03-31 5:55 ` Németh Márton
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=47F07CBE.5000900@freemail.hu \
--to=nm127@freemail.hu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=trenn@suse.de \
--cc=yhlu.kernel@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.