Kalle Valo wrote: > "John W. Linville" <linville@xxxxxxxxxxxxx> writes: > >> On Fri, Jan 16, 2009 at 05:07:50PM +0000, Hin-Tak Leung wrote: >>> Since a few days ago, my dmesg is looking like this - instead of the >>> older AA:BB:CC:DD:EE:FF form >>> with the mac address of the AP. >>> That ffff88* looks like a pointer/address to me? Is this change intentional? >>> >>> -------------- >>> wlan2 direct probe responded >>> wlan2: authenticate with AP ffff880070995aa0 >>> wlan2: authenticated >>> wlan2: associate with AP ffff880070995aa0 >>> wlan2: RX ReassocResp from ffff88001431f01a (capab=0x431 status=0 aid=1) >>> wlan2: associated > > Works for me: > > [37125.111672] wlan0: authenticate with AP 00:12:17:e7:98:de > [37125.113509] wlan0: authenticated > [37125.113514] wlan0: associate with AP 00:12:17:e7:98:de > [37125.115875] wlan0: RX AssocResp from 00:12:17:e7:98:de (capab=0x11 status=0 aid=1) > [37125.115881] wlan0: associated > > This is on x86 32bit with iwl3945 and latest wireless-testing. > >> Odd...some problem with the "%pM" printk conversion? What kernel >> are you running? > > And on what architecture? > I have got the same problem on x86_64 with rtl8187, kernel 2.6.27 and compat-wireless-2008-01-16. [ 3064.480766] wlan0: authenticate with AP ffff8801291dfa20 [ 3064.482271] wlan0: authenticated [ 3064.482275] wlan0: associate with AP ffff8801291dfa20 [ 3064.485021] wlan0: RX AssocResp from ffff88011128c01a (capab=0x411 status=0 aid=1) [ 3064.485025] wlan0: associated Hauke
Attachment:
signature.asc
Description: OpenPGP digital signature
