From: Johannes Stezenbach <js@linuxtv.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Shuah Khan <shuah.kh@samsung.com>,
linux-media@vger.kernel.org
Subject: Re: em28xx breaks after hibernate
Date: Fri, 26 Sep 2014 17:22:28 +0200 [thread overview]
Message-ID: <20140926152228.GA21876@linuxtv.org> (raw)
In-Reply-To: <20140926150602.GA15766@linuxtv.org>
On Fri, Sep 26, 2014 at 05:06:02PM +0200, Johannes Stezenbach wrote:
> 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?
I backed out Mauro's test patch, now it seems to work
(v3.17-rc5-734-g214635f, no patches, em28xx as modules).
But I'm not 100% sure the above was related to this,
it seemed the 930C got upset during all the testing
and I had to unplug it to get it back working.
Best Regards,
Johannes
next prev parent reply other threads:[~2014-09-26 15:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 12:53 em28xx breaks after hibernate Johannes Stezenbach
2014-09-25 13:45 ` Shuah Khan
2014-09-25 14:10 ` Mauro Carvalho Chehab
2014-09-25 15:07 ` Shuah Khan
2014-09-25 16:01 ` Johannes Stezenbach
2014-09-25 17:36 ` Johannes Stezenbach
2014-09-25 18:01 ` Shuah Khan
2014-09-25 17:40 ` Shuah Khan
2014-09-25 18:17 ` Johannes Stezenbach
2014-09-25 18:45 ` Shuah Khan
2014-09-25 19:03 ` Shuah Khan
2014-09-26 7:41 ` Johannes Stezenbach
2014-09-26 8:00 ` Johannes Stezenbach
2014-09-26 8:08 ` Johannes Stezenbach
2014-09-26 10:14 ` Mauro Carvalho Chehab
2014-09-26 11:07 ` Johannes Stezenbach
2014-09-26 11:42 ` Mauro Carvalho Chehab
2014-09-26 12:02 ` Johannes Stezenbach
2014-09-26 12:11 ` Mauro Carvalho Chehab
2014-09-26 12:03 ` Mauro Carvalho Chehab
2014-09-26 12:27 ` Johannes Stezenbach
2014-09-26 13:12 ` Mauro Carvalho Chehab
2014-09-26 13:25 ` Johannes Stezenbach
2014-09-26 14:25 ` Shuah Khan
2014-09-26 14:25 ` Johannes Stezenbach
2014-09-26 14:30 ` Shuah Khan
2014-09-26 15:06 ` Johannes Stezenbach
2014-09-26 15:22 ` Johannes Stezenbach [this message]
2014-09-26 15:43 ` Mauro Carvalho Chehab
2014-09-28 10:55 ` Johannes Stezenbach
2014-09-28 11:12 ` Mauro Carvalho Chehab
2014-09-28 11:54 ` Johannes Stezenbach
2014-09-28 12:35 ` Mauro Carvalho Chehab
2014-09-28 12:57 ` Mauro Carvalho Chehab
2014-09-29 2:38 ` Mauro Carvalho Chehab
2014-09-26 15:22 ` Shuah Khan
2014-09-26 15:35 ` Mauro Carvalho Chehab
2014-09-26 15:40 ` Mauro Carvalho Chehab
2014-09-26 15:42 ` Johannes Stezenbach
2014-09-26 15:48 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140926152228.GA21876@linuxtv.org \
--to=js@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=shuah.kh@samsung.com \
--cc=shuahkh@osg.samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.