From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73619] XServer frequently freezes for a few seconds
Date: Tue, 14 Jan 2014 21:06:10 +0000 [thread overview]
Message-ID: <bug-73619-502-ZueqQ6bO8Z@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73619-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 790 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73619
--- Comment #2 from Alexander Richardson <arichardson.kde@gmail.com> ---
Created attachment 92092
--> https://bugs.freedesktop.org/attachment.cgi?id=92092&action=edit
logs
Bisecting is quite tricky, I have so far only used the binary kernel packages.
I can try, however it will probably take a long time until I find something
useful if at all. I am not sure when I can call a version good because
sometimes the system can run fine for multiple hours and only then start having
these freezes.
I currently don't have the time to bisect, so I was hoping there would be some
kernel parameters to increase verbosity.
Would running a debug kernel be of any use?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1666 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
next prev parent reply other threads:[~2014-01-14 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 17:38 [Bug 73619] New: XServer frequently freezes for a few seconds bugzilla-daemon
2014-01-14 18:41 ` [Bug 73619] " bugzilla-daemon
2014-01-14 21:06 ` bugzilla-daemon [this message]
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-ZueqQ6bO8Z@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