public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Haumer <andreas@xss.co.at>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	andrew@walrond.org, luming.yu@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: ACPI: problem on ASUS PR-DLS533
Date: Fri, 16 Jan 2004 14:14:41 +0100	[thread overview]
Message-ID: <4007E3C1.1020100@xss.co.at> (raw)
In-Reply-To: <20040116122550.23331cf5.skraw@ithnet.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

Stephan von Krawczynski wrote:
> On Fri, 16 Jan 2004 08:30:13 -0200 (BRST)
> Marcelo Tosatti <marcelo.tosatti@cyclades.com> wrote:
>
>
>>>I don't know if Stephan filed the report as you requested, but I have tried
>>>to independantly confirm this regression on a TR-DLSR server I have here,
>>>but unfortunately neither 2.4.23 or 2.4.24 will boot from the Mylex 170
>>>Raid card(DAC960) with ACPI enabled, so I never get to lspci :(
>>>
>>>I could perhaps capture the boot messages over serial port, if that would
>>>be helpful?
>>
>>Yes, please, with and without ACPI. (I suppose disabling ACPI fixes the
>>problem?)
>>
>>Stephan: There is nothing from 2.4.23 to .24 which could cause such
>>breakage. It probably didnt work with 2.4.23 also?
>
>
> Hello,
>
> I am sorry for the long delay, I ran completely out of time unfortunately.
> In short:
> You are right, there is no regression between .23 and .24, shoot me.
> Anyway I know there was a former kernel that worked with ACPI on this board.
> I wanted to return the info which one though, but don't have it yet.
> Anyway as soon as I find some spare time I will go hunting...
>
For the system I noticed the ACPI problems (Asus PR-DLS533),
the regression occured after 2.4.21

With pristine 2.4.21 the system could boot with ACPI enabled,
but with the new ACPI patches introduced with the 2.4.21-ac
series (and integrated in the 2.4.x series later on) it did not.

Does your board have several PCI busses (lspci -v) ?
It seems the problem is with the BIOS not correctly initializing
and/or reporting some ACPI data structures, so the Linux ACPI code
does not find (and therefore initialize) some devices on higher PCI
bus numbers.

It looks like it's Asus who should fix their BIOS.

Does anyone know how the other OS(tm) does handle
ACPI PCI bus initialisation on these boards? Do
they have some workaround for such broken BIOS?
(I have never tried the other OS(tm) on this board)

- - andreas

- --
Andreas Haumer                     | mailto:andreas@xss.co.at
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAB+O/xJmyeGcXPhERArLfAKCgPxnCWEA2gSC4O0k9plGhNp231gCgpz1m
TVH4WHTDK2u+4HVFZA3x0m4=
=NyKq
-----END PGP SIGNATURE-----


  reply	other threads:[~2004-01-16 13:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12  5:14 ACPI: problem on ASUS PR-DLS533 Yu, Luming
2004-01-15 18:14 ` Andrew Walrond
2004-01-16 10:30   ` Marcelo Tosatti
2004-01-16 11:25     ` Stephan von Krawczynski
2004-01-16 13:14       ` Andreas Haumer [this message]
2004-01-16 13:22         ` Stephan von Krawczynski
2004-01-16 12:07     ` Andrew Walrond
     [not found] <BF1FE1855350A0479097B3A0D2A80EE0020ADE84@hdsmsx402.hd.intel.com>
2004-01-18 18:19 ` Len Brown
  -- strict thread matches above, loose matches on Subject: below --
2004-01-18  4:23 Yu, Luming
2004-01-18 11:42 ` Andreas Haumer
2004-01-18 16:01   ` Andrew Walrond
2004-01-18 17:00     ` Stephan von Krawczynski
2004-01-18  4:18 Yu, Luming
2004-01-18  9:01 ` Andrew Walrond
2004-01-07 10:50 Yu, Luming
2004-01-07 12:35 ` Stephan von Krawczynski
2004-01-07 22:58   ` Marcelo Tosatti
2003-12-23 12:04 Andreas Haumer
2003-12-23 14:48 ` Andrew Walrond
2003-12-23 15:21   ` Andreas Haumer
2004-01-07 10:37     ` Stephan von Krawczynski
2004-01-07 14:30       ` Andrew Walrond

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=4007E3C1.1020100@xss.co.at \
    --to=andreas@xss.co.at \
    --cc=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@intel.com \
    --cc=marcelo.tosatti@cyclades.com \
    --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