Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 25

Thread: Wireless connection lost (disconnects) when idle after locking screen

  1. #11
    Join Date
    Mar 2008
    Beans
    30

    Re: Wireless connection lost (disconnects) when idle after locking screen

    phones can also cause interference(never found a phone that does though) and other radio devices. Try switching channels it could be the solution.

    Its sort of ironic that as i help you with ur wireless my own has been playing up with different symptoms now. Try:

    sudo apt-get install linux-backports-modules-jaunty

    that should install some updated drivers and hopefully it will work.

    ive got a theory on idea if it will work. Ur wireless doesn't drop with windows does it? it only drops when ubuntu makes alot of connections, window has a limit. I think you might want to limit the number of half open tcp connections in your bt client.it could be your router just cant handle it (mines cant).
    Last edited by Randomperson_1000; September 6th, 2009 at 05:06 PM.

  2. #12
    Join Date
    Jun 2008
    Location
    The Netherlands
    Beans
    150
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Wireless connection lost (disconnects) when idle after locking screen

    Hey, sorry for my delayed reply. Thanks for getting back to me. Actually I just lost my connection again, this time without locking my session (dmesg below, though I don't think there's anything new in it). Good to know it's unrelated, I guess. I was downloading a 4 GB file with Firefox, but had a bittorrent client running (not sure if it was doing anything). I decreased the maximum number of connections from 200 to 100 and the half-open connections from 50 to 20 (or should these be even lower to make any difference?) and will first wait and see if it improves. If not, I'll try the backports (not that I don't want to use that right away, by the way, but I'd like to know what causes the problem instead of applying two solutions and not knowing which one fixed it ).

    UPDATE: interestingly enough, when I restarted my Firefox download, I lost my connection again within just a couple of minutes. Exact same problem as always. I'm currently downloading it for the third time, this time without my bittorrent client running in the background. Does Firefox make more than 1 connection, like a bittorrent client, when using it to download a file? If not, it should work this way. If it doesn't, I'll install the backports modules and see if the problem persists.

    Code:
    [ 4585.064184] iwlagn: Read index for DMA queue txq_id (2) index 97 is out of range [0-256] 110 103
    [ 4585.064194] iwlagn: Read index for DMA queue txq_id (2) index 98 is out of range [0-256] 110 103
    [ 4589.736573] wlan0: No ProbeResp from current AP 00:0c:f6:1e:16:5e - assume out of range
    [ 4590.336567] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms.
    [ 4590.837402] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4590.837412] iwlagn: Error setting new RXON (-110)
    [ 4590.837425] wlan0: direct probe to AP 00:0c:f6:1e:16:5e try 1
    [ 4591.037063] wlan0: direct probe to AP 00:0c:f6:1e:16:5e try 2
    [ 4591.236571] wlan0: direct probe to AP 00:0c:f6:1e:16:5e try 3
    [ 4591.438959] wlan0: direct probe to AP 00:0c:f6:1e:16:5e timed out
    [ 4600.844781] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms.
    [ 4601.344085] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4601.344094] iwlagn: Error setting new RXON (-110)
    [ 4605.164282] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4605.164291] iwlagn: Error setting new RXON (-110)
    [ 4605.667152] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms.
    [ 4606.165082] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4606.165086] iwlagn: Error setting new RXON (-110)
    [ 4606.664271] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms.
    [ 4607.164279] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4607.164288] iwlagn: Error setting new RXON (-110)
    [ 4612.164079] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms.
    [ 4612.664308] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4612.664317] iwlagn: Error setting new RXON (-110)
    [ 4617.664280] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms.
    [ 4618.164270] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4618.164279] iwlagn: Error setting new RXON (-110)
    [ 4623.164269] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms.
    [ 4623.664073] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4623.664082] iwlagn: Error setting new RXON (-110)
    [ 4628.664277] iwlagn: Error sending REPLY_SCAN_CMD: time out after 500ms.
    [ 4629.164276] iwlagn: Error sending REPLY_RXON: time out after 500ms.
    [ 4629.164285] iwlagn: Error setting new RXON (-110)
    [ 4629.164302] iwlagn: No space for Tx
    [ 4629.164306] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4633.665802] iwlagn: No space for Tx
    [ 4633.665814] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4633.665836] iwlagn: No space for Tx
    [ 4633.665840] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4633.665844] iwlagn: Error setting new RXON (-28)
    [ 4633.665851] iwlagn: No space for Tx
    [ 4633.665855] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4638.667435] iwlagn: No space for Tx
    [ 4638.667447] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4638.667470] iwlagn: No space for Tx
    [ 4638.667474] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4638.667478] iwlagn: Error setting new RXON (-28)
    [ 4638.667485] iwlagn: No space for Tx
    [ 4638.667489] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4643.669436] iwlagn: No space for Tx
    [ 4643.669448] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4643.669472] iwlagn: No space for Tx
    [ 4643.669477] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4643.669481] iwlagn: Error setting new RXON (-28)
    [ 4643.669488] iwlagn: No space for Tx
    [ 4643.669491] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4645.036548] iwlagn: No space for Tx
    [ 4645.036560] iwlagn: Error sending REPLY_STATISTICS_CMD: enqueue_hcmd failed: -28
    [ 4648.671486] iwlagn: No space for Tx
    [ 4648.671498] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4648.671519] iwlagn: No space for Tx
    [ 4648.671523] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4648.671527] iwlagn: Error setting new RXON (-28)
    [ 4648.671534] iwlagn: No space for Tx
    [ 4648.671537] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4653.672198] iwlagn: No space for Tx
    [ 4653.672209] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4653.672230] iwlagn: No space for Tx
    [ 4653.672234] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4653.672238] iwlagn: Error setting new RXON (-28)
    [ 4653.672245] iwlagn: No space for Tx
    [ 4653.672249] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4658.674066] iwlagn: No space for Tx
    [ 4658.674078] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4658.674101] iwlagn: No space for Tx
    [ 4658.674106] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4658.674110] iwlagn: Error setting new RXON (-28)
    [ 4658.674117] iwlagn: No space for Tx
    [ 4658.674121] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4663.676136] iwlagn: No space for Tx
    [ 4663.676146] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4663.676167] iwlagn: No space for Tx
    [ 4663.676171] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4663.676175] iwlagn: Error setting new RXON (-28)
    [ 4663.676182] iwlagn: No space for Tx
    [ 4663.676186] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4675.655306] iwlagn: No space for Tx
    [ 4675.655317] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4675.655339] iwlagn: No space for Tx
    [ 4675.655343] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4675.655347] iwlagn: Error setting new RXON (-28)
    [ 4675.655354] iwlagn: No space for Tx
    [ 4675.655358] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4795.656160] iwlagn: No space for Tx
    [ 4795.656172] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4795.656195] iwlagn: No space for Tx
    [ 4795.656199] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4795.656203] iwlagn: Error setting new RXON (-28)
    [ 4795.656210] iwlagn: No space for Tx
    [ 4795.656214] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 4915.655755] iwlagn: No space for Tx
    [ 4915.655767] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 4915.655789] iwlagn: No space for Tx
    [ 4915.655794] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 4915.655798] iwlagn: Error setting new RXON (-28)
    [ 4915.655805] iwlagn: No space for Tx
    [ 4915.655809] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 5035.655125] iwlagn: No space for Tx
    [ 5035.655138] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 5035.655160] iwlagn: No space for Tx
    [ 5035.655165] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 5035.655169] iwlagn: Error setting new RXON (-28)
    [ 5035.655176] iwlagn: No space for Tx
    [ 5035.655180] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 5155.655431] iwlagn: No space for Tx
    [ 5155.655443] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 5155.655464] iwlagn: No space for Tx
    [ 5155.655468] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 5155.655473] iwlagn: Error setting new RXON (-28)
    [ 5155.655480] iwlagn: No space for Tx
    [ 5155.655483] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 5275.655602] iwlagn: No space for Tx
    [ 5275.655615] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 5275.655639] iwlagn: No space for Tx
    [ 5275.655643] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 5275.655647] iwlagn: Error setting new RXON (-28)
    [ 5275.655654] iwlagn: No space for Tx
    [ 5275.655658] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 5339.421919] iwlagn: No space for Tx
    [ 5339.421930] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 5339.421949] iwlagn: No space for Tx
    [ 5339.421954] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 5339.421958] iwlagn: Error setting new RXON (-28)
    [ 5339.421965] iwlagn: No space for Tx
    [ 5339.421969] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 5344.423411] iwlagn: No space for Tx
    [ 5344.423423] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 5344.423446] iwlagn: No space for Tx
    [ 5344.423450] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 5344.423454] iwlagn: Error setting new RXON (-28)
    [ 5344.423461] iwlagn: No space for Tx
    [ 5344.423465] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 5349.424931] iwlagn: No space for Tx
    [ 5349.424943] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 5349.424967] iwlagn: No space for Tx
    [ 5349.424971] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 5349.424976] iwlagn: Error setting new RXON (-28)
    [ 5349.424983] iwlagn: No space for Tx
    [ 5349.424987] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 5354.426436] iwlagn: No space for Tx
    [ 5354.426448] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 5354.426471] iwlagn: No space for Tx
    [ 5354.426475] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 5354.426479] iwlagn: Error setting new RXON (-28)
    [ 5354.426486] iwlagn: No space for Tx
    [ 5354.426490] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    [ 5359.427934] iwlagn: No space for Tx
    [ 5359.427945] iwlagn: Error sending REPLY_SCAN_CMD: enqueue_hcmd failed: -28
    [ 5359.427969] iwlagn: No space for Tx
    [ 5359.427973] iwlagn: Error sending REPLY_RXON: enqueue_hcmd failed: -28
    [ 5359.427977] iwlagn: Error setting new RXON (-28)
    [ 5359.427983] iwlagn: No space for Tx
    [ 5359.427987] iwlagn: Error sending REPLY_TX_POWER_DBM_CMD: enqueue_hcmd failed: -28
    Last edited by pveurshout; September 16th, 2009 at 08:04 PM.

  3. #13
    Join Date
    Jun 2008
    Location
    The Netherlands
    Beans
    150
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Wireless connection lost (disconnects) when idle after locking screen

    Quote Originally Posted by Randomperson_1000 View Post
    ive got a theory on idea if it will work. Ur wireless doesn't drop with windows does it? it only drops when ubuntu makes alot of connections, window has a limit. I think you might want to limit the number of half open tcp connections in your bt client.it could be your router just cant handle it (mines cant).
    Unfortunately this wasn't the problem. The connection just dropped again although I significantly decreased the number of connections (also, my previous laptop using Hardy never had any problems with the network even though I used it intensively for bittorrenting as well).

    I installed the linux-backports-modules-jaunty as you suggested and will report back either when it works for a couple of days (while intensively using the connection) or as soon as it breaks (hopefully not).

  4. #14
    Join Date
    Jun 2008
    Location
    The Netherlands
    Beans
    150
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Wireless connection lost (disconnects) when idle after locking screen

    Hey, after installing the backports modules my dmesg keeps flooding with these messages:
    Code:
    [   75.919076] wlan0: beacon loss from AP ffff88013fd70ac0 - sending probe request
    [  115.877120] wlan0: beacon loss from AP ffff88013fd70ac0 - sending probe request
    It works fine (though it's too early to say whether the original problem has been solved by this) but I can only assume something else is wrong now. Any idea why these messages keep popping up?

  5. #15
    Join Date
    Jun 2008
    Location
    The Netherlands
    Beans
    150
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Wireless connection lost (disconnects) when idle after locking screen

    Unfortunately, I just lost my connection again.. installing linux-backports-modules-jaunty didn't help either

    Code:
    [ 5880.996571] iwlagn 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
    <repeated many times>
    EDIT: found this, which says it's fixed in kernel 2.6.30.5. Anyone got any idea when this kernel version will become available for Ubuntu??
    Last edited by pveurshout; October 1st, 2009 at 10:06 PM.

  6. #16
    Join Date
    Jul 2007
    Beans
    46
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Wireless connection lost (disconnects) when idle after locking screen

    I'm seeing a similar problem on my Lenovo ThinkPad T500. At home it drops connections every half hour or so. At work I cannot reproduce the problem.

    At home I'm using WPA, at work it's WEP. I believe that's the problem but have no solution.
    Life is short: Void the warranty.

  7. #17
    Join Date
    Jun 2008
    Location
    The Netherlands
    Beans
    150
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Wireless connection lost (disconnects) when idle after locking screen

    Quote Originally Posted by kngunn View Post
    I'm seeing a similar problem on my Lenovo ThinkPad T500. At home it drops connections every half hour or so. At work I cannot reproduce the problem.

    At home I'm using WPA, at work it's WEP. I believe that's the problem but have no solution.
    That's too bad do you have any idea whether this will remain a problem in Karmic?

  8. #18
    Join Date
    Jul 2007
    Beans
    46
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Wireless connection lost (disconnects) when idle after locking screen

    Yes. It's a problem in Karmic as well.
    Life is short: Void the warranty.

  9. #19
    Join Date
    Aug 2005
    Beans
    4

    Re: Wireless connection lost (disconnects) when idle after locking screen

    Hi all, same problem here. I'm running an up to date fresh install of 9.04 on a Dell 630c.. I'm sitting about 5 meters away from my access point and use WPA2.

    The strange thing is that it connects upon boot, fails after 5 minutes or so randomly and then never reconnects.

    When I play with the settings, remove the auto configuration it 'might' reconnect, but often not. If it does, the connection is more or less stable for a longer period. When I connect a cable, the wireless suddenly remembers it should connect and at that time I have two IP addresses, one for wireless and one for the wired connection.

    This is driving me crazy since I don't have problems on two different macs, a windows machine and a pda connecting without problems.

    this dmesg log repeats itself about 50 times:
    363.618859] wlan0: associated
    [ 373.641137] wlan0: disassociating by local choice (reason=3)
    [ 375.477449] wlan0: authenticate with AP 00:18:39:a1:28:a0
    [ 375.490172] wlan0: authenticate with AP 00:18:39:a1:28:a0
    [ 375.490193] wlan0: authenticated
    [ 375.490199] wlan0: associate with AP 00:18:39:a1:28:a0
    [ 375.495522] wlan0: RX ReassocResp from 00:18:39:a1:28:a0 (capab=0x411 status=0 aid=3)
    [ 375.495527] wlan0: associated

    I hope someone finds a solution for this

  10. #20
    Join Date
    Oct 2009
    Beans
    3

    Re: Wireless connection lost (disconnects) when idle after locking screen

    It does not really help to fix the problem, but:

    iwlagn is extremely poor quality driver in Linux.

    Have used hours and hours by fixing the problems. It is killing 64-bit systems. The driver somehow blocks the system - sometimes for tens of seconds. I _have_ been writing device drivers, so I _do_ know that there's something seriously wrong.

    With HP EliteBook laptops it helps to disable 11n using module parameters - which you'll find conveniently using strings to module binary. The problem exist in all Elitebooks (we have 3 of those).

    Currently sitting between shoes at my corridor using Ethernet cable because iwlagn gave totally out an system propably needs rebooting. I'm seriously considering to buy some other adapter.

    Also whenever you need to change your wifi channel to say 9 - iwlagn does not work .. it just loops and loops and loops .. and the rest of your system is totally locked. And you see messages like:

    Oct 22 20:33:06 hoopotin kernel: [253394.883189] psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 3 bytes away.

    This is due the handy logic of locking all interrupts within the driver? Is there really another driver or code accessing the same registers as iwlagn driver does? do you really need to lock everything?
    I could use stronger words also.

    This is just an open cry for better coding.

    (I seriously think government should pay pension for coders - which produce bad code - not to code at all)

    //arl

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •