-
Notifications
You must be signed in to change notification settings - Fork 5.2k
i2c_bcm2708 crashed #804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The Raspberry Pi kernel is already updated to prevent this from happening. You appear to be running Archlinux, is that correct? |
Actually I think the fix is #780 which I've only just merged. |
Can you run rpi-update and test? That includes #780. |
Closing due to no response. Please reopen if still an issue with updated firmware. |
popcornmix
pushed a commit
that referenced
this issue
Aug 20, 2015
The clocks need to be prepared before being enabled. Without it a warning appears in the drivers probe path : WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:707 clk_core_enable+0x84/0xa0() Modules linked in: CPU: 0 PID: 1 Comm: swapper Not tainted 4.2.0-rc3-cm-x300+ #804 Hardware name: CM-X300 module [<c000ed50>] (unwind_backtrace) from [<c000ce08>] (show_stack+0x10/0x14) [<c000ce08>] (show_stack) from [<c0017eb4>] (warn_slowpath_common+0x7c/0xb4) [<c0017eb4>] (warn_slowpath_common) from [<c0017f88>] (warn_slowpath_null+0x1c/0x24) [<c0017f88>] (warn_slowpath_null) from [<c02d30dc>] (clk_core_enable+0x84/0xa0) [<c02d30dc>] (clk_core_enable) from [<c02d3118>] (clk_enable+0x20/0x34) [<c02d3118>] (clk_enable) from [<c0200dfc>] (pxa3xx_gcu_probe+0x148/0x338) [<c0200dfc>] (pxa3xx_gcu_probe) from [<c022eccc>] (platform_drv_probe+0x30/0x94) Signed-off-by: Robert Jarzmik <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello !
Raspberry Pi Model B with 3.18.5-2-ARCH armv6l GNU/Linux
i2c driver crashes after random time with this message:
I have posted this error already in the raspberry pi forum:
http://www.raspberrypi.org/forums/viewtopic.php?f=44&t=98176
jeanleflambeur said:
he posted me a patch:http://pastebin.com/zhz81fpM
and said i have to compile a new kernel with it. But i don't want this way.
I want to know if this is a kernel(driver) problem or my fault that the driver crashes ??
And if it is a driver bug, can you fix it in the mainline kernel ?
(Sorry I'm no kernel hacker, just programming c in userspace)
regards
Marco Oklitz
The text was updated successfully, but these errors were encountered: