From: Pontus Fuchs <pontus.fuchs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Resume regression with nouveau 3.8rc1 (bisected)
Date: Sat, 05 Jan 2013 10:10:06 +0100 [thread overview]
Message-ID: <50E7EDEE.9090403@gmail.com> (raw)
In-Reply-To: <20130103191201.GA25680-OI9uyE9O0yo@public.gmane.org>
On 01/03/2013 08:12 PM, Marcin Slusarz wrote:
> On Thu, Jan 03, 2013 at 01:58:10PM +0100, Marcin Slusarz wrote:
>> I bisected the problem down to this commit:
>>
>> 186ecad21: drm/nv50/disp: move remaining interrupt handling into core
>>
>> Hardware is 8400M GS (10de:0427) in a Dell XPS M1330.
>> There's already open bug report for that:
>> https://bugs.freedesktop.org/show_bug.cgi?id=58729
> Yay, a bug fix was just posted there ;).
Hi, I tried that patch but it didn't help :(
I see this in my kernel log after resume:
nouveau E[ PFB][0000:01:00.0] trapped read at 0x002001a020 on
channel 0x00007b23 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT
nouveau E[ 1177] failed to idle channel 0xcccc0000
[TTM] Failed to expire sync object before buffer eviction
[TTM] Failed to expire sync object before buffer eviction
[TTM] Failed to expire sync object before buffer eviction
//Pontus
next prev parent reply other threads:[~2013-01-05 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 15:19 Resume regression with nouveau 3.8rc1 (bisected) Pontus Fuchs
[not found] ` <50E45007.5080706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-03 12:58 ` Marcin Slusarz
2013-01-03 19:12 ` Marcin Slusarz
[not found] ` <20130103191201.GA25680-OI9uyE9O0yo@public.gmane.org>
2013-01-05 9:10 ` Pontus Fuchs [this message]
[not found] ` <50E7EDEE.9090403-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-05 14:03 ` Marcin Slusarz
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=50E7EDEE.9090403@gmail.com \
--to=pontus.fuchs-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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