From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: next-0519 on thinkpad x60: sound related? window manager crash
Date: Thu, 21 May 2020 09:41:59 +0200 [thread overview]
Message-ID: <20200521074110.GA3895@amd.ucw.cz> (raw)
In-Reply-To: <20200520110900.GA8203@amd>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
Hi!
> My window manager stopped responding. I was able to recover machine
> using sysrq-k.
>
> I started writing nice report, when session failed second time. And
> then third time on next attempt.
>
> Any ideas?
>
> I'll send this out before this locks up...
Today it crashed again, with similar oops in the log.
My records say:
fb57b1fabcb2 (HEAD, tag: next-20200519, origin/master, origin/HEAD) HEAD@{0}: checkout: moving from bdecf38f228bcca73b31ada98b5b7ba1215eb9c9 to next-20200519
bdecf38f228b (tag: next-20200515) HEAD@{1}: checkout: moving from 30e2206e11ce27ae910cc0dab21472429e400a87 to next-20200515
So it is well possible that 0515 worked okay for few
days. Hmm. Perhaps I'll try going to 0516 and see if it is stable?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next parent reply other threads:[~2020-05-21 7:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200520110900.GA8203@amd>
2020-05-21 7:41 ` Pavel Machek [this message]
2020-05-20 11:11 next-0519 on thinkpad x60: sound related? window manager crash Pavel Machek
2020-05-20 11:37 ` Takashi Iwai
2020-05-20 11:39 ` Pavel Machek
2020-05-20 11:43 ` Takashi Iwai
2020-06-07 15:58 ` Alex Xu (Hello71)
2020-06-08 6:19 ` Christoph Hellwig
2020-06-08 13:53 ` Alex Xu (Hello71)
2020-06-09 2:31 ` David Rientjes
2020-06-09 5:43 ` Christoph Hellwig
2020-06-09 8:05 ` Takashi Iwai
2020-06-09 8:43 ` Christoph Hellwig
2020-06-09 9:09 ` Takashi Iwai
2020-06-09 9:17 ` Christoph Hellwig
2020-06-09 9:31 ` Takashi Iwai
2020-06-09 11:02 ` Takashi Iwai
2020-06-09 11:31 ` Christoph Hellwig
2020-06-09 11:38 ` Takashi Iwai
2020-06-09 11:40 ` Christoph Hellwig
2020-06-09 11:45 ` Takashi Iwai
2020-06-09 11:49 ` Christoph Hellwig
2020-06-09 13:16 ` Jaroslav Kysela
2020-06-10 5:26 ` David Rientjes
2020-06-10 7:14 ` Christoph Hellwig
2020-06-09 11:47 ` Christoph Hellwig
2020-06-09 15:12 ` Takashi Iwai
[not found] ` <<s5hr1uogtna.wl-tiwai@suse.de>
2020-06-11 14:51 ` Alex Xu (Hello71)
2020-06-11 17:11 ` Takashi Iwai
2020-06-13 16:25 ` Alex Xu (Hello71)
2020-06-14 9:54 ` Takashi Iwai
2020-06-14 12:07 ` Alex Xu (Hello71)
2020-06-14 15:40 ` Takashi Iwai
2020-06-11 14:51 ` Alex Xu (Hello71)
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=20200521074110.GA3895@amd.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).