From: Daniel Vetter <daniel@ffwll.ch>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] i915: remove pm_qos request on error
Date: Sat, 25 Jan 2014 12:53:56 +0100 [thread overview]
Message-ID: <20140125115356.GC9772@phenom.ffwll.local> (raw)
In-Reply-To: <20140125091336.GA1703@redhat.com>
On Sat, Jan 25, 2014 at 10:13:37AM +0100, Stanislaw Gruszka wrote:
> Not removing pm qos request and free memory for it can cause crash,
> when some other driver use pm qos. For example, this oops:
>
> BUG: unable to handle kernel paging request at fffffffffffffff8
> IP: [<ffffffff81307a6b>] plist_add+0x5b/0xd0
> Call Trace:
> [<ffffffff810acf25>] pm_qos_update_target+0x125/0x1e0
> [<ffffffff810ad071>] pm_qos_add_request+0x91/0x100
> [<ffffffffa053ec14>] e1000_open+0xe4/0x5b0 [e1000e]
>
> was caused by earlier i915 probe failure:
>
> [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
> [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 head 00003004 tail 00000000 start 00003000
> [drm:i915_driver_load] *ERROR* failed to init modeset
> i915: probe of 0000:00:02.0 failed with error -5
>
> Bug report:
> http://bugzilla.redhat.com/show_bug.cgi?id=1057533
>
> Reported-by: Giandomenico De Tullio <ghisha@gmail.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Picked up for -fixes, thanks for the patch. I've remove the movement of
the to pm_qos_add_request though. If we want to clean this is I think an
intel_irq_fini which is called both here and in the unload code is better.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-01-25 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 9:13 [PATCH] i915: remove pm_qos request on error Stanislaw Gruszka
2014-01-25 11:53 ` 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=20140125115356.GC9772@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sgruszka@redhat.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