public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe-l3A5Bk7waGM@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [ACPI Debug] String: Length 0x0F, "Entering RTMP()"
Date: Wed, 15 Sep 2004 08:06:15 +0200	[thread overview]
Message-ID: <20040915060615.GB2304@suse.de> (raw)
In-Reply-To: <1095197368.5430.8.camel@d845pe>

On Tue, Sep 14 2004, Len Brown wrote:
> On Tue, 2004-09-14 at 02:16, Jens Axboe wrote:
> > Hi,
> > 
> > 2.6.9-rc2 is throwing a lot of these errors on my system:
> > 
> > [ACPI Debug] String: Length 0x0F, "Entering RTMP()"
> > [ACPI Debug] String: Length 0x0F, "Entering TIN2()"
> > [ACPI Debug] String: Length 0x0F, "Existing RTMP()"
> > 
> > About 450 of these three lines repeated so far, seem to get one every
> > 5
> > seconds or so. Box is an Athlon64 solo, let me know if you want more
> > info (and what).
> > 
> > --
> > Jens Axboe
> 
> These are due to debug statements in your BIOS AML code.
> The Linux AML interpreter recognizes them and sends
> them to the console.
> 
> Start by checking that you're running a production BIOS.

I'm not

> echo 0 >/proc/acpi/debug_level should make them go away.

Ah thanks, yes that works!

-- 
Jens Axboe



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m

      reply	other threads:[~2004-09-15  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040914061641.GD2336@suse.de>
     [not found] ` <20040914061641.GD2336-l3A5Bk7waGM@public.gmane.org>
2004-09-14 21:29   ` [ACPI Debug] String: Length 0x0F, "Entering RTMP()" Len Brown
2004-09-15  6:06     ` Jens Axboe [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=20040915060615.GB2304@suse.de \
    --to=axboe-l3a5bk7wagm@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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