Ok I have done some more investigation and seems like I found it. I went through syslog in range of 2 minutes before and after bug notice (which I controlled with ping). I did this for 4 times to reduce possibility of something missing.
Really do not know why I did not noticed this earlier, but I think there was too much "<info>" debug messages that I considered it as "normal" obviously: There are never ending cycles about exchanging IPv6 addresses: ---------------------------------------------------------------------------------------------------------------------------- [nm-ip6-manager.c:1340] netlink_notification(): netlink event type 20 [nm-ip6-manager.c:885] process_address_change(): (eth0): address cache size: 6 -> 6: [nm-ip6-manager.c:835] dump_address_change(): (eth0) new address: <IPv6 address 1> [nm-ip6-manager.c:1340] netlink_notification(): netlink event type 20 [nm-ip6-manager.c:885] process_address_change(): (eth0): address cache size: 6 -> 6: [nm-ip6-manager.c:835] dump_address_change(): (eth0) new address: <IPv6 address 2> [nm-ip6-manager.c:1340] netlink_notification(): netlink event type 52 Between that, there are also this messages (in any pattern I could notice): ---------------------------------------------------------------------------------------------------------------------------- [nm-ip6-manager.c:1340] netlink_notification(): netlink event type 24 [nm-ip6-manager.c:1340] netlink_notification(): netlink event type 25 And finally, in time of bug occurs (+/- 5 seconds) there is this particular message: ---------------------------------------------------------------------------------------------------------------------------- [nm-netlink-monitor.c:167] link_msg_handler(): netlink link message: iface idx 3 flags 0x1003 This message just brought me there: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657495 and it seems be related. So I read it and disabled IPv6 in sysctl.conf. All <"info"> debug messages are gone. Will report definitely later if it helped but seems so. This also explains why I did not noticed nothing in Precise, because I remember I disabled IPv6 before this bug has been discovered. Cannot recall reason, but I'm pretty sure. I haven't found this bug on launchpad, but I think description should be modified to reflect this investigation. Thank you for "psychically" force me to check this again, I was about to buy router as a workaround :P ** Bug watch added: Debian Bug tracker #657495 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657495 -- 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/1129251 Title: Ethernet connection - damaged packets Status in “linux” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: New Bug description: Hi, I have serious trouble with Ethernet connection on fresh new install of Raring. Basically, after some time, in scale of minutes to days, it just stops responding. Not messages about disconnect at all, but due to ifconfig the RX packets become damaged (counters dropped, overruns and frame become filled). I know, this type of "random" errors are hard to debug, but I would do almost anything in my capabilities to help to solve this really annoying bug. I consulted it here: http://ubuntuforums.org/showthread.php?t=2116513 but to sum and complete it up: * I have laptop with Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0) and atl1c driver module loaded and associated with it * using Wcid instead of network-manager resolved the problem, but I hate that manager so I have reverted back to network-manager * problem was not present in up-to-date Precise installation * problem persists after purging and reinstalling network-manager * problem persists with usage of Precise stable release up-to-date network-manager* packages (and this fact + report from ifconfig (which can catch that) makes me believe that problem is related with driver and not with network-manager) * network-manager nor atl1c does not provide any debug details in syslog when problem occurs * also tried compile and use other versions of atl1c and also alx (which, as I found out, drops support of older hardware periodically, so did not help at all) from "linux backports" with no luck * mainline kernel did not help, because of missing driver (but I have no problem wit trying to compile and load it, not sure if this could help) * to temporarily resolve issue, driver must be reloaded or connection reset by pulling out and reconnecting cable or restart whole system * while using live session I did not noticed any errors, but to be honest, I would have to run it for about two days to confirm this * wireless connection works flawlessly * tried also with different cables, problem not occurred in Precise and also not occur in Windows operating system, so this is not hardware related So much thanks and feel free to direct me for collecting necessary informations. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-6-generic 3.8.0-6.13 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: budovi 3217 F.... pulseaudio Date: Mon Feb 18 16:59:18 2013 HibernationDevice: RESUME=UUID=79baaf5e-05cb-4c1a-9b68-bec79ad0e3af InstallationDate: Installed on 2013-02-12 (5 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130212) MachineType: Micro-Star INT'L CO., LTD. MS-16Y1 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=6c01485e-7824-43c3-b40b-9c44d150f131 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-6-generic N/A linux-backports-modules-3.8.0-6-generic N/A linux-firmware 1.102 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Y1IMS.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: MS-16Y1 dmi.board.vendor: Micro-Star INT'L CO., LTD. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Micro-Star INT'L CO., LTD. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Y1IMS.300:bd12/26/2011:svnMicro-StarINT'LCO.,LTD.:pnMS-16Y1:pvr1.0:rvnMicro-StarINT'LCO.,LTD.:rnMS-16Y1:rvr1.0:cvnMicro-StarINT'LCO.,LTD.:ct9:cvr1.0: dmi.product.name: MS-16Y1 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star INT'L CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1129251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
