On 7/25/19 12:27 PM, Tom Prohaszka wrote: > Here is the backtrace: > > can1 456 [8] 0F 00 00 00 00 00 00 00 > can1 354 [8] 0F 00 00 00 00 00 00 00 > can1 331 [8] 0F 00 00 00 00 00 00 00 > can1 234 [8] 01 00 00 00 00 00 00 00 > can1 044 [8] 00 00 00 00 00 00 07 00 > can1 354 [8]^C can1 456 [8] 0F 00 00 00 00 00 00 00 Do you reproduce the problem by pressing Ctrl+c? > root@ccimx6ulcvdp:~/tmp# BUG: using __this_cpu_add() in preemptible > [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 > BUG: using __this_cpu_add() in preemptible [00000000] code: irq/194-mcp25xx/805 Hmm according to the code, it should print a backtrace here... See https://elixir.bootlin.com/linux/v4.9.65/source/lib/smp_processor_id.c#L46 > preempt_disable_notrace(); > > if (!printk_ratelimit()) > goto out_enable; > > printk(KERN_ERR "BUG: using %s%s() in preemptible [%08x] code: %s/%d\n", > what1, what2, preempt_count() - 1, current->comm, current->pid); > > print_symbol("caller is %s\n", (long)__builtin_return_address(0)); > dump_stack(); Can you enable some of the in-kernel debugging stuff: Kernel hacking -> Memory Debugging -> Debug object operations (everyting) -> Kernel memory leak detector (enable) -> Debug preemptible kernel (enable) -> Lock Debugging (spinlocks, mutexes, etc...) (everything, but not the self tests) -> Stack backtrace support (enable) .. and send output when it breaks. Marc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
Attachment:
signature.asc
Description: OpenPGP digital signature
