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]
Message-ID: <46B23E08.4070106@redhat.com>
Date:	Thu, 02 Aug 2007 16:26:48 -0400
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Cal Peake <cp@...olutedigital.net>
CC:	Gabriel C <nix.or.die@...glemail.com>,
	Frank Hale <frankhale@...il.com>,
	Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel ACPI Mailing List <linux-acpi@...r.kernel.org>,
	len.brown@...el.com, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: ACPI on Averatec 2370

On 08/02/2007 03:42 PM, Cal Peake wrote:
> On Thu, 2 Aug 2007, Chuck Ebbert wrote:
> 
>> On 08/02/2007 01:50 PM, Cal Peake wrote:
>>> This problem seems to be getting worse. With the latest linus tree, after 
>>> the initial hang where the power button is needed to bring the system back 
>>> to life, the boot process slows to a crawl.
>>>
>>> Although if I repeatedly press the shift key it'll help move things along. 
>>> I'm guessing the keyboard interrupt firing off is doing something to help 
>>> it. The system seems OK though after booting is finished.
>>>
>>> Upon shutdown it actually stalls out without help from the shift key.
>>>
>>> Any thoughts on this, or tips to help debug it further?
>> Try the 'nolapic_timer' option.
> 
> Ah, thank you Chuck! This looks to have fixed the stalling/hanging 
> problems I was having.
> 
> Now I'm wondering if arch/i386/kernel/cpu/amd.c:amd_apic_timer_broken() 
> can (or needs to) be updated for this particular CPU revision.

What does your /proc/cpuinfo say?

-
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