From: jrnieder@gmail.com (Jonathan Nieder)
To: linux-arm-kernel@lists.infradead.org
Subject: Dockstar fails to boot since v3.0-rc6-6-g3835d69
Date: Thu, 6 Sep 2012 00:18:06 -0700 [thread overview]
Message-ID: <20120906071806.GA383@mannheim-rule.local> (raw)
In-Reply-To: <1346915288@msgid.manchmal.in-ulm.de>
Christoph Biedl wrote:
> Comparing .config and playing
> suggests that disabling CONFIG_ARM_PATCH_PHYS_VIRT is a least a
> workaround. Anything more I can test?
Hmm, my previous reaction might have been premature --- this might
be [1] after all. Any idea why 3835d69a6c70 affected anything? If
you take a .config that reproduced this and try
git checkout 3835d69a6c70^
make deb-pkg
does that give you a non-broken kernel?
Do you use uBoot, and if so, what version? If not, what bootloader?
Thanks,
Jonathan
[1] https://bugzilla.kernel.org/show_bug.cgi?id=42680
next prev parent reply other threads:[~2012-09-06 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 5:40 Dockstar fails to boot since v3.0-rc6-6-g3835d69 Andrew Lunn
2012-09-06 7:10 ` Christoph Biedl
2012-09-06 7:18 ` Jonathan Nieder [this message]
2012-09-06 17:28 ` Christoph Biedl
-- strict thread matches above, loose matches on Subject: below --
2012-09-05 20:37 Christoph Biedl
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=20120906071806.GA383@mannheim-rule.local \
--to=jrnieder@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).