From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Andrew Nelless <andrew@nelless.net>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.21-rc1: framebuffer/console boot failure
Date: Mon, 05 Mar 2007 14:12:38 +0800 [thread overview]
Message-ID: <1173075158.4158.1.camel@daplas> (raw)
In-Reply-To: <35793.86.7.220.119.1173019974.squirrel@wmbeta.mxes.net>
On Sun, 2007-03-04 at 14:52 +0000, Andrew Nelless wrote:
> On Mon, February 26, 2007 11:09 pm, Antonino A. Daplas wrote:
> >
> > Not sure if the timer override workaround for nvidia chipsets is the
> > culprit, but if you want, you can choose to revert that to the previous behavior (which is
> > ignoring ACPI timer override). Open arch/x86_64/kernel/earlyquirk.c:nvidia_bugs() and change
> > this line:
> >
> > if (acpi_table_parse(ACPI_SIG_HPET, nvidia_hpet_check)) return; into this:
> >
> > acpi_table_parse(ACPI_SIG_HPET, nvidia_hpet_check); /* return; */
> >
> >
> > Tony
> >
>
> This fixes the problem. After a lot of rebooting
> and testing the problem is definitely gone when this
> check is patched out and the ACPI timer override is
> ignored. It looks like there should be a cleaner
> patch than just obliterating the condition and return
> though.
>
> Perhaps the code should remain as is and
> "acpi_use_timer_override" could be complimented
> by exposing the "acpi_skip_timer_override" option to
> the kernel command line?
acpi_skip_timer_override is still documented in
Documentation/kernel-parameters.txt.
Tony
prev parent reply other threads:[~2007-03-05 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35472.86.7.220.119.1172237750.squirrel@wmbeta.mxes.net>
2007-02-24 11:09 ` 2.6.21-rc1: framebuffer/console boot failure Andrew Morton
2007-02-24 22:57 ` Andrew Nelless
2007-02-24 23:00 ` Andrew Nelless
2007-02-24 23:30 ` Antonino A. Daplas
2007-02-25 11:07 ` Andrew Nelless
2007-02-26 12:41 ` Antonino A. Daplas
2007-02-26 18:48 ` Andrew Nelless
2007-02-26 23:09 ` Antonino A. Daplas
2007-03-04 14:52 ` Andrew Nelless
2007-03-05 6:12 ` Antonino A. Daplas [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=1173075158.4158.1.camel@daplas \
--to=adaplas@gmail.com \
--cc=andrew@nelless.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).