This message contains a list of some regressions from 2.6.27, 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.27, 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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.27. 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 regressions introduced between 2.6.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. Please verify if it still should
be listed and let me know (either
This message contains a list of some regressions introduced between 2.6.26 and
2.6.27, 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.26
and 2.6.27, please
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. 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.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. Please verify if it still should
be listed and let me know (either
how can i verify this?
yes i think so [now i'm using the 2.6.28, i dont' have the freeze but
the acpi get the same errors;
if you want say me what tests i should try
--
To unsubscribe from this list: send the line unsubscribe kernel-testers in
the body of a message to [EMAIL PROTECTED]
More
Rafael J. Wysocki wrote at LKML:
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.27. Please verify if it still should be listed and let me know
(either way).
Yes, it is
On Sun, Nov 02, 2008 at 05:07:05PM +0100, Rafael J. Wysocki wrote:
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.27. Please verify if it still should be listed and let
From: Rafael J. Wysocki [EMAIL PROTECTED]
Date: Sun, 2 Nov 2008 17:07:10 +0100 (CET)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11940
Subject : Unable to handle kernel paging request at
iov_iter_copy_from_user_atomic
Submitter : Alexander Beregalov [EMAIL
On Sunday, 2 of November 2008, David Miller wrote:
From: Rafael J. Wysocki [EMAIL PROTECTED]
Date: Sun, 2 Nov 2008 17:07:10 +0100 (CET)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11940
Subject : Unable to handle kernel paging request at
On Sun, Nov 2, 2008 at 5:07 PM, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
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.27. Please verify if it still should be listed
On Sun, Nov 02, 2008 at 05:07:09PM +0100, Rafael J. Wysocki wrote:
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.27. Please verify if it still should be listed and let
On Sun, Nov 02, 2008 at 05:07:06PM +0100, Rafael J. Wysocki wrote:
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.27. Please verify if it still should be listed and let
On Sunday, 2 of November 2008, Vegard Nossum wrote:
On Sun, Nov 2, 2008 at 5:07 PM, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
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
On Sunday, 2 of November 2008, Vegard Nossum wrote:
On Sun, Nov 2, 2008 at 5:07 PM, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
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
Rafael J. Wysocki writes:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced between 2.6.26 and 2.6.27. Please verify if it still should
be
On Sunday, 2 of November 2008, Paul Mackerras wrote:
Rafael J. Wysocki writes:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.26 and 2.6.27.
The following bug entry is on the current list of known regressions
introduced
On Sunday, 2 of November 2008, Carlos R. Mafra wrote:
On Sun 2.Nov'08 at 17:07:01 +0100, Rafael J. Wysocki wrote:
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.27.
[Rafael J. Wysocki - Sun, Nov 02, 2008 at 05:49:34PM +0100]
| This message has been generated automatically as a part of a report
| of regressions introduced between 2.6.26 and 2.6.27.
|
| The following bug entry is on the current list of known regressions
| introduced between 2.6.26 and 2.6.27.
68 matches
Mail list logo