Re: Kernel 4.13 is broken on m68k

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/05/2017 12:43 AM, Andreas Schwab wrote:
On Okt 04 2017, John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx> wrote:

Ok, switching just the initrd to the one from 4.13 while keeping the 4.12 kernel
image results in the same crash. Maybe the glibc is broken?

It's busybox.  Try setting BUSYBOX=n in
/etc/initramfs-tools/initramfs.conf (or deinstall busybox).

Indeed. I also just found that out.

$ busybox ash -c 'echo ${x}'
ash: syntax error: missing '}'

Thanks. That's a very handy testcase.

busybox has gotten new maintainers in Debian and they have stripped
"-O2" from CFLAGS so that it's building with "-Os" now [1].

Maybe that caused the code to be miscompiled. I hope I won't have
to bisect busybox.

Adrian

[1] https://anonscm.debian.org/cgit/d-i/busybox.git/commit/?id=8a115a910fb3cd7a525972e150a32f8aeb1da492

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@xxxxxxxxxx
`. `'   Freie Universitaet Berlin - glaubitz@xxxxxxxxxxxxxxxxxxx
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux