On Thu 2009-04-16 23:45:04, 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.29. Please verify if it still should be listed and let me know
* Rafael J. Wysocki r...@sisk.pl 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.29. Please verify if it still should be listed and let me know
(either way).
Alan Jenkins wrote:
Alan Jenkins wrote:
Bjorn Helgaas wrote:
On Tuesday 14 April 2009 09:17:28 am Arjan van de Ven wrote:
On Tue, 14 Apr 2009 08:59:01 -0600
Bjorn Helgaas bjorn.helg...@hp.com wrote:
I can't help with the real problem
On Sunday 26 April 2009, David Miller wrote:
From: Rafael J. Wysocki r...@sisk.pl
Date: Sat, 25 Apr 2009 21:31:45 +0200 (CEST)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13111
Subject : Linux 2.6.30-rc1 tg3 endian issues with MAC addresses
on BCM5701
On Sunday 26 April 2009, Jeff Chua wrote:
On Sun, Apr 26, 2009 at 3:31 AM, Rafael J. Wysocki r...@sisk.pl wrote:
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13118
Subject : iptables very slow after commit
784544739a25c30637397ace5489eeb6e15d7d49
Submitter
On Sunday 26 April 2009, Ingo Molnar wrote:
* Rafael J. Wysocki r...@sisk.pl 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.29. Please verify if it still
On Sunday 26 April 2009, Justin Madru wrote:
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.29. Please verify if it still should be listed
On Saturday 25 April 2009, Pavel Machek wrote:
On Thu 2009-04-16 23:45:04, 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.29. Please verify
[NOTES:
* The number of regressions related to DRI is alarming, especially that for
some of the reporters have identified the bad commits.
* I have closed some bugs where there was no activity.]
This message contains a list of some regressions introduced between 2.6.28 and
2.6.29, for which
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. Please verify if it still should
be listed and let me know (either
Handled-By : Andi Kleen a...@firstfloor.org
Patch : http://patchwork.kernel.org/patch/19330/
http://patchwork.kernel.org/patch/19406/
This patch regresses on older GCC versions
I don't think that's correct. There's been a demonstration that some gcc
versions
On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between
2009/4/25 Rafael J. Wysocki r...@sisk.pl:
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.29. Please verify if it still should be listed and let me know
(either way).
* 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. Please verify if it
On Sun, 26 Apr 2009 11:31:03 +0200
Ingo Molnar mi...@elte.hu wrote:
* Rafael J. Wysocki r...@sisk.pl 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.29.
On Sunday 26 April 2009, Angel wrote:
On Sun, 26 Apr 2009 11:46:26 +0200 (CEST)
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.28 and 2.6.29.
The following bug entry is on the current list
On Sunday 26 April 2009, Mathieu Desnoyers wrote:
* 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.28 and 2.6.29.
The following bug entry is on the current list of known regressions
On Sunday 26 April 2009, Alexander Beregalov wrote:
2009/4/25 Rafael J. Wysocki r...@sisk.pl:
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.29. Please verify if it
On Sun, 26 Apr 2009, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.28 and 2.6.29.
The following bug entry is on the current list of known regressions
introduced between 2.6.28 and 2.6.29. Please verify if
Hello,
yes, this bug entry should be listed. This bug prevents people from
using live-cd's or testing the 2.6.29 (if they know about this bug...).
Am Sonntag, den 26.04.2009, 11:46 +0200 schrieb Rafael J. Wysocki:
This message has been generated automatically as a part of a report
of
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.29. Please verify if it still should be listed and let me know
(either way).
This is still
On Sunday 26 April 2009, Alan Stern wrote:
On Sat, 25 Apr 2009, 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.29. Please verify if it
On Sunday 26 April 2009, Nico Schottelius wrote:
Rafael J. Wysocki [Sun, Apr 26, 2009 at 11:46:25AM +0200]:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.28 and 2.6.29.
Sure, still broken. For some version it works, for most newer
On Sunday 26 April 2009, Daniel Bierstedt wrote:
Hello,
yes, this bug entry should be listed. This bug prevents people from
using live-cd's or testing the 2.6.29 (if they know about this bug...).
Thanks for the update.
Rafael
--
To unsubscribe from this list: send the line unsubscribe
50 matches
Mail list logo
