From: Mohammed Shafi <shafi.wireless@gmail.com>
To: Walter Goldens <goldenstranger@yahoo.com>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>,
gwingerde@gmail.com, Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: rt2x00: rt2800usb causing kernel panic /compat-wireless/
Date: Wed, 18 May 2011 18:11:46 +0530 [thread overview]
Message-ID: <BANLkTimwBB35HhOBjOq=OyhrVWq9MOZ3tA@mail.gmail.com> (raw)
In-Reply-To: <294183.47547.qm@web161601.mail.bf1.yahoo.com>
On Wed, May 18, 2011 at 5:26 PM, Walter Goldens
<goldenstranger@yahoo.com> wrote:
>> > A very peculiar bug.
>> >
>> > With compat-wireless from 16.05 a nasty bug started to
>> manifest itself. Right around association time, the
>> rt2800usb causes kernel panic. The system freezes and the
>> Caps Lock and Num Lock leds on the keyboard begin to flash.
>>
>> also ath9k, iwlagn.
>>
>> >
>> > Unfortunately there are no recoverable traces after
>> the system failure to aid this bug report or to indicate its
>> origin.
>> >
>> > I believe it may somehow be related to Ubuntu's
>> network-manager. If I turn off the network-manager service,
>> I can go into monitor mode for example, but if
>> network-manager is running and I plug my USB dongle, it
>> starts to associate, a second or two later the system is in
>> complete meltdown.
>>
>> same thing, monitor mode worked perfectly fine.
>>
>> >
>> > Nothing concrete, but a hunch is telling me this has
>> something to do with the association mechanism of the
>> rt2800usb. Compat-wireless from few days back exhibits no
>> such foul play.
>>
>> yes just right at the association complete freeze.
>>
>
> That's strange. I wonder what's the connection with this bug and network-manager. Because when I manually tried to associate, dmesg reported the association attempt timed out.
no even when we use iw dev connect command we can see the panic. some
expert suspected that there is a chance of kfree_rcu in
compat-wireless may have caused the problem
>
> Walter
>
--
shafi
next prev parent reply other threads:[~2011-05-18 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 8:18 rt2x00: rt2800usb causing kernel panic /compat-wireless/ Walter Goldens
2011-05-18 9:16 ` Mohammed Shafi
2011-05-18 11:56 ` Walter Goldens
2011-05-18 12:41 ` Mohammed Shafi [this message]
2011-05-18 12:51 ` Gertjan van Wingerde
2011-05-18 13:04 ` Mohammed Shafi
2011-05-18 14:41 ` Larry Finger
2011-05-18 14:46 ` Mohammed Shafi
2011-05-18 15:45 ` Mohammed Shafi
2011-05-18 15:48 ` Mohammed Shafi
2011-05-18 16:04 ` Mohammed Shafi
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='BANLkTimwBB35HhOBjOq=OyhrVWq9MOZ3tA@mail.gmail.com' \
--to=shafi.wireless@gmail.com \
--cc=goldenstranger@yahoo.com \
--cc=gwingerde@gmail.com \
--cc=hauke@hauke-m.de \
--cc=ivdoorn@gmail.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 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.