All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: usb and preempt oopses with 2.6.6-rc1 on ppc
Date: Mon, 19 Apr 2004 16:09:24 +1000	[thread overview]
Message-ID: <1082354963.1677.11.camel@gaston> (raw)
In-Reply-To: <1082354034.1717.8.camel@localhost>

On Mon, 2004-04-19 at 15:53, Soeren Sonnenburg wrote:
> Hi.
> 
> I get the following 2 oopses with the 2.6.6-rc1 kernel on my G4 powerbook.
> The first one is an usb oops (from 2.6.5) and the second one probably a preempt issue on ppc.

The first one is probably an existing USB / bluetooth problem that
you should report to the appropriate list

> This is the usb oops I get when I don't hciconfig hci0 down and stop all
> blue-* programs before *REMOVING* the bluetooth dongle.

The second one looks like a VM bug actually. I spotted a patch going
to Linus tree today fixing vma corruption, could be related...

Ben



      reply	other threads:[~2004-04-19  6:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19  5:53 usb and preempt oopses with 2.6.6-rc1 on ppc Soeren Sonnenburg
2004-04-19  6:09 ` Benjamin Herrenschmidt [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=1082354963.1677.11.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=kernel@nn7.de \
    --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.