From: Malte Cornils <mcornils-mcycREo4Un4@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: ACPI breakage (was: 2.6.x: local APIC results in hang at boot)
Date: Thu, 4 Mar 2004 23:48:53 +0100 [thread overview]
Message-ID: <200403042348.53040.mcornils@usta.de> (raw)
In-Reply-To: <1078340727.12999.4.camel-D2Zvc0uNKG8@public.gmane.org>
Am Mittwoch, 3. März 2004 20:05 schrieben Sie:
> > Linux version 2.6.2-rc3
>
> perhaps you can upgrade your kernel and let us know how it goes -- there
> have been some apic related fixes since then.
Hi, I have tested this with 2.6.4-rc2 and the same thing occurs.
If you need any further info, please let me know. And thanks for making
notebooks work well under Linux!
-Malte
> On Mon, 2004-03-01 at 16:02, Malte Cornils wrote:
> > > >ACPI: Subsystem revision 20040116
> > > >ACPI: IRQ9 SCI: Edge set to Level Trigger.
> > > >
> > > >and then nothing happens.
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
next prev parent reply other threads:[~2004-03-04 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200402031047.i13Algrs019289@harpo.it.uu.se>
[not found] ` <200402031047.i13Algrs019289-gq7oiAaKCbRt3AgVzhmPzw@public.gmane.org>
2004-03-01 21:02 ` ACPI breakage (was: 2.6.x: local APIC results in hang at boot) Malte Cornils
[not found] ` <200403012202.16728.mcornils-mcycREo4Un4@public.gmane.org>
2004-03-03 19:05 ` Len Brown
[not found] ` <1078340727.12999.4.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-04 22:48 ` Malte Cornils [this message]
[not found] ` <200403042348.53040.mcornils-mcycREo4Un4@public.gmane.org>
2004-03-08 13:39 ` Malte Cornils
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=200403042348.53040.mcornils@usta.de \
--to=mcornils-mcycreo4un4@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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