From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Danny ter Haar <dth@ncc1701.cistron.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: No luck getting 2.6.x kernel to work with ACPI on compaq laptop
Date: Mon, 26 Apr 2004 08:25:12 +0200 [thread overview]
Message-ID: <20040426062512.GA11567@bitwizard.nl> (raw)
In-Reply-To: <c65252$9cs$1@news.cistron.nl>
On Wed, Apr 21, 2004 at 05:51:30AM +0000, Danny ter Haar wrote:
> My Compaq presario 700EA locks up dead during boot with
> ACPI enabled. With bootoption acpi=off (or not compiled into the kernel)
> the machine works just fine.
>
> I put on acpi debug and typed over by hand (laptop's dont have serial
> ports these days anymore) :
>
> ACPI: Subsystem revision 20040326
> tbxface-0017[03] acpi_load_tables: ACPI tables succesfully acquired
> Parsing all Control Methods: [......]
> Table [DSDT] (id F005) - 433 Objects with 44 Devices 109 Methods 15
> Regions
> Parsing all Control Methods:
> Table [SSDT] (id f003) - 3 objects with 0 Devices 0 Methods 0 Regions
> ACPI: IRQ10 SCI: Edge set to level trigger
>
> After this the machine is dead in the water.
> No magic sysrq or anything.
It sounds as if some driver is using IRQ10, and that another device
is also on that IRQ. This will create an interrupt storm the moment
you switch the triggering from edge to level....
So: Which devices use IRQ10 when the computer works?
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
**** "Linux is like a wigwam - no windows, no gates, apache inside!" ****
next prev parent reply other threads:[~2004-04-26 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 5:51 No luck getting 2.6.x kernel to work with ACPI on compaq laptop Danny ter Haar
2004-04-26 6:25 ` Rogier Wolff [this message]
2004-04-26 7:05 ` Danny ter Haar
[not found] <A6974D8E5F98D511BB910002A50A6647615F9628@hdsmsx403.hd.intel.com>
2004-04-22 3:21 ` Len Brown
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=20040426062512.GA11567@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=dth@ncc1701.cistron.net \
--cc=linux-kernel@vger.kernel.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