From: Stanislaw Gruszka <sgruszka@redhat.com>
To: David Herrmann <dh.herrmann@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rt73usb: WARN(x) in check_sdata_in_driver()
Date: Sat, 11 Aug 2012 18:34:07 +0200 [thread overview]
Message-ID: <20120811163406.GA10564@redhat.com> (raw)
In-Reply-To: <CANq1E4RH5fHM5LPddD+A_w-G7k0=0scP0jpmqHnygX6Q9_Xecw@mail.gmail.com>
On Sat, Aug 11, 2012 at 03:47:55PM +0200, David Herrmann wrote:
> Hi Stanislaw
>
> On Sat, Aug 11, 2012 at 12:27 AM, Stanislaw Gruszka <sgruszka@redhat.com>wrote:
>
> > Hi
> >
> > On Sun, Jul 15, 2012 at 07:34:58PM +0200, David Herrmann wrote:
> > > I use an ASUStek WL-167g USB wlan adapter (quite old) using rt73usb.ko
> > > (Ralink). After resuming from suspend I get:
> > >
> > > [152743.736783] ------------[ cut here ]------------
> > > [152743.736798] WARNING: at net/mac80211/driver-ops.h:12
> > > ieee80211_send_deauth_disassoc+0x1a8/0x1b0()
> > > [152743.736801] Hardware name: N150P/N210P/N220P
> > > [152743.736804] wlan0: Failed check-sdata-in-driver check, flags: 0x4
> >
> > Does it still happen on 3.5.1 ?
> >
>
> Thanks for asking. With 3.5.1 I get "phy0 -> rt2x00lib_request_firmware:
> Error - Failed to request Firmware."
> But:
> $ wc /lib/firmware/rt73.bin
> 5 44 2048 /lib/firmware/rt73.bin
> So I wonder were that comes from. udevd segfaults twice while hotplugging
> the device. And finally I get "link becomes ready" but I get ENODEV when
> starting wpa_supplicant. It all seems a bit weird and I have no idea how to
> debug this.
>
> I will try putting the firmware blob into the kernel binary.
Looks like some change broke udev, but how? Do you have the same thing with
3.5.0 ? Perhaps updating udev could help.
You do not use NetworkManager or similar only pure wpa_supplicant? That would
explain why I'm not seeing the problem on my setup. Could you provide me
your wpa_supplicant.conf (after removing psk and ssid entries) ?
What wpa_supplicant version you are using?
Thanks
Stanislaw
next prev parent reply other threads:[~2012-08-11 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 17:34 rt73usb: WARN(x) in check_sdata_in_driver() David Herrmann
2012-08-10 22:27 ` Stanislaw Gruszka
[not found] ` <CANq1E4RH5fHM5LPddD+A_w-G7k0=0scP0jpmqHnygX6Q9_Xecw@mail.gmail.com>
2012-08-11 16:34 ` Stanislaw Gruszka [this message]
[not found] ` <CANq1E4T=ajt6yt6NMfdyM4mjNgVkevF_nS7tVC-UAs3YpgLYfQ@mail.gmail.com>
2012-08-11 19:09 ` Stanislaw Gruszka
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=20120811163406.GA10564@redhat.com \
--to=sgruszka@redhat.com \
--cc=dh.herrmann@googlemail.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).