public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <Stephen.Clark@seclark.us>
To: sergio@sergiomb.no-ip.org
Cc: Dave Jones <davej@redhat.com>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: fc6 kernel 2.6.18-1.2798 breaks acpi on HP laptop n5430
Date: Thu, 02 Nov 2006 09:40:18 -0500	[thread overview]
Message-ID: <454A0352.8010207@seclark.us> (raw)
In-Reply-To: <1162441409.7677.23.camel@monteirov>

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.



-- 

"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)




  reply	other threads:[~2006-11-02 14:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 17:48 fc6 kernel 2.6.18-1.2798 breaks acpi on HP laptop n5430 Stephen Clark
2006-11-01 20:12 ` Alexey Dobriyan
2006-11-01 21:17   ` Stephen Clark
2006-11-01 23:55     ` Dave Jones
2006-11-02  1:08       ` Stephen Clark
2006-11-02  1:50         ` Stephen Clark
2006-11-02  3:03         ` Dave Jones
2006-11-02  4:23           ` Sergio Monteiro Basto
2006-11-02 14:40             ` Stephen Clark [this message]
2006-11-02 14:47               ` Sergio Monteiro Basto
2006-11-02 17:39                 ` Stephen Clark
2006-11-03  0:21                   ` Sergio Monteiro Basto

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=454A0352.8010207@seclark.us \
    --to=stephen.clark@seclark.us \
    --cc=adobriyan@gmail.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergio@sergiomb.no-ip.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