drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy

2016-12-01 Thread Robin H. Johnson
On Thu, Dec 01, 2016 at 08:38:15AM +0100, Vlastimil Babka wrote: > >> By default config this should not be used on x86. > > What do you mean by that statement? > > I mean that the 16 mbytes for generic CMA area is not a default on x86: > > config CMA_SIZE_MBYTES > int "Size in Mega Bytes

drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy

2016-12-01 Thread Robin H. Johnson
On Wed, Nov 30, 2016 at 10:24:59PM +0100, Vlastimil Babka wrote: > [add more CC's] > > On 11/30/2016 09:19 PM, Robin H. Johnson wrote: > > Somewhere in the Radeon/DRM codebase, CMA page allocation has either > > regressed in the timeline of 4.5->4.9, and/or the

drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy

2016-11-30 Thread Robin H. Johnson
Somewhere in the Radeon/DRM codebase, CMA page allocation has either regressed in the timeline of 4.5->4.9, and/or the drm/radeon code is doing something different with pages. Given that I haven't seen ANY other reports of this, I'm inclined to believe the problem is drm/radeon specific (if I don'

[PATCH resend] PCI: QEMU top-level IDs for (sub)vendor & device

2016-03-06 Thread Robin H. Johnson
Introduce PCI_VENDOR/PCI_SUBVENDOR/PCI_SUBDEVICE defines to replace the constants scattered in the kernel already used to detect QEMU. They are defined in the QEMU codebase per docs/specs/pci-ids.txt. Signed-off-by: Robin H. Johnson Reviewed-by: Takashi Iwai Reviewed-by: Gerd Hoffmann

[PATCH] PCI: QEMU top-level IDs for (sub)vendor & device

2016-01-25 Thread Robin H. Johnson
Introduce PCI_VENDOR/PCI_SUBVENDOR/PCI_SUBDEVICE defines to replace the constants scattered in the kernel already used to detect QEMU. They are defined in the QEMU codebase per docs/specs/pci-ids.txt. Signed-off-by: Robin H. Johnson --- This change prompted by a near-miss in the review of

KMS/radeon regression: failure to set modes on CEDAR & TAHITI; v3.11 vs 3.12-rc5/rc7

2013-11-07 Thread Robin H. Johnson
On Thu, Nov 07, 2013 at 11:52:13AM -0500, Alex Deucher wrote: > >> Culprit likely d1e3b5564834ea24dee6b364a172365f64865fe5 try reverting that > >> one. > > Confirmed as the buggy commit via bisect. > > Then reverted in 3.12 and 3.12 suddenly works. > I'm not sure how you would even be hitting thos

KMS/radeon regression: failure to set modes on CEDAR & TAHITI; v3.11 vs 3.12-rc5/rc7

2013-11-07 Thread Robin H. Johnson
On Wed, Nov 06, 2013 at 05:43:45PM -0500, Jerome Glisse wrote: > On Wed, Nov 06, 2013 at 05:48:55PM +0000, Robin H. Johnson wrote: > > On Wed, Nov 06, 2013 at 12:16:31PM -0500, Alex Deucher wrote: > > > On Wed, Nov 6, 2013 at 12:14 PM, Robin H. Johnson > > > wrote

KMS/radeon regression: failure to set modes on CEDAR & TAHITI; v3.11 vs 3.12-rc5/rc7

2013-11-07 Thread Robin H. Johnson
On Wed, Nov 06, 2013 at 05:37:11PM -0500, Jerome Glisse wrote: > On Wed, Nov 06, 2013 at 05:48:55PM +0000, Robin H. Johnson wrote: > > On Wed, Nov 06, 2013 at 12:16:31PM -0500, Alex Deucher wrote: > > > On Wed, Nov 6, 2013 at 12:14 PM, Robin H. Johnson > > > wrote

KMS/radeon regression: failure to set modes on CEDAR & TAHITI; v3.11 vs 3.12-rc5/rc7

2013-11-06 Thread Robin H. Johnson
On Wed, Nov 06, 2013 at 12:16:31PM -0500, Alex Deucher wrote: > On Wed, Nov 6, 2013 at 12:14 PM, Robin H. Johnson > wrote: > > (Resending to dri-devel because the first one didn't make it). > > > > I apologize for not sending this sooner, but I wanted to be reall

KMS/radeon regression: failure to set modes on CEDAR & TAHITI; v3.11 vs 3.12-rc5/rc7

2013-11-06 Thread Robin H. Johnson
(Resending to dri-devel because the first one didn't make it). I apologize for not sending this sooner, but I wanted to be really sure that I wasn't introducing the bug elsewhere, and I was lacking time to even narrow it down this far. TL;DR: 3.11 kernel does proper modeset for dual 1920x1200 out