Brett, Could we, in the interim, turn off the radio disabled check until the driver is properly fixed? I've hard-coded it to false which seems to work for me. Thanks, Sean On Tue, Dec 14, 2010 at 9:26 AM, Sean Paul <seanpaul@xxxxxxxxxx> wrote: > Hi Brett, > I've been testing on a Lenovo S10-3t, with the 4313 chipset. I've > tried 2 other S10-3t units with the same result (making doubly sure > the switch was in the on position). I haven't tried another model with > the 4313 in it. > > Is it possible that Larry's experiences with the b43 driver and rfkill > are related? > > Thanks, > > Sean > > On Mon, Dec 13, 2010 at 2:32 PM, Brett Rudley <brudley@xxxxxxxxxxxx> wrote: >> >>> -----Original Message----- >>> From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless- >>> owner@xxxxxxxxxxxxxxx] On Behalf Of Sean Paul >>> Sent: Monday, December 13, 2010 10:39 AM >>> To: Larry Finger >>> Cc: Brett Rudley; linux-wireless@xxxxxxxxxxxxxxx >>> Subject: Re: brcm80211 locking up >>> >>> Hi Larry, >>> Thanks for the insight. It's very difficult to debug this since the >>> loop is hosing my system, so it's unclear whether an unload/reload >>> would fix the issue. >>> >>> Brett: Do you know the cause of the loop? >> >>> Two issues: >> >> - Something on your machine is forcing the radio off. >> - The driver isn't handling the radio off condition during load. >> >> The latter is on our todo list and I just haven't had time to deal with yet. >> >> The former is odd... I haven't seen this before (except for when my RF switch was actually off). >> >> What machine is this and have you seen the problem on any other type of machines? Does it happen all the time, some of the time? >> >> Brett >> >> >> > -- 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
