From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>, x86@kernel.org
Subject: 5.3-rc2: hang when closing chromium?
Date: Thu, 1 Aug 2019 21:00:15 +0200 [thread overview]
Message-ID: <20190801190015.GA20288@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
Hi!
It seems 5.3-rc2 on x220 (running 32bit userland) hangs when I attempt
to close web browser (chromium). It happened twice so far.
Syslog says:
Aug 1 20:31:00 duo systemd[1]: Failed to start RealtimeKit Scheduling
Policy Service.
Aug 1 20:31:00 duo systemd[1]: Unit rtkit-daemon.service entered
failed state.
Aug 1 20:31:25 duo dbus[3342]: [system] Failed to activate service
'org.freedesktop.Realtim
eKit1': timed out
Aug 1 20:33:39 duo pulseaudio[4056]: ALSA woke us up to write new
data to the device, but t
here was actually nothing to write!
Aug 1 20:33:39 duo pulseaudio[4056]: Most likely this is a bug in the
ALSA driver 'snd_hda_
intel'. Please report this issue to the ALSA developers.
Aug 1 20:33:39 duo pulseaudio[4056]: We were woken up with POLLOUT
set -- however a subsequ
ent snd_pcm_avail() returned 0 or another value < min_avail.
Aug 1 20:35:01 duo CRON[6567]: (root) CMD (command -v debian-sa1 >
/dev/null && debian-sa1
1 1)
Aug 1 20:37:24 duo systemd[1]: Starting Cleanup of Temporary
Directories...
Aug 1 20:37:24 duo systemd[1]: Started Cleanup of Temporary
Directories.
Aug 1 20:46:26 duo rsyslogd: [origin software="rsyslogd"
swVersion="8.4.2" x-pid="3274" x-info="http://www.rsyslog.com"] start
...so nothing from the crash.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
reply other threads:[~2019-08-01 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190801190015.GA20288@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 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.