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 73619] New: XServer frequently freezes for a few seconds
Date: Tue, 14 Jan 2014 17:38:43 +0000	[thread overview]
Message-ID: <bug-73619-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 73619
          Assignee: dri-devel@lists.freedesktop.org
           Summary: XServer frequently freezes for a few seconds
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: arichardson.kde@gmail.com
          Hardware: Other
            Status: NEW
           Version: 10.0
         Component: Drivers/DRI/R600
           Product: Mesa

The XServer randomly freezes for a few seconds or sometimes even 1-2 minutes. I
cannot move the mouse, and the screen does not update.

I have a HD4850 card running on a 
3.12.6-1.g080d0df-desktop SMP PREEMPT x86_64 kernel with Mesa 10.0.1 (both from
openSuSE packages). These freezes also happen with the default 3.11 kernel, I
upgraded in the hope of it being fixed, but the issue is still present.

These issues started after the upgrade to openSuSE 13.1 which has a 3.11 kernel
instead of the previous 3.7 kernel. The Mesa version did not change, I was
always running the latest released version. My guess is it has something to do
with the r600 kernel changes in 3.8+.

During these freeze periods I can ssh into my system and top shows no CPU
usage, so the XServer seems to be sleeping instead of being in a busy loop.
dmesg gives me no messages and /var/log/XOrg.0.log is also empty.

I don't know how to get any more detailed logging output. If you provide me
with the necessary environment variables/kernel parameters I will give you
these logs.

Not sure if this helps, but most of the time the freeze happens when I open a
new tab in firefox or switch to a different one. However it also happens at
random intervals using other programs.
It can sometimes take quite a long time until this freeze happens, however once
it has occured once, it usually happens again after a short timespan (1-2
minutes or even less).

Is it possible to debug the XServer just like a normal program using gdb? If
yes I will try to provide a useful backtrace once the next longer freeze
happens

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

[-- Attachment #1.2: Type: text/html, Size: 3451 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

             reply	other threads:[~2014-01-14 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 17:38 bugzilla-daemon [this message]
2014-01-14 18:41 ` [Bug 73619] XServer frequently freezes for a few seconds bugzilla-daemon
2014-01-14 21:06 ` bugzilla-daemon
2014-01-20 13:05 ` bugzilla-daemon
2014-01-20 14:51 ` bugzilla-daemon
2014-03-18 11:53 ` bugzilla-daemon
2014-03-19 20:27 ` bugzilla-daemon
2019-09-18 19:12 ` 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-73619-502@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