This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Hi Jeremy
I've tested it again with a live image of Lucid Beta 1. Now it's working fine
and stable! So apparently this bug is fixed in the new kernel 2.6.32.
Shall I post more information about it and do you still want me to test it with
an upstream kernel?
Thanks a lot for your work and help.
** Tags removed: needs-kernel-logs
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
Bug in atl2 network driver
https://bugs.launchpad.net/bugs/442407
You received this bug notification because you are a
Hi Simon,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/releases/ .
If it remains
Update:
It happened again (several times): In the middle of an NX-session the network
connection to the server is suddenly closed. The buggy interface of the server
doesn't respond anymore (no ping no nothing). The only thing that helps
temporary is a reboot of the system. I suppose this atl2
Update:
It happened again (several times): In the middle of an NX-session the network
connection to the server is suddenly closed. The buggy interface of the server
doesn't respond anymore (no ping no nothing). The only thing that helps
temporary is a reboot of the system. I suppose this atl2
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we can't fix it without more information.
Please run the following command which will attach necessary
information:
apport-collect BUGNUMBER
if you are using Karmic Koala (9.10) or newer, or
OK. Hope this helpes.
Update: The disabled ipv6 network function doesn't change the situation,
because the error messages in dmesg are the same (The same thing about
ipv6 duplicate addresses). The part in my first post about eth0: link
is not ready was my fault. The actual dmesg messages that
