I am trying to track down a problem where our CAN Cape drops CAN frames. It appears to be associated with a situation where the BBone clock suddenly jumps ahead. Meanwhile, part of the difficulty in trouble shooting is that the Linux ring buffer gets filled up with generic output from the ?Bosch? CAN driver; so dmesg does not yield any valuable information. Following is an example of the dmesg logs I would like to squash:
I think I know what needs to be done to keep this message from getting to the ring buffer, the problem is that I used “netinstall” to install my kernel, rootfs, etc., to my SD card, and now I need to modify part of the kernel source. I would like to make sure that I am using the exact version of the kernel source that is currently installed on my SD card. How should I go about acquiring the exact same kernel source to make the necessary modifications?
My problem is: How am I assured that “git checkout origin/am33x-v3.2” acquires 3.2.42-psp27 now, and in the future? Is there another git command I should be using to acquire a specific version? I am still a noob at git. I can see already that my git command above only got me 3.2.33-psp26. Is that because I did on a previously fetched directory?
Also, once I acquire the source and modify, do I just run tools/rebuild.sh?
Finally, once I build, just run tools/install_kernel.sh?
My problem is: How am I assured that "git checkout origin/am33x-v3.2"
acquires 3.2.42-psp27 now, and in the future?
For absolute 100% guarantee:
git checkout 3.2-psp27 -b tmp
and it'll set:
as top of your git tree..
But the branch is safe, the only thing i have planned for v3.2 is
fixes for "Ubuntu Saucy"'s gcc-4.8 which looks to be painful...
Is there another git command I
should be using to acquire a specific version? I am still a noob at git. I
can see already that my git command above only got me 3.2.33-psp26. Is that
because I did on a previously fetched directory?
FWIW: To anyone else out there in Beagle-land that would like to eliminate the pesky CAN debug messages from the Linux ring buffer, it looks like it can be done via menuconfig. Network support → CAN bus subsystem support → CAN Device Drivers; uncheck CAN devices debugging messages.
I have not tested yet, but that looks to be the culprit. I will confirm once testing is complete.