Arch Linux

derelict

Member

Registered: 2006-07-25

Posts: 81

Kernel 2.6.23 bnx2 driver does not properly identify link speed

I recently upgraded to kernel version 2.6.23 and have lost my network connectivity. I cannot get into or out of the box. If I boot with a rescue disk using kernel 2.6.22 then everything works fine. I can ping, ssh, rsync you name it. I haven't changed any config files. Am I missing some obvious change that took place between the old and new kernels? I'll gladly post any relevant info.

The only thing that looks weird so far is that the eth0 shows up as a 100MB connection. It's a gig card plugged into a gig port in a Cisco 6509.

The switch shows the port as up and up and set to Full-duplex, 1000Mb/s.

Booting into kernel 2.6.23 dmesg output shows:

bnx2: eth0 NIC Copper Link is Up, 100 Mbps full duplex

Booting into kernel 2.6.22 dmesg output shows:

bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex

I think the mismatched link speed in kernel 2.6.23 is killing my network connectivity. I'm not sure how to check for other symptoms and I don't know how to fix it.

Anyone familiar with this issue?

Last edited by derelict (2007-11-06 20:08:47)

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: Kernel 2.6.23 bnx2 driver does not properly identify link speed

So, what's your "network connectivity"? Wired? Wireless? Which module? Anything suspicious in dmesg output?

---

1000

derelict

Member

Registered: 2006-07-25

Posts: 81

Re: Kernel 2.6.23 bnx2 driver does not properly identify link speed

I reverted to kernel 2.6.22.9-1 from my pacman cache and everything seems to be working now.
Due to the nature of the problem I'm not sure this is a task for arch developers It's more for kernel developers to know about.

Last edited by derelict (2007-11-06 20:30:31)

derelict

Member

Registered: 2006-07-25

Posts: 81

Re: Kernel 2.6.23 bnx2 driver does not properly identify link speed

Has anyone else experienced this issue? I'm just curious at this point how to approach this issue.
Specifically I've got a BCM5708 chipset for my ethernet controller and I'm not sure of the scope of this bug.
Are other chipsets affected? Should I notify the kernel developers?