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:	Mon, 5 Mar 2007 15:06:58 -0000 (GMT)
From:	"Andrew" <andrew@...less.net>
To:	"Antonino A. Daplas" <adaplas@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [4/6] 2.6.21-rc2: known regressions

On Mon, March 5, 2007 10:35 am, Antonino A. Daplas wrote:
>
> This is not a framebuffer nor console problem.
>
>
> I think Andrew Nelless confirmed that the cause is from the above
> commit. How to fix it, I don't know.  Perhaps the acpi_skip_timer_override boot option has to
> be used.
>
> Tony
>

Yes, apologies for taking so long with this.
I tried the acpi_skip_timer_override boot option last night,
after Tony pointed it out, and this also works around the
problem.

To summarize the cause is the changes made to early-quirks.c
in the mentioned commit and when this is reverted the problem
goes away.

There doesn't seem to be any sign of a living HPET on this
board or any way of enabling it in the current BIOS revision
but it seems on intermittent boots the check in early-quirks.c
returns, the timer override doesn't happen, and the kernel
fails to boot properly.

Btw, this is the Asus A8N-VM *CSM* main board, the non-CSM
variety actually has a nForce 410 rather than an
nForce 430 chip. I don't know whether they behave any
differently but the two boards actually have different BIOS
releases.

If reverting the commit would disable the HPET on boards
that do actually support it I personally don't mind using
the acpi_skip_timer_override workaround.

-
  Andrew

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ