From: "J.A. Magallon" <jamagallon@able.es>
To: Paul P Komkoff Jr <i@stingr.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at arch/i386/kernel/apm.c:1699!
Date: Mon, 14 Oct 2002 23:33:32 +0200 [thread overview]
Message-ID: <20021014213332.GA2053@werewolf.able.es> (raw)
In-Reply-To: <20021014144941.GA1217@stingr.net>; from i@stingr.net on Mon, Oct 14, 2002 at 16:49:41 +0200
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
On 2002.10.14 Paul P Komkoff Jr wrote:
>------------[ cut here ]------------
>kernel BUG at arch/i386/kernel/apm.c:1699!
>
>#ifdef CONFIG_SMP
> /* 2002/08/01 - WT
> * This is to avoid random crashes at boot time during initialization
> * on SMP systems in case of "apm=power-off" mode. Seen on ASUS A7M266D.
> * Some bioses don't like being called from CPU != 0.
> * Method suggested by Ingo Molnar.
> */
> if (smp_processor_id() != 0) {
> current->cpus_allowed = 1;
> schedule();
> if (unlikely(smp_processor_id() != 0))
> BUG();
> }
>#endif
>
>Why ? :()
>
>2.5.42-mm2, 2xPPro-233, etc ...
>
Bug in apm vs O1-scheduler. The apm task is moved from processor 0.
I took the fix from -ac tree. Just diff kernel/apm.c from -mm and from
-ac. That worked for me for 2.4 kernels. Perhaps 2.5 needs some additional
fix in other files. (err, I suppose that fix is in Alan's 2.5 tee also...)
Hope this helps.
Anyways, patch for 2.4 attached. I suppose it won't apply on 2.5, but you
can try...
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.20-pre10-jam1 (gcc 3.2 (Mandrake Linux 9.0 3.2-2mdk))
[-- Attachment #2: 17-apm-O1-sched.bz2 --]
[-- Type: application/x-bzip, Size: 2441 bytes --]
prev parent reply other threads:[~2002-10-14 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 14:49 kernel BUG at arch/i386/kernel/apm.c:1699! Paul P Komkoff Jr
2002-10-14 21:33 ` J.A. Magallon [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=20021014213332.GA2053@werewolf.able.es \
--to=jamagallon@able.es \
--cc=i@stingr.net \
--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;
as well as URLs for NNTP newsgroup(s).