Bug 355211 - Please include patch for 2.6.21 kernel
Summary: Please include patch for 2.6.21 kernel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: iperf
Version: 7
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gabriel Somlo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-27 14:03 UTC by Jérôme Benoit
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-28 01:12:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jérôme Benoit 2007-10-27 14:03:53 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.8.1.8) Gecko/20071019 Fedora/2.0.0.8-1.fc7 Firefox/2.0.0.8

Description of problem:
See http://dast.nlanr.net/Projects/Iperf2.0/patch-iperf-linux-2.6.21.txt for more information.

Version-Release number of selected component (if applicable):
iperf-2.0.2-3.fc7

How reproducible:
Always


Steps to Reproduce:
1. Run iperf on Fedora 7 up2date
2. Fire top in terminal and watch iperf eating CPU ...
3.

Actual Results:


Expected Results:


Additional info:
Comment 1 Gabriel Somlo 2007-10-28 01:12:17 UTC 
applied patch and rebuilt for F-7, F-8, and devel.
Comment 2 Jérôme Benoit 2007-11-19 17:49:11 UTC 
Hi,

Any chance to have this update pushed anytime soon ?

Cheers.
Comment 3 Gabriel Somlo 2007-11-19 18:26:52 UTC 
sorry, just realized I gotta go through Bodhi to make these really
available to the outside world... So I did that, and the fix should be
available shortly.
Comment 4 Fedora Update System 2007-11-20 17:47:31 UTC 
iperf-2.0.2-4.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 5 Fedora Update System 2007-11-20 17:56:53 UTC 
iperf-2.0.2-4.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.