public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Malte Cornils <mcornils-mcycREo4Un4@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: 03 Mar 2004 14:05:28 -0500	[thread overview]
Message-ID: <1078340727.12999.4.camel@dhcppc4> (raw)
In-Reply-To: <200403012202.16728.mcornils-mcycREo4Un4@public.gmane.org>

> Linux version 2.6.2-rc3

Malte,
perhaps you can upgrade your kernel and let us know how it goes -- there
have been some apic related fixes since then.

thanks,
-Len

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.




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

  parent reply	other threads:[~2004-03-03 19:05 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 [this message]
     [not found]         ` <1078340727.12999.4.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-04 22:48           ` Malte Cornils
     [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=1078340727.12999.4.camel@dhcppc4 \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mcornils-mcycREo4Un4@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