On Sat, 2008-07-19 at 16:21 -0400, Andy Walls wrote: > On Sat, 2008-07-19 at 12:33 -0400, Gerhard R. Wittreich wrote: > > Andy, > > > > Attached is the file with the debug=321 data. Let me know what else I > > can do. I am very willing to provide you any data you need to get > > this driver working for everyone. > > Something is really wrong with your PCI(e) bus or your CX23418 chip's > behavior. Here's what debug=321 looks like on my machine:
> Here's what your log shows: > > All the values being read back are wrong. In fact, the values read back > are always either 0xf or 0x7 depending on which CX23418 I2C control > register, RD or WR, is being read. > > You have a PCI bus problem, a problem with your CX23418 chip, or the > driver just isn't initializing the CX23418 properly. There's also one more odd thing I forgot. It's only the first I2C bus of your CX23418 that has a problem, and not the second I2C bus that your analog tuner is on. Your long log file didn't show the tuner devices being configured, as I suspect the syslog daemon may have gotten swamped, but it did show the tuner and second I2C bus being cleaned up: Jul 19 12:23:06 wittregr-pvr kernel: [12572.684393] cx18-0 i2c: i2c exit Jul 19 12:23:06 wittregr-pvr kernel: [12572.684777] i2c 0-004c: uevent Jul 19 12:23:06 wittregr-pvr kernel: [12572.684847] i2c-adapter i2c-0: adapter [cx18 i2c driver #0-0] unregistered Jul 19 12:23:06 wittregr-pvr kernel: [12572.684887] tuner 1-0043: remove Jul 19 12:23:06 wittregr-pvr kernel: [12572.684894] tda9887 1-0043: destroying instance Jul 19 12:23:06 wittregr-pvr kernel: [12572.684909] i2c 1-0043: uevent Jul 19 12:23:06 wittregr-pvr kernel: [12572.684955] tuner 1-0061: remove Jul 19 12:23:06 wittregr-pvr kernel: [12572.684965] i2c 1-0061: uevent Jul 19 12:23:06 wittregr-pvr kernel: [12572.685028] i2c-adapter i2c-1: adapter [cx18 i2c driver #0-1] unregistered So one I2C interface in the CX23418 can behave properly, while the other can't. That could point to a problem in the CX23418, or with certain PCI bus lines on the PCI bus segment the CX23418 is on, or with PCI bus lines in the CX23418 itself, or the PCI bus lines in the bridge chip for that PCI bus segment. Really odd. Regards, Andy > My immediate suggestions are related to finding possible PCI bus > problems: > > 1. Try a different PCI slot > > 2. Try the card in a different motherboard if you can, to rule out the > possibility of a bad card > > 3. In the output of lspci -vv look for error conditions in the "Status:" > (>TAbort+ <TAbort+ <MAbort+ >SERR+ <PERR+) on the CX23418, the CPU host > bridge, or any bridge in between them (or on any device). > > 4. Make sure the latency timers for all the PCI devices have reasonable > values. > > Maybe others on the list have other ideas. > > I'll have to ask Hans about how to verify the CX23418's I2C hardware > block is getting set up properly. > > Regards, > Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
