From: Pat LaVarre <p.lavarre@ieee.org>
To: len.brown@intel.com
Cc: kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: oops ACPI in Linux-2.6.6-bk1
Date: 14 May 2004 08:57:55 -0600 [thread overview]
Message-ID: <1084546675.7796.12.camel@patibmrh9> (raw)
In-Reply-To: <1084511992.12354.256.camel@dhcppc4>
> There were no ACPI changes between 2.6.6 and 2.6.6-bk1.
The change my newbie eye sees here is that the effect of CONFIG_ACPI=y
changes from imperceptible in 2.6.6 to kernel won't boot in 2.6.6-bk1.
> Does 2.6.6 work for you?
2.6.6 works for me, yes, as did 2.6.5, 2.6.4, etc. ...
$ grep 'CONFIG_ACPI=' .config
CONFIG_ACPI=y
$ grep 'ACPI.*=y$' .config | grep -v '^#' | wc -l
16
$
The motherboard labels in front of me include:
"INTEL DESKTOP BOARD"
"D865GBF/D865PERC".
> > > ACPI: Subsystem revision 20040326 ...
> > > [<c01eef72>] acpi_ev_save_method_info+0x44/0x75 ...
> > > Unable to handle kernel NULL pointer dereferencec01e1194 ...
> > > Kernel panic: Aiee, killing interrupt handler! ...
> > > Unable <o ha1dleUn kernel NULL pointer dereferenceer
> > dereferenceOoops: ...
> > > Unable to handle kernel NULL pointer dereference at virtual address
> > ...
> >
> > Theory confirmed:
> >
> > Deleting CONFIG_ACPI=y etc. via `make xconfig` fixes this.
>
> what theory?
Thanks for making the time to say I was unclear.
In launching a thread titled "oops ACPI" I was guessing that lossy dmesg
spew appearing immediately past "ACPI: Subsystem revision 20040326" was
caused by me living too close to `make defconfig`. I then revisited
`make xconfig`, asked to turn off ACPI, and suddenly life got better.
I'm working from local copies of the kernel.org files:
$ ls -l *2.6.6*
-rw-rw-r-- 1 pat pat 34896138 May 10 11:14 linux-2.6.6.tar.bz2
-rw------- 1 pat pat 1072216 May 12 08:47 patch-2.6.6-bk1.bz2
$
I can fsck the containing volume, but I haven't yet otherwise learned
how to crc-check their integrity.
Pat LaVarre
next prev parent reply other threads:[~2004-05-14 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FB4FE@hdsmsx403.hd.intel.com>
2004-05-14 5:19 ` oops ACPI in Linux-2.6.6-bk1 Len Brown
2004-05-14 14:57 ` Pat LaVarre [this message]
2004-06-09 17:48 ` Pat LaVarre
2004-05-12 15:28 Pat LaVarre
2004-05-13 15:02 ` Pat LaVarre
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=1084546675.7796.12.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=kernelnewbies@nl.linux.org \
--cc=len.brown@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.