From: Vlastimil Babka <vbabka@suse.cz>
To: "Mario Kleiner" <mario.kleiner.de@gmail.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
mgraesslin@kde.org, "David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
kwin@kde.org
Subject: Re: linux-4.4 bisected: kwin5 stuck on kde5 loading screen with radeon
Date: Mon, 18 Jan 2016 11:49:59 +0100 [thread overview]
Message-ID: <569CC357.8030302@suse.cz> (raw)
In-Reply-To: <5699C5E5.90702@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On 01/16/2016 05:24 AM, Mario Kleiner wrote:
>
>
> On 01/15/2016 01:26 PM, Ville Syrjälä wrote:
>> On Fri, Jan 15, 2016 at 11:34:08AM +0100, Vlastimil Babka wrote:
>
> I'm currently running...
>
> while xinit /usr/bin/ksplashqml --test -- :1 ; do echo yay; done
>
> ... in an endless loop on Linux 4.4 SMP PREEMPT on HD-5770 and so far i
> can't trigger a hang after hundreds of runs.
>
> Does this also hang for you?
No, test mode seems to be fine.
> I think a drm.debug=0x21 setting and grep'ping the syslog for "vblank"
> should probably give useful info around the time of the hang.
Attached. Captured by having kdm running, switching to console, running
"dmesg -C ; dmesg -w > /tmp/dmesg", switch to kdm, enter password, see
frozen splashscreen, switch back, terminate dmesg. So somewhere around
the middle there should be where ksplashscreen starts...
> Maybe also check XOrg.0.log for (WW) warnings related to flip.
No such warnings there.
> thanks,
> -mario
>
>
>>> Thanks,
>>> Vlastimil
>>
[-- Attachment #2: dmesg.gz --]
[-- Type: application/gzip, Size: 77399 bytes --]
next prev parent reply other threads:[~2016-01-18 10:50 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 10:34 linux-4.4 bisected: kwin5 stuck on kde5 loading screen with radeon Vlastimil Babka
2016-01-15 12:26 ` Ville Syrjälä
2016-01-15 12:40 ` Vlastimil Babka
2016-01-16 4:24 ` Mario Kleiner
2016-01-16 4:24 ` Mario Kleiner
2016-01-18 10:49 ` Vlastimil Babka [this message]
2016-01-18 14:06 ` Vlastimil Babka
2016-01-18 14:14 ` Christian König
2016-01-18 14:14 ` Christian König
2016-01-20 20:25 ` Vlastimil Babka
2016-01-20 20:25 ` Vlastimil Babka
2016-01-20 20:32 ` Mario Kleiner
2016-01-20 20:32 ` Mario Kleiner
2016-01-21 3:43 ` Michel Dänzer
2016-01-21 3:43 ` Michel Dänzer
2016-01-21 5:31 ` Mario Kleiner
2016-01-21 5:31 ` Mario Kleiner
2016-01-21 6:38 ` Michel Dänzer
2016-01-21 6:38 ` Michel Dänzer
2016-01-21 6:41 ` Michel Dänzer
2016-01-21 6:41 ` Michel Dänzer
2016-01-21 7:58 ` Daniel Vetter
2016-01-21 7:58 ` Daniel Vetter
2016-01-21 8:36 ` Michel Dänzer
2016-01-21 8:36 ` Michel Dänzer
2016-01-21 10:09 ` Daniel Vetter
2016-01-21 10:09 ` Daniel Vetter
2016-01-22 3:06 ` Michel Dänzer
2016-01-22 3:06 ` Michel Dänzer
2016-01-22 15:18 ` Ville Syrjälä
2016-01-22 15:18 ` Ville Syrjälä
2016-01-22 18:29 ` Mario Kleiner
2016-01-22 18:29 ` Mario Kleiner
2016-01-23 18:23 ` Mario Kleiner
2016-01-23 18:23 ` Mario Kleiner
2016-01-25 4:15 ` Michel Dänzer
2016-01-25 4:15 ` Michel Dänzer
2016-01-25 13:16 ` Mario Kleiner
2016-01-25 13:16 ` Mario Kleiner
2016-01-25 13:23 ` Ville Syrjälä
2016-01-25 13:44 ` Mario Kleiner
2016-01-25 13:44 ` Mario Kleiner
2016-01-25 14:53 ` Ville Syrjälä
2016-01-25 14:53 ` Ville Syrjälä
2016-01-25 16:38 ` Mario Kleiner
2016-01-25 18:51 ` Daniel Vetter
2016-01-25 18:51 ` Daniel Vetter
2016-01-25 19:30 ` Mario Kleiner
2016-01-25 19:30 ` Mario Kleiner
2016-01-25 20:32 ` Daniel Vetter
2016-01-25 20:32 ` Daniel Vetter
2016-01-25 21:42 ` Mario Kleiner
2016-01-25 21:42 ` Mario Kleiner
2016-01-25 22:05 ` Daniel Vetter
2016-01-25 22:05 ` Daniel Vetter
2016-01-21 8:28 ` Mario Kleiner
2016-01-21 8:28 ` Mario Kleiner
2016-01-21 9:15 ` Vlastimil Babka
2016-01-21 9:15 ` Vlastimil Babka
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=569CC357.8030302@suse.cz \
--to=vbabka@suse.cz \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kwin@kde.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.kleiner.de@gmail.com \
--cc=mgraesslin@kde.org \
--cc=ville.syrjala@linux.intel.com \
/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.