From: Christoffer Holmstedt <christoffer@christofferholmstedt.se>
To: linux-wpan@vger.kernel.org
Subject: RPi model B - bluetooth-next kernel, shutdown always reboots the RPi
Date: Thu, 4 Jun 2015 08:34:16 +0200 [thread overview]
Message-ID: <20150604063416.GA3045@probook-6560b> (raw)
I know some of you are using the RPi as well so I start by asking here, perhaps
linux-rpi-kernel list is the next step. When I run "shutdown -h 0" the RPi
turns off but in a few seconds U-Boot starts again and boots linux, so I can't
turn it off from software. The only solution is to pull the plug, which will
eventually corrupt the SD card so that is not a good long-term solution.
Others have had simliar problems with kernels 3.8 - 3.12 but back then it was
something about activity on some GPIO (e.g. SCL) could trigger boot. This is
not the case now as my problem exists both with the Openlabs board connected
and disconnected.
There are a lot of moving parts here, during shutdown Raspbian with 4.1.0-rcX
kernel doesn't set proper registers perhaps or U-Boot is missing some
configuration so I'm not sure how to debug this issue. Installing a fresh
raspbian installation on the SD card with 3.18 kernel "shutdown -h 0" works
just fine. As soon as I "install" U-Boot and the blutooth-next kernel it stops
working.
Any pointers to a solution, debug steps or even a tutorial on how the
shutdown/boot-up process works is appreciated, because I'm totally lost on this
one.
Regards
--
Christoffer Holmstedt
next reply other threads:[~2015-06-04 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 6:34 Christoffer Holmstedt [this message]
2015-06-04 7:41 ` RPi model B - bluetooth-next kernel, shutdown always reboots the RPi Alexander Aring
2015-06-04 9:33 ` Christoffer Holmstedt
2015-06-05 9:05 ` Guido Günther
2015-06-05 9:12 ` Alexander Aring
2015-06-08 12:29 ` Christoffer Holmstedt
2015-06-09 8:42 ` Guido Günther
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=20150604063416.GA3045@probook-6560b \
--to=christoffer@christofferholmstedt.se \
--cc=linux-wpan@vger.kernel.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 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.