On Fri, Sep 26, 2014 at 08:30:32AM -0600, Shuah Khan wrote: > On 09/26/2014 08:25 AM, Johannes Stezenbach wrote: > > > > So, what is happening is that the em28xx driver still async initializes > > while the initramfs already has started resume. Thus the rootfs in not > > mounted and the firmware is not loadable. Maybe this is only an issue > > of my qemu test because I compiled a non-modular kernel but don't have > > the firmware in the initramfs for testing simplicity? > > > > > > Right. We have an issue when media drivers are compiled static > (non-modular). I have been debugging that problem for a while. > We have to separate the two cases - if you are compiling em28xx > as static then you will run into the issue. So I compiled em28xx as modules and installed them in my qemu image. One issue solved, but it still breaks after resume: [ 20.212162] usb 1-1: reset high-speed USB device number 2 using ehci-pci [ 20.503868] em2884 #0: Resuming extensions [ 20.505275] em2884 #0: Resuming video extensionem2884 #0: Resuming DVB extension [ 20.533513] drxk: status = 0x439130d9 [ 20.534282] drxk: detected a drx-3913k, spin A2, xtal 20.250 MHz [ 23.008852] em2884 #0: writing to i2c device at 0x52 failed (error=-5) [ 23.011408] drxk: i2c write error at addr 0x29 [ 23.013187] drxk: write_block: i2c write error at addr 0x8303b4 [ 23.015440] drxk: Error -5 while loading firmware [ 23.017291] drxk: Error -5 on init_drxk [ 23.018835] em2884 #0: fe0 resume 0 Any idea on this? 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
