Re: unable to bring up iwlagn wireless after update from 2.6.29.6 to 2.6.31-rc3

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]

On Fri, 2009-07-17 at 02:51 +0300, Thomas Backlund wrote:

> > pressing rfkill when I have a working wireless gets this:

> And here is the above rfkill/ iwlagn error with "debug=0x01043fff":
> 
> Jul 17 02:41:06 tmb-laptop klogd: rfkill_schedule_toggle(1)
> Jul 17 02:41:06 tmb-laptop klogd: __rfkill_handle_normal_op(1, 1) [1]
> Jul 17 02:41:06 tmb-laptop klogd: ieee80211 phy0: I iwl_rx_handle r = 
> 77, i = 75, REPLY_RX, 0xc3

Yeah the errors are kinda expected.. not sure how we can hide them.

> Oh, btw is this below a refcounting bug?
> For each time I unload & reload the iwlagn,
> the number in front of phy0 gets increased:
> 
> [root@tmb-laptop rfkill]# ./rfkill list
> 0: acer-wireless: Wireless LAN
> 	Soft blocked: no
> 	Hard blocked: no
> 1: acer-bluetooth: Bluetooth
> 	Soft blocked: yes
> 	Hard blocked: no
> 5: phy0: Wireless LAN
> 	Soft blocked: no
> 	Hard blocked: no

No, we just assign increasing numbers all the time.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]