Linux

Bug #446146
Comment #162

Comment 162 for bug 446146

Revision history for this message

Andy Whitcroft (apw) wrote on 2009-11-06:

#162

To reiterate, the initial fix for the E169 issue is committed (only). It is not Fix Released, when it _is_ released it will be switched to that state automatically by the launchpad janitor as the packages are put into the archive. Please do not confuse people further by moving it Fix Released. Although there is much talk of other modems on this bug report, the fix tied to this bug number is currently only known for certain to fix E169 modems. When this bug goes Fix Released that will only confirm that _that_ one fix has released.

We need therefore to confirm specifically whether the fixes we are proposing to release fix all of the modem or if more action is required. There are unconfirmed reports that the fix for this bug also fixes the E220 modems and E629 modems. There is also a second fix coming in the 2.6.31.5 update which is reported to help more of these devices. To help confirm these reports and ensure will have all of these covered I have made TWO test kernels:

1) 2.6.31-16.50lp446146apw5 -- this contains both of the fixes above and represents what we are currrently planning on releasing as an update,

2) 2.6.31-16.50lp446146apw10 -- this contains an additional patch revert as suggested by BenH, should the previous kernel not work for you.

This bug has become very confused so we need testing from those who can test, plus very clear testing and reporting on those tests to ensure we are releasing the right fixes. So could those who are able to test these kernels, first test the *apw5* kernel at the URL below, please report your testing on that kernel stating clearly the Huawei model number you are testing with, and attaching the dmesg output to your report:

http://people.canonical.com/~apw/lp446146-karmic/test1/

If and ONLY if that kernel does not work for you could you then test the second *apw10* kernel and report on that one too, again reporting the Huawei model number you are testing and attaching the dmesg output to your report:

http://people.canonical.com/~apw/lp446146-karmic/test2/

To reiterate, the initial fix for the E169 issue is committed (only).  It is not Fix Released, when it _is_ released it will be switched to that state automatically by the launchpad janitor as the packages are put into the archive.  Please do not confuse people further by moving it Fix Released.  Although there is much talk of other modems on this bug report, the fix tied to this bug number is currently only known for certain to fix E169 modems.  When this bug goes Fix Released that will only confirm that _that_ one fix has released.

We need therefore to confirm specifically whether the fixes we are proposing to release fix all of the modem or if more action is required. There are unconfirmed reports that the fix for this bug also fixes the E220 modems and E629 modems.  There is also a second fix coming in the 2.6.31.5 update which is reported to help more of these devices.  To help confirm these reports and ensure will have all of these covered I have made TWO test kernels:

1) 2.6.31-16.50lp446146apw5 -- this contains both of the fixes above and represents what we are currrently planning on releasing as an update,

2) 2.6.31-16.50lp446146apw10 -- this contains an additional patch revert as suggested by BenH, should the previous kernel not work for you.

This bug has become very confused so we need testing from those who can test, plus very clear testing and reporting on those tests to ensure we are releasing the right fixes.  So could those who are able to test these kernels, first test the *apw5* kernel at the URL below, please report your testing on that kernel stating clearly the Huawei model number you are testing with, and attaching the dmesg output to your report:

http://people.canonical.com/~apw/lp446146-karmic/test1/

http://people.canonical.com/~apw/lp446146-karmic/test2/