From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Linker and duplicate symbols
Date: Fri, 9 Sep 2016 09:31:46 +0100 [thread overview]
Message-ID: <d91adc155504284b4ce033bede22ece0@hamnavoe.com> (raw)
In-Reply-To: <63814C1E-B962-4221-B9E6-2B1BBDBB55F7@yahoo.ca>
> Only weird problem is when I do fshalt -r. My pi2 goes unstable with panics on reboot. Cold reset brings it back to normal.
Sorry, I have seen this failure too, but only on pi3. If you run with
*ncpu=1 the soft reboot seems to work reliably. But my scheme for
rebooting from multicore state is clearly not right. Unfortunately I
don't know of any way of forcing an arm reset after loading the new
kernel without also resetting the gpu back to the load-from-sdcard
point. I'll welcome any suggestions for a way to do this. I think
linux on the pi supports kexec, so it might be possible to reverse
engineer from that and find a way that works. On the other hand, if
you search the web for "raspbian kexec" most of the hits seem to be of
the "doesn't work" variety, so maybe not.
> Does your latest code work on Pi zero? I don't yet have one to test it.
Yes it does. If you boot different kernels from the same sdcard you need
to use [pi0] as a section header for the zero. (Discovered by trial and
error because this doesn't seem to be documented anywhere.)
next prev parent reply other threads:[~2016-09-09 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 2:34 Chris McGee
2016-09-02 10:20 ` Richard Miller
2016-09-02 15:56 ` Chris McGee
2016-09-02 16:11 ` Richard Miller
2016-09-09 0:48 ` Chris McGee
2016-09-09 8:31 ` Richard Miller [this message]
2016-09-09 14:55 ` Chris McGee
2016-09-09 16:37 ` Richard Miller
2016-09-02 16:12 ` cinap_lenrek
2016-09-02 20:00 ` Chris McGee
2016-09-02 22:34 ` Steve Simon
2016-09-03 16:58 ` Chris McGee
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=d91adc155504284b4ce033bede22ece0@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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).