Bug#649412: linux-image-3.1.0-1-amd64: "No route to host" after some time with iwlagn and kernel 3.1
Hi,
2011/11/26 Ben Hutchings <ben@decadent.org.uk>:
> On Sun, 2011-11-20 at 16:58 -0200, Fernando Tarlá Cardoso Lemos wrote:
>> Package: linux-2.6
>>
>> Version: 3.1.1-1
>> Severity: normal
>>
>> After upgrading to 3.1, I get somewhat periodic network problems with iwlagn.
>> This is a Dell laptop (Vostro 3450) with a Centrino 1030 BGN interface. I'm
>> using a 802.11g (not 802.11n) router with WPA2 authentication. The router
>> advertises the SSID. I haven't had the opportunity to test this with other
>> routers yet.
>>
>> I boot up, and after a few minutes (usually between 400 and 1000 seconds after
>> I've connected), I get "Destination Host Unreachable" network errors:
>
> It looks to me as if you accidentally pressed some key combination that
> turns wifi off and on:
>
> [...]
>> [ 930.958778] keyboard: can't emulate rawmode for keycode 240
>> [ 930.958808] keyboard: can't emulate rawmode for keycode 240
>> [ 930.964597] iwlagn 0000:01:00.0: RF_KILL bit toggled to disable radio.
>> [ 930.964762] iwlagn 0000:01:00.0: Not sending command - RF KILL
>> [ 930.964770] iwlagn 0000:01:00.0: Error sending REPLY_QOS_PARAM: enqueue_hcmd failed: -5
> [...]
>> [ 932.827396] keyboard: can't emulate rawmode for keycode 240
>> [ 932.827427] keyboard: can't emulate rawmode for keycode 240
>> [ 932.834164] iwlagn 0000:01:00.0: RF_KILL bit toggled to enable radio.
> [...]
>
> Is that possible? Otherwise, it's also conceivable that these events
> are being triggered wrongly.
Nope, I pressed it on purpose so I could fill the bug report. Fn + F2
triggers rfkill, if I press that twice I get a reconnection and then I
get connectivity back. I did this one or twice so I could gather
enough information to submit the report. The first time I lose
connectivity, there are no rfkill-related messages.
I couldn't find anything in the logs that could point out to the
problem, unfortunately. :-(
Regards,
Reply to: