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

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...

Regards,
Stephan

  reply	other threads:[~2004-01-16 11:26 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 [this message]
2004-01-16 13:14       ` Andreas Haumer
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=20040116122550.23331cf5.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=andreas@xss.co.at \
    --cc=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@intel.com \
    --cc=marcelo.tosatti@cyclades.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