[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688703
Ti
Peter Matulis / Ryan Blazecka, the potential fix commit noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/688703/comments/11
is available for Lucid as per http://kernel.ubuntu.com/git?p=ubuntu
/ubuntu-lucid.git;a=commit;h=6151b3d435feeeae7487032fcd5c8c7f281ba05c .
When you updated to th
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688703
Title:
[lucid] netxen_nic driver and ethernet bonding broken at boot time
To manage notifications about this bug go
@Joseph
Not me personally, nor professionally, but I did want to keep this one
open because I *thought* I was getting access to the appropriate
hardware. So this is the blocker for me right now (ability to test).
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
@Peter
Can you confirm if this is still an issue for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688703
Title:
[lucid] netxen_nic driver and ethernet bonding broken at boot time
To manage n
Sorry, I forgot to mention, issue is the same but I'm running Debian Squeeze
with that kernel.
Andy Whitcroft's advise solved it for me (at least partly). It seemed more than
reasonable to report back here..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Well, the main issue I can see is that I would have no clue where that
kernel comes from. The main version number indicates Lucid (10.04). But
then the official kernel package released as 2.6.32-21 and there is no
-xen flavour. So all odds are open...
--
You received this bug notification because
Damn. This just took me 8 hours.
My system is a supermicro H8DGU-F which uses an Intel 82576 Gigabit NIC.
In my case there are two problems.
- Firstly, the igb network driver supplied by the xen kernel
(2.6.32-5-xen-amd64) isn't up-to-date. So I compiled it from source
http://downloadcenter.in
There is some possible race mentioned in the examples/readme of
ifenslave. Basically the suggested way is to have no slaves defined in
the bonding definition but add definitions for the slaves. Like
auto bond0
iface bond0 inet static
...
bond-slaves none
...
auto eth0
iface eth0 inet manual
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688703
Title:
[lucid] netxen_nic driver and ethernet bonding broken at boot time
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I tried the new kernel, using the commandline that Pete posted. The
problem was not fixed by that kernel. In fact, it was arguably made
worse, as on that kernel, even a manual restart of networking does not
get the network to work. I am attaching a dmesg log of the new kernel's
boot.
When I manual
@Ryan,
You can download the kernel image from the URL that apw gave you and you
can install with:
sudo dpkg -i linux-
image-2.6.32-27-server_2.6.32-27.49lp688703v201012201823_amd64.deb
Then you can hold down the shift key on reboot which will bring up the
grub menu then you can select the test k
Here [1] is the dmesg output for the manual restart of networking
(running "sudo /etc/init.d/networking restart").
Triggering the bonding driver to load earlier in boot did not fix
things. I added "bonding" to /etc/modules, and restarted the system.
Networking still failed to initialize correctly.
It does sound a little like a race condition. Probabally in the
initialisation order or timing of configuration of the bonding driver.
Some of the messages imply that actions are being done in the wrong
order:
[ 6.405552] bonding: bond0: doing slave updates when interface is
down.
First, I se
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2:
ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 10.04
15 matches
Mail list logo
