Ubuntu
linux-source-2.6.17 package

Hard lock using BCM5751 (tigon3)

Bug #72790 reported by QuentinHartman
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

Binary package hint: linux-image-2.6.17-10-generic

I have several HP dx5150 desktops. When I have sustained network usage on the onboard NIC ( Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 20) ) for extended periods of time I eventually get a hard freeze. I have confirmed this behavior on at least one other machine, so I'm pretty sure it's not faulty hardware. If I disable the onboard NIC and use another one ( In this case an intel e1000 PCI desktop) it apparently solves the problem. This problem seems to be new to Edgy because I have a number of machines running Dapper which do not seem to have this problem. dmesg and lspci output attached.

Revision history for this message
QuentinHartman (qhartman) wrote :

Here are the attachments

Ben Collins (ben-collins)
Changed in linux-source-2.6.17:
importance: Undecided → High
status: Unconfirmed → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-kernel-team
milestone: edgy-updates → none
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron Alpha series was recently released which contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ .

Also, we will keep this report open against the actively developed kernel bug against 2.6.17 this will be closed. Thanks.

Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.17:
status: Confirmed → Won't Fix
Revision history for this message
QuentinHartman (qhartman) wrote :

I no longer have access to the hardware that was exhibiting this bug. Fixed or not, I can no longer test it.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks for the update Quentin. I'm going to close this report for now since you no longer have the hardware to test with. If anyone does have this hardware and is able to verify, please reopen this report (ie set the Status back to New). Thanks.

Changed in linux:
status: Incomplete → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.