dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65192] [r600g] Screensavers lock up machine (screen goes blank, keyboard unresponsive, sound loops; sysrq/ssh possible)
Date: Tue, 04 Jun 2013 23:26:52 +0000	[thread overview]
Message-ID: <bug-65192-502-HQVvcUxMKm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-65192-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Luzipher <luziphermcleod@yahoo.ie> ---
Unfortunately I couldn't confirm my thoughts. But I still am quite sure I did
not have those problems earlier - I had screensavers and youtube last year and
didn't notice regular crashes. I frequently use this linux installation, in
fact it's my main os for several years now, so I really would have noticed.
Maybe it's another package ? X, libdrm, radeon-ucode, xf86-video-ati come to
mind. Maybe mostly radeon-ucode, as I have the feeling that the problems
started at about the same time as the buzz on the uvd code drop.

Well, tests done (I could reproduce the crash on every of these with directly
started juggler3d on closing the window, mostly first or second try):

mesa-9.0.3 (forgot to get glxinfo)

mesa-9.0.1.ebuild, glxinfo:
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 3.0 Mesa 9.0.1
OpenGL shading language version string: 1.30

mesa-8.0.4-r1.ebuild, glxinfo:
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 2.1 Mesa 8.0.4
OpenGL shading language version string: 1.20
with 8.0.4, I got only garbage and a lot of these messages:
radeon: The kernel rejected CS, see dmesg for more information.
dmesg:
[ 1580.805418] radeon 0000:02:00.0: r600_cs_track_validate_cb invalid tiling 6
for 0 (0x08110668)
[ 1580.805463] radeon 0000:02:00.0: r600_packet3_check:1720 invalid cmd stream
573
[ 1580.805465] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !



I also tried the oldest kernel I have with 8.0.4, it's a vanilla 3.4.0-rc6.
Even there I could get the same crash after closing the window with the garbage
output.

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

[-- Attachment #1.2: Type: text/html, Size: 2672 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:[~2013-06-04 23:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 22:35 [Bug 65192] New: Screensavers lock up machine (screen goes blank, keyboard unresponsive, sound loops; sysrq/ssh possible) bugzilla-daemon
2013-05-30 22:39 ` [Bug 65192] " bugzilla-daemon
2013-05-30 22:43 ` [Bug 65192] [r600g] " bugzilla-daemon
2013-05-31  9:19 ` bugzilla-daemon
2013-05-31 16:31 ` bugzilla-daemon
2013-06-03 14:42 ` bugzilla-daemon
2013-06-03 17:02 ` bugzilla-daemon
2013-06-03 17:17 ` bugzilla-daemon
2013-06-03 18:02 ` bugzilla-daemon
2013-06-04 17:06 ` bugzilla-daemon
2013-06-04 23:26 ` bugzilla-daemon [this message]
2013-07-30 23:38 ` bugzilla-daemon
2013-07-30 23:39 ` 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-65192-502-HQVvcUxMKm@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