Hi jow,
I already had CONFIG_KERNEL_KALLSYMS enabled (seems to be default).
However, I've checked with the file, you gave me earlier [1].
I was NOT able to reproduce the problem. I.e. buildbot's images
do not boot, while mine boot on WRT54G(L) even when using your config.
Regarding [1], I did the
Hi,
can you check whether you can reproduce the hang when you enable kernel
debugging and kernel symbols?
See
http://phase1.builds.lede-project.org/builders/brcm47xx%2Flegacy/builds/60/steps/newconfig/logs/stdio
for the things the buildbot does besides choosing a target.
~ Jo
__
Related to my last post to the list "brcm47xx legacy broken in trunk?"
I'm not sure whether "legacy broken in trunk" is the right terminology.
When I started to dig into the problem, I cloned the repo and built the
image myself. It worked immediately.
To confirm my findings, I downloaded today's
