[beagleboard] Re: 4.4 kernel regression when installing Debian jessie
I just tried with 4.6, using netinstall's --use-testing-kernel, and can confirm this particular issue is gone; my thanks to Robert C Nelson for the hint. Le jeudi 5 mai 2016 20:07:50 UTC+2, tz.s...@gmail.com a écrit : > > Hello, > > When using Robert C Nelson's netinstall script to setup a BB xm (rev C), > the following occurs at 73% of step "Installing the base system": > > [ 888.240295] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! > [kswapd0:30] > [ 916.240295] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! > [kswapd0:30] > [ 944.240295] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! > [kswapd0:30] > > This message keeps repeating. This bug can be reproduced every time, and > the board remains stuck at this point. > > This appears to be a kernel regression that happened sometime between 4.1 > and 4.4 (the version with the bug > being linux-image-4.4.8-armv7-x6). When switching > to linux-image-4.1.23-armv7-x7 with the --use-lts-4_1-kernel, > installation proceeds correctly. So until this bug is better understood > and fixed, I recommend to other BB xm > users to avoid the latest 4.4 kernel and stick to 4.1 or older. > > Best regards, > > Tziang > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/06818877-2c5f-4ce5-9089-bc8dda8da870%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: v4.4.x-ti changes (r25+)
Hello Robert, This is really useful, thanks. I'll consider 3.14 instead as you suggest, and 4.6 too. Best regards, Tziang > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1f2c6077-d043-43f8-beb1-ed744772fb1a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: v4.4.x-ti changes (r25+)
Hello Robert, This is excellent news! I hope this fixes the installation issue I just reported for the BB xm, will give it a try when the deb become available. Best regards, Tziang -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5732c5a6-5e51-4910-a2a1-799952f14796%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] 4.4 kernel regression when installing Debian jessie
Hello, When using Robert C Nelson's netinstall script to setup a BB xm (rev C), the following occurs at 73% of step "Installing the base system": [ 888.240295] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kswapd0:30] [ 916.240295] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kswapd0:30] [ 944.240295] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:30] This message keeps repeating. This bug can be reproduced every time, and the board remains stuck at this point. This appears to be a kernel regression that happened sometime between 4.1 and 4.4 (the version with the bug being linux-image-4.4.8-armv7-x6). When switching to linux-image-4.1.23-armv7-x7 with the --use-lts-4_1-kernel, installation proceeds correctly. So until this bug is better understood and fixed, I recommend to other BB xm users to avoid the latest 4.4 kernel and stick to 4.1 or older. Best regards, Tziang -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/86c43cb6-22ba-43c6-93f5-c124db8db306%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Difference between -ti and bone* kernel?
Hello Robert, Thanks for the fast reply. I'm unsure what you mean by "sgx = no comment". Is sgx no longer officially supported by TI? Also I would like to provide more light about my building issues with the stock Graphics SDK provided by TI: - issue 1: "error: implicit declaration of function fb2display" occurred because I forgot to add TI_PLATFORM=ti335x. The complete command line is make GRAPHICS_INSTALL_DIR=/home/tzsw/Graphics_SDK_5_01_01_02 KERNEL_INSTALL_DIR=/home/tzsw/ti-linux-kernel BUILD=release OMAPES=8.x FBDEV=yes TI_PLATFORM=ti335x all - issue 2: "fatal error: omapfb/omapfb.h: No such file or directory" is a known issue with the TI Graphics SDK. Does TI not test its SDK against its kernel? Robert C Nelson's ti-sdk-pvr repository on github has the fix, in particular the 5.01.01.01-ti branch: https://github.com/RobertCNelson/ti-sdk-pvr/commits/5.01.01.01-ti Tziang -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/af6173ed-2453-42be-aa32-ba4b5f8ae938%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Difference between -ti and bone* kernel?
Hello all,
I've noticed some bad HDMI jitter/flickering when using the -bone kernel,
which is present both in 3.14 and latest 4.1. However this flickering is
not present when using the -ti kernel, regardless of the version; the -ti
version is used by default in rcn's netinstall script. Unfortunately,
building sgx modules fails with the -ti kernel ("error: implicit
declaration of function fb2display") but works fine, using the same SDK,
when using -bone kernel as compiled with rcn's bb-kernel repo (branch
am33x-3.14).
Therefore I'm wondering what is ultimately the difference between those two
(isn't it a waste of effort to maintain two separate kernels?), and if any
of you had a solution for this build issue. Hopefully I'd like to use the
kernel with the least bugs, which seems to be -ti so far regarding HDMI.
Nonetheless I'd like to thank Robert C. Nelson for his work and in
particular the very useful netinstall/bb-kernel repos.
Best regards,
Tziang
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/f80d3cc8-2bf3-4620-aae5-4b2363f4344d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
