Bug 829251

Summary:	HP NC373i (Broadcom BCM5708) problems after update
Product:	[Fedora] Fedora	Reporter:	birger <b1r63r>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17	CC:	gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ethernet tg3 first=3.3.7 regression-from=3.3.4
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-12 16:32:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description birger 2012-06-06 10:19:31 UTC

Description of problem:
After installation of F17 from the live image on HP DL380 G5 the em1 nic worked fine. The first thing I did was to du a yum update and reboot. em1 still comes up, but i cannot ping anything. tcpdump just seems to hang. killing tcpdump takes a looong time. a typical result is that it captures 2 packets while dropping ~1500. Booting the old kernel doesn't help. Even removing the old kernel and running grub2-mkconfig doesn't have any effect.


Version-Release number of selected component (if applicable):
the first install with kernel 3.3.4-5 worked fine. the update to 3.3.7-1 (along with a lot of other updates) broke it.

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
The server is updated with the latest firmware dvd image from HP.

Comment 1 birger 2012-06-06 10:44:01 UTC

this server also has a card with dual intel 82571EB ethernet ports. the intel ports work fine, so i have a working workaround :-)

Comment 2 birger 2012-06-07 06:56:23 UTC

Correction: "Even removing the old kernel and running grub2-mkconfig doesn't have any effect" is wrong. I meant removing the *new* kernel.

Comment 3 Josh Boyer 2012-07-05 18:44:43 UTC

Is this still happening with the 3.4.x kernel updates?