All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: poma <pomidorabelisima@gmail.com>
Cc: "Nouveau Dev" <nouveau@lists.freedesktop.org>,
	"Michel Dänzer" <michel@daenzer.net>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"Ben Skeggs" <bskeggs@redhat.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Daniel Vetter" <daniel.vetter@intel.com>,
	"Thierry Reding" <treding@nvidia.com>
Subject: Re: [PATCH] drm/nouveau: Fix pre-nv50 pageflip events
Date: Wed, 2 Dec 2015 09:55:26 +0100	[thread overview]
Message-ID: <20151202085526.GA17050@phenom.ffwll.local> (raw)
In-Reply-To: <CAF+9+UPxVnRU_RJLTpr6qVFZU8A3oz9pzMF_yStjk5gBpharkg@mail.gmail.com>

On Wed, Dec 02, 2015 at 06:40:32AM +0100, poma wrote:
> On Tue, Dec 1, 2015 at 6:30 PM, Mario Kleiner
> <mario.kleiner.de@gmail.com> wrote:
> > When we are at it, the one with the title "[PATCH] drm/nouveau: Use
> > drm_vblank_on/off consistently" from Daniel, which has a reviewed and tested
> > by me also never made it into nouveau.
> >
> > Maybe pick that up as well?
> >
> > -mario
> >
> 
> If you refer to
> "[1/3] drm/nouveau: Use drm_vblank_on/off consistently"
> https://patchwork.freedesktop.org/patch/50771
> 
> this is the result:
> patched 4.4.0-0.rc3.git0.1.fc24.x86_64 with it,
> i.e. 1-3-drm-nouveau-Use-drm_vblank_on-off-consistently.patch
> 
> # cat /var/log/Xorg.0.log
> [   126.360]
> X.Org X Server 1.18.0
> ...
> [   126.909] (EE) [drm] Failed to open DRM device for pci:0000:02:00.0: -19
> [   126.909] (EE) No devices detected.
> [   126.909] (EE)
> Fatal server error:
> [   126.909] (EE) no screens found(EE)
> [   126.909] (EE)
> Please consult ....

Kernel log needed if the drm device isn't there. And this is pretty much
impossible, worst case modesetting is functionally busted.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-12-02  8:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 21:55 [PATCH] drm/nouveau: Fix pre-nv50 pageflip events Daniel Vetter
2015-11-02  7:45 ` Michel Dänzer
2015-11-16 15:11   ` Daniel Vetter
     [not found]     ` <20151116151100.GU16848-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2015-12-01 15:08       ` poma
2015-12-01 15:55         ` Daniel Vetter
     [not found]           ` <20151201155519.GW17050-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2015-12-01 17:30             ` Mario Kleiner
2015-12-02  5:40               ` poma
2015-12-02  8:55                 ` Daniel Vetter [this message]
     [not found]                   ` <20151202085526.GA17050-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2015-12-02 16:03                     ` poma
     [not found] ` <1446242140-6766-1-git-send-email-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2015-11-06 17:19   ` Thierry Reding
2015-11-07 23:12     ` Mario Kleiner
2015-11-09 13:34     ` Mario Kleiner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151202085526.GA17050@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=bskeggs@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=michel@daenzer.net \
    --cc=nouveau@lists.freedesktop.org \
    --cc=pomidorabelisima@gmail.com \
    --cc=treding@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.