From: "Brown, Len" <len.brown@intel.com>
To: "Stephan von Krawczynski" <skraw@ithnet.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Problem Report 2.4.23 ACPI and ASUS TRL-DLS
Date: Mon, 1 Dec 2003 11:33:43 -0500 [thread overview]
Message-ID: <BF1FE1855350A0479097B3A0D2A80EE0CC8881@hdsmsx402.hd.intel.com> (raw)
Stephan,
Looks like this is ACPI specific and applies to all releases.
Please file an ACPI bug with the details below so we can get to the
bottom of it.
Thanks,
-Len
How to file a bug against ACPI:
http://bugzilla.kernel.org/
Category: Power Management
Component: ACPI
Please attach /proc/interrupts and the dmesg output showing the failure,
if possible;
And the same for the success case (pci=noacpi).
Please attach the output from lspci -v
Please attach the output from acpidmp, available in /usr/sbin/, or in
here
http://www.intel.com/technology/iapc/acpi/downloads/pmtools-20010730.tar
.gz
Please attach the output from dmidecode, available in /usr/sbin/, or
here:
http://www.nongnu.org/dmidecode/
> -----Original Message-----
> From: Stephan von Krawczynski [mailto:skraw@ithnet.com]
> Sent: Monday, December 01, 2003 11:11 AM
> To: Brown, Len
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Problem Report 2.4.23 ACPI and ASUS TRL-DLS
>
>
> On 30 Nov 2003 03:45:48 -0500
> Len Brown <len.brown@intel.com> wrote:
>
> > On Sat, 2003-11-29 at 12:10, Stephan von Krawczynski wrote:
> > > Hello,
> > >
> > > I just found out that enabling ACPI (kernel 2.4.23) on an
> ASUS TRL-DLS
> > > board
> > > leads to a failing boot, caused by not configuring the
> onboard scsi
> > > aic
> > > interfaces. In fact they are simply gone from the pci list (no
> > > kidding).
> > > Disabling ACPI leads to a perfectly working box with:
> >
> > Did earlier 2.4 or 2.6 kernels with ACPI configured work properly on
> > this box?
>
> Hello Len,
>
> sorry for delayed answer.
> Actually I never tried 2.6 on this box. Regarding earlier 2.4
> I can only tell
> you that SuSE 9.0 kernel (some patched
> 2.4.21-whoeverdidwhatever) does not boot
> either with acpi-enabled.
>
> > Does the failing kernel do any better if you tell it to boot with
> > "pci=noacpi"
>
> Yes, works.
>
> > or "noapic"?
>
> No, does not work.
>
> Hope that helps.
>
> Regards,
> Stephan
>
next reply other threads:[~2003-12-01 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 16:33 Brown, Len [this message]
[not found] <BF1FE1855350A0479097B3A0D2A80EE00184CE53@hdsmsx402.hd.intel.com>
2003-11-30 8:45 ` Problem Report 2.4.23 ACPI and ASUS TRL-DLS Len Brown
2003-12-01 16:10 ` Stephan von Krawczynski
-- strict thread matches above, loose matches on Subject: below --
2003-11-29 17:10 Stephan von Krawczynski
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=BF1FE1855350A0479097B3A0D2A80EE0CC8881@hdsmsx402.hd.intel.com \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).