dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83616] Sydtem crashes in xonotic with kernel 3.17-rc since linux commit 86302eeadebfab94530b00f5e53a23f911ff41e4
Date: Mon, 08 Sep 2014 21:46:41 +0000	[thread overview]
Message-ID: <bug-83616-502-TlrvJ0UlWw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83616-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1553 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=83616

--- Comment #11 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
(In reply to comment #10)
> (In reply to comment #7)
> > This fixes ONE of the bugs Christian and me are hunting for some days, now.
> > Making my RV730 AGP (!!!) working with 3.17-rcX/drm-next-3.18-wip, again.
> > 
> > Crashed with mplayer -vo vdpau XXX immediatly.
> > 
> > But 'allow UVD to use a second 256MB segment' gave no speedup, at least for
> > me.
> > 
> > Maybe it is the 'second' bug (regression) introduced with the switch from
> > 3.16 to 3.17 (drm-next).
> > 
> [snip]
> > 
> > Tried after bisection with reverting:
> > drm-radeon-fix-display-handling-in-radeon_gpu_reset.patch
> > 
> > Any ideas, Alex/Christian?
> 
> I'm not sure what you are asking.  What issue are you having?

Sorry Alex, but is this intended (it is in the logs since 3.16+, too)?

[   11.316570] radeon 0000:01:00.0: (-1) pin WB bo failed
[   11.316582] radeon 0000:01:00.0: f2fb0c00 unpin not necessary
[   11.316601] radeon 0000:01:00.0: disabling GPU acceleration
[   11.369220] radeon 0000:01:00.0: f6064000 unpin not necessary

[   11.433188] [TTM] Finalizing pool allocator
[   11.433309] [TTM] Zone  kernel: Used memory at exit: 0 kiB
[   11.433317] [TTM] Zone highmem: Used memory at exit: 0 kiB
[   11.433320] [drm] radeon: ttm finalized

[   11.433325] [drm] Forcing AGP to PCIE mode

So, maybe GTT/GART grows to big?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2677 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-09-08 21:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 15:34 [Bug 83616] New: Sydtem crashes in xonotic with kernel 3.17-rc since linux commit 86302eeadebfab94530b00f5e53a23f911ff41e4 bugzilla-daemon
2014-09-08 15:37 ` [Bug 83616] " bugzilla-daemon
2014-09-08 16:55 ` bugzilla-daemon
2014-09-08 17:05 ` bugzilla-daemon
2014-09-08 17:18 ` bugzilla-daemon
2014-09-08 18:05 ` bugzilla-daemon
2014-09-08 18:21 ` bugzilla-daemon
2014-09-08 20:14 ` bugzilla-daemon
2014-09-08 20:55 ` bugzilla-daemon
2014-09-08 20:56 ` bugzilla-daemon
2014-09-08 20:58 ` bugzilla-daemon
2014-09-08 21:34 ` bugzilla-daemon
2014-09-08 21:46 ` bugzilla-daemon [this message]
2014-09-08 21:56 ` bugzilla-daemon
2014-09-09  6:25 ` [Bug 83616] System " bugzilla-daemon
2014-09-19 11:12 ` bugzilla-daemon
2014-09-19 11:13 ` bugzilla-daemon
2019-11-19  8:55 ` bugzilla-daemon

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=bug-83616-502-TlrvJ0UlWw@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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;
as well as URLs for NNTP newsgroup(s).