From: "Jerome Lacoste" <jerome.lacoste@gmail.com>
To: "Oliver Neukum" <oneukum@suse.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: khubd taking 100% CPU after unproperly removing USB webcam
Date: Tue, 16 Jan 2007 11:03:39 +0100 [thread overview]
Message-ID: <5a2cf1f60701160203j6dc5911fsddcb1e1babc6ae98@mail.gmail.com> (raw)
In-Reply-To: <200701161046.29262.oneukum@suse.de>
On 1/16/07, Oliver Neukum <oneukum@suse.de> wrote:
> Am Dienstag, 16. Januar 2007 10:10 schrieb Jerome Lacoste:
> > Hi,
> >
> > I unplugged my (second) webcam, forgotting to stop ekiga, and khubd is
> > now taking 100% CPU.
> >
> > - lsusb doesn't return
> > - /etc/init.d/udev restart didn't resolve the problem.
> >
> > Is that a problem one may want to investigate or should I just forget
> > about it (problem being cause by a user error)?
>
> If your are using this driver
> http://mxhaard.free.fr/download.html
>
> then it appears that it most likely hanging here:
>
> for (n = 0; n < SPCA50X_NUMFRAMES; n++)
> if (waitqueue_active(&spca50x->frame[n].wq))
> wake_up_interruptible(&spca50x->frame[n].wq);
> if (waitqueue_active(&spca50x->wq))
> wake_up_interruptible(&spca50x->wq);
> gspca_kill_transfert(spca50x);
> PDEBUG(3, "Disconnect Kill isoc done");
> up(&spca50x->lock);
> while (spca50x->user)
> schedule();
>
> This driver's disconnect handling is buggy. As this is an out of tree
> driver, please contact the original author.
OK thanks for your answer.
I also found out that ekiga was still running. I killed it and that
stopped the hang.
Jerome
prev parent reply other threads:[~2007-01-16 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 9:10 khubd taking 100% CPU after unproperly removing USB webcam Jerome Lacoste
2007-01-16 9:17 ` Oliver Neukum
2007-01-16 9:46 ` Oliver Neukum
2007-01-16 10:03 ` Jerome Lacoste [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=5a2cf1f60701160203j6dc5911fsddcb1e1babc6ae98@mail.gmail.com \
--to=jerome.lacoste@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.de \
/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