From: Thomas Hellstrom <thellstrom@vmware.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: Device loses its IRQ number on driver unload?
Date: Mon, 9 Mar 2015 17:02:11 +0100 [thread overview]
Message-ID: <54FDC403.8050209@vmware.com> (raw)
In-Reply-To: <20150309152247.GM24485@phenom.ffwll.local>
On 03/09/2015 04:22 PM, Daniel Vetter wrote:
> On Mon, Mar 09, 2015 at 11:04:01AM +0100, Thomas Hellstrom wrote:
>> Hi,
>>
>> I'm not sure this started with 4.0 but when I rmmod the device driver
>> like so
>> rmmod vmwgfx
>>
>> The device loses its IRQ line as shown in lscpi:
>> Flags: bus master, medium devsel, latency 64 <irq missing here>
>>
>> and a subsequent modprobe will fail since pdev->irq is 0.
>>
>> Is anyone else seeing this with other drivers?
> I seen occasionally (over the past couple of kernels) random zeros in pdev
> but dismissed it as broken machines or bugs in i915 (we have them ...).
> Usually the box died chasing a NULL pointer from pdev. Otherwise no.
> -Daniel
OK. Thanks for the info. Since in my case this is 100% reproducible I
guess I have an excellent opportunity to bisect the problem :-/
/Thomas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-09 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 10:04 Device loses its IRQ number on driver unload? Thomas Hellstrom
2015-03-09 15:22 ` Daniel Vetter
2015-03-09 16:02 ` Thomas Hellstrom [this message]
2015-03-09 20:25 ` Dave Airlie
2015-03-10 12:55 ` Thomas Hellstrom
2015-03-10 14:01 ` Alex Deucher
2015-03-10 21:05 ` Dave Airlie
2015-03-11 6:40 ` Thomas Hellstrom
2015-03-11 7:22 ` Dave Airlie
2015-03-11 9:28 ` Thomas Hellstrom
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=54FDC403.8050209@vmware.com \
--to=thellstrom@vmware.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
/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