From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: LMML <linux-media@vger.kernel.org>,
"Frank Schäfer" <fschaefer.oss@googlemail.com>
Subject: Re: em28xx list_add corruption reported by list debug
Date: Sun, 22 Dec 2013 18:22:42 +0200 [thread overview]
Message-ID: <52B711D2.7060608@iki.fi> (raw)
In-Reply-To: <52B710AE.2070606@iki.fi>
On 22.12.2013 18:17, Antti Palosaari wrote:
> On 22.12.2013 17:55, Mauro Carvalho Chehab wrote:
>> Em Sun, 22 Dec 2013 13:06:00 -0200
>> Mauro Carvalho Chehab <m.chehab@samsung.com> escreveu:
>>
>>> Em Sun, 22 Dec 2013 00:27:21 +0200
>>> Antti Palosaari <crope@iki.fi> escreveu:
>>>
>>>> I ran also this kind of bug. Device was PCTV 290e, which has that video
>>>> unused. I have no any analog em28xx webcam to test if that happens
>>>> here too.
>>>>
>>>> Fortunately I found one video device which does not crash nor dump
>>>> debug
>>>> bug warnings. It is some old gspca webcam. Have to look example how
>>>> those videobuf callbacks are implemented there..
>>>>
>>>> regards
>>>> Antti
>>>>
>>>>
>>>> [crope@localhost linux]$ cat /dev/video0
>>>> cat: /dev/video0: Invalid argument
>>>> [crope@localhost linux]$ cat /dev/video0
>>>> cat: /dev/video0: Device or resource busy
>>>> [crope@localhost linux]$
>>>>
>>>>
>>>> joulu 22 00:08:24 localhost.localdomain kernel: em28174 #0: no endpoint
>>>> for analog mode and transfer type 0
>>>
>>> It seems that there's something bad on em28174 registration: it
>>> should not
>>> be creating a v4l2 device, if the device is DVB only.
>>>
>>> The thing is that, when this driver was created, all devices were either
>>> analog only or hybrid. Only very recently, pure DVB devices got added.
>>>
>>> It shouldn't be that hard to split em28xx_init_dev() into a few routines
>>> that would only register v4l2 if the device has analog support.
>>>
>>> Again, this changeset:
>>> https://patchwork.linuxtv.org/patch/17967/
>>>
>>> Seems to be part of such solution, as it already splits the v4l2
>>> register logic into a separate function.
>>
>> Ok, if I didn't make any mistake, this changeset should do the trick:
>> https://patchwork.linuxtv.org/patch/21282/
>>
>> Please notice that this is compile-tested only.
>
> I started to testing that patch, but now I get following compilation
> errors:
>
> WARNING: "em28xx_detect_sensor" [drivers/media/usb/em28xx/em28xx.ko]
> undefined!
> WARNING: "em28xx_init_camera" [drivers/media/usb/em28xx/em28xx.ko]
> undefined!
> WARNING: "em28xx_resolution_set"
> [drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
> WARNING: "em28xx_colorlevels_set_default"
> [drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
> WARNING: "em28xx_set_outfmt" [drivers/media/usb/em28xx/em28xx-v4l.ko]
> undefined!
> WARNING: "em28xx_read_reg_req_len"
> [drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
> WARNING: "em28xx_wake_i2c" [drivers/media/usb/em28xx/em28xx-v4l.ko]
> undefined!
> WARNING: "em28xx_set_alternate" [drivers/media/usb/em28xx/em28xx-v4l.ko]
> undefined!
> WARNING: "em28xx_vbi_supported" [drivers/media/usb/em28xx/em28xx-v4l.ko]
> undefined!
> WARNING: "em28xx_release_resources"
> [drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
> WARNING: "em28xx_boards" [drivers/media/usb/em28xx/em28xx-v4l.ko]
> undefined!
>
> anyhow, I am not sure if those are related or not. I will re-compile
> whole kernel to see (build only media).
It builds very fast as compile caching. Errors are still there. My tree
is latest media/master + my SDR patches.
CRC d20c387c
Kernel: arch/x86/boot/bzImage is ready (#78)
ERROR: "em28xx_detect_sensor" [drivers/media/usb/em28xx/em28xx.ko]
undefined!
ERROR: "em28xx_init_camera" [drivers/media/usb/em28xx/em28xx.ko] undefined!
ERROR: "em28xx_resolution_set" [drivers/media/usb/em28xx/em28xx-v4l.ko]
undefined!
ERROR: "em28xx_colorlevels_set_default"
[drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
ERROR: "em28xx_set_outfmt" [drivers/media/usb/em28xx/em28xx-v4l.ko]
undefined!
ERROR: "em28xx_read_reg_req_len"
[drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
ERROR: "em28xx_wake_i2c" [drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
ERROR: "em28xx_set_alternate" [drivers/media/usb/em28xx/em28xx-v4l.ko]
undefined!
ERROR: "em28xx_vbi_supported" [drivers/media/usb/em28xx/em28xx-v4l.ko]
undefined!
ERROR: "em28xx_release_resources"
[drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
ERROR: "em28xx_boards" [drivers/media/usb/em28xx/em28xx-v4l.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2013-12-22 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 22:27 em28xx list_add corruption reported by list debug Antti Palosaari
2013-12-22 15:06 ` Mauro Carvalho Chehab
2013-12-22 15:55 ` Mauro Carvalho Chehab
2013-12-22 16:17 ` Antti Palosaari
2013-12-22 16:22 ` Antti Palosaari [this message]
2013-12-22 17:09 ` Mauro Carvalho Chehab
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=52B711D2.7060608@iki.fi \
--to=crope@iki.fi \
--cc=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.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.