On Fri, Jul 23, 2010 at 14:47, 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.34. Please verify if it still should be listed and let
On Fri, Jul 23, 2010 at 1:42 PM, Rafael J. Wysocki wrote:
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16372
> Subject : Regression 2.6.34->2.6.35-rc4: radeaon KMS an RS690 broken
> Submitter : Torsten Kaiser
> Date : 2010-07-11 19:56 (13 days old)
> Mes
On Friday, July 23, 2010, Larry Finger wrote:
> On 07/23/2010 06:42 AM, Rafael J. Wysocki wrote:
> > This message contains a list of some regressions from 2.6.34,
> > 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 k
On Friday, July 23, 2010, Ben Hutchings wrote:
> Another one for you:
>
> http://article.gmane.org/gmane.linux.drivers.mtd/30834
>
> This has no Bugzilla entry; should I submit one?
Yes, please. And please make it block bug #16055.
Rafael
--
To unsubscribe from this list: send the line "unsubs
On Friday, July 23, 2010, Kees Cook wrote:
> Hi Rafael,
>
> On Fri, Jul 23, 2010 at 01:47:30PM +0200, 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
On Friday, July 23, 2010, Tim Gardner wrote:
> On 07/23/2010 01:47 PM, 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.34. Pl
On Friday, July 23, 2010, John W. Linville wrote:
> On Fri, Jul 23, 2010 at 01:47:29PM +0200, 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 regressi
On Friday, July 23, 2010, Dave Chinner wrote:
> On Fri, Jul 23, 2010 at 02:15:54PM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.33 and 2.6.34.
> >
> > The following bug entry is on the current list
On Friday, July 23, 2010, Tim Gardner wrote:
> On 07/23/2010 02:15 PM, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.33 and 2.6.34.
> >
> > The following bug entry is on the current list of known regression
On Friday, July 23, 2010, Bjorn Helgaas wrote:
> On Friday, July 23, 2010 06:15:50 am Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.33 and 2.6.34.
> >
> > The following bug entry is on the current list of
On Friday, July 23, 2010, Thomas Meyer wrote:
> Am Freitag, den 23.07.2010, 14:15 +0200 schrieb Rafael J. Wysocki:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.33 and 2.6.34.
> >
> > The following bug entry is on the current list
On Fri, Jul 23, 2010 at 10:41:43AM -0400, Nick Bowler wrote:
>
> I actually haven't been able to reproduce with kernels since a couple
> weeks ago (still reproducible if I go back to 2.6.35-rc3, though).
> Seems to be fixed somehow, can anyone else confirm?
I'll try to reproduce it over the weeke
On Fri, 23 Jul 2010 19:50:56 +0200
Tino Keitel wrote:
> On Fri, Jul 23, 2010 at 10:33:36 -0700, Jesse Barnes wrote:
>
> [...]
>
> > I think this may actually be an X server bug. 2.6.34 introduced some
>
> Hi,
>
> that seems to be not a kernel issue indeed, as at some point I never
> got this
On Fri, Jul 23, 2010 at 10:33:36 -0700, Jesse Barnes wrote:
[...]
> I think this may actually be an X server bug. 2.6.34 introduced some
Hi,
that seems to be not a kernel issue indeed, as at some point I never
got this hang again. However, I upgraded to new versions of Mesa, DRM,
and also new
On Fri, 23 Jul 2010 14:15:55 +0200 (CEST)
"Rafael J. Wysocki" wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.33 and 2.6.34.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 an
On Fri, 23 Jul 2010 14:15:52 +0200 (CEST)
"Rafael J. Wysocki" wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.33 and 2.6.34.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 an
On Fri, 23 Jul 2010 07:11:34 -0700 (PDT)
Shawn Starr wrote:
>
>
> Still continues. I can however hibernate and resume from hibernation ok.
>
If it works on Fedora, maybe you could get it working with a similar
upstream kernel (same version, same config) and then bisect?
--
Jesse Barnes, Int
On Fri, 23 Jul 2010 13:47:31 +0200 (CEST)
"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.34. Please verify if it still should be
On Fri, Jul 23, 2010 at 01:47:29PM +0200, 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.34. Please verify if it still should be list
On 13:47 Fri 23 Jul , 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.34. Please verify if it still should be listed and let the t
On 07/23/2010 06:42 AM, Rafael J. Wysocki wrote:
This message contains a list of some regressions from 2.6.34,
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.
Bug-Entry : http://bugzilla.kernel.org/show_
On Friday, July 23, 2010 06:15:50 am Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.33 and 2.6.34.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 and 2.6.34.
Still continues. I can however hibernate and resume from hibernation ok.
>- Original Message
>From: Rafael J. Wysocki
>To: Linux Kernel Mailing List
>Cc: Kernel Testers List ; Maciej Rutecki
>Sent: Fri, July 23, 2010 7:47:31 AM
>Subject: [Bug #16311] [REGRESSION][SUSPEND] 2.6.35-rcX
On Fri, Jul 23, 2010 at 02:15:54PM +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.33 and 2.6.34.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 and 2.
On 07/23/2010 06:33 AM, Markus Trippelsdorf wrote:
On Fri, Jul 23, 2010 at 01:47:36PM +0200, 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.3
On Fri, Jul 23, 2010 at 01:47:36PM +0200, 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.34. Please verify if it still should be list
Hi Rafael,
On Fri, Jul 23, 2010 at 01:47:30PM +0200, 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.34. Please verify if it still sh
On 07/23/2010 02:15 PM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it
On 07/23/2010 01:47 PM, 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.34. Please verify if it still should be listed and let the tracking
t
"Rafael J. Wysocki" writes:
> 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.34. Please verify if it still should be listed and let the tracking
> team
> know
Another one for you:
http://article.gmane.org/gmane.linux.drivers.mtd/30834
This has no Bugzilla entry; should I submit one?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note tha
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message contains a list of some post-2.6.33 regressions introduced before
2.6.34, 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.33 regressions, please let us kno
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
This message contains a list of some regressions from 2.6.34,
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.34, please let us
know either and we'll add th
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.34. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
93 matches
Mail list logo
