From: Bruno Ducrot <ducrot@poupinou.org>
To: Thomas Renninger <trenn@suse.de>
Cc: Ben B <kernel@bb.cactii.net>, linux-acpi@vger.kernel.org
Subject: Re: DSDT/ASL compiler error
Date: Sun, 20 Aug 2006 12:09:43 +0200 [thread overview]
Message-ID: <20060820100943.GE4945@poupinou.org> (raw)
In-Reply-To: <1155991812.4302.1357.camel@queen.suse.de>
On Sat, Aug 19, 2006 at 02:50:12PM +0200, Thomas Renninger wrote:
> On Fri, 2006-08-18 at 22:18 +0200, Bruno Ducrot wrote:
> > On Fri, Aug 18, 2006 at 03:09:56PM +0200, Thomas Renninger wrote:
> > > (unfortunately, I hoped that was the missing hint to fix some things on
> > > this system).
> >
> > What things need to be fixed? I'm just curious.
>
> - _PPC always returns 1, therefore highest freq cannot be set
> (also reported recently on cpufreq list)
> https://bugzilla.novell.com/show_bug.cgi?id=179702
>
> - The other one could be an EC issue:
> battery and AC status is not updated.
> May be an interference with the mouse driver from the comments,
> no idea yet.
> https://bugzilla.novell.com/show_bug.cgi?id=200169
>
> Any hints are greatly appreciated...
> AFAIK both (at least first on several Core Duo models) phenomenons seem
> to happen on several (all?) new HP models.
>
My first though is to try atpic instead of apic and maybe tweak
apci_sci= parameter? I'll look more in details the bug.
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2006-08-20 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 17:03 DSDT/ASL compiler error Ben B
2006-08-18 10:33 ` Thomas Renninger
2006-08-18 11:25 ` Bruno Ducrot
2006-08-18 12:10 ` Ben B
2006-08-18 20:17 ` Bruno Ducrot
2006-08-18 13:09 ` Thomas Renninger
2006-08-18 20:18 ` Bruno Ducrot
2006-08-19 12:50 ` Thomas Renninger
2006-08-20 10:09 ` Bruno Ducrot [this message]
2006-08-20 10:22 ` Bruno Ducrot
2006-08-20 14:34 ` Thomas Renninger
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=20060820100943.GE4945@poupinou.org \
--to=ducrot@poupinou.org \
--cc=kernel@bb.cactii.net \
--cc=linux-acpi@vger.kernel.org \
--cc=trenn@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.