Bug 18342 - Пропадания пакетов на wifi-интерфейсе
Summary: Пропадания пакетов на wifi-интерфейсе
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: NetworkManager (show other bugs)
Version: unstable
Hardware: all Linux
: P2 critical
Assignee: Mikhail Efremov
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-25 03:32 MSK by barabashka
Modified: 2009-10-16 14:20 MSD (History)
3 users (show)

See Also:

Attachments
lost-wifi-adhoc-messages (3.52 KB, text/plain)
2008-12-29 05:42 MSK, Ivan Zakharyaschev 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description barabashka 2008-12-25 03:32:38 MSK 
При использовании NetworkManager'а происходит пропадание пакетов на интерфейсе с переодичностью 5-10 пакетов на 100.

1508 bytes from 192.168.0.1: icmp_seq=99 ttl=128 time=7.93 ms
1508 bytes from 192.168.0.1: icmp_seq=106 ttl=128 time=8.50 ms
1508 bytes from 192.168.0.1: icmp_seq=107 ttl=128 time=8.58 ms
1508 bytes from 192.168.0.1: icmp_seq=108 ttl=128 time=8.42 ms
^C
--- 192.168.0.1 ping statistics ---
108 packets transmitted, 92 received, 14% packet loss, time 107446ms
rtt min/avg/max/mdev = 7.886/8.440/10.144/0.360 ms

При использовании etcnet на том же оборудовании данной проблемы не наблюдается.

lspci
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82566MC Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
15:00.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev ff)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)

lspci -n
00:00.0 0600: 8086:2a00 (rev 0c)
00:01.0 0604: 8086:2a01 (rev 0c)
00:19.0 0200: 8086:104d (rev 03)
00:1a.0 0c03: 8086:2834 (rev 03)
00:1a.1 0c03: 8086:2835 (rev 03)
00:1a.7 0c03: 8086:283a (rev 03)
00:1b.0 0403: 8086:284b (rev 03)
00:1c.0 0604: 8086:283f (rev 03)
00:1c.1 0604: 8086:2841 (rev 03)
00:1c.2 0604: 8086:2843 (rev 03)
00:1c.3 0604: 8086:2845 (rev 03)
00:1c.4 0604: 8086:2847 (rev 03)
00:1d.0 0c03: 8086:2830 (rev 03)
00:1d.1 0c03: 8086:2831 (rev 03)
00:1d.2 0c03: 8086:2832 (rev 03)
00:1d.7 0c03: 8086:2836 (rev 03)
00:1e.0 0604: 8086:2448 (rev f3)
00:1f.0 0601: 8086:2815 (rev 03)
00:1f.1 0101: 8086:2850 (rev 03)
00:1f.2 0106: 8086:2829 (rev 03)
00:1f.3 0c05: 8086:283e (rev 03)
01:00.0 0300: 10de:0429 (rev a1)
03:00.0 0280: 8086:4230 (rev 61)
15:00.0 0607: 1180:0476 (rev ba)
15:00.1 0c00: 1180:0832 (rev 04)
15:00.2 0805: 1180:0822 (rev 21)
15:00.3 0880: 1180:0843 (rev ff)
15:00.4 0880: 1180:0592 (rev 11)
15:00.5 0880: 1180:0852 (rev 11)

 uname -a
Linux localhost.localdomain 2.6.25-std-def-alt9 #1 SMP Wed Sep 10 13:51:09 MSD 2008 i686 GNU/Linux
firmware-iwl4965-228.57-alt1.23

 rpm -qa|grep Netwo
NetworkManager-0.7.0-alt15
NetworkManager-glib-0.7.0-alt15
NetworkManager-gnome-0.7.0-alt8
rpm -qa|grep etcnet
etcnet-0.9.7-alt2
etcnet-defaults-server-0.9.7-alt2
Comment 1 Mikhail Efremov 2008-12-25 14:28:19 MSK 
В /var/log/messages есть сообщения от NM после установки соединения? Если есть - покажите.
Comment 2 barabashka 2008-12-25 14:56:34 MSK 
(In reply to comment #1)
> В /var/log/messages есть сообщения от NM после установки соединения? Если есть -
> покажите.
> 

В messages нет ничего, на 12 консоли появляются с некой переодичностью

daemons/warnings

Dec 25 13:30:55 localhost NetworkManager: <WARN>  check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Missing link name TLV (errno = Invalid argument

daemons/info

Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) starting connection 'Auto althome'
Dec 25 14:38:40 localhost NetworkManager: <info>  (wlan0): device state change: 3 -> 4
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 25 14:38:40 localhost NetworkManager: <info>  (wlan0): device state change: 4 -> 5
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0/wireless): access point 'Auto althome' has security, but secrets are required.
Dec 25 14:38:40 localhost NetworkManager: <info>  (wlan0): device state change: 5 -> 6
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 25 14:38:40 localhost NetworkManager: <info>  (wlan0): device state change: 6 -> 4
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 25 14:38:40 localhost NetworkManager: <info>  (wlan0): device state change: 4 -> 5
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0/wireless): connection 'Auto althome' has security, and secrets exist.  No new secrets needed.
Dec 25 14:38:40 localhost NetworkManager: <info>  Config: added 'ssid' value 'althome'
Dec 25 14:38:40 localhost NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Dec 25 14:38:40 localhost NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Dec 25 14:38:40 localhost NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Dec 25 14:38:40 localhost NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 25 14:38:40 localhost NetworkManager: <info>  Config: set interface ap_scan to 1
Dec 25 14:38:40 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Dec 25 14:38:40 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associated
Dec 25 14:38:41 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Dec 25 14:38:41 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Dec 25 14:38:41 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'althome'.
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec 25 14:38:41 localhost NetworkManager: <info>  (wlan0): device state change: 5 -> 7
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Dec 25 14:38:41 localhost NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Dec 25 14:38:42 localhost NetworkManager: <info>  (wlan0): device state change: 7 -> 8
Dec 25 14:38:42 localhost NetworkManager: <info>  Policy set 'Auto althome' (wlan0) as default for routing and DNS.
Dec 25 14:38:42 localhost NetworkManager: <info>  Activation (wlan0) successful, device activated.
Dec 25 14:38:42 localhost NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Dec 25 14:38:57 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> associating
Dec 25 14:38:57 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Dec 25 14:38:57 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Dec 25 14:38:57 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Dec 25 14:38:57 localhost NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Comment 3 Ivan Zakharyaschev 2008-12-29 05:42:57 MSK 
Created attachment 3173 [details]
lost-wifi-adhoc-messages

Не знаю, имеет ли это отношение: у меня на iwl3945 с одной стороны (и iopw2200 с другой) в ad-hoc сети теряется 37% пакетов, при этом пишется куча сообщений на стороне iwl3945:

kernel: wlan0: Configured IBSS beacon template
kernel: phy0: Adding new IBSS station ....

(дальше MAC или что-то подобное)

несколько штук в секунду. Я подозреваю, что при такой интенсивности сообщений оно нормально работать не сможет.

Остальные сообщения, которые попали в /var/log/messages, приложены.
Comment 4 ildar 2008-12-29 07:09:42 MSK 
(In reply to comment #2)
> В messages нет ничего

попробуйте сравнить вывод iwconfig в обоих случаях, может наведёт на какие-то мысли.
Comment 5 Mikhail Efremov 2008-12-29 19:46:35 MSK 
(In reply to comment #3)
> Не знаю, имеет ли это отношение: у меня на iwl3945 с одной стороны (и iopw2200 с
> другой) в ad-hoc сети теряется 37% пакетов, при этом пишется куча сообщений на
> стороне iwl3945:
Это тоже только при использовании NM? 

> Остальные сообщения, которые попали в /var/log/messages, приложены.

NetworkManager: <WARN>  scan_results_cb(): could not get scan results: An error ocurred getting scan results..

wpa_supplicant вместо результатов сканирования по каким-то причинам прислал эту ошибку. Похоже в этом случае все-таки баг не NM.
Comment 6 Mikhail Efremov 2008-12-30 21:46:56 MSK 
Есть шанс, что NetworkManager-0.7.0-alt17 может помочь.
Comment 7 barabashka 2009-03-18 01:46:58 MSK 
(В ответ на комментарий №6)
> Есть шанс, что NetworkManager-0.7.0-alt17 может помочь.

Помог давно
Comment 8 Ivan Zakharyaschev 2009-10-16 14:20:51 MSD 
Спасибо за ответ!

(В ответ на комментарий №5)
> (In reply to comment #3)
> > Не знаю, имеет ли это отношение: у меня на iwl3945 с одной стороны (и iopw2200 с
> > другой) в ad-hoc сети теряется 37% пакетов, при этом пишется куча сообщений на
> > стороне iwl3945:
> Это тоже только при использовании NM? 

Нет, получается, это не только при использовании NM: https://bugzilla.altlinux.org/show_bug.cgi?id=21962 (там без NM), так что это не связанная с этим проблема.