Re: How to collect debug information while booting kernel on powerpc 32 bit
On 7/1/20 4:51 PM, Giuseppe Sacco wrote: > How may I debug the problem? I tried a lot of kernel parameters without > having any additional information on the screen. Would it be helpful to > connect a serial cable (where?), use it to connect a console, and get > more info? Is there any parameter that may be used for collecting more > information when creating the initrd image? Try setting up a netconsole [1][2], that usually works just fine. Adrian > [1] https://wiki.ubuntu.com/Kernel/Netconsole > [2] https://www.kernel.org/doc/Documentation/networking/netconsole.txt -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
How to collect debug information while booting kernel on powerpc 32 bit
Hello, I cannot boot a powerbook g4 with kernels more recent than 3.16. Using 5.6 and 5.7 from sid, the system blocks after printing these lines: pmac32_cpufreq: registering PowerMac CPU frequency driver pamc32_cpufreq: Low: 667 MHz, High: 867 Mhz, Boot: 667 MHz I opened a bug report (#963689) but I would like to contribute more information. How may I debug the problem? I tried a lot of kernel parameters without having any additional information on the screen. Would it be helpful to connect a serial cable (where?), use it to connect a console, and get more info? Is there any parameter that may be used for collecting more information when creating the initrd image? Thank you, Giuseppe
GCC and binutils plans for bullseye
Debian bullseye will be based on a gcc-10 package taken from the gcc-10 upstream branch, and binutils based on a binutils package taken from the 2.35 branch. I'm planning to make gcc-10 the default after gcc-10 (10.2.0) is available (upstream targets mid July). binutils will be updated before making the GCC switch. The GCC 10 switch involves some minor library transitions for D, gccgo, M2, which should be no-brainers. The gnat transition will be handled separately by the debian Ada maintainers. binutils should be pretty stable until the bullseye release, not planning an update to 2.36. GCC 10 should be updated to 10.3, or close to 10.3 (the release date is not yet known, could be Feb 2021). I'd like to get rid off GCC 8 and GCC 9 for the bullseye release. Matthias
