public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Rosenkraenzer <bero@arklinux.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Fernando Pablo Lopez-Lezcano <nando@ccrma.stanford.edu>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, mingo@elte.hu,
	Len Brown <len.brown@intel.com>,
	acpi-devel@lists.sourceforge.net
Subject: Re: 2.6.9rc2-mm4 oops
Date: Sun, 17 Oct 2004 18:14:59 +0200	[thread overview]
Message-ID: <200410171815.00274.bero@arklinux.org> (raw)
In-Reply-To: <200410071431.20400.bjorn.helgaas@hp.com>

On Thursday 07 October 2004 22:31, Bjorn Helgaas wrote:

> > 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?
>
> Any update on all this?  I've tried to reproduce the problem on
> my Athlon box, but so far I've been unsuccessful.

Tried a couple of boxes (with versions up to 2.6.9-rc4-mm1), it appears to be 
100% reproducable on boxes that don't have a floppy drive while it works ok 
on boxes that do have a floppy drive.

The system still works reliably after the oops btw.

LLaP
bero

      parent reply	other threads:[~2004-10-17 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 19:14 2.6.9rc2-mm4 oops 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
2004-10-17 16:14                 ` Bernhard Rosenkraenzer [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=200410171815.00274.bero@arklinux.org \
    --to=bero@arklinux.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=bjorn.helgaas@hp.com \
    --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