From: Keith Owens <kaos@ocs.com.au>
To: Neale Banks <neale@lowendale.com.au>
Cc: Stephen Rothwell <sfr@linuxcare.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.18: apm initialised before dmi_scan?
Date: Tue, 30 Jan 2001 23:48:51 +1100 [thread overview]
Message-ID: <1211.980858931@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 30 Jan 2001 22:47:02 +1100." <Pine.LNX.4.05.10101302229400.12161-100000@marina.lowendale.com.au>
On Tue, 30 Jan 2001 22:47:02 +1100 (EST),
Neale Banks <neale@lowendale.com.au> wrote:
>Looking more closely at a 2.2.18 bootup tonight I see that apm stuff
>appears in dmesg before dmi_scan does (I added "#define DUMP_DMI" in
>dmi_scan.c).
>
>If this implies that apm is initialised *before* the dmi_scan then there
>is potentially a problem with buggy BIOSen that oops instead of reporting
>power status
This should fix the link order, at the (small) expense of compiling
dmi_scan for exported symbols, even though it does not really export
symbols. Against 2.2.18.
Index: 18.1/arch/i386/kernel/Makefile
--- 18.1/arch/i386/kernel/Makefile Thu, 23 Nov 2000 11:48:07 +1100 kaos (linux-2.2/E/b/40_Makefile 1.1.4.4 644)
+++ 18.2(w)/arch/i386/kernel/Makefile Tue, 30 Jan 2001 23:47:17 +1100 kaos (linux-2.2/E/b/40_Makefile 1.1.4.4 644)
@@ -15,8 +15,8 @@ all: kernel.o head.o init_task.o
O_TARGET := kernel.o
O_OBJS := process.o signal.o entry.o traps.o irq.o vm86.o \
ptrace.o ioport.o ldt.o setup.o time.o sys_i386.o \
- bluesmoke.o dmi_scan.o
-OX_OBJS := i386_ksyms.o
+ bluesmoke.o
+OX_OBJS := i386_ksyms.o dmi_scan.o
MX_OBJS :=
ifdef CONFIG_PCI
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-30 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 11:47 2.2.18: apm initialised before dmi_scan? Neale Banks
2001-01-30 12:48 ` Keith Owens [this message]
2001-01-31 11:54 ` Neale Banks
2001-01-31 11:45 ` Keith Owens
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=1211.980858931@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neale@lowendale.com.au \
--cc=sfr@linuxcare.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