oops in bttv
7 answers - 2660 bytes -

What I did was to call settings of the flashplayer and press on the
webcam symbol there. The system didn't crash, just this oops:
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000006
5
printing eip:
c01875b0
*pde = 00000000
: 0000 [#1]
PREEMPT SMP
Modules linked in: tuner tvaudio msp3400 bttv video_buf firmware_class ir_common
compat_ioctl32 btcx_risc tveeprom videodev v4l2_common nfs vfat fat nfsd export
fs lockd sunrpc snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq
snd_seq_device reiserfs rtc microcode radeon drm intel_agp agpgart snd_intel8x0
snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc sd_m
od usb_storage libusual usbhid uhci_hcd usbcore e100
CPU: 0
EIP: 0060:[<c01875b0>] Not tainted VLI
EFLAGS: 00010292 (2.6.18-rc1 #80)
EIP is at sysfs_add_file+0x10/0x76
eax: 00000001 ebx: f9bd6d14 ecx: 00000004 edx: f9bd6d14
esi: f9bde920 edi: 00000001 ebp: dc489eac esp: dc489e94
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 11377, ti=dc489000 task=f21ff6b0 task.ti=dc489000)
Stack: f9bde920 f9bde920 00000004 f9bde920 f9bde920 00000000 dc489eb4 c018763c
dc489ebc c0220cc3 dc489ec8 f9bc3073 c19b4800 dc489ee4 f9bc35de 00000000
20bd7818 f9bd7880 f9bd7880 ffffffed dc489ef0 c01c3c1b c19b4800 dc489f04
Call Trace:
[<c018763c>] sysfs_create_file+0x26/0x28
[<c0220cc3>]
[<f9bc3073>] bttv_register_video+0x8c/0x147 [bttv]
[<f9bc35de>] bttv_probe+0x4ab/0x593 [bttv]
[<c01c3c1b>] pci_call_probe+0xd/0x10
[<c01c3c4f>] __pci_device_probe+0x31/0x43
[<c01c3c82>] pci_device_probe+0x21/0x34
[<c0220429>] driver_probe_device+0x47/0x94
[<c0220542>] __driver_attach+0x5e/0x89
[<c021fada>] bus_for_each_dev+0x38/0x5d
[<c0220581>] driver_attach+0x14/0x16
[<c021ff2c>] bus_add_driver+0x5f/0x98
[<c02209a8>] driver_register+0x75/0x7a
[<c01c3e3e>]
[<f9bc3b3b>] bttv_init_module+0x9f/0xa1 [bttv]
[<c01325f7>] sys_init_module+0x95/0x1c5
[<c010291b>] syscall_call+0x7/0xb
[<b7ea781e>] 0xb7ea781e
Code: 01 00 00 00 6a 00 e8 f9 cf f8 ff 89 d8 e8 2f 40 fe ff 5b 8d 65 f4 5b 5e 5f
5d c3 55 89 e5 57 89 c7 56 53 89 d3 83 ec 0c 89 4d f0 <8b40 64 89 45 ec 8b 47
1c 05 84 00 00 00 0f b7 72 08 c7 45 e8
EIP: [<c01875b0>] sysfs_add_file+0x10/0x76 SS:ESP 0068:dc489e94
Gentoo, Firefox 1.5-r4, xorg 7.0-r1, Shockwave Flash 7.0 r63 plugin,
Linux Kernel from Linus GIT:
Config and full dmesg attached
No.1 | | 371 bytes |
| 
Tue, Jul 11, 2006 at 10:49:40PM +0200, Alex Riesen wrote:
What I did was to call settings of the flashplayer and press on the
webcam symbol there. The system didn't crash, just this oops:
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000006
5
Does this happen every time you modprobe bttv ?
Regards,
Frederik
No.2 | | 410 bytes |
| 
Frederik Deweerdt, Wed, Jul 12, 2006 11:44:16 +0200:
Tue, Jul 11, 2006 at 10:49:40PM +0200, Alex Riesen wrote:
What I did was to call settings of the flashplayer and press on the
webcam symbol there. The system didn't crash, just this oops:
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000006
5
Does this happen every time you modprobe bttv ?
Yep.
No.3 | | 420 bytes |
| 
Em Ter, 2006-07-11 22:49 +0200, Alex Riesen escreveu:
What I did was to call settings of the flashplayer and press on the
webcam symbol there. The system didn't crash, just this oops:
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000006
5
Hmm Are you using it on what machine? It might be related to an
improper handling at compat32 module.
Cheers,
Mauro.
No.4 | | 452 bytes |
| 
7/15/06, Mauro Carvalho Chehab <mchehab (AT) infradead (DOT) orgwrote:
What I did was to call settings of the flashplayer and press on the
webcam symbol there. The system didn't crash, just this oops:
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000006
5
Hmm Are you using it on what machine? It might be related to an
improper handling at compat32 module.
32bit. PIV, 2Gb, highmem on.
No.5 | | 1352 bytes |
| 
Nish Aravamudan wrote:
7/17/06, Alex Riesen <raa.lkml (AT) gmail (DOT) comwrote:
>7/15/06, Mauro Carvalho Chehab <mchehab (AT) infradead (DOT) orgwrote:
>What I did was to call settings of the flashplayer and press on the
>webcam symbol there. The system didn't crash, just this oops:
>>
>BUG: unable to handle kernel NULL pointer dereference at virtual
>address 0000006
>5
>Hmm Are you using it on what machine? It might be related to an
>improper handling at compat32 module.
>>
>32bit. PIV, 2Gb, highmem on.
Is this the same bug as
It LKS the same to me I have tried to reproduce this PS
unsuccessfully, but it seems to be happening for many other users.
I can't imagine why I am unable to reproduce it.
Hopefully Andrew will pull from Mauro's v4l-dvb.git for the new
changesets before he releases the next -mm
The sanity checking cleanups have already been pushed up there:
;a=commitdiff;;
You might notice a tragic flaw in the previous code
bttv_register_video was checking the return value on a void Maybe
we'll get some better debug output after this patch gets out.
Cheers,
Michael Krufky
No.6 | | 570 bytes |
| 
7/17/06, Alex Riesen <raa.lkml (AT) gmail (DOT) comwrote:
7/15/06, Mauro Carvalho Chehab <mchehab (AT) infradead (DOT) orgwrote:
What I did was to call settings of the flashplayer and press on the
webcam symbol there. The system didn't crash, just this oops:
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000006
5
Hmm Are you using it on what machine? It might be related to an
improper handling at compat32 module.
32bit. PIV, 2Gb, highmem on.
Is this the same bug as
Thanks,
Nish
No.7 | | 3640 bytes |
| 
Em Qua, 2006-07-19 13:19 -0400, Michael Krufky escreveu:
Nish Aravamudan wrote:
7/17/06, Alex Riesen <raa.lkml (AT) gmail (DOT) comwrote:
>7/15/06, Mauro Carvalho Chehab <mchehab (AT) infradead (DOT) orgwrote:
>What I did was to call settings of the flashplayer and press on the
>webcam symbol there. The system didn't crash, just this oops:
>>
>BUG: unable to handle kernel NULL pointer dereference at virtual
>address 0000006
>5
>Hmm Are you using it on what machine? It might be related to an
>improper handling at compat32 module.
>>
>32bit. PIV, 2Gb, highmem on.
Is this the same bug as
It LKS the same to me I have tried to reproduce this PS
unsuccessfully, but it seems to be happening for many other users.
I can't imagine why I am unable to reproduce it.
Also I couldn't reproduce it here. I'm testing with -rc2 + v4l/dvb git
patches available at my git tree
(;a=summary):
[ 661.840349] bttv0: using tuner=4
[ 661.849056] kobject tuner: registering. parent: <NULL>, set: module
[ 661.849111] kobject_uevent
[ 661.849125] fill_kobj_path: path = '/module/tuner'
[ 661.849535] bus i2c: add driver tuner
[ 661.849538] kobject tuner: registering. parent: <NULL>, set: drivers
[ 661.849556] kobject_uevent
[ 661.849567] fill_kobj_path: path = '/bus/i2c/drivers/tuner'
[ 661.849603] i2c-core: driver [tuner] registered
[ 661.849953] DEV: registering device: ID = 'dvb0'
[ 661.849956] kobject dvb0: registering. parent: 0000:05:06.0, set:
devices
[ 661.849976] PM: Adding info for bttv-sub:dvb0
[ 661.849991] bus bttv-sub: add device dvb0
[ 661.850002] kobject_uevent
[ 661.850013] fill_kobj_path: path =
'/'
[ 661.850043] bttv0: add subdevice "dvb0"
[ 661.850048] bound device '0000:05:06.0' to driver 'bttv'
[ 661.996816] bttv1: osprey eeprom: card=89 name= 210/220/230
serial=6166834
[ 661.996819] bttv1: using tuner=-1
[ 661.996822] bttv1: i2c: checking for TDA9887 @ 0x86 <7>i2c_adapter
i2c-1: master_xfer[0] R, addr=0x43, len=1
[ 661.998953] not found
[ 661.998966] CLASS: registering class device: ID = 'video0'
[ 661.998969] kobject video0: registering. parent: video4linux, set:
class_obj
[ 661.998997] kobject_uevent
[ 661.999008] fill_kobj_path: path = '/class/video4linux/video0'
[ 661.999011] class_uevent - name = video0
[ 661.999014] fill_kobj_path: path =
'/'
[ 661.999046] bttv1: registered device video0
[ 661.999059] CLASS: registering class device: ID = 'vbi0'
[ 661.999062] kobject vbi0: registering. parent: video4linux, set:
class_obj
[ 661.999084] kobject_uevent
[ 661.999095] fill_kobj_path: path = '/class/video4linux/vbi0'
[ 661.999098] class_uevent - name = vbi0
[ 661.999101] fill_kobj_path: path =
'/'
[ 661.999130] bttv1: registered device vbi0
[ 661.999156] bttv1: PLL: 28636363 =35468950 . ok
[ 662.015287] bound device '0000:06:04.0' to driver 'bttv'
[ 662.015305] pci: Bound Device 0000:06:04.0 to Driver bttv
Both Twinhan and boards initialized well. No oops (although -rc2
had several troubles with event devices on x86_64: mouse, keyboard and
analog gameport didn't worked at the machine - I could access only via
network connection).
Cheers,
Mauro.