public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Joschka Sulzer <joschkasulzer@aol.com>
To: sanjoy@mrao.cam.ac.uk
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI-Problems with debian-etch & Kernel 2.6.16
Date: Tue, 28 Mar 2006 19:39:52 +0200	[thread overview]
Message-ID: <442974E8.5000403@aol.com> (raw)
In-Reply-To: <E1FO4hA-0000e4-00@skye.ra.phy.cam.ac.uk>

sanjoy@mrao.cam.ac.uk schrieb:
>> These messages appear every 10 seconds!
>>     
>
> Do you have thermal polling turned on?
>
> more /proc/acpi/thermal_zone/*/polling_frequency
>
> Not that you should turn the polling off, but maybe every time a
> thermal poll is run, the embedded controller (ec) does an UPDT, which
> also means it looks at the battery state.  And maybe the UPDT causes
> the namespace AE_NOT_FOUND.  Perhaps it didn't cause a problem before
> because the default used to be ec_intr=0, and the ec worked fine with
> that setting.
>
> You could try booting with ec_intr=0 to see if it suppresses the
> problem.
>
> I've spent a while (see bugzilla #5989) debugging the consequences of
> changing the default from ec_intr=0 to ec_intr=1 (which happened in
> 2.6.16-rc* sometime -- see the #5989 bugzilla entries for the exact
> git commit id).  Probably it's a good change in general -- I leave
> that to the experts -- but it has certainly exposed a few troubles in
> the mangy BIOS on my TP 600X.
>   

I don't care anymore; updating to 2.6.16 solved my problems ;-)
Now the Kernel boots without any Kernelparameters at all !


      reply	other threads:[~2006-03-28 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 15:04 ACPI-Problems with debian-etch & Kernel 2.6.16 Joschka Sulzer
2006-03-28  3:16 ` Sanjoy Mahajan
2006-03-28 17:39   ` Joschka Sulzer [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=442974E8.5000403@aol.com \
    --to=joschkasulzer@aol.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=sanjoy@mrao.cam.ac.uk \
    /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