public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Fix module unloading with DRM_I915_UMS=n
Date: Mon, 25 Nov 2013 09:41:37 +0100	[thread overview]
Message-ID: <20131125084137.GR27344@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGQpmxfKay5eUt4VG6-LzJm7-55MS+ciB+GFhET=cKeajg@mail.gmail.com>

On Fri, Nov 22, 2013 at 05:25:41PM -0200, Paulo Zanoni wrote:
> 2013/11/15 Daniel Vetter <daniel.vetter@ffwll.ch>:
> > Oops, makes testing early boot failures in i915.ko a bit more pain, so
> > let's fix it.
> >
> > v2: We already have a bit of static storage to track this (Chris).
> >
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> I can reproduce the failure by booting with i915.modeset=0, then get
> the oops when "rmmod i915".
> 
> Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Tested-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> 
> I also looked at Chris' patch. I think that since we take the early
> "return 0" inside i915_init, we never call drm_pci_init, so it doesn't
> make too much sense to fix the problem inside drm_pci_exit.

Thanks for review&testing, patch merged.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2013-11-25  8:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 10:28 [PATCH] drm/i915: Fix module unloading with DRM_I915_UMS=n Daniel Vetter
2013-11-15 10:34 ` Chris Wilson
2013-11-15 16:16   ` Daniel Vetter
2013-11-15 20:58     ` Chris Wilson
2013-11-15 21:49       ` Daniel Vetter
2013-11-22 19:25     ` Paulo Zanoni
2013-11-25  8:41       ` Daniel Vetter [this message]

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=20131125084137.GR27344@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=przanoni@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox