On Tue, 3 Feb 2009, Jean-Francois Moine wrote:
On Tue, 3 Feb 2009 12:21:55 -0600 (CST) kilgota@xxxxxxxxxxxxxxxxxxxxxx wrote:I should add to the above that now I have tested, and indeed this change does not solve the problem of kernel oops after disconnect while streaming. It does make one change. The xterm does not go wild with error messages. But it is still not possible to close the svv window. Moreover, ps ax reveals that [svv] is running as an unkillable process, with [sq905/0] and [sq905/1], equally unkillable, in supporting roles. And dmesg reveals an oops. The problem is after all notorious by now, so I do not see much need for yet another log of debug output unless specifically asked for such.Why is there 2 sq905 processes? What is the oops? (Your last trace was good, because it gave the last gspca/sq905 messages and the full oops)
Right, here is the output. I have not searched for precise differences, but a glance at it leaves me with the feeling that it is the same old same old. This was done on the Pentium 4 Dual Core, with gspca_main loaded with option debug=255, and this is the dmesg output which resulted when I pulled the cord of the camera.
Theodore Kilgore
Attachment:
newest.txt.bz2
Description: Binary data
