Am Friday 17 December 2010 schrieben Sie:
> On Fri, 2010-12-17 at 12:19 +0100, Boris Cuber wrote:
> > Hello linux-media people!
> >
> > I have to problems with my dvb card ("TeVii S470"). I already
> > filed 2 bug reports some time ago, but no one seems to have
> > noticed/read them, so i'm trying it here now.
> > If you need a "full" dmesg, then please take a look at
> > https://bugzilla.kernel.org/attachment.cgi?id=40552
> >
> > 1) "TeVii S470 dvbs-2 card (cx23885) is not usable after
> > pm-suspend/resume" https://bugzilla.kernel.org/show_bug.cgi?id=16467
>
> The cx23885 driver does not implement power management. It would likely
> take many, many hours of coding and testing to implement it properly.
>
> If you need resume/suspend, use the power management scripts on your
> machine to kill all the applications using the TeVii S470, and then
> unload the cx23885 module just before suspend.
>
> On resume, have the power management scripts reload the cx23885 module.
>
Well, this doesn't work. If i did tune a channel before or used the dvb card
somehow for watching tv, unloading and reloading the cx23885
module also makes the card unuseable.
In dmesg there's lots of "do_IRQ: 1.161 No irq handler for vector (irq -1)"
messages then. This can only be fixed by rebooting the computer.
[/dmesg]
Dec 18 14:33:09 localhost kernel: [ 943.911488] cx23885 driver version 0.0.2
loaded
Dec 18 14:33:09 localhost kernel: [ 943.911525] cx23885 0000:04:00.0: PCI INT
A -> GSI 16 (level, low) -> IRQ 16
Dec 18 14:33:09 localhost kernel: [ 943.911949] CORE cx23885[0]: subsystem:
d470:9022, board: TeVii S470 [card=15,autodetected]
Dec 18 14:33:09 localhost kernel: [ 944.039513] cx23885_dvb_register()
allocating 1 frontend(s)
Dec 18 14:33:09 localhost kernel: [ 944.039515] cx23885[0]: cx23885 based dvb
card
Dec 18 14:33:09 localhost kernel: [ 944.041022] DS3000 chip version: 0.192
attached.
Dec 18 14:33:09 localhost kernel: [ 944.041025] DVB: registering new adapter
(cx23885[0])
Dec 18 14:33:09 localhost kernel: [ 944.041027] DVB: registering adapter 0
frontend 0 (Montage Technology DS3000/TS2020)...
Dec 18 14:33:09 localhost kernel: [ 944.069473] TeVii S470 MAC=
00:18:bd:5b:2d:bc
Dec 18 14:33:09 localhost kernel: [ 944.069479] cx23885_dev_checkrevision()
Hardware revision = 0xb0
Dec 18 14:33:09 localhost kernel: [ 944.069487] cx23885[0]/0: found at
0000:04:00.0, rev: 2, irq: 16, latency: 0, mmio: 0xfea00000
Dec 18 14:33:09 localhost kernel: [ 944.069496] cx23885 0000:04:00.0: setting
latency timer to 64
Dec 18 14:33:09 localhost kernel: [ 944.069572] cx23885 0000:04:00.0: irq 42
for MSI/MSI-X
Dec 18 14:33:09 localhost kernel: [ 944.069496] cx23885 0000:04:00.0: setting
latency timer to 64
Dec 18 14:33:09 localhost kernel: [ 944.069572] cx23885 0000:04:00.0: irq 42
for MSI/MSI-X
Dec 18 14:33:14 localhost kernel: [ 948.624193] do_IRQ: 1.161 No irq handler
for vector (irq -1)
Dec 18 14:33:15 localhost kernel: [ 949.604243] do_IRQ: 1.161 No irq handler
for vector (irq -1)
Dec 18 14:33:16 localhost kernel: [ 950.606246] do_IRQ: 2.161 No irq handler
for vector (irq -1)
...
[/dmesg]
> > 2) "cx23885: ds3000_writereg: writereg error on =kernel-2.6.36-rc with
> > TeVii" S470 dvb-s2 card
> > -> https://bugzilla.kernel.org/show_bug.cgi?id=18832
> >
> > These error messages show up in dmesg while switching channels in
> > mplayer/kaffeine.
> > [dmesg output]
> > [ 919.789976] ds3000_writereg: writereg error(err == -6, reg == 0x03,
> > value == 0x11)
>
> They look like I2C bus errors; error -6 is ENXIO, which is probably
> coming from cx23885-i2c.c.
>
> The device handled by the ds3000 driver is not responding properly to
> the CX23885. It could be that some other device on that I2C bus is hung
> up or the ds3000 device itself. Maybe some GPIO settings are set wrong?
>
> The cx23885 module supports an i2c_probe and i2c_debug module option
> that will turn on some messages related to i2c.
>
>
> I really have no other advice, except that if you do a git bisect
> process, you may find the commit(s) that caused the problem.
>
> Regards,
> Andy
>
> > Are these issues known? If so, are there any fixes yet? When will these
> > get into mainline? Could somebody point me into the right direction.
> > Can i help somehow to debug these problems?
> >
> > Thank you in advance.
> >
> > Regards,
> >
> > Boris Cuber
> >
> > PS: Thank Emanuel for helping me out with this mail ,)
--
http://boris64.net 20xx ;)
Attachment:
signature.asc
Description: This is a digitally signed message part.
