[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAN_LGv1C7XPHTzXyFjJStffRE_BXxi5tNyJ4cV98RvPfbwFkGA@mail.gmail.com>
Date: Fri, 21 Jun 2013 19:02:35 +0600
From: "Alexander E. Patrakov" <patrakov@...il.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Jiang Liu <jiang.liu@...wei.com>, alexdeucher@...il.com,
Bjorn Helgaas <bhelgaas@...gle.com>,
Yinghai Lu <yinghai@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Yijing Wang <wangyijing@...wei.com>,
linux-acpi@...r.kernel.org, Jiang Liu <liuj97@...il.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [BUGFIX v2 0/4] fix bug 56531, 59501 and 59581
2013/6/21 Rafael J. Wysocki <rjw@...k.pl>:
> The thing below looks like a radeon problem?
>
> [ 52.268389] ------------[ cut here ]------------
> [ 52.268395] WARNING: at drivers/gpu/drm/ttm/ttm_page_alloc_dma.c:533 ttm_dma_free_pool+0x101/0x110 [ttm]()
Yes. Let's ignore it for now, as it is a separate bug, likely a
special case of https://bugzilla.kernel.org/show_bug.cgi?id=59681
> But it looks like the removal actually succeeded.
It did.
> [ 52.273103] pci_bus 0000:0b: busn_res: [bus 0b] is released
> [ 52.273732] pci_bus 0000:0c: busn_res: [bus 0c] is released
> [ 52.273816] pci_bus 0000:16: busn_res: [bus 16] is released
>
> Is the re-dock attempt included? It doesn't seem to leave any trace ...
It is, and indeed it left no traces. See the followup when I attached
the result of manually rescanning the bus - you have already commented
on the deadlock there.
--
Alexander E. Patrakov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists