Dear Ralph, I had a crash when testing the latest ddbridge driver. I didn't manage to get all the call trace, but I manage to get some information where the crash is coming from. It seems to be related with a irq processing problem or scheduling/power management. Using gdb and the call trace address, it shows me an origin in line 2021 from this code "tasklet_schedule(&dev->dma[0].tasklet);" : 2016 if (s & 0x00000004) 2017 irq_handle_i2c(dev, 2); 2018 if (s & 0x00000008) 2019 irq_handle_i2c(dev, 3); 2020 2021 if (s & 0x00000100) 2022 tasklet_schedule(&dev->dma[0].tasklet); 2023 if (s & 0x00000200) 2024 tasklet_schedule(&dev->dma[1].tasklet); 2025 if (s & 0x00000400) Here is a part of the call trace I managed to get: error_code init_sched_groups_power get_signal_to_deliver wake_up_common spin_lock_irqsave wake_up irq_handler+0x2a5/0x490 [ddbridge] => this translate to the code above Sebastien -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
