From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [regression] 2.6.34-rc1 to -rc3 on zaurus: no longer boots
Date: Thu, 8 Apr 2010 18:53:53 +0800 [thread overview]
Message-ID: <i2mf17812d71004080353oa8459642v33f88993eee87a99@mail.gmail.com> (raw)
In-Reply-To: <20100408044409.GA14982@elf.ucw.cz>
On Thu, Apr 8, 2010 at 12:44 PM, Pavel Machek <pavel@ucw.cz> wrote:
> On Wed 2010-04-07 22:52:08, Marek Vasut wrote:
>> 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?
>> >
>> > 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
>> ;-)
>
> ? You know which patch causes it ?
Just have some time to try this out on my corgi, and the kernel runs
happily.
Pavel,
Which exact model are you running your kernel?
next prev parent reply other threads:[~2010-04-08 10:53 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
2010-04-08 4:44 ` Pavel Machek
2010-04-08 10:53 ` Eric Miao [this message]
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=i2mf17812d71004080353oa8459642v33f88993eee87a99@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).