Hi Leonardo,
Leonardo Taccari wrote:
> On Sat, Jan 31, 2009 at 06:44:52PM +0000, Jeremy Morse wrote:
>> A full dmesg would be most useful, there's a known issue with USB2
>> webcams and USB1.1 host controllers, we can see if this is related.
> I will attach it on this mail.
Looks like your webcam is attaching to a high speed controller, so that
rules out the known issue.
> uvideo_open: sc=0xcb76d808
> uvideo_set_format: sc=0xcb76d808
> uvideo: error probe/GET_MAX: SHORT_XFER (16)
> uvideo: error commit/SET_CUR: TIMEOUT (15)
> uvm_fault(0x0cacfe1a0, 0, 1) -> 0xe
> fatal page fault in supervisor mode
> trap type 6 code 0 eip 7f4 cs 8 eflags 210282 cr2 7f4 ilevel 0
> kernel: supervisor trap page fault, code=0
> Stopped in pid 406.1 (mplayer) at 0x7f4: invalid address
> db{0}> bt
> uvm_fault(0x0cacfe1a0, 0, 1) -> 0xe
> fatal page fault in supervisor mode
> trap type 6 code 0 eip c0418991 cs 8 eflags 210246 cr2 7f4 ilevel 8
> kernel: supervisor trap page fault, code=0
> Faulted in DDB; continuing...
Hrmn. The first two errors indicate either uvideo or your webcam doing
something abnormal, but after that it just returns an error to mplayer,
I can't see where it might be causing this fault in that code path.
Unfortunately it looks like the fault also prevents ddb from printing
the full stack trace. Curses. If instead you type `call dumpsys', ddb
will produce a core dump that can be used for further debugging,
savecore will copy it to /var/crash when the system next starts. Could
you also enable the line 'makeoptions DEBUG="-g"' in your kernel config
to produce a debugging symbol file.
Ideally I'd like to get my hands on that coredump and have a look at
what it's doing wrong, but as it can contain private details you can't
just upload it to the internet. If you produce it and are fine with
sending it to me, I'll find a secure way of transfering it.
--
Thanks,
Jeremy
Attachment:
signature.asc
Description: OpenPGP digital signature