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 21:09:53 +0200 [thread overview]
Message-ID: <20120811190951.GA2432@redhat.com> (raw)
In-Reply-To: <CANq1E4T=ajt6yt6NMfdyM4mjNgVkevF_nS7tVC-UAs3YpgLYfQ@mail.gmail.com>
On Sat, Aug 11, 2012 at 08:46:47PM +0200, David Herrmann wrote:
> Yes, I generated the wpa_supplicant.conf via netcfg (a network manager from
> ArchLinux) and used it by hand. I often noticed doing everything by myself
> works, but using netcfg or NetworkManager results in a timeout during
> wlan-connection. Haven't debugged this, but it is not related to this bug
> as it happens with other devices, too.
>
> I now got everything running again, are you still interested in the
> wpa_supplicant.conf? Sorry, for the noice.
> Anyway, I haven't encountered the kernel-warnings, yet, but I will keep
> looking. I haven't found a way to reliably reproduce them, but I saw them
> quite often with linux-next a month ago and they seem to be gone now.
>
> Have you pushed any patches regarding this bug or do you just assume that
> this was some untested code in linux-next that should be fixed in the
> stable series for now?
We have various mac80211 fixes that could be related with this problem,
but I do not see any particular which address that directly. Perhaps
warnings ware some side effect of other bug.
> I will tell you if the bugs occur again, but as I said, they seem gone.
> Anyway, thanks for your time!
Yeh, if warnings come back, please post me wpa_supplicant.conf, and
eventually some other informations important to reproduce the problem
(except .config which you already provided).
Thanks
Stanislaw
prev parent reply other threads:[~2012-08-11 19:09 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
[not found] ` <CANq1E4T=ajt6yt6NMfdyM4mjNgVkevF_nS7tVC-UAs3YpgLYfQ@mail.gmail.com>
2012-08-11 19:09 ` Stanislaw Gruszka [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=20120811190951.GA2432@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).