From: Mikael Pettersson <mikpe@csd.uu.se>
To: "Sumit Pandya" <sumit@elitecore.com>
Cc: <linux-kernel@vger.kernel.org>, <len.brown@intel.com>
Subject: Re: OOPS - APIC or othere?
Date: Wed, 17 Nov 2004 11:49:48 +0100 [thread overview]
Message-ID: <16795.11468.681748.425014@alkaid.it.uu.se> (raw)
In-Reply-To: <HGEFKOBCHAIJDIEJLAKDGEMECAAA.sumit@elitecore.com>
Sumit Pandya writes:
> Hi All,
> At one of our client I faced timer problem in kernel-2.4.26 and I tried to
> fixed with patching "arch/i386/kernel/mpparse.c" file taken from
> patch-2.4.27.
> ... ... ...
> Mikael Pettersson:
> o i386 and x86_64 ACPI mpparse timer bug
> ... ... ...
> After booting up the system now I get OOPS. Did I applied partial patch by
> taking only patch for mpparse.c from the whole buntch? Does it broken
> dependency to some other functionality? I've ACPI support enabled into
> kernel.
The effect of the bug was that the timer generated twice as
many interrupts, making the kernel's wall-clock timer twice
as fast.
There were no OOPS issues related with that patch. Therefore,
your OOPS indicates dependencies on other changes in mpparse
and/or the ACPI code. Why hack a 2.4.26 kernel in this way?
Just put a 2.4.27 or 2.4.28-rc4 in there and be done with it :-)
/Mikael
next prev parent reply other threads:[~2004-11-17 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 10:06 Sumit Pandya
2004-11-17 10:49 ` Mikael Pettersson [this message]
2004-11-17 16:42 ` Zwane Mwaikambo
[not found] ` <HGEFKOBCHAIJDIEJLAKDAEMKCAAA.sumit@elitecore.com>
2004-11-26 6:42 ` Marcelo Tosatti
2004-11-26 13:35 ` Zwane Mwaikambo
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=16795.11468.681748.425014@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit@elitecore.com \
/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
all inboxes | Powered by JetHome®