From: Paul Albrecht <albrecht@rdi1.com>
To: Greg KH <greg@kroah.com>
Cc: Paul Albrecht <albrecht@rdi1.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: coldplug zd1211rw wireless driver results in firefox segfault
Date: Mon, 27 Aug 2007 11:23:44 -0400 [thread overview]
Message-ID: <1188228224.800.2.camel@albrecht.rdi1.com> (raw)
In-Reply-To: <20070825013808.GA24439@kroah.com>
On Fri, 2007-08-24 at 18:38 -0700, Greg KH wrote:
> On Fri, Aug 24, 2007 at 04:21:42PM -0400, Paul Albrecht wrote:
> > Hi,
> >
> > I'm trying to use a hawking hwu54g with the zd1211rw driver in the
> > 2.6.20 linux kernel. It works ok when I hotplug the device, but causes
> > firefox to segfault when I coldplug the device.
> >
> > As I get the segfault whether or not I bring the device up, I'm
> > wondering if there's a problem with the usb subsystem initialization.
> >
> > Any ideas? Please cc me because I don't usually subscribe to the lkml.
>
> Can you try a newer kernel? That driver has gotten a lot of work in the
> past 6 months.
Tried 2.6.21 and that worked. Thanks.
Paul Albrecht
prev parent reply other threads:[~2007-08-27 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 20:21 coldplug zd1211rw wireless driver results in firefox segfault Paul Albrecht
2007-08-25 1:38 ` Greg KH
2007-08-27 15:23 ` Paul Albrecht [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=1188228224.800.2.camel@albrecht.rdi1.com \
--to=albrecht@rdi1.com \
--cc=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox