Soeren Sonnenburg wrote:
On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
On Tue, Nov 17, 2009 at 05:06:47AM +0100, Soeren Sonnenburg wrote:
On Mon, 2009-11-16 at 20:01 -0800, Dmitry Torokhov wrote:
On Tue, Nov 17, 2009 at 03:59:03AM +0100, Soeren Sonnenburg wrote:
On Sat, 2009-11-21 at 09:56 +0100, Soeren Sonnenburg wrote:
On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
On Tue, Nov 17, 2009 at 05:06:47AM +0100, Soeren Sonnenburg wrote:
On Mon, 2009-11-16 at 20:01 -0800, Dmitry Torokhov wrote:
On Tue, Nov 17, 2009 at 03:59:03AM +0100,
Soeren Sonnenburg wrote:
On Sat, 2009-11-21 at 09:56 +0100, Soeren Sonnenburg wrote:
On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
On Tue, Nov 17, 2009 at 05:06:47AM +0100, Soeren Sonnenburg wrote:
On Mon, 2009-11-16 at 20:01 -0800, Dmitry Torokhov wrote:
On Sat, 2009-11-21 at 01:58 -0800, Justin P. Mattock wrote:
Soeren Sonnenburg wrote:
On Sat, 2009-11-21 at 09:56 +0100, Soeren Sonnenburg wrote:
On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
On Tue, Nov 17, 2009 at 05:06:47AM +0100, Soeren Sonnenburg wrote:
Soeren Sonnenburg wrote:
On Sat, 2009-11-21 at 01:58 -0800, Justin P. Mattock wrote:
Soeren Sonnenburg wrote:
On Sat, 2009-11-21 at 09:56 +0100, Soeren Sonnenburg wrote:
On Wed, 2009-11-18 at 18:59 -0800, Dmitry Torokhov wrote:
On Tue, Nov 17, 2009 at 05:06:47AM
Hi everyone,
(as usual, please cc, thanks)
not that I ask for reopen ..
On Mo, 16 Nov 2009, Rafael J. Wysocki wrote:
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14618
Subject : OOM killer, page fault
Well, it hit with OOM although I had 60+% in cache.
I cached
Rafael J. Wysocki wrote:
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=3D14256
Subject
This message contains a list of some regressions from 2.6.31, for which there
are no fixes in the mainline I know of. If any of them have been fixed already,
please let me know.
If you know of any other unresolved regressions from 2.6.31, please let me know
either and I'll add them to the list.
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message has been generated automatically as a part of a report
of recent regressions.
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry :
This message contains a list of some regressions introduced between 2.6.30 and
2.6.31, for which there are no fixes in the mainline I know of. If any of them
have been fixed already, please let me know.
If you know of any other unresolved regressions introduced between 2.6.30
and 2.6.31, please
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed and let me know (either
Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known regressions
introduced between 2.6.30 and 2.6.31. Please verify if it still should
be listed
No, it is not resolved.
Attachments have been recently added to the bug and it would be highly
desirable for whoever introduced those regressions in 2.6.31 to
examine them and participate in resolving the issue. Alternately,
reverting those ACL caching changes to 2.6.30 status would be equally
On Sat, 21 Nov 2009 09:38:22 -0800
Justin P. Mattock justinmatt...@gmail.com wrote:
Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current list of known
On Sat, 21 Nov 2009, Rafael J. Wysocki wrote:
The following bug entry is on the current list of known regressions
from 2.6.31. Please verify if it still should be listed and let me know
(either way).
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14597
Subject :
Kristoffer Ericson wrote:
On Sat, 21 Nov 2009 09:38:22 -0800
Justin P. Mattockjustinmatt...@gmail.com wrote:
Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is
On Saturday 21 November 2009, Niel Lambrechts wrote:
Hi Rafael,
On 21 Nov 2009, at 5:02 PM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.30 and 2.6.31.
The following bug entry is on the current
71 matches
Mail list logo
