From: Marek Michalkiewicz <marekm-HuSaFJn/uQtscumT1wHf3A@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: MS-6368L ACPI IRQ problem still in 2.4.21
Date: Tue, 24 Jun 2003 00:15:41 +0200 [thread overview]
Message-ID: <20030623221541.GA8096@alf.amelek.gda.pl> (raw)
Hi,
long time ago I noticed a problem with the ACPI IRQ not working
if it is _not_ shared with some other PCI IRQ. The problem still
exists in the 2.4.21 kernel, confirmed on two machines with the
MSI MS-6368L motherboard (VIA PLE133 chipset).
I need ACPI for just one thing: to run "shutdown -h now" after the
power button is pressed. (The box is a server which usually has
no keyboard connected.)
As I can see in /proc/interrupts, the BIOS usually allocates IRQ9
for ACPI (not shared with anything else), and the IRQ9 counter is
always zero. Pressing the power button has no effect at all.
There is an easy workaround: in BIOS setup, set IRQ9 to "Legacy ISA"
instead of "PCI/ISA PnP" so that ACPI gets some other IRQ, shared
with some other PCI devices (in my case, IRQ11 is shared by: acpi,
usb-uhci, usb-uhci, eth0). Then the power button works fine.
Is this a known problem? Should I complain to MSI (BIOS fix),
or is this a Linux bug? Any patches I should try? This looks
a bit unusual to me - one would expect problems if an IRQ _is_
shared, and some broken hardware/driver doesn't like sharing...
If there is no known fix, perhaps the "Legacy ISA" workaround
(which I discovered by accident) should be documented somewhere?
Thanks,
Marek
next reply other threads:[~2003-06-23 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 22:15 Marek Michalkiewicz [this message]
[not found] ` <20030623221541.GA8096-doiv7TgLjtAqfaPKo25k7GZHpeb/A1Y/@public.gmane.org>
2003-06-23 22:23 ` [ACPI] MS-6368L ACPI IRQ problem still in 2.4.21 Matthew Wilcox
[not found] ` <20030623222311.GD25982-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-06-24 5:46 ` Marek Michalkiewicz
[not found] ` <20030624054612.GA20235-doiv7TgLjtAqfaPKo25k7GZHpeb/A1Y/@public.gmane.org>
2003-06-24 11:26 ` Matthew Wilcox
[not found] ` <20030624112630.GB451-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-06-24 22:18 ` Marek Michalkiewicz
[not found] ` <20030624221809.GA1805-doiv7TgLjtAqfaPKo25k7GZHpeb/A1Y/@public.gmane.org>
2003-06-25 0:28 ` Sérgio Monteiro Basto
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=20030623221541.GA8096@alf.amelek.gda.pl \
--to=marekm-husafjn/uqtscumt1whf3a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox