From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Fernando Pablo Lopez-Lezcano <nando@ccrma.stanford.edu>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
Len Brown <len.brown@intel.com>,
acpi-devel@lists.sourceforge.net,
Bernhard Rosenkraenzer <bero@arklinux.org>
Subject: Re: 2.6.9rc2-mm4 oops
Date: Fri, 1 Oct 2004 09:04:52 -0600 [thread overview]
Message-ID: <200410010904.52892.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1096594616.11297.688.camel@cmn37.stanford.edu>
On Thursday 30 September 2004 7:36 pm, Fernando Pablo Lopez-Lezcano wrote:
> On Thu, 2004-09-30 at 16:04, Bjorn Helgaas wrote:
> > Like Pierre, I was able to reproduce this with DEBUG_PAGEALLOC.
> > I found a struct acpi_driver in hpet.c that was erroneously marked
> > __init, and the attached patch fixed the oops for me. Can you give
> > this a whirl?
>
> Sorry, I did, and still get the oops. This is it this time (looks the
> same to me):
>
> inserting floppy driver for 2.6.8.1-1.520.1nov.rhfc2.ccrma
> Unable to handle kernel paging request at virtual address f8881920
Can you post your .config? If you don't have CONFIG_HPET turned
on, my patch wouldn't help. Also, can you look up the bad address
(e.g., f8881920) in /proc/kallsyms? When I reproduced it, the
faulting address was hpet_acpi_driver. Maybe you've found a
similar bug in a different driver.
next prev parent reply other threads:[~2004-10-01 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 19:14 Fernando Pablo Lopez-Lezcano
2004-09-30 19:49 ` Andrew Morton
2004-09-30 21:22 ` Bjorn Helgaas
2004-09-30 23:04 ` Bjorn Helgaas
2004-10-01 1:36 ` Fernando Pablo Lopez-Lezcano
2004-10-01 15:04 ` Bjorn Helgaas [this message]
2004-10-01 17:52 ` Fernando Pablo Lopez-Lezcano
2004-10-01 22:33 ` Bjorn Helgaas
2004-10-07 20:31 ` Bjorn Helgaas
2004-10-07 21:09 ` Fernando Pablo Lopez-Lezcano
2004-10-17 16:14 ` Bernhard Rosenkraenzer
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=200410010904.52892.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=bero@arklinux.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nando@ccrma.stanford.edu \
/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®