Bug#648397: firmware-bnx2: alloc errors in kernel log and weird ip issue
I have played around with configuring a public IP with my T1 provider today and fianlly got it to work. However it does not work externally (outside of the network) after a reboot.
The server I'm using is a Dell PowerEdge and it apparently uses the BNX2 firmware. I have found that I can get the public IP addresses I assigned externally if I were to restart /etc/init.d/networking.
I have took a look at the kernel log and the only thing I see that looks like it could be the problem is as below.
Nov 10 21:18:50 server kernel: [ 28.479518] alloc irq_desc for 115 on node -1
Nov 10 21:18:50 server kernel: [ 28.479521] alloc kstat_irqs on node -1
Nov 10 21:18:50 server kernel: [ 28.479530] bnx2 0000:02:00.0: irq 115 for MSI/MSI-X
This message appeares repeatedly 18 times which brings me to think it is my issue. I have created a workaround init script which depends on network and waits 2 seconds before stopping and
starting the networking service and one other service which does not work after restarting the network until it's restarted.
An example of my network interface configuration is below.
iface eth0 inet static
iface eth1 inet static
I would not know of anything else that would be required to configure another network interface.
So this bugreport is more of a bug with an unkown cause, however I am pretty persistent and will test things out durring the weekend if I receive suggestions.
-- System Information:
Debian Release: 6.0.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
firmware-bnx2 depends on no packages.
firmware-bnx2 recommends no packages.
Versions of packages firmware-bnx2 suggests:
ii initramfs-tools 0.98.8 tools for generating an initramfs
ii linux-image-2.6.32-5-amd64 [l 2.6.32-39 Linux 2.6.32 for 64-bit PCs
-- no debconf information