From: "Arend van Spriel" <arend@broadcom.com>
To: "Daniel Halperin" <dhalperi@cs.washington.edu>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"gregkh@suse.de" <gregkh@suse.de>
Subject: Re: %d in wlan log messages
Date: Thu, 26 May 2011 19:53:21 +0200 [thread overview]
Message-ID: <4DDE9391.6020302@broadcom.com> (raw)
In-Reply-To: <BANLkTina0R-SJamJ_GFbxJsYcvvdyxzZNg@mail.gmail.com>
On 05/26/2011 05:09 PM, Daniel Halperin wrote:
> On Thu, May 26, 2011 at 7:29 AM, Arend van Spriel<arend@broadcom.com> wrote:
>> [ 563.120590] wlan%d: authenticate with c0:c1:c0:04:b8:2c (try 1)
>> [ 563.128143] wlan%d: authenticated
>> [ 563.131517] wlan%d: associate with c0:c1:c0:04:b8:2c (try 1)
>> [ 563.140933] wlan%d: RX AssocResp from c0:c1:c0:04:b8:2c (capab=0x411
>> status=0 aid=4)
>> [ 563.148714] wlan%d: associated
>> [ 563.177019] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
>>
>> On latest staging-next I noticed above mentioned log messages. I assume
>> these message are from cfg80211 or mac80211. Has this been reported?
>>
> Interface names [including any numbers] are set by userspace, right?
> On my Ubuntu 10.04.2 LTS system, it's
> /etc/udev/rules.d/70-persistent.net.rules (or so, this is from
> memory). Not a kernel bug.
>
> Dan
Weird. I did not change anything in udev rules (using Ubuntu 10.10 over
here). So the only variant in my setup is move to 2.6.39. Can you
explain that netdev apparently has the proper interface id (see
timestamp [563.177019] above?
Gr. AvS
--
Almost nobody dances sober, unless they happen to be insane.
-- H.P. Lovecraft --
next prev parent reply other threads:[~2011-05-26 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 14:29 %d in wlan log messages Arend van Spriel
2011-05-26 15:09 ` Daniel Halperin
2011-05-26 15:18 ` Denis 'GNUtoo' Carikli
2011-05-26 17:53 ` Arend van Spriel [this message]
2011-05-26 17:55 ` John W. Linville
2011-05-26 18:46 ` Arend van Spriel
2011-05-26 21:08 ` Rafał Miłecki
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=4DDE9391.6020302@broadcom.com \
--to=arend@broadcom.com \
--cc=dhalperi@cs.washington.edu \
--cc=gregkh@suse.de \
--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.