On 20.09.2011 03:29, Remco Rijnders wrote:
> On Thu, Sep 08, 2011 at 08:53:19AM +0200, Alexey wrote in
> <4e68665f.3090...@fisher-privat.net>:
>> Am 08.09.2011 08:07, schrieb Remco Rijnders:
>>> On Thu, Sep 08, 2011 at 07:49:00AM +0200, Alexey wrote in
>>> <4e68574c.6020...@fisher-privat.net>:
>>>> Hi,
>>>>
>>>> to get the idea of what is wrong here, we need at least dmesg. If you
>>>> can't provide dmesg, but you can compile kernel, do git bisect.
>>>
>>
>> You can use netconsole:
>> http://www.tocpcs.com/howto-log-a-kernel-panic-it-can-be-done/
>>
>> or attach usb-serial adapter and log the dmegs over serial on other
>> computer
>> For both his methods you need  second computer.
>>
>> or boot in verbose mode, no splash screen or so, and make a photo of
>> log from display.  Here you will need only one computer.
> 
> Hi,
> 
> Apologies for the late revert. I've been busy with other things and
> spent too much time on trying to get netconsole working without luck.
> Anyways, using git bisect I came to the following result:
> 
> [remmy@ketelbinkie uvcvideo]$ git bisect bad
> a96aa5342d575980e5b572cde88036f3a878ebee is the first bad
> commit                                                                        
>                                                                           
> commit
> a96aa5342d575980e5b572cde88036f3a878ebee                                      
>                                                                               
>                                                
> Author: Laurent Pinchart
> <laurent.pinch...@ideasonboard.com>                                           
>                                                                               
>                              
> Date:   Tue Jun 28 18:17:48 2011
> -0300                                                                         
>                                                                               
>                      
>                                                                               
>                                                                               
>                                                       
>     [media] uvcvideo: Ignore entities for terminals with no supported
> format                                                                        
>                                                               
>                                                                               
>                                                                               
>                                                       
>     If a streaming interface has no supported format, the driver
> won't                                                                         
>                                                                    
>     create a video device for the associated terminal. Fix an oops
> by                                                                            
>                                                                  
>     ignoring that terminal when creating links between
> entities.                                                                     
>                                                                              
>                                                                               
>                                                                               
>                                                       
>     Signed-off-by: Laurent Pinchart
> <laurent.pinch...@ideasonboard.com>                                           
>                                                                               
>                   
>     Signed-off-by: Mauro Carvalho Chehab
> <mche...@redhat.com>                                                          
>                                                                               
>              
>                                                                               
>                                                                               
>                                                       
> :040000 040000 0296cc04d3923f1f93205ac6164802b514ad3162
> b4753a4e36122dc9605bcb44caa4aa1328146d0d M      drivers  
> 
> I'm not 100% sure that this is the proper commit as the kernel crashes
> at a later point (at the KDM login screen) than in my initial
> observation where it would not even complete booting.
> 
> Furthermore, while doing the git bisect good thing, at the last point I
> had to do "make CONFIG_DEBUG_SECTION_MISMATCH=y" as the kernel would not
> compile without it anymore.
> 
> That said, I notice that the kernel panic this kernel resulted in is
> very similar to that which gudvinr reported on the 11th, also with an
> ASUS system so I am beginning to see a pattern there.
> 
> Some fuzzy screenshots:
> 
> http://milkzilla.webconquest.com/~remmy/UVC/1.jpg
> http://milkzilla.webconquest.com/~remmy/UVC/2.jpg
> 
> Please let me know if I can do anything further to help debug this. For
> now I have disabled the camera in the bios which allows me to otherwise
> use the computer as normal but I suspect there are quite a few people
> out there who bump into similar issues.
> 
> Thanks and regards,


Can you please try this patch?

Regards,
Alexey
diff --git a/drivers/media/video/uvc/uvc_entity.c b/drivers/media/video/uvc/uvc_entity.c
index 48fea37..29e2399 100644
--- a/drivers/media/video/uvc/uvc_entity.c
+++ b/drivers/media/video/uvc/uvc_entity.c
@@ -49,7 +49,7 @@ static int uvc_mc_register_entity(struct uvc_video_chain *chain,
 		if (remote == NULL)
 			return -EINVAL;
 
-		source = (UVC_ENTITY_TYPE(remote) != UVC_TT_STREAMING)
+		source = (UVC_ENTITY_TYPE(remote) == UVC_TT_STREAMING)
 		       ? (remote->vdev ? &remote->vdev->entity : NULL)
 		       : &remote->subdev.entity;
 		if (source == NULL)
_______________________________________________
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Reply via email to