public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Philippe Troin <phil@fifi.org>,
	Mohamed Ikbel Boulabiar <boulabiar@gmail.com>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: webcam problem after suspend/hibernate
Date: Sun, 11 Apr 2010 17:44:37 +0200	[thread overview]
Message-ID: <20100411154437.GA16098@elf.ucw.cz> (raw)
In-Reply-To: <201004111253.58237.laurent.pinchart@ideasonboard.com>

Hi!

> > > My testing shows that:
> > >  1. If I remove uvcvideo BEFORE suspend and reinsert it after resume,
> > >  
> > >     it works.  However, I cannot always rmmod uvcvideo before suspend
> > >     as it may be in use.
...
> > > I think uvcvideo is failing to reinitialize the camera on resume, and
> > > forcing an uvcvideo "reset" with either of these three methods kicks
> > > uvcvideo into working again.
> > 
> > Ok, that puts the problem firmly into uvcvideo area.
> 
> No, it doesn't.

I believe that the fact that rmmod/insmod fixes it means that problem
is in the driver (and not in ehci or something like that).

> First of all, the dmesg output available on pastebin.com is difficult to 
> understand. As it seems you perform several suspend/resume cycles there. 
> Mohamed, could you please
> 
> - clear the kernel log ('dmesg -c' as root)
> - suspend and resume your system
> - post the kernel log content ('dmesg')
> - clear the kernel log
> - try to use your webcam with whatever test software your prefer
> - describe the failure (application error messages, ...)
> - post the kernel log content

Good idea.

> > Try changing its _resume routine to whatever is done on device
> > unplug... it should be rather easy, and is quite close to "correct"
> > solution.
> 
> That's not a solution. Devices are supposed to resume properly without being 
> reset. The camera might be crashing, or the USB core might be doing something 
> wrong, requiring some kind of reset. I'd like to diagnose the problem 
> correctly before trying to fix it.

Ok. (You are right that simulating rmmod/insmod is not the same as
proper suspend/resume support, but I still guess it would help with
debugging.)
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2010-04-11 15:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 21:55 webcam problem after suspend/hibernate Mohamed Ikbel Boulabiar
2010-03-30 23:25 ` Laurent Pinchart
2010-03-31 19:51   ` Mohamed Ikbel Boulabiar
2010-04-01 16:56     ` Pavel Machek
2010-04-01 17:05       ` Philippe Troin
2010-04-04 13:22         ` Pavel Machek
2010-04-04 18:58           ` Philippe Troin
2010-04-04 19:34             ` Pavel Machek
2010-04-06  9:32               ` Mohamed Ikbel Boulabiar
2010-04-06 13:30                 ` Pavel Machek
2010-04-11 10:53               ` Laurent Pinchart
2010-04-11 15:44                 ` Pavel Machek [this message]

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=20100411154437.GA16098@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=boulabiar@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=phil@fifi.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox