public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Nils Faerber <nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: OT: Asus L3C BIOS update
Date: Sat, 7 Jun 2003 00:43:35 +0200	[thread overview]
Message-ID: <20030606224335.GB11776@hell.org.pl> (raw)
In-Reply-To: <20030528112032.32b0e481.nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>

Thus wrote Nils Faerber:
> > Does it happen to fix the occasional:
> > acpi_bus-0447 [2181] acpi_bus_set_power    : Device does not support
> > D1 acpi_power-0363 [2194] acpi_power_transition : Error transitioning
> > device [CFAN] to D0 acpi_bus-0496 [2193] acpi_bus_set_power    : Error
> > transitioning device [CFAN] to D0
> > 
> > at boot time, and a consequent oops + hang of everything which makes
> > use of ACPI? This is so rare that I consider it a sort of hardware /
> > BIOS bug(happens once a month, or so), but I would be really happy to
> > have it fixed. Or is it only me who experiences those?
> I think I have seen this too and yes I think it is gone now :)
> At least the bootup error message does not appear anymore.

Unfortunately, I've experienced this at least once for the new BIOS.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

      parent reply	other threads:[~2003-06-06 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25 13:45 OT: Asus L3C BIOS update Nils Faerber
     [not found] ` <20030525154505.5b5967ad.nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
2003-05-26 18:41   ` Nils Faerber
     [not found]     ` <20030527212456.GB9203@hell.org.pl>
     [not found]       ` <20030528112032.32b0e481.nils@kernelconcepts.de>
     [not found]         ` <20030528112032.32b0e481.nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
2003-06-06 22:43           ` Karol Kozimor [this message]

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=20030606224335.GB11776@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@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