From: Pavel Machek <pavel@ucw.cz>
To: pali.rohar@gmail.com, sre@debian.org, sre@ring0.de,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com
Subject: 4.0-rc1 to -rc4: random sound and speed problems on n900
Date: Tue, 31 Mar 2015 09:26:20 +0200 [thread overview]
Message-ID: <20150331072620.GA30788@amd> (raw)
Hi!
4.0-rc4 (or more specifically 7b09ac704bac2de5bf0362793edc22a0094e381c
based kernel boots really really slowly on n900, and there's an ugly
backtrace from sound in the dmesg.
I re-tested 4.0-rc4 and it worked ok. Weird. I guess we have some
random stuff going on during boot....
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.0-rc1 to -rc4: random sound and speed problems on n900
Date: Tue, 31 Mar 2015 09:26:20 +0200 [thread overview]
Message-ID: <20150331072620.GA30788@amd> (raw)
Hi!
4.0-rc4 (or more specifically 7b09ac704bac2de5bf0362793edc22a0094e381c
based kernel boots really really slowly on n900, and there's an ugly
backtrace from sound in the dmesg.
I re-tested 4.0-rc4 and it worked ok. Weird. I guess we have some
random stuff going on during boot....
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2015-03-31 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 7:26 Pavel Machek [this message]
2015-03-31 7:26 ` 4.0-rc1 to -rc4: random sound and speed problems on n900 Pavel Machek
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=20150331072620.GA30788@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=sre@debian.org \
--cc=sre@ring0.de \
--cc=tony@atomide.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.