All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Brian Rogers <brian_rogers@comcast.net>
Cc: video4linux-list@redhat.com
Subject: Re: gspca "scheduling while atomic" crash
Date: Sun, 03 Aug 2008 10:33:51 +0200	[thread overview]
Message-ID: <1217752431.1714.11.camel@localhost> (raw)
In-Reply-To: <48954612.7000906@comcast.net>

On Sat, 2008-08-02 at 22:45 -0700, Brian Rogers wrote:
> I have the following device:
> Bus 007 Device 002: ID 0c45:60fc Microdia PC Camera with Mic (SN9C105)
> 
> Whether I build 2.6.27-rc1 or merge the stable branch of 
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git 
> into my Intrepid kernel (2.6.26), the system will lock up when I try to 
> get video from my webcam.
> 
> To see the kernel output, I do this in the console:
> mplayer -ao aa -tv device=v4l2:width=640:height=480:fps=30 tv://
> 
> The result is a rapid stream of two alternating messages:
> BUG: scheduling while atomic: swapper/0/0x8001???? (didn't get it all)
> bad: scheduling from the idle thread!
> 
> During this the system doesn't respond to anything. It's a Core2 Duo 
> running 64-bit Ubuntu Intrepid with 4GB of RAM. What other info should I 
> provide to investigate this problem?

Hello Brian,

I think I saw the problem: usb_control_msg() is called at interrupt
level..

I hope to have a patch this morning.

Cheers.

-- 
Ken ar c'hentañ |             ** Breizh ha Linux atav! **
Jef             |               http://moinejf.free.fr/


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

      reply	other threads:[~2008-08-03  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03  5:45 gspca "scheduling while atomic" crash Brian Rogers
2008-08-03  8:33 ` Jean-Francois Moine [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=1217752431.1714.11.camel@localhost \
    --to=moinejf@free.fr \
    --cc=brian_rogers@comcast.net \
    --cc=video4linux-list@redhat.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.