[NOTES:
* In this cycle the regressions reported by e-mail will only be put into the
Bugzilla 1 week after they have been submitted, if not fixed in the
meantime. The reason is that some regressions are fixed in less than a
week time and there's no point listing them. [We also hope
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.33. 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.33. 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.33. 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.33. 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.33. 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.33. 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.33. 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.33. 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.33. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
[NOTE:
Well, we seem to have two reports that are almost 2 months old and with
patches. Somebody care to push those patches to Linus or say why they
are invalid, pretty please?]
This message contains a list of some post-2.6.32 regressions introduced before
2.6.33, for which there are no fixes
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. 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.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. Please verify if it still should
be listed and let the tracking team
On Sun, Mar 21, 2010 at 09:30:51PM +0100, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and
On Monday 22 March 2010, Wolfram Sang wrote:
On Sun, Mar 21, 2010 at 09:30:51PM +0100, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.32 and 2.6.33.
The following bug entry is on the current list of known
It hasn't recurred since I filed the bug report (6 days ago), but as far
as I know it is still a problem.
I'm reasonably sure, but not 100%, that it's a regression: I might have
observed it on Debian's 2.6.32 kernel. If so, it happened much less often.
--
To unsubscribe from this list: send the
On Monday 22 March 2010, Sanjoy Mahajan wrote:
It hasn't recurred since I filed the bug report (6 days ago), but as far
as I know it is still a problem.
I'm reasonably sure, but not 100%, that it's a regression: I might have
observed it on Debian's 2.6.32 kernel. If so, it happened much
On Sun, 21 Mar 2010, Rafael J. Wysocki wrote:
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33. Please verify if it still should
be listed and let the tracking team know (either way).
Bug-Entry :
On Sun, 2010-03-21 at 21:30 +0100, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.32 and 2.6.33.
The following bug entry is on the current list of known regressions
introduced between 2.6.32 and 2.6.33.
53 matches
Mail list logo