On Fri, Sep 26, 2014 at 09:03:16AM -0300, Mauro Carvalho Chehab wrote: > > The patch I sent you (or some fixed version of it) is part of the > solution, but this still bothers me: > > > > [ 3.776854] [<ffffffff813f974f>] drxk_attach+0x546/0x656 > > > [ 3.777675] [<ffffffff814c22a3>] em28xx_dvb_init.part.3+0xa3e/0x1cdf > > > [ 3.778652] [<ffffffff8106555c>] ? trace_hardirqs_on_caller+0x183/0x19f > > > [ 3.779690] [<ffffffff81065585>] ? trace_hardirqs_on+0xd/0xf > > > [ 3.780615] [<ffffffff814c5b45>] ? mutex_unlock+0x9/0xb > > > [ 3.781428] [<ffffffff814c0f50>] ? em28xx_v4l2_init.part.11+0xcbd/0xd04 > > > [ 3.782487] [<ffffffff814230cf>] em28xx_dvb_init+0x1d/0x1f > > Why em28xx_dvb_init() is being called? > > That should only happen if the device is re-probed again, but > the reset_resume code should have been preventing it. Well, I stuck a WARN_ON(1) into drxk_release(), it is not called during hibernate+resume. Do you have a better suggestion to debug it? Johannes -- 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
