summaryrefslogtreecommitdiffstats
path: root/crypto/scatterwalk.c
diff options
context:
space:
mode:
authorMichael Ellerman <mpe@ellerman.id.au>2015-03-30 08:38:09 +0200
committerMichael Ellerman <mpe@ellerman.id.au>2015-04-10 12:02:48 +0200
commit7e862d7e7d118e3becc5b495af10ca076f087180 (patch)
treebea93c57723e1db0ba9015df85c85bf070c1daa7 /crypto/scatterwalk.c
parentpowerpc: Replace mem_init_done with slab_is_available() (diff)
downloadlinux-7e862d7e7d118e3becc5b495af10ca076f087180.tar.xz
linux-7e862d7e7d118e3becc5b495af10ca076f087180.zip
powerpc: Reword the "returning from prom_init" message
We get way too many bug reports that say "the kernel is hung in prom_init", which stems from the fact that the last piece of output people see is "returning from prom_init". The kernel is almost never hung in prom_init(), it's just that it's crashed somewhere after prom_init() but prior to the console coming up. The existing message should give a clue to that, ie. "returning from" indicates that prom_init() has finished, but it doesn't seem to work. Let's try something different. This prints: Quiescing Open Firmware ... Booting Linux via __start() ... Which hopefully makes it clear that prom_init() is not the problem, and although __start() probably isn't either, it's at least the right place to begin looking. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Wistfully-Acked-by: Jeremy Kerr <jk@ozlabs.org>
Diffstat (limited to 'crypto/scatterwalk.c')
0 files changed, 0 insertions, 0 deletions