All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Oops in USB / dev code plugging/unplugging multi flash reader
Date: Wed, 28 Nov 2007 15:24:15 -0800	[thread overview]
Message-ID: <20071128232415.GA11926@suse.de> (raw)
In-Reply-To: <474DF713.5070102@rtr.ca>

On Wed, Nov 28, 2007 at 06:17:39PM -0500, Mark Lord wrote:
> Greg KH wrote:
>> On Wed, Nov 28, 2007 at 03:02:35PM -0500, Mark Lord wrote:
>>> While testing a new USB reader/cable today,
>>> I was plugging/unplugging the USB multi-flash reader (22 in 1),
>>> and produced this weird oops.
>>>
>>> There's a locking problem in there somewhere, Greg.
>>>
>>> 2.6.23.8
>> Can you duplicate this without the closed source ATI graphics driver 
>> loaded?
> ..
>
> I don't know if I can reproduce it easily regardless.
> But that fglrx module has ZERO users, so it was completely benign here
> (I've now deleted it from my system).
>
> The tracebacks clearly show USB/dev error.

I'm not disagreeing, but I've seen some very strange crap over the years
come from those closed source video drivers so I do not trust them at
all.

If you can reproduce this without it loaded, please send the new oops
message to the linux-usb mailing list and the developers there will be
glad to work with you to track this down.

Oh, can you also reproduce it with 2.6.24-rc3?

thanks,

greg k-h

      reply	other threads:[~2007-11-29  0:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 20:02 [BUG] Oops in USB / dev code plugging/unplugging multi flash reader Mark Lord
2007-11-28 20:27 ` Greg KH
2007-11-28 23:17   ` Mark Lord
2007-11-28 23:24     ` Greg KH [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=20071128232415.GA11926@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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.