search for: drm_setup_crtcs

...0 [drm] which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (crtc_ww_class_mutex){+.+.}: ww_mutex_lock+0x43/0x80 drm_modeset_lock+0x71/0x130 [drm] drm_helper_probe_single_connector_modes+0x7d/0x6b0 [drm_kms_helper] drm_setup_crtcs+0x15e/0xc90 [drm_kms_helper] __drm_fb_helper_initial_config_and_unlock+0x29/0x480 [drm_kms_helper] nouveau_fbcon_init+0x138/0x1a0 [nouveau] nouveau_drm_load+0x173/0x7e0 [nouveau] drm_dev_register+0x134/0x1c0 [drm] drm_get_pci_dev+0x8e/0x160 [drm] nouveau_dr...

...gt; [ 5.428844] [drm:drm_mode_debug_printmodeline], Modeline 47:"640x400" 60 20000 640 664 720 800 400 403 409 417 0x40 0x6 > [ 5.428855] [drm:drm_mode_debug_printmodeline], Modeline 48:"640x350" 60 17500 640 664 720 800 350 353 363 366 0x40 0x6 > [ 5.428867] [drm:drm_setup_crtcs], > [ 5.428873] [drm:drm_enable_connectors], connector 11 enabled? no > [ 5.428880] [drm:drm_enable_connectors], connector 13 enabled? yes > [ 5.428887] [drm:drm_target_preferred], looking for cmdline mode on connector 13 > [ 5.428894] [drm:drm_target_preferred], found mode...

https://bugs.freedesktop.org/show_bug.cgi?id=51971 Bug #: 51971 Summary: MacBook Pro 10,1 Retina - Display Resets, No Connectors Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium

Hi again, I got a new dmesg log with the debug parameters, but I guess I could not isolate VESA. I blacklisted it at /etc/modprobe.d/blacklist.conf but comparing those logs I see no difference... Is it possible to isolate VESA somehow without removing it? The new logs are here, I'm posting full content because I'm not sure what information is more relevant...

...774,6 +2834,11 @@ int drm_fb_helper_hotplug_event(struct drm_fb_helper *fb_helper) > return err; > } > > + if (fb_helper->hotplug_suspended) { > + mutex_unlock(&fb_helper->lock); > + return err; > + } > + > DRM_DEBUG_KMS("\n"); > > drm_setup_crtcs(fb_helper, fb_helper->fb->width, fb_helper->fb->height); > diff --git a/include/drm/drm_fb_helper.h b/include/drm/drm_fb_helper.h > index b069433e7fc1..30881131075c 100644 > --- a/include/drm/drm_fb_helper.h > +++ b/include/drm/drm_fb_helper.h > @@ -232,6 +232,14 @@ struc...

...probing all the outputs attached to the fb @@ -2774,6 +2834,11 @@ int drm_fb_helper_hotplug_event(struct drm_fb_helper *fb_helper) return err; } + if (fb_helper->hotplug_suspended) { + mutex_unlock(&fb_helper->lock); + return err; + } + DRM_DEBUG_KMS("\n"); drm_setup_crtcs(fb_helper, fb_helper->fb->width, fb_helper->fb->height); diff --git a/include/drm/drm_fb_helper.h b/include/drm/drm_fb_helper.h index b069433e7fc1..30881131075c 100644 --- a/include/drm/drm_fb_helper.h +++ b/include/drm/drm_fb_helper.h @@ -232,6 +232,14 @@ struct drm_fb_helper { * Se...

> On Tue, Apr 01, 2014 at 02:53:02PM -0400, Ilia Mirkin wrote: >I believe that ch7006 is the only external encoder that's supposed to >work, so you're in luck. It sounds like it passes the nv04_tv_identify >stage of nv04_tv_create -- perhaps it fails later? Although based on >the prints, it's even doing dpms stuff (but it hits _detect a second >time... odd). Try

...tor+0xe0/0xe0 [nouveau] > nvkm_ioctl+0xe2/0x180 [nouveau] > nvkm_client_ioctl+0x12/0x20 [nouveau] > nvif_object_ioctl+0x47/0x50 [nouveau] > nvif_object_init+0xc8/0x120 [nouveau] > nvc0_fbcon_accel_init+0x5c/0x960 [nouveau] > nouveau_fbcon_create+0x5a5/0x5d0 [nouveau] > ? drm_setup_crtcs+0x27b/0xcb0 [drm_kms_helper] > ? __lock_is_held+0x5e/0xa0 > __drm_fb_helper_initial_config_and_unlock+0x27c/0x520 [drm_kms_helper] > drm_fb_helper_hotplug_event.part.29+0xae/0xc0 [drm_kms_helper] > drm_fb_helper_hotplug_event+0x1c/0x30 [drm_kms_helper] > nouveau_fbcon_output_pol...

...; drm_fb_helper *fb_helper) > > return err; > > } > > > > + if (fb_helper->hotplug_suspended) { > > + mutex_unlock(&fb_helper->lock); > > + return err; > > + } > > + > > DRM_DEBUG_KMS("\n"); > > > > drm_setup_crtcs(fb_helper, fb_helper->fb->width, fb_helper->fb- > > >height); > > diff --git a/include/drm/drm_fb_helper.h b/include/drm/drm_fb_helper.h > > index b069433e7fc1..30881131075c 100644 > > --- a/include/drm/drm_fb_helper.h > > +++ b/include/drm/drm_fb_helper.h...

Hello, I've just been hit by this old bug which is still present in 4.14: https://bugs.freedesktop.org/show_bug.cgi?id=80675 On MCP79 (ION), when stolen memory is set to 32MB in BIOS, console is blank but X11 works. When the stolen memory is increased to 64MB, console works fine. Bisected it to this: 4f6029da58ba9204c98e33f4f3737fe085c87a6f is the first bad commit commit

...nvkm_ioctl+0xe2/0x180 [nouveau] > > nvkm_client_ioctl+0x12/0x20 [nouveau] > > nvif_object_ioctl+0x47/0x50 [nouveau] > > nvif_object_init+0xc8/0x120 [nouveau] > > nvc0_fbcon_accel_init+0x5c/0x960 [nouveau] > > nouveau_fbcon_create+0x5a5/0x5d0 [nouveau] > > ? drm_setup_crtcs+0x27b/0xcb0 [drm_kms_helper] > > ? __lock_is_held+0x5e/0xa0 > > __drm_fb_helper_initial_config_and_unlock+0x27c/0x520 [drm_kms_helper] > > drm_fb_helper_hotplug_event.part.29+0xae/0xc0 [drm_kms_helper] > > drm_fb_helper_hotplug_event+0x1c/0x30 [drm_kms_helper] > >...

...en... -nouveau: DRM:00005039:00005039: init completed in 268us +nouveau: DRM:00005039:00005039: init completed in 274us nouveau 0000:02:00.0: DRM: MM: using M2MF for buffer copies nouveau 0000:02:00.0: disp: supervisor 00000010 000002a0 nouveau 0000:02:00.0: disp: Core: @@ -405,7 +405,7 @@ [drm:drm_setup_crtcs [drm_kms_helper]] desired mode 1280x1024 set on crtc 34 (0,0) nouveau: DRM:ffff0000:0000003d: init running... nouveau: DRM:ffff0000:0000003d: init children... -nouveau: DRM:ffff0000:0000003d: init completed in 71us +nouveau: DRM:ffff0000:0000003d: init completed in 68us nouveau: DRM:ffff0000:000...

...l+0xa0/0xa0 [nouveau] ? gf100_gr_dtor+0xe0/0xe0 [nouveau] nvkm_ioctl+0xe2/0x180 [nouveau] nvkm_client_ioctl+0x12/0x20 [nouveau] nvif_object_ioctl+0x47/0x50 [nouveau] nvif_object_init+0xc8/0x120 [nouveau] nvc0_fbcon_accel_init+0x5c/0x960 [nouveau] nouveau_fbcon_create+0x5a5/0x5d0 [nouveau] ? drm_setup_crtcs+0x27b/0xcb0 [drm_kms_helper] ? __lock_is_held+0x5e/0xa0 __drm_fb_helper_initial_config_and_unlock+0x27c/0x520 [drm_kms_helper] drm_fb_helper_hotplug_event.part.29+0xae/0xc0 [drm_kms_helper] drm_fb_helper_hotplug_event+0x1c/0x30 [drm_kms_helper] nouveau_fbcon_output_poll_changed+0xb8/0x110 [nou...

This series is intended to add support for shutting down the GPU on kernel shutdown/reboot using the ->shutdown() hook, similar to what amdgpu does. This is mainly intended to workaround a bios issue on the P50 that was preventing nouveau from initializing the dedicated GM107 GPU on that system properly. You can find more details on this issue in the patch labeled "Shut down GPU on kernel

...] > > > nvkm_client_ioctl+0x12/0x20 [nouveau] > > > nvif_object_ioctl+0x47/0x50 [nouveau] > > > nvif_object_init+0xc8/0x120 [nouveau] > > > nvc0_fbcon_accel_init+0x5c/0x960 [nouveau] > > > nouveau_fbcon_create+0x5a5/0x5d0 [nouveau] > > > ? drm_setup_crtcs+0x27b/0xcb0 [drm_kms_helper] > > > ? __lock_is_held+0x5e/0xa0 > > > __drm_fb_helper_initial_config_and_unlock+0x27c/0x520 [drm_kms_helper] > > > drm_fb_helper_hotplug_event.part.29+0xae/0xc0 [drm_kms_helper] > > > drm_fb_helper_hotplug_event+0x1c/0x30 [drm_km...

This is the next version of https://patchwork.freedesktop.org/series/46815/ With a lot more thought put into it so as to avoid the potential deadlock scenarios I missed. This also required fixing some bogus DRM helper usage. Try and deadlock me now, nouveau. I dare you!!! Lyude Paul (8): drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement drm/nouveau: Enable polling even if we

...417 0x40 0x6 [ 5.428844] [drm:drm_mode_debug_printmodeline], Modeline 47:"640x400" 60 20000 640 664 720 800 400 403 409 417 0x40 0x6 [ 5.428855] [drm:drm_mode_debug_printmodeline], Modeline 48:"640x350" 60 17500 640 664 720 800 350 353 363 366 0x40 0x6 [ 5.428867] [drm:drm_setup_crtcs], [ 5.428873] [drm:drm_enable_connectors], connector 11 enabled? no [ 5.428880] [drm:drm_enable_connectors], connector 13 enabled? yes [ 5.428887] [drm:drm_target_preferred], looking for cmdline mode on connector 13 [ 5.428894] [drm:drm_target_preferred], found mode 1024x768 [ 5.428...

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the

Hi all, First thing first: It works, I now no longer have a few dropped frames every 10s on my testbox here with the pageflip i-g-t tests. Random notes: - New design has per-crtc locks to protect the crtc input-side (pageflip, cursor) for r/w and the output state of the crtc (mode, dpms) as read-only. It also required completely revamped fb lifecycle management, those are now refcounted