From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Odd BUG on wireless-testing master-2010-08-05
Date: Fri, 6 Aug 2010 09:50:58 -0400 [thread overview]
Message-ID: <20100806135057.GA2753@tuxdriver.com> (raw)
In-Reply-To: <AANLkTinwbLXVHmC9eUczoe-ntT=adyFFx6C6Q=GcBc79@mail.gmail.com>
On Thu, Aug 05, 2010 at 03:31:06PM -0700, Luis R. Rodriguez wrote:
> I just ran into this. My first load of master-2010-08-05 was fine but
> I started getting a lot of disconnects on AR9003 hardware after a
> period of RX'ing data over an encrypted legacy network. Instead of
> checking dmesg I just rebooted though. After that I connected to the
> same AP again, started Rx'ing for a while and then shortly got this:
>
>
> [ 818.749585] BUG: unable to handle kernel paging request at 00003f3f00000000
> [ 818.749594] IP: [<ffffffff814ee0d8>] unix_stream_recvmsg+0x3f8/0x790
> After a reboot I got a hard hang which I could not capture any logs
> for. I rebooted and am up now but not seeing these issues yet. John,
> does this smell like what you were seeing or is this different?
Yeah, I'm seeing that too. There is some netdev stuff in
wireless-testing at the moment that I suspect was undercooked...
Sorry for the inconvenience while this gets sorted-out!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-08-06 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 22:31 Odd BUG on wireless-testing master-2010-08-05 Luis R. Rodriguez
2010-08-06 13:50 ` John W. Linville [this message]
2010-08-06 19:05 ` Luis R. Rodriguez
2010-08-07 19:04 ` Christian Lamparter
2010-08-08 5:20 ` Kalle Valo
2010-08-08 8:33 ` Johannes Berg
2010-08-08 9:34 ` Luis R. Rodriguez
2010-08-15 17:39 ` Kalle Valo
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=20100806135057.GA2753@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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).