[Bug 739090] New: very high ping, vanishes after rmmod / modprobe
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c0 Summary: very high ping, vanishes after rmmod / modprobe Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rens.groenewegen@xs4all.nl QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 iwlagn intel driver with centrino N 1030 wifi card in laptop dell inspiron 14z with openSuSE 12.1 and openSuSE 11.4 ping are very high after system boot. (linux only, not with windows 7 ) remote desktop VNC, rdesktop is unusable. XBMC does not work with DLNA/Upnp servers. then after unloading and modprobe iwlagn again, with parameter to disable N networking, ping around 2-4 msec (still high, but acceptable) since this is a laptop, that goes into sleep and resume all the time, i need to perform this sequence many times a day, which is irritating.... :-) my other laptop does not have the issue (realtek, not intel, but also opensuse) see ping stats below: =>ping gamez PING gamez.fritz.box (192.168.1.20) 56(84) bytes of data. 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=1 ttl=64 time=4.10 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=2 ttl=64 time=1.83 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=3 ttl=64 time=0.952 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=4 ttl=64 time=1.93 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=5 ttl=64 time=0.979 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=6 ttl=64 time=1.10 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=7 ttl=64 time=6.04 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=8 ttl=64 time=7.60 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=9 ttl=64 time=1.27 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=10 ttl=64 time=9.71 ms ^C --- gamez.fritz.box ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9013ms rtt min/avg/max/mdev = 0.952/3.554/9.713/3.016 ms linux-53g0:root[/etc/init.d] =>ping gamez PING gamez.fritz.box (192.168.1.20) 56(84) bytes of data. 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=1 ttl=64 time=7.91 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=3 ttl=64 time=35.4 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=4 ttl=64 time=58.1 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=6 ttl=64 time=97.1 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=7 ttl=64 time=120 ms ^C --- gamez.fritz.box ping statistics --- 8 packets transmitted, 5 received, 37% packet loss, time 7013ms rtt min/avg/max/mdev = 7.918/63.841/120.542/40.716 ms linux-53g0:root[/etc/init.d] =>rmmod iwlagn linux-53g0:root[/etc/init.d] =>modprobe iwlagn 11n_disable=1 linux-53g0:root[/etc/init.d] =>ping gamez PING gamez.fritz.box (192.168.1.20) 56(84) bytes of data. 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=1 ttl=64 time=6.35 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=2 ttl=64 time=2.35 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=3 ttl=64 time=4.67 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=4 ttl=64 time=4.61 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=5 ttl=64 time=2.24 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=6 ttl=64 time=2.23 ms ^C --- gamez.fritz.box ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5007ms rtt min/avg/max/mdev = 2.231/3.745/6.355/1.577 ms linux-53g0:root[/etc/init.d] => Reproducible: Always Steps to Reproduce: 1. boot, do ping: ping very high 2. rmmod / modprobe 3. ping ok again 4. sleep system or hibernate 5. ping very high 6. rmmod/modprobe 7. ping ok again. Expected Results: stabke ping, under 1 msec, like the results when in microsoft windows 7 (x64) when loading windows driver with ndiswrapper, problem goes away. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c1 --- Comment #1 from rens groenewegen <rens.groenewegen@xs4all.nl> 2012-01-02 00:35:45 UTC --- did some more testing. at first I thought disabling N capability helped, but it does not. the workaround is to rmmod and modprobe iwlagn, and then the latency problem is goone. performance is not stellar, around 3 -4 mbyte per second upload /download, on G or on N ( I have 2 accesspoints, one with G+N and one on B+G ) this is output from dmesg: [ 1302.904681] sd 0:0:0:0: [sda] Starting disk [ 1302.904717] iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio. [ 1302.904733] xhci_hcd 0000:03:00.0: setting latency timer to 64 [ 1302.904786] atl1c 0000:04:00.0: wake-up capability disabled by ACPI [ 1302.904792] atl1c 0000:04:00.0: PME# disabled [ 1303.056853] Extended CMOS year: 2000 [ 1303.154502] usb 2-1.5: reset full speed USB device number 3 using ehci_hcd [ 1303.230238] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1303.249227] btusb 2-1.5:1.0: no reset_resume for driver btusb? [ 1303.249234] btusb 2-1.5:1.1: no reset_resume for driver btusb? [ 1303.264181] ata2.00: configured for UDMA/100 [ 1303.318263] usb 1-1.4: reset high speed USB device number 3 using ehci_hcd [ 1306.241739] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1306.243011] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded [ 1306.245514] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded [ 1306.246476] ata1.00: configured for UDMA/133 [ 1306.282231] PM: resume of devices complete after 3382.832 msecs [ 1306.282523] PM: Finishing wakeup. [ 1306.282524] Restarting tasks ... done. [ 1306.289580] video LNXVIDEO:00: Restoring backlight state [ 1306.353639] usb 1-1.5: new high speed USB device number 5 using ehci_hcd [ 1306.390091] Disabling lock debugging due to kernel taint [ 1306.391346] ndiswrapper version 1.56 loaded (smp=yes, preempt=no) [ 1306.704125] usb 1-1.5: New USB device found, idVendor=0bda, idProduct=0138 [ 1306.704135] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1306.704137] usb 1-1.5: Product: USB2.0-CRW [ 1306.704139] usb 1-1.5: Manufacturer: Generic [ 1306.704140] usb 1-1.5: SerialNumber: 20090516388200000 [ 1306.727308] scsi7 : usb-storage 1-1.5:1.0 [ 1306.740313] usb 1-1.5: USB disconnect, device number 5 [ 1306.758207] usbcore: registered new interface driver ndiswrapper [ 1309.038946] xhci_hcd 0000:03:00.0: PME# enabled [ 1309.077072] EXT4-fs (sda7): re-mounted. Opts: user_xattr,acl,barrier=1,stripe=4,data=ordered,commit=600 [ 1309.343932] EXT4-fs (sda7): re-mounted. Opts: acl,user_xattr,commit=600 [ 1309.399849] atl1c 0000:04:00.0: irq 49 for MSI/MSI-X [ 1309.482493] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1309.489517] iwlagn 0000:02:00.0: L1 Enabled; Disabling L0S [ 1309.496238] iwlagn 0000:02:00.0: Radio type=0x2-0x2-0x1 [ 1309.592852] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1311.314170] wlan0: authenticate with bc:05:43:8e:6f:7f (try 1) [ 1311.316980] wlan0: authenticated [ 1311.338514] wlan0: associate with bc:05:43:8e:6f:7f (try 1) [ 1311.341604] wlan0: RX AssocResp from bc:05:43:8e:6f:7f (capab=0x431 status=0 aid=2) [ 1311.341607] wlan0: associated [ 1311.345021] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1313.079534] ehci_hcd 0000:00:1a.0: PCI INT A disabled [ 1313.079576] ehci_hcd 0000:00:1a.0: PME# enabled [ 1313.079633] ehci_hcd 0000:00:1d.0: PCI INT A disabled [ 1313.079668] ehci_hcd 0000:00:1d.0: PME# enabled [ 1321.570857] wlan0: no IPv6 routers present [ 1345.599782] wlan0: deauthenticating from bc:05:43:8e:6f:7f by local choice (reason=3) [ 1345.607296] cfg80211: Calling CRDA to update world regulatory domain [ 1345.612282] cfg80211: World regulatory domain updated: [ 1345.612285] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 1345.612288] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 1345.612290] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 1345.612292] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 1345.612294] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 1345.612296] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 1345.902757] wlan0: authenticate with 00:50:7f:60:e8:70 (try 1) [ 1345.904397] wlan0: authenticated [ 1345.916031] wlan0: associate with 00:50:7f:60:e8:70 (try 1) [ 1345.921166] wlan0: RX AssocResp from 00:50:7f:60:e8:70 (capab=0x431 status=0 aid=1) [ 1345.921171] wlan0: associated [ 1345.926262] cfg80211: Calling CRDA for country: TW [ 1345.928895] cfg80211: Regulatory domain changed to country: TW [ 1345.928898] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 1345.928901] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 1345.928903] cfg80211: (5270000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 1345.928906] cfg80211: (5735000 KHz - 5815000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 1390.556430] wlan0: deauthenticating from 00:50:7f:60:e8:70 by local choice (reason=3) [ 1390.580175] cfg80211: Calling CRDA to update world regulatory domain [ 1390.719932] cfg80211: World regulatory domain updated: [ 1390.719935] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 1390.719937] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 1390.719940] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 1390.719942] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 1390.719943] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 1390.719945] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 1390.720829] iwlagn 0000:02:00.0: PCI INT A disabled [ 1394.531362] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d [ 1394.531366] Copyright(c) 2003-2011 Intel Corporation [ 1394.531455] iwlagn 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 1394.531519] iwlagn 0000:02:00.0: setting latency timer to 64 [ 1394.531565] iwlagn 0000:02:00.0: pci_resource_len = 0x00002000 [ 1394.531567] iwlagn 0000:02:00.0: pci_resource_base = ffffc90001cbc000 [ 1394.531569] iwlagn 0000:02:00.0: HW Revision ID = 0x34 [ 1394.531908] iwlagn 0000:02:00.0: irq 48 for MSI/MSI-X [ 1394.532026] iwlagn 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1030 BGN, REV=0xB0 [ 1394.532189] iwlagn 0000:02:00.0: L1 Enabled; Disabling L0S [ 1394.549345] iwlagn 0000:02:00.0: device EEPROM VER=0x71a, CALIB=0x6 [ 1394.549348] iwlagn 0000:02:00.0: Device SKU: 0X150 [ 1394.549350] iwlagn 0000:02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3 [ 1394.549367] iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [ 1394.551642] iwlagn 0000:02:00.0: loaded firmware version 17.168.5.1 build 33993 [ 1394.551841] Registered led device: phy3-led [ 1394.551942] ieee80211 phy3: Selected rate control algorithm 'iwl-agn-rs' [ 1394.578333] iwlagn 0000:02:00.0: L1 Enabled; Disabling L0S [ 1394.585035] iwlagn 0000:02:00.0: Radio type=0x2-0x2-0x1 [ 1394.674976] iwlagn 0000:02:00.0: L1 Enabled; Disabling L0S [ 1394.681667] iwlagn 0000:02:00.0: Radio type=0x2-0x2-0x1 [ 1394.782262] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1397.029831] wlan0: authenticate with 00:50:7f:60:e8:70 (try 1) [ 1397.031650] wlan0: authenticated [ 1397.051016] wlan0: associate with 00:50:7f:60:e8:70 (try 1) [ 1397.053589] wlan0: RX AssocResp from 00:50:7f:60:e8:70 (capab=0x431 status=0 aid=1) [ 1397.053592] wlan0: associated [ 1397.060046] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1397.060115] cfg80211: Calling CRDA for country: TW [ 1397.063040] cfg80211: Regulatory domain changed to country: TW [ 1397.063042] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 1397.063044] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) [ 1397.063045] cfg80211: (5270000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) [ 1397.063047] cfg80211: (5735000 KHz - 5815000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) [ 1407.730534] wlan0: no IPv6 routers present l -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c2 --- Comment #2 from rens groenewegen <rens.groenewegen@xs4all.nl> 2012-01-03 16:56:47 UTC --- Created an attachment (id=469570) --> (http://bugzilla.novell.com/attachment.cgi?id=469570) screenshot. speedtest on internet screenshot. ping on internet 12x faster than LAN -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c3 --- Comment #3 from rens groenewegen <rens.groenewegen@xs4all.nl> 2012-01-10 22:54:34 UTC --- turning on and then of powermanagement seems to have an influence..... =>ping gamez PING gamez.fritz.box (192.168.1.20) 56(84) bytes of data. 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=1 ttl=64 time=6.80 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=2 ttl=64 time=3.73 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=3 ttl=64 time=1.63 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=4 ttl=64 time=2.72 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=5 ttl=64 time=2.30 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=6 ttl=64 time=1.66 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=7 ttl=64 time=1.81 ms ^C --- gamez.fritz.box ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6007ms rtt min/avg/max/mdev = 1.630/2.952/6.808/1.718 ms linux-53g0:root[/etc/pm/sleep.d] =>iwconfig wlan0 power timeout 700ms linux-53g0:root[/etc/pm/sleep.d] =>ping gamez PING gamez.fritz.box (192.168.1.20) 56(84) bytes of data. 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=3 ttl=64 time=580 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=4 ttl=64 time=604 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=5 ttl=64 time=628 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=6 ttl=64 time=652 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=7 ttl=64 time=676 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=8 ttl=64 time=700 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=9 ttl=64 time=724 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=10 ttl=64 time=748 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=11 ttl=64 time=772 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=13 ttl=64 time=820 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=15 ttl=64 time=862 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=16 ttl=64 time=886 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=17 ttl=64 time=911 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=18 ttl=64 time=935 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=19 ttl=64 time=959 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=20 ttl=64 time=166 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=21 ttl=64 time=1006 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=22 ttl=64 time=0.920 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=24 ttl=64 time=48.4 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=25 ttl=64 time=70.5 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=26 ttl=64 time=92.9 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=27 ttl=64 time=105 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=28 ttl=64 time=128 ms 64 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=29 ttl=64 time=150 ms ^C --- gamez.fritz.box ping statistics --- 29 packets transmitted, 24 received, 17% packet loss, time 28019ms rtt min/avg/max/mdev = 0.920/551.509/1006.821/341.073 ms linux-53g0:root[/etc/pm/sleep.d] =>ping -s 1000 gamez PING gamez.fritz.box (192.168.1.20) 1000(1028) bytes of data. 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=1 ttl=64 time=432 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=4 ttl=64 time=796 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=5 ttl=64 time=820 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=6 ttl=64 time=844 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=8 ttl=64 time=884 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=9 ttl=64 time=90.6 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=10 ttl=64 time=216 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=13 ttl=64 time=798 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=14 ttl=64 time=822 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=15 ttl=64 time=846 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=16 ttl=64 time=871 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=17 ttl=64 time=895 ms ^C --- gamez.fritz.box ping statistics --- 17 packets transmitted, 12 received, 29% packet loss, time 16023ms rtt min/avg/max/mdev = 90.615/693.318/895.797/269.000 ms linux-53g0:root[/etc/pm/sleep.d] =>iwconfig wlan0 power off linux-53g0:root[/etc/pm/sleep.d] =>ping -s 1000 gamez PING gamez.fritz.box (192.168.1.20) 1000(1028) bytes of data. 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=1 ttl=64 time=1.33 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=2 ttl=64 time=1.35 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=3 ttl=64 time=5.63 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=4 ttl=64 time=1.28 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=5 ttl=64 time=1.30 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=6 ttl=64 time=1.24 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=7 ttl=64 time=1.60 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=8 ttl=64 time=2.74 ms 1008 bytes from gamez.fritz.box (192.168.1.20): icmp_seq=9 ttl=64 time=15.4 ms ^C --- gamez.fritz.box ping statistics --- 9 pack -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c4 kk zhang <kkzhang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |kkzhang@novell.com Resolution| |NORESPONSE --- Comment #4 from kk zhang <kkzhang@novell.com> 2012-03-09 07:27:35 UTC --- Long time no response.So closed.Feel free to reopen it.Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c5 Jan Engelhardt <jengelh@medozas.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |jengelh@medozas.de Component|Network |Kernel Resolution|NORESPONSE | --- Comment #5 from Jan Engelhardt <jengelh@medozas.de> 2012-03-10 08:53:03 UTC --- (Revert bogus close.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c6 --- Comment #6 from rens groenewegen <rens.groenewegen@xs4all.nl> 2012-03-10 22:41:26 UTC --- gents, I think i pinpointed this issue. it is related to powermanagement of the wireless card: the powermanagement as done by KDE powermgmt is a fixed interval thing. it sets for example the interval to 500 msec, in between the card does nothing..... which saves power, of course. (this is what e.g. powertop tool from Intel suggests to do) however, that renders the machine useless for example gaming, remote desktops (VDI, vnc, rdesktop etcetera) since you need sub 100 msec responsiveness on a gui desktop, otherwise it is useless..... These are the examples of what *can* be tuned : iwconfig eth0 power period 2 iwconfig eth0 power 500m unicast iwconfig eth0 power timeout 300u all iwconfig eth0 power saving 3 iwconfig eth0 power off iwconfig eth0 power min period 2 power max period 4 I guess Kde guys should look at their choices, or offer options to the user. A timeout is probably more intelligent. if nothing happens, the card goes to sleep, and wakes up on activity. so maybe this is not a bug, but should rather be a product improvement in KDE powermanagement. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c7 Jan Engelhardt <jengelh@medozas.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |KDE4 Workspace AssignedTo|bnc-team-screening@forge.pr |kde-maintainers@suse.de |ovo.novell.com | OS/Version|Other |Linux Severity|Major |Enhancement --- Comment #7 from Jan Engelhardt <jengelh@medozas.de> 2012-03-10 22:48:23 UTC --- Was my first thought too that it simply was overly aggressive hardware PM. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=739090 https://bugzilla.novell.com/show_bug.cgi?id=739090#c8 Albert Cieszkowski <albert.cieszkowski@cc.com.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |albert.cieszkowski@cc.com.p | |l --- Comment #8 from Albert Cieszkowski <albert.cieszkowski@cc.com.pl> 2012-09-22 17:21:49 UTC --- I ran into this "condition" on OpenSUSE 12.2 - very irritating.... I resolved it by removing power management for wireless: sudo chmod -x /usr/lib/pm-util//usr/lib/pm-utils/power.d/wireless -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=739090 http://bugzilla.novell.com/show_bug.cgi?id=739090#c9 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |jslaby@suse.com Resolution|--- |WONTFIX --- Comment #9 from Jiri Slaby <jslaby@suse.com> --- This version is out of maintenance, if you still see the problem, please reopen and move the bug to a more recent product. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com