linux-kernel - Re: [2.6.31-rc1] iwlagn (4965): regression when hardware rf switch is used

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1246269203.7775.26.camel@johannes.local>
Date:	Mon, 29 Jun 2009 11:53:23 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-wireless@...r.kernel.org, Netdev <netdev@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6.31-rc1] iwlagn (4965): regression when hardware rf switch
 is used

On Mon, 2009-06-29 at 11:48 +0200, Frans Pop wrote:
> On Monday 29 June 2009, Johannes Berg wrote:
> > > [enable]
> > > usb 3-1: new full speed USB device using uhci_hcd and address 3
> > > usb 3-1: configuration #1 chosen from 1 choice
> >
> > That is completely unrelated. You plugged in a USB device too :)
> 
> No, it's my "bluetooth + wlan" device. Note that disabling wireless with 
> the hardware switch also gives 'usb 3-1: USB disconnect, address 2'.
> 
> From lsusb:
> Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + 
> WLAN) Interface [Integrated Module]

Ah :) That's just bluetooth then though, not wifi.

> > > A lot uglier with those errors. And after that I have to run
> > > ifdown/ifup before networking is up again (ifup only does not work as
> > > it will complain "interface already configured"):
> >
> > And that's actually expected, and/or a bug in the debian networking
> > scripts.
> > (You can trigger the same problem by doing
> > ifup wlan0
> > ip link set wlan0 down
> > ifup wlan0 -> error)
> 
> OK, I can accept that. Wonder why it does work with 2.6.30 then. But it 
> can certainly wait until the driver problem you mentioned is resolved.

2.6.30 didn't have the "ip link set wlan0 down" on rfkill behaviour, but
overall that makes life for everybody (except people who actually use
ifup/down) much easier.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)