On Sun, Jun 20, 2010 at 3:11 PM, Rafael J. Wysocki <[email protected]> wrote:
> This message contains a list of some regressions from 2.6.34,
> for which there are no fixes in the mainline known to the tracking team.
> If any of them have been fixed already, please let us know.
>
> If you know of any other unresolved regressions from 2.6.34, please let us
> know either and we'll add them to the list. Also, please let us know
> if any of the entries below are invalid.
>
> Each entry from the list will be sent additionally in an automatic reply
> to this message with CCs to the people involved in reporting and handling
> the issue.
>
>
> Listed regressions statistics:
>
> Date Total Pending Unresolved
> ----------------------------------------
> 2010-06-21 46 37 26
> 2010-06-09 15 13 10
Leaving only the 802.11, and Bluetooth (none) ones:
> Unresolved regressions
> ----------------------
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16235
> Subject : [REGRESSION] [IWL3945] Broadcast is broken?
> Submitter : Maciej Rutecki <[email protected]>
> Date : 2010-06-14 17:24 (7 days old)
> Message-ID : <[email protected]>
> References : http://marc.info/?l=linux-kernel&m=127653628301300&w=2
As noted by Maxim, the fix is in some Intel tree, but not upstream yet
(if so why ?)
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16232
> Subject : 2.6.35-rc3 - WARNING:iwl_set_dynamic_key
> Submitter : Mario Guenterberg <[email protected]>
> Date : 2010-06-14 11:55 (7 days old)
> Message-ID : <20100614115510.GA7904@guenti-laptop>
> References : http://marc.info/?l=linux-kernel&m=127651695627147&w=2
Rafael, this one actually has a supplied patch by Reinette and she's
waiting on the user.
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16201
> Subject : SIOCGIWFREQ ioctl fails to get frequency info
> Submitter : nuh <[email protected]>
> Date : 2010-06-14 10:45 (7 days old)
John is waiting on some user sample code to reproduce.
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16176
> Subject : Microcode errors with iwl3945
> Submitter : Steinar H. Gunderson <[email protected]>
> Date : 2010-06-10 19:28 (11 days old)
One issue replaced with another, but the microcode issues seems to be
fixed now on rc3.
> Regressions with patches
> ------------------------
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16196
> Subject : 2.6.35-rc2-git1 - WARNING: at net/wireless/mlme.c:341 cfg80211_send_assoc_timeout+0x107/0x11e [cfg80211]()
> Submitter : Miles Lane <[email protected]>
> Date : 2010-06-07 19:06 (14 days old)
> Message-ID : <[email protected]>
> References : http://marc.info/?l=linux-kernel&m=127593758817428&w=2
> Handled-By : Johannes Berg <[email protected]>
> Patch : http://marc.info/?l=linux-wireless&m=127608099427316&w=2
Patch confirmed to work.
> For details, please visit the bug entries and follow the links given in
> references.
>
> As you can see, there is a Bugzilla entry for each of the listed regressions.
> There also is a Bugzilla entry used for tracking the regressions from 2.6.34,
> unresolved as well as resolved, at:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=16055
>
> Please let the tracking team know if there are any Bugzilla entries that
> should be added to the list in there.
>
> Thanks!
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
On Mon, 2010-06-21 at 11:49 -0700, Luis R. Rodriguez wrote:
> On Sun, Jun 20, 2010 at 3:11 PM, Rafael J. Wysocki <[email protected]> wrote:
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16235
> > Subject : [REGRESSION] [IWL3945] Broadcast is broken?
> > Submitter : Maciej Rutecki <[email protected]>
> > Date : 2010-06-14 17:24 (7 days old)
> > Message-ID : <[email protected]>
> > References : http://marc.info/?l=linux-kernel&m=127653628301300&w=2
>
> As noted by Maxim, the fix is in some Intel tree, but not upstream yet
> (if so why ?)
The patch was merged into our tree a few days ago. It will be sent
upstream after our validation passes, which should be by the end of this
week. The repo in which it was merged is accessible to all if the patch
is needed sooner - a link is now included in that bug report.
Reinette