Need Source Associated with Netinstall

Hello,

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:

[238639.139831] d_can d_can.1: can0: obj no:57, msgval:0xffffffff

[238639.336364] d_can d_can.1: can0: obj no:58, msgval:0xffffffff

[238639.539703] d_can d_can.1: can0: obj no:59, msgval:0xffffffff

[238639.739807] d_can d_can.1: can0: obj no:60, msgval:0xffffffff

[238639.938537] d_can d_can.1: can0: obj no:61, msgval:0xffffffff

[238640.137023] d_can d_can.1: can0: obj no:62, msgval:0xffffffff

[238640.339965] d_can d_can.1: can0: obj no:63, msgval:0xffffffff

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?

Configuration Information:

  • kernel rev: 3.2.42-psp27

  • distro: Ubuntu 12.10

Thanks!

(via: raw src)
Grab v3.2.0 from:
kernel.org

patch/defconfig from:
http://rcn-ee.net/deb/quantal-armhf/v3.2.42-psp27/

(or)
My build repo:
https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.2

Regards,

Thanks for responding Robert.

I had already assumed that I was going to make use of your build repo: https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.2

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?

Thanks for responding Robert.

I had already assumed that I was going to make use of your build repo:
https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.2

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:
https://github.com/RobertCNelson/linux-dev/commit/cba06f45b51891ba9dff1f26d41fc69bf46c7714

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?

Probably.. Just do to get all changes...

git checkout master -f
git branch -D tmp | true
git pull
git checkout origin/am33x-v3.2 -b tmp

Also, once I acquire the source and modify, do I just run tools/rebuild.sh?

Start the build first with "./build_kernel.sh" it'll populate the
KERNEL directory with source/patch/config..

After-which, you can make modifications and re-build with
"./tools/rebuild.sh" without worrying about losing your modifications.

Regards,

OK. Thanks again. Looks like I am all set.

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.

Confirmed. The config setting described above disables CAN device driver logging.