If you are using the CAN device and the c_can driver, then implementing the
kernel mod and re-building/re-installing would seem to be your only option.
If you need to use CAN and can use a USB-to-CAN adapter, or some other
serial-to-CAN adapter, then maybe you could get around this problem.
Hello again...
Never mind any of the stuff I previously mentioned regarding changing of
the kernel config parameters. The problem is rooted in my original comment
about the c_can driver. There is a patch that exists that solves this
problem. Unfortunately, it was inserted into the mainline
Those config parameters are used for the kernel build. They are part of a
huge collection of compiler flags used for controlling how the kernel is
built.
In your initial post, I noticed that you mentioned you were using a custom
kernel; therefore, I assumed that you understood how to modify
The only reason I know we're using a custom kernel is because our former
Linux guy told me so. Never recompiled a kernel before but I have a
cursory grasp of what's involved.
Former coworker's linux laptop has a folder named Robert C Nelson that
contains what seems to be the custom kernel mod
My kernel is no longer crashing. Unfortunately, I do not have the exact
work-around - as I was messing around with a lot of stuff to try to get
this to work.
The one thing consistent in all this is the backtrace (/var/log/kern.log)
in that the routine c_can_get_berr_counter is doing something
Note that there are plenty of other things in my kernel config. I only
showed the differences between the original (when I would get kernel panic)
and the modified (no kernel panic).
On Wednesday, November 26, 2014 10:07:00 AM UTC-5, beagler001 wrote:
My kernel is no longer crashing.
Complete newbie - where can I find these config parameters?
--
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
No solution here yet, but I have found some very relevant discussions out
there. Something must have changed with the kernel scheduler that requires
drivers (CAN in our case) to be updated. I copied the BeagleBone kernel
support guru to this post (Robert Nelson). Perhaps he is already aware of
Thanks, very informative links, particularly the last one.
On Friday, November 21, 2014 8:09:41 AM UTC-7, beagler001 wrote:
No solution here yet, but I have found some very relevant discussions out
there. Something must have changed with the kernel scheduler that requires
drivers (CAN in
Hello Me Nee,
Yes. I am having the same problem. How are you doing on this? Have you
figured anything out?
I too am using the CAN interface on the BeagleBone Black device.
Let me know, and I can update you with my findings if you still need help.
On Thursday, November 13, 2014 12:41:48 PM
Haven't figured a software way around this yet. For now we're avoiding the
direct CAN interface to the Beaglebone and instead using our external
custom hardware to relay serial CAN messages to the Beaglebone. We don't
have issues with this format.
That said, if you have a fix I'd love to
11 matches
Mail list logo
