linux-kernel - Re: 2.6.21-rc1: framebuffer/console boot failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 4 Mar 2007 14:52:54 -0000 (GMT)
From:	"Andrew Nelless" <andrew@...less.net>
To:	"Antonino A. Daplas" <adaplas@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: 2.6.21-rc1: framebuffer/console boot failure

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?

This seems to have been exposed in the past:
https://www.x86-64.org/pipermail/discuss/2005-April/005948.html

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/