From: Adrian Bunk <bunk@stusta.de>
To: Diego Calleja <diegocg@gmail.com>
Cc: luca.risolia@studio.unibo.it, linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, gregkh@suse.de
Subject: Re: Oops with w9968cf
Date: Sat, 31 Dec 2005 15:32:29 +0100 [thread overview]
Message-ID: <20051231143229.GI3811@stusta.de> (raw)
In-Reply-To: <20051212151820.5656ddd8.diegocg@gmail.com>
On Mon, Dec 12, 2005 at 03:18:20PM +0100, Diego Calleja wrote:
> While playing with the webcam support in kde 3.5 (kopete), creative
> webcam go plus.... (2.6.15-rc5)
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000000c
> printing eip:
> c019b162
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT SMP
> Modules linked in: ovcamchip w9968cf videodev i2c_core ipt_REJECT radeon drm thermal fan button processor ac battery ipt_MASQUERADE iptable_nat ip_nat ip_conntrack iptable_filter ip_tables usbhid snd_ca0106 snd_rawmidi snd_seq_device snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm parport_pc floppy snd_timer parport ohci_hcd snd pcspkr usbcore e100 soundcore snd_ac97_bus snd_page_alloc
> CPU: 0
> EIP: 0060:[<c019b162>] Not tainted VLI
> EFLAGS: 00010246 (2.6.15-rc5)
> EIP is at sysfs_hash_and_remove+0x22/0xef
> eax: f4789bc8 ebx: f76338a8 ecx: c19b2d40 edx: c533de44
> esi: 00000000 edi: f6a79600 ebp: f8962f40 esp: ec721f04
> ds: 007b es: 007b ss: 0068
> Process kopete (pid: 21843, threadinfo=ec721000 task=c91bfab0)
> Stack: f6a79600 f4789bc8 e9ce0788 f76338a8 f76338a0 f6a79600 f8962f40 c022e426
> 00000000 f8962fbc f76338a0 f8870f00 f7094830 f387ed08 c022e488 f4bc0000
> f89617c2 ec721f54 f89c1deb f89c8abc f8870f00 f4bc00bc 00000000 f4bc0000
> Call Trace:
> [<c022e426>] class_device_del+0xa6/0x100
> [<c022e488>] class_device_unregister+0x8/0x10
> [<f89617c2>] video_unregister_device+0x32/0x4d [videodev]
> [<f89c1deb>] w9968cf_release_resources+0x3b/0xf0 [w9968cf]
> [<f89c24d0>] w9968cf_release+0x40/0x100 [w9968cf]
> [<c0163a01>] __fput+0x91/0x180
> [<c0162097>] filp_close+0x47/0x90
> [<c0103061>] syscall_call+0x7/0xb
> Code: 26 00 8d bc 27 00 00 00 00 55 57 56 53 83 ec 0c 89 44 24 04 89 14 24 8b 50 10 8b 70 58 85 d2 74 73 f0 ff 4a 78 0f 88 cd 00 00 00 <8b> 46 0c 8d 68 fc 8b 4d 04 0f 18 01 90 83 c6 0c 89 c3 39 f0 89
> <6>usb 1-1: OV7620 image sensor initialized
> usb 1-1: USB disconnect, address 5
> usb 1-1: Disconnecting Creative Labs Video Blaster WebCam Go Plus...
Hi Diego,
thanks for your report.
Is this issue still present in kernel 2.6.15-rc7?
Which was the last working kernel?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-12-31 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 14:18 Oops with w9968cf Diego Calleja
2005-12-31 14:32 ` Adrian Bunk [this message]
2005-12-31 19:48 ` Diego Calleja
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=20051231143229.GI3811@stusta.de \
--to=bunk@stusta.de \
--cc=diegocg@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=luca.risolia@studio.unibo.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox