Created an attachment (id=555784) updated analysis script for trace from comment 39
(In reply to comment #39) > Created an attachment (id=552961) [details] > the wanted log-file, while the failure occurs > > sporadic errors are some times hard to reproduce, this time it was easier Thank you for this second trace and sorry for my long delay in analyzing it. cat c39-trace | ./analyze.py rfd 114 recv, frame len 1510 / 192 (-1318 left before page end) rfd 113 mapped, page left 2496 rfd 115 recv, frame len 1298 / 192 (-1106 left before page end) rfd 114 mapped, page left 1984 rfd 116 recv, frame len 1298 / 3008 (1710 left before page end) rfd 115 mapped, page left 2240 rfd 117 recv, frame len 1298 / 448 (-850 left before page end) [...] rfd 470 mapped, page left 1984 rfd 472 recv, frame len 102 / 192 (90 left before page end) rfd 471 mapped, page left 3264 rfd 473 recv, frame len 94 / 2496 (2402 left before page end) rfd 472 mapped, page left 64 [...] rfd 471 recv, frame len 1298 / 3264 (1966 left before page end) rfd 470 mapped, page left 192 overflow (repeated 198 times) after rfd 471, rrd 472 frame len 102 / 64 (-38 left before page end) It shows that the driver can in fact receive into some buffers that straddle page boundaries and can write frames large enough to cross this boundary, without crashing. However, once again the crash happens when writing into a buffer that starts 64B before the page end. Like in the trace from comment 35, that is the smallest distance present in the trace. These traces show that the adapter crashes in a more constrained situation (writing accross the page boundary to a buffer that starts 64B before the end of a page) than the initial hypothesis (writing to any buffer that crosses a page boundary). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1175091 Title: Cable Ethernet conn. "die" with Atheros Network Card in Ubuntu 13.04 Status in “network-manager” package in Ubuntu: Confirmed Status in Fedora: Unknown Status in openSUSE: Confirmed Bug description: In New Ubuntu 13.04 the network connections crash on 13.04 in cable Ethernet connection. The connection works for about 2-3 minutes, and after "die". Unplug/plug the cable sometimes helps to re-work the connection manager. I suppose the problem in the Atheros drivers In Ubuntu 12.10 the network works perfectly. The bug is confermed by many other users. The problem seems to be more present when using static IP (type of network configuration : manual) WIFI works perfectly (Card is Atheros too) My network Ethernet card is ATHEROS AR8152 command : lshw -C network -network description: Wireless interface product: AR9285 Wireless Network Adapter (PCI-Express) vendor: Atheros Communications Inc. physical id: 0 bus info: pci@0000:0c:00.0 logical name: wlan0 version: 01 serial: 90:a4:de:4a:7a:28 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath9k driverversion=3.8.0-19-generic firmware=N/A ip=10.173.129.175 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn resources: irq:17 memory:f69f0000-f69fffff *-network description: Ethernet interface product: AR8152 v2.0 Fast Ethernet vendor: Qualcomm Atheros physical id: 0 bus info: pci@0000:09:00.0 logical name: eth0 version: c1 serial: 78:2b:cb:f0:56:35 capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=atl1c driverversion=1.0.1.1-NAPI latency=0 link=no multicast=yes port=twisted pair resources: irq:47 memory:f68c0000-f68fffff ioport:df00(size=128) Without this 13.04 is unuseful. Thanx Stefano Pecchenino [email protected] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CRDA: country IT: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Wed May 1 10:23:15 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-30 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) IpRoute: default via 10.173.128.1 dev wlan0 proto static 10.173.128.0/20 dev wlan0 proto kernel scope link src 10.173.129.175 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH FASTWEB-PEKKE e24676af-073a-4071-8e25-a3dc1c022421 802-11-wireless 1367396634 mer 01 mag 2013 10:23:54 CEST yes no /org/freedesktop/NetworkManager/Settings/1 ADSL Ufficio 8db2aff6-e740-4f53-81de-e260b2c883db 802-3-ethernet 0 never no no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0 connected enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1175091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
