[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#522705: marked as done ([atl2] network dies after a half-hour on Eee PC 701)



Your message dated Tue, 7 Apr 2009 14:58:07 +0200
with message-id <20090407125807.GJ4442@stro.at>
and subject line Re: [atl2] network dies after a half-hour on Eee PC 701
has caused the Debian Bug report #522705,
regarding [atl2] network dies after a half-hour on Eee PC 701
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
522705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522705
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.29-1-686
Version: 2.6.29-1
Severity: normal

I'm using an Eee PC 701, which has a wired interface:

    03:00.0 Ethernet controller: Attansic Technology Corp. L2 100 Mbit Ethernet Adapter (rev a0)

This has worked fine with previous kernel versions.  After upgrading
to .29, I find that after a few deciminutes the network stops working
completely.  mtr, for example, can't see packets come or go.

There is nothing reported in dmesg after the initial boot messages
except about the ath5k ("phy0: noise floor calibration timeout") and
snd-hda-intel drivers.

I also tried different cat5 cables and wall points, and manually
assigning a different IP address to the one that DHCP has been giving
me (successfully) for weeks.  Nor does an "ifdown --force eth0 && ifup
eth0" help at all.  The only thing that fixes the wired NIC is to do a
full reboot.

>From memory (I did the test on Friday), mii-tool reported a 100mbit
link even after the failure.  traceroute didn't show anything
interesting either.

As an interim measure I have downgraded back to .26, and this has been
working for twenty-five minutes so far without the NIC dying.

Prior to the failure, on a .29 kernel, "mtr google.com.au" reported a
40% to 60% packet loss to one of the internal routers in the office,
192.168.2.254.  That host was the second hop.  Neither the first hop
(another internal router) nor the later hops (at the ISP or on
internet) had such packet loss.

This problem also first manifested after a large storm, which knocked
out some of our routers but not the Eee PC.  I initially thought that
this storm had caused a physical problem in the device, but 1)
rebooting all our routers and switches didn't help; and 2) using a .26
kernel seems to make the problem go away.  Therefore I think the storm
was simply coincidental, it just happened to also be the first time I
used the wired NIC under .29.

-- Package-specific info:

-- System Information:
Debian Release: squeeze/sid
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.29-1-686 depends on:
ii  debconf [debconf-2.0]         1.5.26     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.1     tools for generating an initramfs
ii  module-init-tools             3.7-pre9-1 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.29-1-686 recommends:
ii  libc6-i686                    2.9-6      GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.29-1-686 suggests:
ii  grub                       0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.29           <none>        (no description available)

-- debconf information:
  linux-image-2.6.29-1-686/preinst/abort-overwrite-2.6.29-1-686:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.29-1-686/preinst/overwriting-modules-2.6.29-1-686: true
  linux-image-2.6.29-1-686/preinst/elilo-initrd-2.6.29-1-686: true
  linux-image-2.6.29-1-686/preinst/lilo-initrd-2.6.29-1-686: true
  linux-image-2.6.29-1-686/postinst/depmod-error-2.6.29-1-686: false
  linux-image-2.6.29-1-686/preinst/initrd-2.6.29-1-686:
  linux-image-2.6.29-1-686/preinst/bootloader-initrd-2.6.29-1-686: true
  linux-image-2.6.29-1-686/postinst/bootloader-error-2.6.29-1-686:
  linux-image-2.6.29-1-686/preinst/failed-to-move-modules-2.6.29-1-686:
  linux-image-2.6.29-1-686/prerm/would-invalidate-boot-loader-2.6.29-1-686: true
  linux-image-2.6.29-1-686/postinst/create-kimage-link-2.6.29-1-686: true
  linux-image-2.6.29-1-686/postinst/bootloader-test-error-2.6.29-1-686:
  linux-image-2.6.29-1-686/preinst/abort-install-2.6.29-1-686:
  linux-image-2.6.29-1-686/postinst/depmod-error-initrd-2.6.29-1-686: false
  linux-image-2.6.29-1-686/postinst/old-initrd-link-2.6.29-1-686: true
  linux-image-2.6.29-1-686/prerm/removing-running-kernel-2.6.29-1-686: true
  linux-image-2.6.29-1-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.29-1-686/postinst/old-system-map-link-2.6.29-1-686: true
  linux-image-2.6.29-1-686/postinst/kimage-is-a-directory:
  linux-image-2.6.29-1-686/postinst/old-dir-initrd-link-2.6.29-1-686: true



--- End Message ---
--- Begin Message ---
Version: 2.6.29-2

fixed in latest linux images due to addition of 2.6.29.1

-- 
maks


--- End Message ---

Reply to: