From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Helmut Auer <vdr@helmutauer.de>
Cc: linux-media@vger.kernel.org
Subject: Re: Kernel oops with current hg (ir-sysfs.c ?)
Date: Tue, 08 Jun 2010 23:35:21 -0300 [thread overview]
Message-ID: <4C0EFDE9.3030404@redhat.com> (raw)
In-Reply-To: <4C0D1F49.4040501@helmutauer.de>
Em 07-06-2010 13:33, Helmut Auer escreveu:
> Am 24.05.2010 17:26, schrieb Martin Dauskardt:
>> I guess it is a similar problem like the one that was solved a few months ago with this patch:
>> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/14232
>>
>> I compiled the current v4l-dvb hg against the 2.6.32 Ubuntu 10.04 kernel
>>
>>
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.629408] DVB: registering new adapter (TT-Budget C-1501 PCI)
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.646949] tda9887 3-0043: i2c i/o error: rc == -5 (should be 4)
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.649823] tda9887 3-0043: i2c i/o error: rc == -5 (should be 4)
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.666028] adapter has MAC addr = 00:d0:5c:c6:5a:11
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692518] Registered IR keymap rc-tt-1500
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692545] BUG: unable to handle kernel NULL pointer dereference at (null)
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692554] IP: [<f825bd7e>] ir_register_class+0x3e/0x190 [ir_core]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692566] *pde = 00000000
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692571] Oops: 0000 [#1] SMP
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692575] last sysfs file: /sys/module/ir_core/initstate
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692580] Modules linked in: rc_tt_1500 tda10021 snd_hda_codec_realtek tuner_simple tuner_types tda9887 tda8290 tuner msp3400 snd_hda_intel$
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692659]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692663] Pid: 375, comm: modprobe Not tainted (2.6.32-22-generic #33-Ubuntu) M56S-S3
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692669] EIP: 0060:[<f825bd7e>] EFLAGS: 00010246 CPU: 0
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692677] EIP is at ir_register_class+0x3e/0x190 [ir_core]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692681] EAX: 00000000 EBX: f6375000 ECX: 00000000 EDX: 00000100
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692686] ESI: f4fa6000 EDI: 00000000 EBP: f61d5d78 ESP: f61d5d4c
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692691] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692697] Process modprobe (pid: 375, ti=f61d4000 task=f61b6680 task.ti=f61d4000)
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692704] Stack:
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692707] 00000246 f825ba47 c24054e0 f825ba47 001d5d64 00000128 f4fa6000 0000003f
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692717] <0> faee9068 00000027 f4fa6000 f61d5db0 f825bb7c 0000009f 00000000 f8ce32ef
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692728] <0> c0588f82 f825cc11 00000296 f637513c f6375120 f6375000 f6827000 f4fa6000
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692741] Call Trace:
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692750] [<f825ba47>] ? __ir_input_register+0x167/0x350 [ir_core]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692759] [<f825ba47>] ? __ir_input_register+0x167/0x350 [ir_core]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692769] [<f825bb7c>] ? __ir_input_register+0x29c/0x350 [ir_core]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692779] [<c0588f82>] ? printk+0x1d/0x23
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692789] [<f8ce1153>] ? budget_ci_attach+0x193/0xd80 [budget_ci]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692800] [<f81ffeac>] ? saa7146_init_one+0x7dc/0x860 [saa7146]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692811] [<c01078d0>] ? dma_generic_alloc_coherent+0x0/0xc0
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692821] [<c0363883>] ? local_pci_probe+0x13/0x20
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692827] [<c0364688>] ? pci_device_probe+0x68/0x90
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692835] [<c03e688d>] ? really_probe+0x4d/0x140
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692843] [<c03ed19e>] ? pm_runtime_barrier+0x4e/0xc0
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692850] [<c03e69bc>] ? driver_probe_device+0x3c/0x60
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692857] [<c03e6a61>] ? __driver_attach+0x81/0x90
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692864] [<c03e5ea3>] ? bus_for_each_dev+0x53/0x80
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692871] [<c03e675e>] ? driver_attach+0x1e/0x20
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692877] [<c03e69e0>] ? __driver_attach+0x0/0x90
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692884] [<c03e6125>] ? bus_add_driver+0xd5/0x280
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692890] [<c03645c0>] ? pci_device_remove+0x0/0x40
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692897] [<c03e6d5a>] ? driver_register+0x6a/0x130
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692903] [<c03648c5>] ? __pci_register_driver+0x45/0xb0
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692913] [<f81fed63>] ? saa7146_register_extension+0x53/0x90 [saa7146]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692923] [<f8ce700d>] ? budget_ci_init+0xd/0xf [budget_ci]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692929] [<c0101131>] ? do_one_initcall+0x31/0x190
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692937] [<f8ce7000>] ? budget_ci_init+0x0/0xf [budget_ci]
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692945] [<c0182340>] ? sys_init_module+0xb0/0x210
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692951] [<c01033ec>] ? syscall_call+0x7/0xb
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.692956] Code: 00 89 c6 8d 80 a0 07 00 00 e8 bf a7 18 c8 ba 00 01 00 00 89 c3 b8 0c d4 25 f8 e8 6e ec 0e c8 89 c7 85 ff 78 6f 8b 83 44 01 $
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.693003] EIP: [<f825bd7e>] ir_register_class+0x3e/0x190 [ir_core] SS:ESP 0068:f61d5d4c
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.693015] CR2: 0000000000000000
>> May 24 13:30:22 ubuntuvdr1 kernel: [ 5.693020] ---[ end trace 2c915ef882a2f862 ]---
>> --I can confirm this. Loading budget_ci from current v4l-dvb hg with kernel 2.6.34 causes kernel oops:
As I've answered at the other thread, there's a fix that will likely solve this bug, already merged upstream.
The patch is available at:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=84b14f181a36eea6591779156ef356f8d198bbfd
>
> It looks to me that v4l-dvb is not really maintained anymore :(
It is maintained, but Douglas had a 2-weeks trip abroad and couldn't find time to backport
the patches during the trip. He is currently working to re-sync the backport tree with the
upstream one.
Cheers,
Mauro.
prev parent reply other threads:[~2010-06-09 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:26 Kernel oops with current hg (ir-sysfs.c ?) Martin Dauskardt
2010-06-07 16:33 ` Helmut Auer
2010-06-09 2:35 ` Mauro Carvalho Chehab [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=4C0EFDE9.3030404@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=vdr@helmutauer.de \
/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.