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: <454A2D54.4060901@seclark.us>
Date:	Thu, 02 Nov 2006 12:39:32 -0500
From:	Stephen Clark <Stephen.Clark@...lark.us>
To:	Sergio Monteiro Basto <sergio@...giomb.no-ip.org>
CC:	Dave Jones <davej@...hat.com>,
	Alexey Dobriyan <adobriyan@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: fc6 kernel 2.6.18-1.2798 breaks acpi on HP laptop n5430

Sergio Monteiro Basto wrote:

>On Thu, 2006-11-02 at 09:40 -0500, Stephen Clark wrote:
>  
>
>>Sergio Monteiro Basto wrote:
>>
>>    
>>
>>>On Wed, 2006-11-01 at 22:03 -0500, Dave Jones wrote:
>>> 
>>>
>>>      
>>>
>>>>On Wed, Nov 01, 2006 at 08:08:31PM -0500, Stephen Clark wrote:
>>>>
>>>>        
>>>>
>>>>>booting without lapic allowed it to boot but now I get
>>>>>...
>>>>>Local APIC disabled by BIOS -- you can enable it with "lapic"
>>>>>...
>>>>>Local APIC not detected. Using dummy APIC emulation.
>>>>>  which means more processor overhead - right?
>>>>>
>>>>>also cpuspeed doesn't work anymore - I don't have a cpufreq dir
>>>>>          
>>>>>
>>>>The Duron had powernow ?
>>>>   
>>>>
>>>>        
>>>>
>>>This story of trying enable lapic when BIOS don't, has been triggered on
>>>kernel2.6.18, but in my opinion is not a bug if lapic on those computers
>>>don't work.
>>>
>>>If you boot without enable lapic, you will see cat /proc/interrupts with
>>>interrupts in XT-PIC.
>>>if you try enable lapic, somehow IRQ routing should change 
>>>and if /proc/interrupts still the same, with IRQs in XT-PIC.
>>>I think, lapic still not enabled and the most you can get it's problems.
>>>Unless you know that lapic works (it is programmed and BIOS wrongly
>>>disable it), you shouldn't try enable lapic because it is probable that
>>>just give problems, to you. 
>>>Historically: In 2002/3 was a very common bug, when kernel was compiled
>>>to support lapic and try enable lapic (even when BIOS don't) and
>>>computer hangs on boot. 
>>> 
>>>
>>>      
>>>
>>Loading the correct kernel arch 686 - fixes my powernow problems - this 
>>is a mobile duron.
>>
>>Booting with lapic worked fine on  fc5 kernel-2.6.18-2200 but it causes 
>>fc6 kernel-2.6.18-2798
>>to hang.
>>    
>>
>
>With lapic boot option enabled, have you a different /proc/interrupts ? 
>have you lapic working ? 
>
>
>
>  
>
No interrupt assignments are the same - but what about the hi-res timer 
the lapic is
supposed to have and linux is suppose to use?

Steve

-- 

"They that give up essential liberty to obtain temporary safety, 
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty 
decreases."  (Thomas Jefferson)



-
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