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

Bug#648397: marked as done (firmware-bnx2: alloc errors in kernel log and weird ip issue)

Your message dated Fri, 11 Nov 2011 07:11:26 +0000
with message-id <1320995486.18929.201.camel@deadeye>
and subject line Re: Bug#648397: firmware-bnx2: alloc errors in kernel log and weird ip issue
has caused the Debian Bug report #648397,
regarding firmware-bnx2: alloc errors in kernel log and weird ip issue
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.)


-- 
648397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648397
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-bnx2
Version: 0.33
Severity: normal


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.

auto eth0
iface eth0 inet static
	address 192.168.1.90
	netmask 255.255.255.0
	allow-hotplug eth0
auto eth1
iface eth1 inet static
        address 111.111.111.122
        netmask 255.255.255.248
	gateway 111.111.111.121

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

--- End Message ---
--- Begin Message --- 
On Thu, 2011-11-10 at 22:33 -0600, grmrgecko wrote:
> Package: firmware-bnx2
> Version: 0.33
> Severity: normal
> 
> 
> 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.
[...]

No, not a bug.

Ask the debian-user list how to set up your routing.

Ben.

-- 
Ben Hutchings
The program is absolutely right; therefore, the computer must be wrong.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: