From: Rafael J. Wysocki
I have recently noticed a 55 sec. delay during the "device freeze"
phase of hibernation on my test-bed HP nx6325. Due to the 100%
reproducibility of it I was able to narrow it down to
radeon_suspend_kms() and then it turned out that the delay occured
so
On Friday, June 18, 2010, Rafał Miłecki wrote:
> 2010/6/18 Rafael J. Wysocki :
> > From: Rafael J. Wysocki
>
> Thanks for you recent involvement in radeon driver!
Well, I'm just trying to address the issues I see on my test boxes.
> I can see you used way shorter commit
On Friday, June 18, 2010, Dave Airlie wrote:
> On Fri, 2010-06-18 at 22:21 +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > I have recently noticed a 55 sec. delay during the "device freeze"
> > phase of hibernation on m
On Saturday, June 19, 2010, Dave Airlie wrote:
> On Sat, 2010-06-19 at 01:23 +0200, Rafael J. Wysocki wrote:
> > On Friday, June 18, 2010, Dave Airlie wrote:
> > > On Fri, 2010-06-18 at 22:21 +0200, Rafael J. Wysocki wrote:
> > > > From: Rafael J. Wysocki
> >
On Saturday, June 19, 2010, Dave Airlie wrote:
> On Sat, 2010-06-19 at 01:23 +0200, Rafael J. Wysocki wrote:
> > On Friday, June 18, 2010, Dave Airlie wrote:
> > > On Fri, 2010-06-18 at 22:21 +0200, Rafael J. Wysocki wrote:
> > > > From: Rafael J. Wysocki
> >
On Saturday, June 19, 2010, Rafael J. Wysocki wrote:
> On Saturday, June 19, 2010, Dave Airlie wrote:
> > On Sat, 2010-06-19 at 01:23 +0200, Rafael J. Wysocki wrote:
> > > On Friday, June 18, 2010, Dave Airlie wrote:
> > > > On Fri, 2010-06-18 at 22:21
[NOTES:
* This list seems to be shrinking at last.
* The bug entries with the NEEDINFO status will be closed next round if the
reporters don't follow up.]
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
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
days old)
First-Bad-Commit:
http://git.kernel.org/linus/cf7500c0ea133d66f8449d86392d83f840102632
Handled-By : Eric W. Biederman
Regressions with patches
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16396
Subject : [bisected] resume from suspend fr
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 a
at 1800 [size=8]
> Expansion ROM at [disabled]
> Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
> Capabilities: [d0] Power Management version 3
> Kernel driver in use: i915
>
> Please let me know what additional infos are required to
On Sunday, August 01, 2010, Stefan Richter wrote:
> Rafael J. Wysocki wrote:
> > If you know of any other unresolved regressions from 2.6.34, please let us
> > know either and we'll add them to the list.
>
> Subject : 2.6.35-rc6+: i915: Bisected regressio
On Sunday, August 01, 2010, Willi Mann wrote:
> Rafael J. Wysocki wrote:
>
> > On Sunday, August 01, 2010, Willi Mann wrote:
> >> Hi!
> >>
> >> On my Thinkpad T500 with Debian-compiled kernel
> >> 2.6.35~rc6-1~experimental.1, I still get OOpses o
ystem
Submitter : tomas m
Date : 2010-07-15 02:32 (18 days old)
Handled-By : Rafael J. Wysocki
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16393
Subject : kernel BUG at fs/block_dev.c:765!
Submitter : Markus Trippelsdorf
Date: 201
[NOTE: This is the last summary report of regressions introduced between
2.6.33 and 2.6.34. Thanks for helping us with tracking these bugs!]
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 t
On Sunday, August 01, 2010, Linus Torvalds wrote:
> On Sun, Aug 1, 2010 at 6:46 AM, Rafael J. Wysocki wrote:
...
>
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16369
> > Subject : Yet another 2.6.35 regression (AGP)?
> > Submitter :
68405ef3398a1fa7f4a0d6d15
Message-ID : <1279008849.2096.913.ca...@ymzhang.sh.intel.com>
References : http://marc.info/?l=linux-kernel&m=127900880212470&w=2
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16396
Subject : [bisected] resume from suspend fr
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 th
On Monday, August 30, 2010, Jonathan Corbet wrote:
> On Mon, 30 Aug 2010 00:36:36 +0200 (CEST)
> "Rafael J. Wysocki" wrote:
>
> > The following bug entry is on the current list of known regressions
> > from 2.6.35. Please verify if it still should be listed
On Wednesday, September 01, 2010, Johan Kullstam wrote:
> "Rafael J. Wysocki" writes:
>
> > 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
[NOTE:
Florian Mickler has joined the regression tracking team. He is going to
browse the list periodically to close fixed regressions, add patches etc.
So, when the listed regressions you care about are fixed, please report
that to Florian. If there's a working patch for a regression you car
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 kno
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 th
r : Jean-Marc Pigeon
Date: 2010-06-12 04:17 (101 days old)
Handled-By : Patrick McHardy
Regressions with patches
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16396
Subject : [bisected] resume from suspend freezes system
Submi
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 th
bject : Radeon HD 4700 needs MSI disabled
Submitter : Rafael Gandolfi
Date: 2010-09-18 12:06 (9 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18522
Subject : [REGRESSION] cdrom drive doesn't detect removal
Submitter : Maxim Levi
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 th
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 kno
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 th
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 kno
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 th
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 kno
xes things by creating a new system-wide, non-reentrant,
> freezable workqueue and using it for disk-events polling.
>
> Signed-off-by: Alan Stern
> CC: Tejun Heo
> CC:
Acked-by: Rafael J. Wysocki
Thanks,
Rafael
> ---
>
> I'm not sure who to send this patch to
This message contains a list of some post-3.1 regressions introduced before
3.2, 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-3.1 regressions, please let us know
either
, we might have been more verbose about what _exactly_ we've been using the
Bugzilla for and what our workflow is, but at the same time people might have
been a bit less harsh to someone who's been doing a service to the community,
completely voluntarily.
Thanks,
Rafael
---
This messag
On Friday, February 24, 2012, David Miller wrote:
> From: "Rafael J. Wysocki"
> Date: Thu, 23 Feb 2012 23:51:20 +0100 (CET)
>
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=42776
> > Subject : OF-related boot crash in 3.3.0-rc3-00188-g3
[NOTE:
Florian Mickler has joined the regression tracking team. He is going to
browse the list periodically to close fixed regressions, add patches etc.
So, when the listed regressions you care about are fixed, please report
that to Florian. If there's a working patch for a regression you car
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 kno
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 th
tables rule
Submitter : Jean-Marc Pigeon
Date: 2010-06-12 04:17 (101 days old)
Handled-By : Patrick McHardy
Regressions with patches
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16396
Subject : [bisected] resume from sus
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 th
bject : Radeon HD 4700 needs MSI disabled
Submitter : Rafael Gandolfi
Date: 2010-09-18 12:06 (9 days old)
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=18522
Subject : [REGRESSION] cdrom drive doesn't detect removal
Submitter : Maxim Levi
This message contains a list of some regressions from 2.6.38,
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.38, please let us
know either and we'll add th
This message contains a list of some post-2.6.37 regressions introduced before
2.6.38, 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.37 regressions, please let us kno
[NOTE:
I have one request for whoever works on fixing the listed regressions. While
your work is highly appreciated anyway, if you have a patch fixing a listed
regression or you know of a commit fixing a listed regression, please drop
a notice into the corresponding Bugzilla entry. This will
This message contains a list of some post-2.6.37 regressions introduced before
2.6.38, 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.37 regressions, please let us kno
[NOTE:
We already have a bug entry for tracking regressions from 3.0:
http://bugzilla.kernel.org/show_bug.cgi?id=40982
but there are no reports linked to it, mostly because Maciej is on vacation,
but also because the frequency of reporting regressions has been low
recently. So, if you're se
On Monday, August 15, 2011, Paul E. McKenney wrote:
> On Sun, Aug 14, 2011 at 09:02:27PM +0200, Rafael J. Wysocki wrote:
> > [NOTE:
> > We already have a bug entry for tracking regressions from 3.0:
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=40982
> &g
This message contains a list of some regressions from 3.0,
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 3.0, please let us
know either and we'll add them to
On Sunday, August 28, 2011, Dave Jones wrote:
> On Sun, Aug 28, 2011 at 08:22:05PM +0200, Rafael J. Wysocki wrote:
>
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=41742
> > Subject: duplicate filename for intel_backlight with the i915
> driver
&
This message contains a list of some post-2.6.39 regressions introduced before
3.0, 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.39 regressions, please let us know
e
[I'm sorry if you receive this message twice, I seem to have problems with
sending it.]
This message contains a list of some regressions from 3.0 and 3.1
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 kno
This message contains a list of some regressions from 3.0 and 3.1
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 3.0 and 3.1, please let us
know either and we'
This message contains a list of some regressions from 2.6.37,
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.37, please let us
know either and we'll add th
This message contains a list of some post-2.6.36 regressions introduced before
2.6.37, 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.36 regressions, please let us kno
On Thursday, February 03, 2011, Takashi Iwai wrote:
> At Thu, 3 Feb 2011 07:42:05 -0800,
> Linus Torvalds wrote:
> >
> > On Thu, Feb 3, 2011 at 3:23 AM, Carlos R. Mafra
> > wrote:
> > > On Thu 3.Feb'11 at 1:03:41 +0100, Rafael J. Wysocki wrote:
lead to
a suspend sequence deadlock.
Unfortunately, it looks like the ACPI video device is registered before the
PCI device that's becoming it's parent, so the above assumption will be
violated.
Thanks,
Rafael
On Sunday, February 06, 2011, Matthew Garrett wrote:
> On Sun, Feb 06, 2011 at 09:35:07PM +0100, Rafael J. Wysocki wrote:
> > > + acpi_get_parent(device->dev->handle, &acpi_parent);
> > > +
> > > + pdev = acpi_get_pci_de
On Sunday, February 06, 2011, Matthew Garrett wrote:
> On Sun, Feb 06, 2011 at 11:41:19PM +0100, Rafael J. Wysocki wrote:
> > On Sunday, February 06, 2011, Matthew Garrett wrote:
> > > Ugh. Ok, how can we fix this?
> >
> > Not nicely, I'm afraid.
On Monday, February 07, 2011, Matthew Garrett wrote:
> On Mon, Feb 07, 2011 at 12:01:25AM +0100, Rafael J. Wysocki wrote:
>
> > Yes, it seems so, but I'm not sure what the short term consequences of that
> > change will be. Perhaps there will be none. :-)
>
> O
On Monday, February 07, 2011, Matthew Garrett wrote:
> On Mon, Feb 07, 2011 at 02:32:35PM -0700, Bjorn Helgaas wrote:
>
> > I'm not familiar with video devices, but I agree, this situation does
> > feel broken. Is it the case that there's a PCI device as well as an
> > ACPI namespace Device for t
This message contains a list of some regressions from 2.6.37,
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.37, please let us
know either and we'll add th
On Sunday, March 27, 2011, Rafael J. Wysocki wrote:
> This message contains a list of some regressions from 2.6.37,
> 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 o
This message contains a list of some regressions from 2.6.38,
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.38, please let us
know either and we'll add th
[NOTE:
This most likely is the last summary report of post-2.6.37 regressions
introduced during the 2.6.38 development cycle. Please let us know what
the current status of those bugs is, if possible, and thanks for all of
the reports, updates and fixes.]
This message contains a list of some p
On Friday, May 20, 2011, Ray Lee wrote:
> [ Adding Chris Wilson (author of the problematic patch) and Rafael Wysocki
> to the message ]
It is on the list of known regressions from 2.6.37, but we're not tracking
them any more now that 2.6.39 is out.
Thanks,
Rafael
> On Fri, May
This message contains a list of some regressions from 3.0 and 3.1
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 3.0 and 3.1, please let us
know either and we'
This message contains a list of some regressions from 2.6.36,
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.36, please let us
know either and we'll add th
[NOTE: This most likely is the last summary report of regressions introduced
between 2.6.35 and 2.6.36.]
This message contains a list of some post-2.6.35 regressions introduced before
2.6.36, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed a
[NOTES:
* This list seems to be shrinking at last.
* The bug entries with the NEEDINFO status will be closed next round if the
reporters don't follow up.]
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
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
vid Hill
Date: 2010-06-09 23:25 (45 days old)
First-Bad-Commit:
http://git.kernel.org/linus/cf7500c0ea133d66f8449d86392d83f840102632
Handled-By : Eric W. Biederman
Regressions with patches
Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16396
Subject :
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 a
so for
> Alex/Jerome.
I'm not reproducing this on Acer Ferrari One (that has an rs780 IIRC),
but it seems I can reproduce it on a desktop box with some PCIe r300.
Tomorrow I'll try .35-rc1 on HP nx6325.
Rafael
it looks like the "legacy" PCI suspend/resume is used, which is not
recommended any more).
Thanks,
Rafael
-- next part --
00:00.0 RAM memory: nVidia Corporation MCP55 Memory Controller (rev a1)
Subsystem: Micro-Star International Co., Ltd. Device 7250
On Monday, June 14, 2010, Alex Deucher wrote:
> On Mon, Jun 14, 2010 at 10:53 AM, Rafael J. Wysocki wrote:
> > Alex, Dave,
> >
> > I'm afraid hibernation is broken on all machines using radeon/KMS with r300
> > after commit ce8f53709bf440100cb9d31b1303291551cf517
On Monday, June 14, 2010, Rafa? Mi?ecki wrote:
> 2010/6/14 Rafael J. Wysocki :
> > On Monday, June 14, 2010, Alex Deucher wrote:
> >> On Mon, Jun 14, 2010 at 10:53 AM, Rafael J. Wysocki wrote:
> >> > Alex, Dave,
> >> >
> >> > I'm afraid
On Monday, June 14, 2010, Alex Deucher wrote:
> On Mon, Jun 14, 2010 at 3:03 PM, Rafael J. Wysocki wrote:
> > On Monday, June 14, 2010, Alex Deucher wrote:
> >> On Mon, Jun 14, 2010 at 10:53 AM, Rafael J. Wysocki wrote:
> >> > Alex, Dave,
> >> >
>
On Tuesday, June 15, 2010, Rafael J. Wysocki wrote:
> On Monday, June 14, 2010, Alex Deucher wrote:
> > On Mon, Jun 14, 2010 at 3:03 PM, Rafael J. Wysocki wrote:
> > > On Monday, June 14, 2010, Alex Deucher wrote:
> > >> On Mon, Jun 14, 2010 at 10:53 AM, Ra
On Wednesday, June 16, 2010, Ondrej Zary wrote:
> On Wednesday 16 June 2010, Rafael J. Wysocki wrote:
> > On Tuesday, June 15, 2010, Rafael J. Wysocki wrote:
> > > On Monday, June 14, 2010, Alex Deucher wrote:
> > > > On Mon, Jun 14, 2010 at 3:03 PM, Rafael J. Wysocki
On Wednesday, June 16, 2010, Alex Deucher wrote:
> On Wed, Jun 16, 2010 at 4:16 PM, Rafael J. Wysocki wrote:
> > On Wednesday, June 16, 2010, Ondrej Zary wrote:
> >> On Wednesday 16 June 2010, Rafael J. Wysocki wrote:
> >> > On Tuesday, June 15, 2010, Rafael J. Wys
On Thursday, June 17, 2010, Alex Deucher wrote:
> 2010/6/17 Rafael J. Wysocki :
> > On Wednesday, June 16, 2010, Alex Deucher wrote:
> >> On Wed, Jun 16, 2010 at 4:16 PM, Rafael J. Wysocki wrote:
> >> > On Wednesday, June 16, 2010, Ondrej Zary wrote:
> >>
From: Rafael J. Wysocki
There is a regression from 2.6.34 related to the recent radeon power
management changes, caused by attempting to cancel a delayed work
item that's never been scheduled. However, the code as is has some
other issues potentially leading to visible problems.
First
On Friday, June 18, 2010, Matt Turner wrote:
> On Thu, Jun 17, 2010 at 7:02 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
...
> > http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
> Probably want to shorten the commit title a bit.
In fact the title
From: Rafael J. Wysocki
I have recently noticed a 55 sec. delay during the "device freeze"
phase of hibernation on my test-bed HP nx6325. Due to the 100%
reproducibility of it I was able to narrow it down to
radeon_suspend_kms() and then it turned out that the delay occured
so
On Friday, June 18, 2010, Rafa? Mi?ecki wrote:
> 2010/6/18 Rafael J. Wysocki :
> > From: Rafael J. Wysocki
>
> Thanks for you recent involvement in radeon driver!
Well, I'm just trying to address the issues I see on my test boxes.
> I can see you used way shorter commit
On Friday, June 18, 2010, Dave Airlie wrote:
> On Fri, 2010-06-18 at 22:21 +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > I have recently noticed a 55 sec. delay during the "device freeze"
> > phase of hibernation on m
On Saturday, June 19, 2010, Dave Airlie wrote:
> On Sat, 2010-06-19 at 01:23 +0200, Rafael J. Wysocki wrote:
> > On Friday, June 18, 2010, Dave Airlie wrote:
> > > On Fri, 2010-06-18 at 22:21 +0200, Rafael J. Wysocki wrote:
> > > > From: Rafael J. Wysocki
> >
On Saturday, June 19, 2010, Dave Airlie wrote:
> On Sat, 2010-06-19 at 01:23 +0200, Rafael J. Wysocki wrote:
> > On Friday, June 18, 2010, Dave Airlie wrote:
> > > On Fri, 2010-06-18 at 22:21 +0200, Rafael J. Wysocki wrote:
> > > > From: Rafael J. Wysocki
> >
On Saturday, June 19, 2010, Rafael J. Wysocki wrote:
> On Saturday, June 19, 2010, Dave Airlie wrote:
> > On Sat, 2010-06-19 at 01:23 +0200, Rafael J. Wysocki wrote:
> > > On Friday, June 18, 2010, Dave Airlie wrote:
> > > > On Fri, 2010-06-18 at 22:21
On Monday, June 21, 2010, Jerome Glisse wrote:
> On Sun, Jun 20, 2010 at 01:43:05AM +0200, Rafael J. Wysocki wrote:
> > On Saturday, June 19, 2010, Rafael J. Wysocki wrote:
> > > On Saturday, June 19, 2010, Dave Airlie wrote:
> > > > On Sat, 2010-06-19 at 01:23
+0xc6/0x1e0
> [ 669.112505] [] ? autoremove_wake_function+0x0/0x40
> [ 669.112505] [] ? worker_thread+0x0/0x1e0
> [ 669.112505] [] kthread+0x8e/0xa0
> [ 669.112505] [] kernel_thread_helper+0x4/0x10
> [ 669.112505] [] ? kthread+0x0/0xa0
> [ 669.112505] [] ? kernel_thread_helper+0x0/0x10
>
> Except for that one there are a few async/* tasks waiting.
It looks like the freezer fails on your system.
How much time did you wait for the failig "pm_test = device" to recover?
Rafael
rch kernel: [] ?
> > radeon_gem_create_ioctl+0x54/0xd0
> > Nov 8 19:28:23 arch kernel: [] ?
> > sock_aio_read+0x10d/0x120
> > Nov 8 19:28:23 arch kernel: [] ? drm_ioctl+0x39c/0x450
> > Nov 8 19:28:23 arch kernel: [] ?
> > radeon_gem_create_ioctl+0x0/0xd0
> > Nov 8 19:28:23 arch kernel: [] ? do_vfs_ioctl+0xa9/0x610
> > Nov 8 19:28:23 arch kernel: [] ? sys_ioctl+0x49/0x80
> > Nov 8 19:28:23 arch kernel: [] ? sys_read+0x4e/0x90
> > Nov 8 19:28:23 arch kernel: [] ?
> > system_call_fastpath+0x16/0x1b
> >
>
> Thomas this bug seems to point to a case where we endup trying adding
> an entry to
> same offset in the rb tree for addr_space_mm. After reviewing
> carefully the locking
> around the rb tree modification & addr_space_mm i am fairly confident
> that no race can
> occur. Would you have any idea on what might go wrong here ? I guess i would
> ultimately need to dump mm & rb tree state when BUG get trigger to try
> to understand
> states of things.
Hmm, why are you using BUG in there in the first place? Would it be _so_
dangerous to continue that we just have to crash here?
Rafael
: 2010-11-04 16:06 (15 days old)
First-Bad-Commit:
http://git.kernel.org/linus/3e384ee6c687cb397581ee8f9440fc8220cfac80
Message-ID : <201011041706.59046.maciej.rutecki at gmail.com>
References : http://marc.info/?l=linux-kernel&m=12684308982&w=2
Handled-By : Ra
This message contains a list of some post-2.6.35 regressions introduced before
2.6.36, 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.35 regressions, please let us kno
On Friday, November 19, 2010, Jesse Gross wrote:
> On Thu, Nov 18, 2010 at 3:50 PM, Rafael J. Wysocki wrote:
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=20462
> > Subject : 2.6.36-rc7-git2 - panic/GPF: e1000e/vlans?
> > Submitter : Nik
On Friday, November 19, 2010, Alex Deucher wrote:
> On Thu, Nov 18, 2010 at 6:23 PM, Rafael J. Wysocki wrote:
> > This message contains a list of some regressions from 2.6.36,
> > for which there are no fixes in the mainline known to the tracking team.
> > If any of them ha
* Invalid command stream !
[ 143.370083] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
This doesn't happen with 2.6.37-rc2.
Full dmesg output is attached, please let me know if you need more information.
Thanks,
Rafael
-- next part --
A non-text attachment was scr
On Wednesday, November 24, 2010, Rafael J. Wysocki wrote:
> Hi,
>
> I cannot start KDE with the 2.6.37-rc3 kernel. The X server and display
> manager start normally, but when I attempt to log into KDE, it attempts to
> start, but then the X apparently crashes and this appears in t
On Wednesday, November 24, 2010, Alex Deucher wrote:
> 2010/11/23 Rafael J. Wysocki :
> > On Wednesday, November 24, 2010, Rafael J. Wysocki wrote:
> >> Hi,
> >>
> >> I cannot start KDE with the 2.6.37-rc3 kernel. The X server and display
> >> mana
401 - 500 of 656 matches
Mail list logo
