You are not logged in.

Pages: 1

#1 2012-05-05 11:49:44

Nati
Member
Registered: 2012-02-05
Posts: 8

[solved] Wireless goes to sleep after a while and need some "push"...

Hello.

I have a strange behavior of the wireless card on my laptop.

the link is working well for some time, then the speed drops down and only after resetting the adapter link it come back to live....

for example: ping to the gateway

PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=254 time=720 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=254 time=4497 ms
64 bytes from 192.168.2.1: icmp_req=3 ttl=254 time=3500 ms
64 bytes from 192.168.2.1: icmp_req=4 ttl=254 time=2501 ms
64 bytes from 192.168.2.1: icmp_req=5 ttl=254 time=1508 ms
64 bytes from 192.168.2.1: icmp_req=6 ttl=254 time=4284 ms
64 bytes from 192.168.2.1: icmp_req=7 ttl=254 time=3284 ms
64 bytes from 192.168.2.1: icmp_req=8 ttl=254 time=2286 ms
64 bytes from 192.168.2.1: icmp_req=9 ttl=254 time=1287 ms
64 bytes from 192.168.2.1: icmp_req=10 ttl=254 time=3944 ms
64 bytes from 192.168.2.1: icmp_req=11 ttl=254 time=2944 ms
64 bytes from 192.168.2.1: icmp_req=12 ttl=254 time=1944 ms
64 bytes from 192.168.2.1: icmp_req=13 ttl=254 time=944 ms

then i executed the following:

$ sudo ip link set wlan0 down
$ sudo ip link set wlan0 up

reconnected to the WIFI network and tried again and now:

PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=254 time=29.3 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=254 time=1233 ms
64 bytes from 192.168.2.1: icmp_req=3 ttl=254 time=226 ms
64 bytes from 192.168.2.1: icmp_req=4 ttl=254 time=2.56 ms
64 bytes from 192.168.2.1: icmp_req=5 ttl=254 time=2.15 ms
64 bytes from 192.168.2.1: icmp_req=6 ttl=254 time=1.34 ms
64 bytes from 192.168.2.1: icmp_req=7 ttl=254 time=0.788 ms
64 bytes from 192.168.2.1: icmp_req=8 ttl=254 time=1.25 ms
64 bytes from 192.168.2.1: icmp_req=9 ttl=254 time=0.975 ms
64 bytes from 192.168.2.1: icmp_req=10 ttl=254 time=1.03 ms
64 bytes from 192.168.2.1: icmp_req=11 ttl=254 time=1.63 ms
64 bytes from 192.168.2.1: icmp_req=12 ttl=254 time=3.55 ms
64 bytes from 192.168.2.1: icmp_req=13 ttl=254 time=1.28 ms

Well, someone have any idea on whats going on here?

Thanks!

Last edited by Nati (2012-05-05 18:34:47)

Offline

#2 2012-05-05 12:03:33

Gcool
Member
Registered: 2011-08-16
Posts: 1,456

Re: [solved] Wireless goes to sleep after a while and need some "push"...

A couple of additional things that might be worth mentioning:

- Which wifi adapter (and driver) are you using? Perhaps post the output of lspci -vvv
- When did you start experiencing this issue? Which packages (if any) were upgraded in that same period?
- What do the logs (/var/log/messages.log) say?

Burninate!

Offline

#3 2012-05-05 14:25:54

Nati
Member
Registered: 2012-02-05
Posts: 8

Re: [solved] Wireless goes to sleep after a while and need some "push"...

Hi, thank you for your reply.

Well, i ready don't remember when i start experiencing this issue. :-(
I thought the problem lies in the router in the first place but now i realize its incorrect.

Information about the wifi adapter:

Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. Device 8181
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 17
	Region 0: I/O ports at 3000 [size=256]
	Region 1: Memory at d9100000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Express (v1) Legacy Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [140 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [160 v1] Device Serial Number 88-55-22-fe-ff-4c-e0-00
	Kernel driver in use: rtl8192se

   

Here is the log:

May  5 15:37:20 localhost dhcpcd[21631]: version 5.5.6 starting
May  5 15:37:20 localhost dhcpcd[21631]: wlan0: sending IPv6 Router Solicitation
May  5 15:37:20 localhost dhcpcd[21631]: wlan0: rebinding lease of 192.168.2.101
May  5 15:37:20 localhost dhcpcd[21631]: wlan0: acknowledged 192.168.2.101 from 192.168.2.1 `TP-LINK'
May  5 15:37:20 localhost dhcpcd[21631]: wlan0: checking for 192.168.2.101
May  5 15:37:24 localhost dhcpcd[21631]: wlan0: sending IPv6 Router Solicitation
May  5 15:37:25 localhost dhcpcd[21631]: wlan0: leased 192.168.2.101 for 259200 seconds
May  5 15:37:25 localhost dhcpcd[21631]: forked to background, child pid 21661
May  5 15:37:28 localhost dhcpcd[21661]: wlan0: sending IPv6 Router Solicitation
May  5 15:37:32 localhost dhcpcd[21661]: wlan0: sending IPv6 Router Solicitation
May  5 15:37:32 localhost dhcpcd[21661]: wlan0: no IPv6 Routers available
May  5 15:42:18 localhost kernel: [ 9447.987317] CE: hpet increased min_delta_ns to 30169 nsec
May  5 16:03:07 localhost kernel: [10695.594848] cfg80211: Calling CRDA to update world regulatory domain
May  5 16:03:07 localhost dhcpcd[21661]: wlan0: carrier lost
May  5 16:03:07 localhost kernel: [10695.774552] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May  5 16:03:07 localhost dhcpcd[27901]: sending signal 1 to pid 21661
May  5 16:03:07 localhost dhcpcd[27901]: waiting for pid 21661 to exit
May  5 16:03:07 localhost dhcpcd[21661]: received SIGHUP, releasing
May  5 16:03:07 localhost dhcpcd[21661]: wlan0: removing interface
May  5 16:03:07 localhost kernel: [10696.069537] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May  5 16:03:07 localhost kernel: [10696.110612] r8169 0000:02:00.0: eth0: link down
May  5 16:03:07 localhost kernel: [10696.111177] ADDRCONF(NETDEV_UP): eth0: link is not ready
May  5 16:03:07 localhost kernel: [10696.299454] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May  5 16:03:09 localhost kernel: [10697.485506] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May  5 16:03:09 localhost kernel: [10697.521609] r8169 0000:02:00.0: eth0: link down
May  5 16:03:09 localhost kernel: [10697.522537] ADDRCONF(NETDEV_UP): eth0: link is not ready
May  5 16:03:09 localhost kernel: [10697.708256] ADDRCONF(NETDEV_UP): wlan0: link is not ready
May  5 16:03:22 localhost kernel: [10710.988318] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May  5 16:03:23 localhost dhcpcd[27973]: version 5.5.6 starting
May  5 16:03:23 localhost dhcpcd[27973]: wlan0: sending IPv6 Router Solicitation
May  5 16:03:23 localhost dhcpcd[27973]: wlan0: rebinding lease of 192.168.2.101
May  5 16:03:23 localhost dhcpcd[27973]: wlan0: acknowledged 192.168.2.101 from 192.168.2.1 `TP-LINK'
May  5 16:03:23 localhost dhcpcd[27973]: wlan0: checking for 192.168.2.101
May  5 16:03:27 localhost dhcpcd[27973]: wlan0: sending IPv6 Router Solicitation
May  5 16:03:28 localhost dhcpcd[27973]: wlan0: leased 192.168.2.101 for 259200 seconds
May  5 16:03:28 localhost dhcpcd[27973]: forked to background, child pid 28000
May  5 16:03:31 localhost dhcpcd[28000]: wlan0: sending IPv6 Router Solicitation
May  5 16:03:35 localhost dhcpcd[28000]: wlan0: sending IPv6 Router Solicitation
May  5 16:03:35 localhost dhcpcd[28000]: wlan0: no IPv6 Routers available
May  5 16:23:35 localhost -- MARK --
May  5 16:43:35 localhost -- MARK --

Thank you.

Last edited by Nati (2012-05-05 14:27:14)

Offline

#4 2012-05-05 15:05:06

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,429

Re: [solved] Wireless goes to sleep after a while and need some "push"...

When you are connected have a look at 

iwconfig

to see if power management for the wifi card is on or off.

Offline

#5 2012-05-05 15:26:45

Nati
Member
Registered: 2012-02-05
Posts: 8

Re: [solved] Wireless goes to sleep after a while and need some "push"...

Thank you,
The power management is set to on.
What is the meaning of this?
If the power management is set it will slows down the link to save energy?

Thank you.

Offline

#6 2012-05-05 15:34:07

Nati
Member
Registered: 2012-02-05
Posts: 8

Re: [solved] Wireless goes to sleep after a while and need some "push"...

@Strike0,
I set the power management to off and its seems the problems gone...
Can you approve please?
The power management can be the cause of this issue?

Offline

#7 2012-05-05 16:35:02

Gcool
Member
Registered: 2011-08-16
Posts: 1,456

Re: [solved] Wireless goes to sleep after a while and need some "push"...

In general, wifi power management causes more issues then it's worth (when working on battery). Probably best to leave it disabled indeed.

Burninate!

Offline

#8 2012-05-05 18:34:12

Nati
Member
Registered: 2012-02-05
Posts: 8

Re: [solved] Wireless goes to sleep after a while and need some "push"...

OK, Well thank you very much!

Offline

#9 2012-05-05 20:01:45

Strike0
Member
From: Germany
Registered: 2011-09-05
Posts: 1,429

Re: [solved] Wireless goes to sleep after a while and need some "push"...

Nati wrote:

The power management can be the cause of this issue?

Yes, unfortunately a lot of wifi drivers have problems with it still apparently, not only yours. I think the main power save strategy is to reduce transmission power of the devices when it is not used, since that is a main factor for energy consumption of it. Problem often seems to be the automatic wake-up which does not work out-the-box. The same applies for resume from suspend-to-mem/disk often, where drivers then fail to re-connect without "kick".

Offline

Pages: 1

Board footer

Powered by FluxBB