From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Stephen.Clark@seclark.us
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: Fri, 03 Nov 2006 00:21:23 +0000 [thread overview]
Message-ID: <1162513283.2616.19.camel@monteirov> (raw)
In-Reply-To: <454A2D54.4060901@seclark.us>
[-- Attachment #1: Type: text/plain, Size: 2904 bytes --]
On Thu, 2006-11-02 at 12:39 -0500, Stephen Clark wrote:
> 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 -
So , you shouldn't try eneble lapic
> but what about the hi-res timer
> the lapic is
> supposed to have and linux is suppose to use?
>
Local APIC and IO-APIC works on Linux many time ago, before hi-res
timer.
The problem is that lapic are in computer but aren't programmed or isn't
suppose to work, this is not clear, why this lapics don't work.
what we know is that BIOS says that computer don't have lapic, so it it
a mistake try enable something that don't work , I think.
I had a Compaq Presario laptop with this problem, so I know this because
I pass throw it. you have one Laptop HP which could be a similar issue.
Regards,
> Steve
>
--
Sérgio M.B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
prev parent reply other threads:[~2006-11-03 0:21 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
2006-11-02 14:47 ` Sergio Monteiro Basto
2006-11-02 17:39 ` Stephen Clark
2006-11-03 0:21 ` Sergio Monteiro Basto [this message]
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=1162513283.2616.19.camel@monteirov \
--to=sergio@sergiomb.no-ip.org \
--cc=Stephen.Clark@seclark.us \
--cc=adobriyan@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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