From: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
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>,
Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Subject: Re: 2.6.9rc2-mm4 oops
Date: 07 Oct 2004 14:09:46 -0700 [thread overview]
Message-ID: <1097183386.3310.261.camel@cmn37.stanford.edu> (raw)
In-Reply-To: <200410071431.20400.bjorn.helgaas@hp.com>
On Thu, 2004-10-07 at 13:31, Bjorn Helgaas wrote:
> On Friday 01 October 2004 4:33 pm, Bjorn Helgaas wrote:
> > On Friday 01 October 2004 11:52 am, Fernando Pablo Lopez-Lezcano wrote:
> > > On Fri, 2004-10-01 at 08:04, Bjorn Helgaas wrote:
> > > > Also, can you look up the bad address
> > > > (e.g., f8881920) in /proc/kallsyms?
> > >
> > > This is what I find:
> > > f8880f80 ? __mod_vermagic5 [xor]
> > > f8880fcd ? __module_depends [xor]
> > > f8881000 t acpi_button_init [button]
> > > f8881000 t init_module [button]
> > > f8884000 t xor_pII_mmx_2 [xor]
> > > f8884130 t xor_pII_mmx_3 [xor]
> >
> > You are remembering that /proc/kallsyms isn't sorted, right?
> >
> > If you still can't match the address to anything interesting,
> > can you see whether it's related to any of the other modules
> > (i.e., see whether it happens even if you don't load any of
> > the other ACPI drivers, or try leaving out any other drivers
> > you can get along without)? Maybe try loading an ACPI driver
> > other than floppy, at the same point in the module load sequence,
> > to see if the problem is specific to floppy, or if floppy is
> > just an innocent bystander?
> >
> > I looked at all the callers of acpi_bus_register_driver(), and
> > they all look fine (except the hpet one I found yesterday). But
> > maybe there's something I missed, or maybe the acpi_bus_drivers
> > list got corrupted somehow.
> >
> > If you don't load the floppy driver, is the system stable?
Even if I load it (unsuccesfully - there's actually no floppy) the
system _appears_ to be fine. If I remember correctly this happens in the
context of device discovery (kudzu).
> Any update on all this? I've tried to reproduce the problem on
> my Athlon box, but so far I've been unsuccessful.
Sorry for the delay, too busy as usual.
BTW, what I sent was actually sorted. I'll see if I can get more
information later today (I have not forgotten).
-- Fernando
next prev parent reply other threads:[~2004-10-07 21:21 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
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 [this message]
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=1097183386.3310.261.camel@cmn37.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=bero@arklinux.org \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®