DragonFly bugs List (threaded) for 2008-12
Re: cxm WinTV PVR-250/350 driver
As you know, I recompiled with the cxm driver built in and it crashed.
You asked about the lines preceding the
"cmx0: could not initialize video decoder"
line. I copied down a bunch more of the messages and combined them here
with the original ones I gave you. There could be typos, but I hope
I got it all correct.
Messages prior to the debugger prompt:
pci1: <NVidia Ultra Vanta TNT2 graphics accelerator> at 0.0 irq 11
cxm0: <Conexant iTVc16 MPEG Coder> mem 0xd4000000-0xd7ffffff irq 11 at device 8.0 on pci0
cxm_iic0: <Conexant iTVc15 / iTVc16 I2C controller> on cxm0
iicbb0: <I2C bit-banging driver> on cxm_iic0
iicbus0: <Philips I2C bus> on iicbb0 master-only
cxm0:LG Innotek TAPE-H001F tuner
cmx0: could not initialize video decoder
Fatal trap 12: page fault while in kernel mode
Fault virtual address = 0xdeadc0f6
fault code = supervisor read, page not present
... more stuff ...
processor flags = interrupt enabled, resume, IOPL=0
current process = 0 (swapper)
current thread = pri 12
... Then a bunch of register and address info...
Stopped at device_delete_child+0xa: movl 0x18(%ebx)%eax
Hmm.. Could the on board NVidia being at the same irq as the MPEG Coder
be a problem?
I ran "trace" as you suggested. There was a lot of output. Here are the last
couple lines, which I am guessing is the last thing it did before the panic.
mi_startup(91b000,c033ec71,c07562c4,c091e674,c091e65c) at mi_startup+0x99
begin() at begin+0x42
I could not get a crash dump. It reported there was no crash dump when
rebooting on the other kernel. I had set dumpdev in /etc/rc.conf. I am
guessing it is because it never got far enough to to run any of the init
scripts which define the crash device. Since it had already panic'd it did not
seem to make a difference running "panic" from the DB prompt. It just gave me
the same register/address information dump that had already been printed.
Well, that's all I have for now.