On Wednesday 30 September 2009, Bob Copeland wrote: > On Wed, Sep 30, 2009 at 09:52:27AM +0200, Frans Pop wrote: > > This is on a laptop I don't use much, but with .31 wireless has always > > been (and still is) reliable (.31-rc5 is the last kernel I built for > > it). On my other laptop wireless (iwlagn) works fine with .32-rc1. > > Although iwlagn works, I would think this kind of thing: > > ath0: authenticated > > ath0: associate with AP 00:14:c1:38:e5:15 (try 1) > > ath0: RX ReassocResp from 00:14:c1:38:e5:15 (capab=0x411 status=0 aid=2) > > ath0: associated > > ath0: deauthenticating by local choice (reason=3) > > ...is some kind of issue with userspace or wext rather than the driver. > Ath5k only had a dozen or so patches this time around, so it should be > easy to bisect if it's a problem in the driver. One possibility is > hardware CCMP support but I've been using it here for some time. I doubt it's a userspace issue, but it does look like the regression was not triggered by the ath5k driver itself. In the mean time I did a bisect on the drivers/net/wireless/ath directory without any results. > By the way, name it what you will, but the standard is wlan0 these days > :) Yep. A leftover from the days I used madwifi :-) I kind of like it though given its similarity to eth0. > > So the difference looks to be how I boot: if I do a *cold* boot > > directly into .32, wireless fails; if I *reboot* from .31 into .32, > > wireless comes up correctly. Reboot from .32 to .32 fails too. > > Is that repeatable? Yes, 100%. Weird heh? That's what made me think it must be an ath5k driver issue as it looks like a hardware initialization problem. Could be PCI or PCMCIA though, although I don't see anything suspicious in dmesg. > Rafael J. Wysocki has a patch floating around to fix PCMCIA resume, > linked here: http://bugzilla.kernel.org/show_bug.cgi?id=13092 Ack. I'll probably wait and see how -rc2 (or 2a or 3 or whatever) behaves before doing a full bisect, but I will come back to this. Thanks, FJP -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
