Bug 330181

Andy, I'm assuming this is already queued up for inclusion in 5.2?

Yes it will get in there.  I'm doing backports and updating my people page on a
more regular basis now, but it will get in there before we ship.

The following proposed patch will be automatically included in the wholesale
RHEL 5.2 tg3 update as stated in bug 253344.

This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

*sigh* Andy to tell you the truth *noone* knows the process which is why
everyone is always provides different answers.

Here's my take:

1 - the z-stream patch and 5.2 patch *should be* identical.  The z-stream is
monkey work and taking subsets of patches will confuse those monkeys and cause
breakage later

2 - the developer, aka Andy, should *never, ever* care about if a patch he posts
is for a z-stream or not.  All developer patches should go against the current
rhel stream, ie 5.2.  This keeps everything simple and developer focused on
fixing issues, *not* process

3 - the z-stream machinery should be automated such that once a 5.2 bz is deemed
a candidate, it should be cloned and the *exact* patch (barring backport tweaks)
is copied over

So according to my take on the whole z-stream thing, bug 253344 is wrong because
it defeats rule #1.  And this bug 330181 *has* to be a 5.2 otherwise it defeats
rule #2 and #3 (the developer knowing about a z-stream bz and the fact people
are commenting on what is essentially an automated copy of a bz). 

Therefore I will commit this patch using this bz and the z-stream folks will
have to use a *different* bz.

These are my opinions and I'm sticking with them.  :-p

Cheers,
Don

(In reply to comment #21)
> *sigh* Andy to tell you the truth *noone* knows the process which is why
> everyone is always provides different answers.
> 
> Here's my take:
> 
> 1 - the z-stream patch and 5.2 patch *should be* identical.  The z-stream is
> monkey work and taking subsets of patches will confuse those monkeys and cause
> breakage later
> 
> 2 - the developer, aka Andy, should *never, ever* care about if a patch he posts
> is for a z-stream or not.  All developer patches should go against the current
> rhel stream, ie 5.2.  This keeps everything simple and developer focused on
> fixing issues, *not* process
> 
> 3 - the z-stream machinery should be automated such that once a 5.2 bz is deemed
> a candidate, it should be cloned and the *exact* patch (barring backport tweaks)
> is copied over
> 
> So according to my take on the whole z-stream thing, bug 253344 is wrong because
> it defeats rule #1.  And this bug 330181 *has* to be a 5.2 otherwise it defeats
> rule #2 and #3 (the developer knowing about a z-stream bz and the fact people
> are commenting on what is essentially an automated copy of a bz). 
> 
> Therefore I will commit this patch using this bz and the z-stream folks will
> have to use a *different* bz.
> 
> These are my opinions and I'm sticking with them.  :-p
> 
> Cheers,
> Don

ACK  :-)

in 2.6.18-58.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Greetings Red Hat Partner,

A fix for this issue should be included in the latest packages contained in
RHEL5.2-Snapshot1--available now on partners.redhat.com.  

Please test and confirm that your issue is fixed.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to ASSIGNED.

If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and I will update bugzilla for you.  If you
need assistance accessing ftp://partners.redhat.com, please contact your Partner
Manager.

Thank you

Greetings Red Hat Partner,

A fix for this issue should be included in the latest packages contained in
RHEL5.2-Snapshot3--available now on partners.redhat.com.  

Please test and confirm that your issue is fixed.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to ASSIGNED.

If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and I will update bugzilla for you.  If you
need assistance accessing ftp://partners.redhat.com, please contact your Partner
Manager.

Thank you

Greetings Red Hat Partner,

A fix for this issue should be included in the latest packages contained in
RHEL5.2-Snapshot4--available now on partners.redhat.com.  

Please test and confirm that your issue is fixed.

After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)

If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to ASSIGNED.

If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and I will update bugzilla for you.  If you
need assistance accessing ftp://partners.redhat.com, please contact your Partner
Manager.

Thank you

Fix verified by first reproducing the issue using tg3 v3.71b
Issue no longer seen w/ below configuration:
-tg3 v3.86 bundled in RHEL 5.2 Beta 20080402-i386
-Compaq D500 w/ 845G/ICH4

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0314.html