From: teunis <teunis@wintersgift.com>
To: Luca Risolia <luca.risolia@studio.unibo.it>,
linux-kernel@vger.kernel.org
Subject: Re: sn9c10x list corruption in 2.6.18.1
Date: Sun, 22 Oct 2006 19:35:03 -0700 [thread overview]
Message-ID: <453C2A57.2030305@wintersgift.com> (raw)
In-Reply-To: <200610222322.46703.luca.risolia@studio.unibo.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Luca Risolia wrote:
> Alle 20:15, domenica 22 ottobre 2006, Dave Jones ha scritto:
>> But it only happens when the user unplugs the camera, and no other
>> webcam driver seems to be affected by this problem.
>
> Simply unplugging the camera does not reproduce any problem here. This is
> the first time I see this bug.
>
>> That's fairly conclusive to me that the driver is misbehaving.
>
> I do not think this implication is correct, as not all the drivers are
> implemented the same way and run under the same kernel configurations.
>
> The code in the driver seems to be okay to me.
>
I've seen crashes (rock solid - system halted, following a core dump)
occasionally when unplugging this device:
sn9c102: V4L2 driver for SN9C10x PC Camera Controllers v1:1.27
usb 2-1: SN9C10[12] PC Camera Controller detected (vid/pid 0x0C45/0x6005)
usb 2-1: TAS5110C1B image sensor detected
usb 2-1: Initialization succeeded
usb 2-1: V4L2 device registered as /dev/video0
usbcore: registered new interface driver sn9c102
It crashed 100% with 2.6.19-rc1-git6. 2.6.19-rc2-mm2: it only crashes
occasionally (1/10 times) making me suspect a lock issue. Haven't the
foggiest where to look and as I only tested this hardware on a whim,
it's not high enough priority for me to debug. I'm also so rusty on
drivers that my eyes would probably be of no help.
I can duplicate this on several different systems - but they're all
EHCI-based USB2 hosts. (Intel Corporation 82801DB/DBM on this laptop)
Maybe that helps.
- - Teunis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFPCpPbFT/SAfwLKMRAu/SAJ9p2pEAZST1b0aI1Pbphp5UF0MgGwCdH3sh
3o7bNGOUXos6A/HjI0izn9U=
=9Fn7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-10-23 2:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 3:11 sn9c10x list corruption in 2.6.18.1 Dave Jones
2006-10-22 11:46 ` Luca Risolia
2006-10-22 18:15 ` Dave Jones
2006-10-22 21:22 ` Luca Risolia
2006-10-23 2:35 ` teunis [this message]
2006-10-23 11:37 ` Luca Risolia
2006-10-23 2:39 ` teunis
2006-10-22 20:37 ` Pekka Enberg
2006-10-22 20:54 ` Dave Jones
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=453C2A57.2030305@wintersgift.com \
--to=teunis@wintersgift.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.