From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216645] Fence fallback timer expired on ring gfx
Date: Mon, 31 Oct 2022 17:56:09 +0000 [thread overview]
Message-ID: <bug-216645-2300-CTaqLX0phh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216645-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216645
--- Comment #4 from Martin Šušla (ask4support@email.cz) ---
Created attachment 303110
--> https://bugzilla.kernel.org/attachment.cgi?id=303110&action=edit
Kernel log interlaced with contents of /proc/interrupts polled every second
#! /bin/sh
print() {
printf "$1" ; seq -s" " $(( $(stty size < $t | sed "s/^/(/; s/ / - 1 )
* /") - ${#1} )) | sed s/[0-9]//g
}
t="$(readlink /proc/self/fd/0)"
d="$(env LANG=C udisksctl mount -b /dev/disk/by-uuid/$1 -o sync 2> /dev/null |
sed "s/^Mounted .* at //g; s/\.$//g")"
[ -d "$d" ] && f=oflag=direct || d="${0%/*}" f=oflag=direct
(sudo dmesg -w & while sleep 1 ; do cat /proc/interrupts ; done) | sudo dd
of="$d/${0##*/}.log" $f &
i=0
seq 28 150000 | while read N ; do
print $N
timeout 3 env DISPLAY=:0 plasma-systemmonitor > /dev/null 2>&1
n=$N ; while [ 0 -lt $n ] ; do
sleep 1
n=$(( $n - 1 ))
i=$(( $i ^ 1 ))
[ "$i" = 1 ] && printf "\33[30m\33[47m" || printf
"\33[37m\33[40m"
print $n
done
done
echo END!
exit
# This script was used to generate it
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-10-31 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 13:22 [Bug 216645] New: Fence fallback timer expired on ring gfx bugzilla-daemon
2022-10-31 13:23 ` [Bug 216645] " bugzilla-daemon
2022-10-31 15:40 ` bugzilla-daemon
2022-10-31 15:42 ` bugzilla-daemon
2022-10-31 17:53 ` bugzilla-daemon
2022-10-31 17:56 ` bugzilla-daemon [this message]
2022-10-31 18:02 ` bugzilla-daemon
2022-10-31 21:53 ` bugzilla-daemon
2022-11-01 8:41 ` 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-216645-2300-CTaqLX0phh@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.