public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Loschwitz <madkiss@madkiss.org>
To: "Georg C. F. Greve" <greve@gnu.org>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: ACPI freezes 2.6.1 on boot
Date: Wed, 21 Jan 2004 16:35:51 +0100	[thread overview]
Message-ID: <20040121153551.GA2615@minerva.local.lan> (raw)
In-Reply-To: <m3isj5a73u.fsf@reason.gnu-hamburg>

[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]

On Wed, Jan 21, 2004 at 12:12:05PM +0100, Georg C. F. Greve wrote:
> Hi all,
> 
> I've seen the mail by Martin Loschwitz of January 1st 2004, in which
> he reported:
> 
>  > I'm writing this mail as I'm discovering ACPI related problems on
>  > my Acer TravelMate 800LCi notebook with Linux 2.6.1-rc1-mm1.
> 
>  > While the system boots up fine with Linux 2.6.1-rc1, with
>  > 2.6.1-rc1-mm1 it hangs while booting. The last message printed to
>  > screen is "ACPI: IRQ 9 was Edge Triggered, setting to Level
>  > Triggerd". This is fully reproducable with a Linux 2.6.0 kernel
>  > which has the ACPI20031203 patch applied.
> 
> I'm now seeing the _exact same problem_ on an ASUS M2400N [*] with a
> Linux 2.6.1 (unpatched) kernel. The kernel freezes after printing 
> 
>  "ACPI: IRQ 9 was Edge Triggered, setting to Level Triggerd" 
> 
> (yes, the typo is in the kernel, it seems)
> 
> I've seen no reply to his mail. Has the problem been solved or is it
> still a known bug(tm)?
> 
> Martin? Were you successful in resolving that problem?
> 
By now means. I, however, didn't even try to get a solution since back
then. Since the bug appeared with a patched 2.6.0 and 2.6.1-mm2, which
was one of the first patches including the new ACPI, it was clear to
me that it was ACPI related and that I would better wait for somebody
to find the root of the evil and to kill it.

I see your "Notebook vs. Linux"-story continues to be unsuccessfull,
though :(

> Regards,
> Georg
> 
> 
> [*] Pentium 4 M Centrino, 1.6, 512MB, Intel 855GM chipset
> 
> -- 
> Georg C. F. Greve                                       <greve@gnu.org>
> Free Software Foundation Europe	                 (http://fsfeurope.org)
> Brave GNU World	                           (http://brave-gnu-world.org)


-- 
  .''`.   Martin Loschwitz           Debian GNU/Linux developer
 : :'  :  madkiss@madkiss.org        madkiss@debian.org
 `. `'`   http://www.madkiss.org/    people.debian.org/~madkiss/
   `-     Use Debian GNU/Linux 3.0!  See http://www.debian.org/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-21 15:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 11:12 PROBLEM: ACPI freezes 2.6.1 on boot Georg C. F. Greve
2004-01-21 15:35 ` Martin Loschwitz [this message]
2004-01-21 16:12   ` Georg C. F. Greve
2004-01-21 18:56 ` Linus Torvalds
2004-01-21 21:15   ` Georg C. F. Greve
2004-01-21 21:51     ` [ACPI] " Sérgio Monteiro Basto
2004-01-21 22:33       ` Georg C. F. Greve
2004-01-21 23:31         ` Sérgio Monteiro Basto
2004-01-22 10:32           ` Georg C. F. Greve
2004-01-21 22:18     ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2004-01-21 16:32 Nakajima, Jun
2004-01-21 21:21 ` Georg C. F. Greve
2004-01-21 22:29   ` Georg C. F. Greve
2004-01-21 21:57 Brown, Len

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=20040121153551.GA2615@minerva.local.lan \
    --to=madkiss@madkiss.org \
    --cc=greve@gnu.org \
    --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