[NOTE:
I have one request for whoever works on fixing the listed regressions. While
your work is highly appreciated anyway, if you have a patch fixing a listed
regression or you know of a commit fixing a listed regression, please drop
a notice into the corresponding Bugzilla entry. This will
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.38. 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.38. 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.38. 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.38. 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.38. 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.38. 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.38. 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.38. 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.38. 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.38. 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.38. 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.38. 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.38. 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.38. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
This message contains a list of some post-2.6.37 regressions introduced before
2.6.38, 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 post-2.6.37 regressions, please let us
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. Please verify if it still should
be listed and let the tracking team
I think we had all assumed that this was the MD problem that should
have been fixed in rc4 (the symptoms matched), but I don't think we
got any confirmation from Bart on that.
Bart? Does the problem still persist in current -git?
Linus
On Sat, Apr 30, 2011 at 12:42 PM, Rafael
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. Please verify if it still should
be listed and let the tracking team
On Sat, Apr 30, 2011 at 12:42 PM, Rafael J. Wysocki r...@sisk.pl wrote:
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=34012
Subject : 2.6.39-rc4+: oom-killer busy killing tasks
Submitter : Christian Kujau li...@nerdbynature.de
Date : 2011-04-22 1:57 (9
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. 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.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. Please verify if it still should
be listed and let the tracking team
On 04/30/2011 01:17 PM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. Please verify if
On 04/30/2011 01:17 PM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.37 and 2.6.38.
The following bug entry is on the current list of known regressions
introduced between 2.6.37 and 2.6.38. Please verify if
47 matches
Mail list logo
