On Sun, Sep 12, 2010 at 09:08:42PM +0200, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and
This message contains a list of some regressions from 2.6.35,
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.35, 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.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
Paul E. McKenney wrote:
On Sun, Sep 12, 2010 at 09:08:42PM +0200, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
Hi Rafael,
can you please add the following, Thanks in advance.
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18872
Subject : Radeon KMS r100 and STR problems
Submitter : Richard Mittendorfer del...@gmx.net
Date: 2010-09-17 18:26 (4 days old)
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.35. 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.35. 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.35. 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.35. 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.35. 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.35. 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.35. 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.35. 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.35. 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.35. 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.35. 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.35. 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.35. 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.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry :
On Mon, Sep 20, 2010 at 09:20:27PM +0200, Rolf Eike Beer wrote:
Paul E. McKenney wrote:
On Sun, Sep 12, 2010 at 09:08:42PM +0200, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The
[Added kernel-testers and others who have reported problems with this board]
On Friday, September 17, 2010 04:53:52 pm Bjorn Helgaas wrote:
Simon Arlott reported that 2.6.35.4 hangs on his GA-MA69VM-S2 690V:
http://lkml.org/lkml/2010/9/9/92
This is a regression, and I'd like to fix it
[Trimming the CC list.]
On Monday, September 20, 2010, Sedat Dilek wrote:
Hi Rafael,
can you please add the following, Thanks in advance.
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18872
Subject : Radeon KMS r100 and STR problems
Submitter : Richard
On Monday, September 20, 2010, Thomas Meyer wrote:
Am 20.09.2010 um 21:08 schrieb Rafael J. Wysocki r...@sisk.pl:
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
This message contains a list of some post-2.6.34 regressions introduced before
2.6.35, 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.34 regressions, please let us
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. Please verify if it still should
be listed and let the tracking team
Am 20.09.2010 um 21:08 schrieb Rafael J. Wysocki r...@sisk.pl:
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.35. Please verify if it still should be listed and
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. Please verify if it still should
be listed and let the tracking team
On Monday, September 20, 2010, Nix wrote:
On 20 Sep 2010, Rafael J. Wysocki said:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced
On Monday, September 20, 2010 01:57:17 pm Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and
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.35. Please verify if it still should be listed and let the tracking
team
know (either
Hi Rafael,
On 20 September 2010 20:57, Rafael J. Wysocki r...@sisk.pl wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34
On Monday, September 20, 2010, Bjorn Helgaas wrote:
On Monday, September 20, 2010 01:57:17 pm Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list
On 20 Sep 2010, Rafael J. Wysocki said:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. Please verify if it
On Mon 20-09-10 21:57:17, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. Please verify
On Monday, September 20, 2010, Jan Kara wrote:
On Mon 20-09-10 21:57:17, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
It had been fixed by Tejun already.
commit 477a3c33d1efa0342a74bd02da2e049191993e2c
Author: Tejun Heo t...@kernel.org
Date: Tue Aug 31 10:54:35 2010 +0200
workqueue: fix GCWQ_DISASSOCIATED initialization
init_workqueues() incorrectly marks workqueues for all possible CPUs
On Tuesday, September 21, 2010, caiq...@redhat.com wrote:
It had been fixed by Tejun already.
commit 477a3c33d1efa0342a74bd02da2e049191993e2c
Author: Tejun Heo t...@kernel.org
Date: Tue Aug 31 10:54:35 2010 +0200
workqueue: fix GCWQ_DISASSOCIATED initialization
On Mon, Sep 20, 2010 at 3:19 PM, Sedat Dilek sedat.di...@googlemail.com wrote:
Hi Rafael,
can you please add the following, Thanks in advance.
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18872
Subject : Radeon KMS r100 and STR problems
Submitter : Richard
60 matches
Mail list logo
