Re: Fwd: improve support for usb board camera

2014-12-11 Thread Kristopher Borer
The kernel version is 3.13.0-32-generic

Here is one example:

BUG: unable to handle kernel NULL pointer dereference at...
IP: [...] xhci_stream_id_to_ring+0x40/0x60
PGD 362a1067 PUD c9f49067 PMD 0
Oops:  [#1] SMP
Modules linked in: elo_mt_input_mod(0F) eeepc_wmi ...
CPU: 1 PID: 20665 Comm: ... Tainted: GF W 0 3.13.0-32-generic #57-Ubuntu
Hardware name: ASUS All Series/B85M-E, BIOS 2105 08/08/2014
task: ...
RIP: ... xhci_stream_id_to_ring+0x40/0x60
...
Call Trace:
  IRQ
  handle_cmd_completion
  xhci_irq
  xhci_mis_irq
  handle_irq_event_percpu
  handle_irq_event
  handle_edge_irq
  handle_irq
  do_IRQ
  common_interrupt
  EOI
...
Kernel panic - not syncing: Fatal exception in interrupt
Shutting down cpus with MMI
drm_kms_helper: panic occured, switching back to text console


Thank you for your help and let me know if I should still contact the
media mailing list.

Kris


On Wed, Dec 10, 2014 at 9:00 PM, Greg KH gre...@linuxfoundation.org wrote:
 On Wed, Dec 10, 2014 at 07:35:48PM -0500, Kristopher Borer wrote:
 Hello,

 I am looking to improve support for a USB board camera. It currently
 works fairly well, but we occasionally cause kernel panics while using
 OpenCV on Ubuntu 14.04.

 What kernel version is that, and what is the oops report show?

 Here is the device: e-consystems.com/5mp-usb-cameraboard.asp

 We do not need an NDA. We can provide hardware, test scripts, and we
 have some internal engineers who can help out.

 You might do best by posting this on the linux-me...@vger.kernel.org
 mailing list, as that is where the authors for that driver are, it might
 just be a simple quirk or bugfix is needed to get this resolved.

 If that doesn't work out, please let me know.

 thanks,

 greg k-h
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel


Re: Fwd: improve support for usb board camera

2014-12-11 Thread Greg KH
On Thu, Dec 11, 2014 at 07:43:15AM -0500, Kristopher Borer wrote:
 The kernel version is 3.13.0-32-generic

Ick, that's 68 thousand patches old (i.e. one year...)

Have you tried the 3.18 kernel release to see if it is better, because:

 
 Here is one example:
 
 BUG: unable to handle kernel NULL pointer dereference at...
 IP: [...] xhci_stream_id_to_ring+0x40/0x60
 PGD 362a1067 PUD c9f49067 PMD 0
 Oops:  [#1] SMP
 Modules linked in: elo_mt_input_mod(0F) eeepc_wmi ...
 CPU: 1 PID: 20665 Comm: ... Tainted: GF W 0 3.13.0-32-generic #57-Ubuntu
 Hardware name: ASUS All Series/B85M-E, BIOS 2105 08/08/2014
 task: ...
 RIP: ... xhci_stream_id_to_ring+0x40/0x60
 ...
 Call Trace:
   IRQ
   handle_cmd_completion
   xhci_irq
   xhci_mis_irq
   handle_irq_event_percpu
   handle_irq_event
   handle_edge_irq
   handle_irq
   do_IRQ
   common_interrupt
   EOI
 ...
 Kernel panic - not syncing: Fatal exception in interrupt
 Shutting down cpus with MMI

That's a xhci (the USB 3 controller) issue, and there have been lots of
xhci fixes in the past year as new controllers have been released and we
have fixed the bugs in them.

And you are using USB 3 streams in your USB 2 camera?  That doesn't make
sense.  What camera driver is this?

Anyway, please try 3.18, that should work.  If not, let's drag this over
to the linux-...@vger.kernel.org mailing list as the xhci developers
should learn about this, it doesn't look like a media driver issue just
yet.

thanks,

greg k-h
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel


Re: Fwd: improve support for usb board camera

2014-12-10 Thread Greg KH
On Wed, Dec 10, 2014 at 07:35:48PM -0500, Kristopher Borer wrote:
 Hello,
 
 I am looking to improve support for a USB board camera. It currently
 works fairly well, but we occasionally cause kernel panics while using
 OpenCV on Ubuntu 14.04.

What kernel version is that, and what is the oops report show?

 Here is the device: e-consystems.com/5mp-usb-cameraboard.asp
 
 We do not need an NDA. We can provide hardware, test scripts, and we
 have some internal engineers who can help out.

You might do best by posting this on the linux-me...@vger.kernel.org
mailing list, as that is where the authors for that driver are, it might
just be a simple quirk or bugfix is needed to get this resolved.

If that doesn't work out, please let me know.

thanks,

greg k-h
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel