From: Marek Vasut <marek.vasut@gmail.com>
To: linux-arm-kernel@lists.infradead.org, maciej.rutecki@gmail.com
Cc: Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
thommycheck@gmail.com, dbaryshkov@gmail.com,
Cyril Hrubis <metan@ucw.cz>,
arminlitzel@web.de, kernel list <linux-kernel@vger.kernel.org>,
utx@penguin.cz, lenz@cs.wisc.edu, rpurdie@rpsys.net,
omegamoon@gmail.com, eric.y.miao@gmail.com,
zaurus-devel@www.linuxtogo.org
Subject: Re: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Date: Wed, 7 Apr 2010 22:52:08 +0200 [thread overview]
Message-ID: <201004072252.08354.marek.vasut@gmail.com> (raw)
In-Reply-To: <201004072226.34272.maciej.rutecki@gmail.com>
Dne St 7. dubna 2010 22:26:34 Maciej Rutecki napsal(a):
> On czwartek, 1 kwietnia 2010 o 08:06:25 Pavel Machek wrote:
> > Hi!
> >
> > > > I tried compiling 2.6.34-rc1, and it does not boot :-(. It does not
> > > > seem to even reset the framebuffer (I'm using kexec -- so it stays
> > > > stuck on on previous screen).
> >
> > Tried again with -rc2 and -rc3, and neither boots :-(. I did not have
> > time to set up serial console, yet :-(. Any ideas?
> > Pavel
>
> I created a Bugzilla entry at
> https://bugzilla.kernel.org/show_bug.cgi?id=15712
> for your bug report, please add your address to the CC list in there,
> thanks!
>
Pavel, you broke it ... and here you say something about sane arm maintainers
;-)
next prev parent reply other threads:[~2010-04-07 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 12:27 2.6.34-rc1 on zaurus: does it boot for you? Pavel Machek
[not found] ` <20100315102830.GA10288@atrey.karlin.mff.cuni.cz>
2010-04-01 6:06 ` [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots Pavel Machek
2010-04-07 20:26 ` Maciej Rutecki
2010-04-07 20:52 ` Marek Vasut [this message]
2010-04-08 4:44 ` Pavel Machek
2010-04-08 10:53 ` Eric Miao
2010-04-08 11:05 ` Pavel Machek
2010-04-08 12:06 ` Eric Miao
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=201004072252.08354.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=utx@penguin.cz \
--cc=zaurus-devel@www.linuxtogo.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).