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
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
[NOTE: This is the last summary report of regressions introduced between
2.6.33 and 2.6.34. Thanks for helping us with tracking these bugs!]
This message contains a list of some post-2.6.33 regressions introduced before
2.6.34, for which there are no fixes in the mainline known to the tracking
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
Rafael J. Wysocki wrote:
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.
Subject : 2.6.35-rc6+: i915: Bisected regression
Submitter : Thomas Meyer tho...@m3y3r.de
Date: Sun, 1 Aug 2010 11:01:00
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team
On Sunday, August 01, 2010, Stefan Richter wrote:
Rafael J. Wysocki wrote:
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.
Subject : 2.6.35-rc6+: i915: Bisected regression
Submitter : Thomas Meyer
On Sun, Aug 1, 2010 at 6:46 AM, Rafael J. Wysocki r...@sisk.pl wrote:
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16400
Subject : 2.6.35-rc5 inconsistent lock state
Submitter : Martin Pirker lkml.collec...@gmail.com
Date: 2010-07-14 20:33 (19 days
On 08/01/2010 08:46 AM, Rafael J. Wysocki 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
On Sunday, August 01, 2010, Linus Torvalds wrote:
On Sun, Aug 1, 2010 at 6:46 AM, Rafael J. Wysocki r...@sisk.pl wrote:
...
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16369
Subject : Yet another 2.6.35 regression (AGP)?
Submitter : Woody Suwalski
On Sunday, August 01, 2010 07:52:16 am Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and
On 08/01/2010 06:52 AM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.34. Please verify if it still should be listed and let the tracking
52 matches
Mail list logo
