Re: Order of dvb devices

2010-01-15 Thread Mika Laitio

True, the ordering is not exactly the same everytime. One will need to
provide PCI Bus related info also to a practical udev configuration to
get things sorted out in a sane way, rather than anything else.


At least in Mandriva, the order and naming of network adapters are 
handled by using a this kind of udev rule which prevents for example eth0 
and eth1 to swap between boots:


[lam...@iiris rules.d]$ cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# Drakx-net rule for eth0 (00:24:e8:9e:66:13)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:11:22:33:44:55", ATTR{type}=="1", KERNEL=="eth*", 
NAME="eth0


# PCI device 0x8086:0x4232 (iwlagn)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="11:22:33:44:55:66", ATTR{type}=="1", KERNEL=="wlan*", 
NAME="wlan0""


I am not sure whether udev rules itself can originally generate this file 
or whether it's mandriva's own tools/scripts that will generate this file 
and add all new adapters it finds that are not yet in the file.


Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] Acoustical mode for femon

2009-12-28 Thread Mika Laitio

The monitoring application produces a sound indicating the signal quality. The
higher the beep the better the signal quality.
This is useful while mounting the antenna for finding the best position without
having to look at the monitor or without even having a monitor.


Thank you for this!  Very useful since it's hard to be outside aiming
and inside looking at a monitor at the same time.  :)


While I was trying to locate astra on last year by rotating the dish I 
used both the cheap (10 euro) beeper that was but in the satellite cable 
end to find out the abbroximately dish direction. Fine tuning was done by 
starring the laptop screen szap output to find out when it started to 
printout LOCKED output. (I used ssh from the laptop to dvb card computer 
where I had put the channel info for one astra channel and tried to szap 
for that one. That of course meant that I needed the correct channel info 
for one channel in satellite even before I could try to scan channels from 
that satellite...)


Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Can't load firmware - HVR4000

2009-03-29 Thread Mika Laitio

The firmware loads correctly now!


Which devices requires i2c-dev module? I mean if I want to buy new dvb 
devices in addition of hvr-4000 and hvr-1300, should I then avoid some 
devices...


Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: The right way to interpret the content of SNR, signal strength and BER from HVR 4000 Lite

2009-03-24 Thread Mika Laitio

That said, the solution takes the approach of "revolutionary" as
opposed to "evolutionary", which always worries me.  While providing a
much more powerful interface, it also means all of the applications
will have to properly support all of the various possible
representations of the data, increasing the responsibility in userland
considerably.


Not necessarily, the application can simply chose to support what
the driver provides as is, thereby doing no translations at all.


From the end user point of view it is not very usefull if he has 2 
different cards and application can not show any usefull signal goodness 
info in a way that would be easy to compare. So I think the attempt to 
standardize to db is good.


Maybe there could then in addition be some other optional method for also 
getting data in some hw specific format in a way that Manu suggested.
But there should anyway be mandatory to have this one "standard goodness 
value" in a way that does not require apps to make any complicate 
comparisons... (I bet half of those apps would be broken for years)


Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] Broken Tuning on Wintv Nova HD S2

2009-01-29 Thread Mika Laitio

Edgar (gimli) Hucek


Does simple patch work ?
I need your Acked-by :)


Hi, I have only saw one version of your patch in mailing list,
did you send the simpler version somewhere?

Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] Broken Tuning on Wintv Nova HD S2

2009-01-28 Thread Mika Laitio

I also can confirm this. Reverting to a previous revision restores
proper tuning to vertical transponders.


I can also confirm it with hvr-4000 and latest drivers v4l-dvb drivers 
from linuxtv org. Before I reverted this patch, I could not get lock 
with vdr for example to:


Sky News;BT:11597:vC56:S19.2E:22000:305+131:306=eng:579:0:28707:1:1026:0
Al 
Jazeera;CANALSATELLITE:11567:vC56:S19.2E:22000:55:56=ara:0:0:9021:1:1024:0


while this worked

Eurosport;SES 
Astra:12226:hC34:S19.2E:27500:101:103=deu:102:0:31200:1:1091:0


Once I reverted that patch, all channels showed up nicely.

Mika



On Tue, Jan 27, 2009 at 10:39 PM, gimli  wrote:

Hi,

the following changesets breaks Tuning to Vertical Transponders :

http://mercurial.intuxication.org/hg/s2-liplianin/rev/1ca67881d96a
http://linuxtv.org/hg/v4l-dvb/rev/2cd7efb4cc19

For example :

DMAX;BetaDigital:12246:vC34M2O0S0:S19.2E:27500:511:512=deu:32:0:10101:1:1092:0


cu

Edgar ( gimli ) Hucek

___
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-...@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] How to use scan-s2?

2009-01-26 Thread Mika Laitio

As an owner of cx24116 device you should know that it doesn't allow any AUTO
settings, so you have to create an INI file with all parameters explicitly
specifed (FEC, modulation, rolloff).

I believe this is the main problem.

Also, please take the latest scan-s2, I've done some changes especily for
cx24116 cards.


Thanks for the hint, I will try to investigate this more.
I didn't know this because the old scan from dvb-apps have seemed to 
find channels even with this simpler Satellite scan data that comes 
withing dvb-apps for Astra.


Could you or somebody else give me an example from the satellite conf file 
where all those fields are filled in? I am little confused from those 
parameters.


How about the channel data generated by the scan-s2 or scan with "-o vdr" 
option. Should I also make some changes to those manually?


I think there must however be a bug either in scan-s2 or hvr-4000 S2API 
driver, if it's will start scanning even if the given input data is 
invalid. I mean that I think the driver and S2API should "hide away" the 
differences between different S/S2 chipsets in a way that same data given 
by the user space application should be acceptable for any card/s2-driver.


Is the bug in the scan-s2 not handling the error message from the driver 
about using "AUTO" values, or is the bug in the driver not "correctly" 
returning the error when all data needed is not set?


Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] How to use scan-s2?

2009-01-25 Thread Mika Laitio

I also run it with "-5".
I personaly don't like to use network advertisements (-n switch) since I
don't trust them.
I use a full frequency filled INI file.


Hi

It might be that the signal is not the best possible for me as I can only 
scan about 500 channels with scan by using a command:

./scan -o vdr -a 1 Astra-19.2E

In Astra-19.2E I have single line:
#Astra 1KR (19.2E) - 10743.75 H - DVB-S (QPSK) - 22000 5/6 - NID:1 - TID:1051
S 10743750 H 2200 5/6

However, once scanned the channels like eurosport, arte, skynews, cnn 
international shows up just fine with vdr-1.6.0.


But if I try to use the same Astra-19.2E file with scan-s2, it can only 
find the channels from frequency 10743750 if I have stopped the "scan" 
after it had found those channels... If I let the scan to run in the end 
to other frequencies, then scan-s2 can not find anything...


./scan-s2 -a 1 -5 -n Astra-19.2E

Propably Klaus Schmidinger reported something related with his TT-3200 in
http://www.mail-archive.com/v...@linuxtv.org/msg08493.html
I have however hvr-4000.

To prove how it goes, here is the tuning log for 4 different runs.
1) scan when allowed it to swich to other frequence after tuning 
channels from 10643750

2) scan-s2 run after that (no channels found)
3) scan when stopping it immediately after it has found channels from 
10643750
4) scan-s2 after that (now it found correctly all 5 channels that are 
repoted to be in 10543750, but failed to tune from other freqs)


1)
[lam...@tinka scan]$ ./scan -a 1 Astra-19.2E
scanning Astra-19.2E
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder 10743750 H 2200 5

tune to: 10743:h:0:22000

DVB-S IF freq is 993750
0x 0x7031: pmt_pid 0x ARD -- EinsExtra (running)
0x 0x7032: pmt_pid 0x ARD -- EinsFestival (running)
0x 0x7033: pmt_pid 0x ARD -- EinsPlus (running)
0x 0x7034: pmt_pid 0x ARD -- arte (running)
0x 0x7035: pmt_pid 0x ARD -- Phoenix (running)
Network Name 'ASTRA'

tune to: 12692:h:0:22000

DVB-S IF freq is 2092250
0x045d 0x32c9: pmt_pid 0x03e9 ORF -- ORF1 (running, scrambled)
0x045d 0x32ca: pmt_pid 0x03ea ORF -- ORF2 (running, scrambled)
0x045d 0x32cb: pmt_pid 0x03f3 ORF -- ORF2 W (running, scrambled)
0x045d 0x32cc: pmt_pid 0x03f4 ORF -- ORF2 N (running, scrambled)
0x045d 0x32cd: pmt_pid 0x03f5 ORF -- ORF2 B (running, scrambled)
0x045d 0x32ce: pmt_pid 0x03f6 ORF -- ORF2 O (running, scrambled)
0x045d 0x32cf: pmt_pid 0x03f7 ORF -- ORF2 S (running, scrambled)
0x045d 0x32d0: pmt_pid 0x03f8 ORF -- ORF2 T (running, scrambled)
0x045d 0x32d1: pmt_pid 0x03f9 ORF -- ORF2 V (running, scrambled)
0x045d 0x32d2: pmt_pid 0x03fa ORF -- ORF2 St (running, scrambled)
0x045d 0x32d3: pmt_pid 0x03fb ORF -- ORF2 K (running, scrambled)
0x045d 0x32d4: pmt_pid 0x03fc ATV+ -- ATV+ (running, scrambled)
0x045d 0x32d5: pmt_pid 0x03eb ORF -- HITRADIO OE3 (running)
0x045d 0x32d6: pmt_pid 0x03ec ORF -- ORF2E (running)
0x045d 0x32d9: pmt_pid 0x03ef arena -- Bundesliga 5 (not running, 
scrambled)
0x045d 0x32da: pmt_pid 0x03f0 arena -- Bundesliga 6 (not running, 
scrambled)

0x045d 0x3390: pmt_pid 0x04b0 ORF -- AlphaCrypt (running)
0x045d 0x339a: pmt_pid 0x04ba ORS -- Siemens Download (running)
0x045d 0x33a4: pmt_pid 0x ORF -- VESTEL OAD2 (running)
0x045d 0x33ae: pmt_pid 0x04ce ORF -- VESTEL DOWNLOAD (running)
^CERROR: interrupted by SIGINT, dumping partial result...
dumping lists (25 services)
...

2) [lam...@tinka scan-s2]$ ./scan-s2 -a 1 
/home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2E

API major 5, minor 0
scanning /home/lamikr/dvb/apps/dvb-apps_20090126/util/scan/Astra-19.2E
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder DVB-S2 10743750 H 2200 5/6 AUTO AUTO
initial transponder DVB-S  10743750 H 2200 5/6 AUTO AUTO
--> Using DVB-S2

tune to: 10743:hC56S1:S0.0W:22000:

DVB-S IF freq is 993750
WARNING: >>> tuning failed!!!

tune to: 10743:hC56S1:S0.0W:22000: (tuning failed)

DVB-S IF freq is 993750
WARNING: >>> tuning failed!!!
--> Using DVB-S

tune to: 10743:hC56S0:S0.0W:22000:

DVB-S IF freq is 993750
WARNING: >>> tuning failed!!!

tune to: 10743:hC56S0:S0.0W:22000: (tuning failed)

DVB-S IF freq is 993750
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.

3) [lam...@tinka scan]$ ./scan -a 1 Astra-19.2E
scanning Astra-19.2E
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder 10743750 H 2200 5

tune to: 10743:h:0:22000

DVB-S IF freq is 993750
0x 0x7031: pmt_pid 0x0064 ARD -- EinsExtra (running)
0x 0x7032: pmt_pid 0x00c8 ARD -- EinsFestival (running)
0x 0x7033: pmt_pid 0x012c ARD -- EinsPlus (running)
0x 0x7034: pmt_pid 0x0190 ARD -- arte (running)
0x 0x7035: pmt_pid 0x01f4 ARD -- Phoenix (running)
^X^CERROR: interrupted by SIGINT, dumping partial result...
dumping lists (5 services)
EinsExtra:10743:

Re: kernel soft lockup on boot loading cx2388x based DVB-S card (TeVii S420)

2009-01-15 Thread Mika Laitio

Firstly i built the v4l from: http://linuxtv.org/hg/v4l-dvb (hg clone) as the 
card was not detected.
On first reboot after new modules are installed i get a kernel soft lockup
cx88[0]/2: cx2388x based DVB/ATSC card
BUG: soft lockup - CPU#0 stuck for 11s! [modprobe:1767]


I just merged on http://linuxtv.org/hg/v4l-dvb a patch for fixing this bug. 
Please test.


Works now ok for me, vdr-1.6.0 is able to show the dvb-t channels 
by using hvr-1300 and dvb-s channels by using the hvr-4000.


vdr-1.7.3 works for me only for dvb-t channels but dvb-s/s2 channels with 
hvr-4000 does not tune.


Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PULL] http://linuxtv.org/hg/~awalls/v4l-dvb

2009-01-13 Thread Mika Laitio

I don't think these changes were ever merged in. I noticed newer
activity in your dev tree though since this request. Is it safe to
grab that as well, or should I go back to this date?


They should be safe.  Please note that I'm recovering from a hard down
of my main machine [root partition superblock got corrupted along with a
lot of the filesystem :( ] so I won't be doing to much more in the next
day or three or four...


Do you know what is the status when/if you could ask Mauro to apply the
patch you send in the "cx88-dvb: Fix order of frontend allocations..." 
thread. Without that patch my system is at least crashing on 2.7.27.7 
kernel when using the latest dvb-vl4 drivers.


I think somebody else also confirmed that this patch fixes the crash.

Mika
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] [PATCH] cx88-dvb: Fix order of frontend allocations (Re: current v4l-dvb - cannot access /dev/dvb/: No such file or directory)

2009-01-12 Thread Mika Laitio

I don't have the hardware to test with.  Please try this patch.


Hi

I tested the patch and it helped me to get the drivers back to normal 
state! My system has hvr-1300 and hvr-4000 and only 1 lnb without diseq.


I am using 2.6.27.7 kernel and I did two test runs.
- First I build the current drivers in http://linuxtv.org/hg/v4l-dvb/
  (revision http://linuxtv.org/hg/v4l-dvb/rev/036cad8c8b51)
  With this driver version linux failed to boot at all.
- Then I merged your patch by hand on top of this v4l-dvb version
  and I got the drivers back to normal version.
  With vdr-1.6.0 I was able to tune both the dvb-t channels from hvr-1300 
and dvb-s channels from hvr-4000. This vdr 1.6.0 uses old non 
S2API/backward compatibility layer of the drivers. I attach your patch 
just in case, as I did the merge by hand.


There is still some problem either within the S2API implementation itself 
for the HVR-4000 or in the way how VDR-1.7.1, 1.7.2 and 1.7.3 
uses S2API because I have not been able to use these newer VDR versions 
that use S2API for tuning to S/S2 channels. Technotrend TT S2 3200 users 
are however able to use these same VDR versions for tuning to S/S2 
channels.


DVB-T channels from hvr-1300 tunes ok with vdr-1.7.3.

I have tested this multiple different versions of D2API drivers both from 
the liplianis tree, stock drivers in 2.6.28 kernel and v4l-dvb tree.


Mika


Signed-off-by: Andy Walls 

diff -r a28c39659c25 linux/drivers/media/video/cx88/cx88-dvb.c
--- a/linux/drivers/media/video/cx88/cx88-dvb.c Sat Jan 10 16:04:45 2009 -0500
+++ b/linux/drivers/media/video/cx88/cx88-dvb.c Sun Jan 11 19:13:10 2009 -0500
@@ -621,33 +621,40 @@ static struct stv0288_config tevii_tuner
.set_ts_params = cx24116_set_ts_param,
};

+static int cx8802_alloc_frontends(struct cx8802_dev *dev)
+{
+   struct cx88_core *core = dev->core;
+   struct videobuf_dvb_frontend *fe = NULL;
+   int i;
+
+   mutex_init(&dev->frontends.lock);
+   INIT_LIST_HEAD(&dev->frontends.felist);
+
+   if (!core->board.num_frontends)
+   return -ENODEV;
+
+   printk(KERN_INFO "%s() allocating %d frontend(s)\n", __func__,
+core->board.num_frontends);
+   for (i = 1; i <= core->board.num_frontends; i++) {
+   fe = videobuf_dvb_alloc_frontend(&dev->frontends, i);
+   if (!fe) {
+   printk(KERN_ERR "%s() failed to alloc\n", __func__);
+   videobuf_dvb_dealloc_frontends(&dev->frontends);
+   return -ENOMEM;
+   }
+   }
+   return 0;
+}
+
static int dvb_register(struct cx8802_dev *dev)
{
struct cx88_core *core = dev->core;
struct videobuf_dvb_frontend *fe0, *fe1 = NULL;
int mfe_shared = 0; /* bus not shared by default */
-   int i;

if (0 != core->i2c_rc) {
printk(KERN_ERR "%s/2: no i2c-bus available, cannot attach dvb 
drivers\n", core->name);
goto frontend_detach;
-   }
-
-   if (!core->board.num_frontends)
-   return -EINVAL;
-
-   mutex_init(&dev->frontends.lock);
-   INIT_LIST_HEAD(&dev->frontends.felist);
-
-   printk(KERN_INFO "%s() allocating %d frontend(s)\n", __func__,
-core->board.num_frontends);
-   for (i = 1; i <= core->board.num_frontends; i++) {
-   fe0 = videobuf_dvb_alloc_frontend(&dev->frontends, i);
-   if (!fe0) {
-   printk(KERN_ERR "%s() failed to alloc\n", __func__);
-   videobuf_dvb_dealloc_frontends(&dev->frontends);
-   goto frontend_detach;
-   }
}

/* Get the first frontend */
@@ -1253,6 +1260,8 @@ static int cx8802_dvb_probe(struct cx880
struct cx88_core *core = drv->core;
struct cx8802_dev *dev = drv->core->dvbdev;
int err;
+   struct videobuf_dvb_frontend *fe;
+   int i;

dprintk( 1, "%s\n", __func__);
dprintk( 1, " ->being probed by Card=%d Name=%s, PCI %02x:%02x\n",
@@ -1268,39 +1277,34 @@ static int cx8802_dvb_probe(struct cx880
/* If vp3054 isn't enabled, a stub will just return 0 */
err = vp3054_i2c_probe(dev);
if (0 != err)
-   goto fail_probe;
+   goto fail_core;

/* dvb stuff */
printk(KERN_INFO "%s/2: cx2388x based DVB/ATSC card\n", core->name);
dev->ts_gen_cntrl = 0x0c;

+   err = cx8802_alloc_frontends(dev);
+   if (err)
+   goto fail_core;
+
err = -ENODEV;
-   if (core->board.num_frontends) {
-   struct videobuf_dvb_frontend *fe;
-   int i;
-
-   for (i = 1; i <= core->board.num_frontends; i++) {
-   fe = 
videobuf_dvb_get_frontend(&core->dvbdev->frontends, i);
-   if (fe == NULL) {
-   printk(KERN_ERR "%s() failed to get 
frontend(%d)\n",
+   

latest S2API segfaults for cx88 (hvr-1300 and hvr-4000)

2009-01-10 Thread Mika Laitio

Hi

I checked out and build today the latest vl4-dvb drivers
(changeset:   10210:985ecd81d993) against the 2.6.27.1 kernel
and the drivers segfaults on load for me.

Attached is the segfault + /proc/interrupts output.

I have in my system both the hvr-1300 and hvr-4000.
Last driver version that I have tested to work is from 2008-12-31.
(changeset:   10165:3e5f56413191 which added the FE_CAN_2G_MODULATION 
flag)


With this older version of driver I am able to tune to dvb-t (from 
hvr-1300) and dvb-s/s2 (from hvr-4000) with command line tools like scan, 
szap,szap2 or older vdr-1.6.0 which is not aware from s2api and uses thus 
older dvb driver api.


But even with that version (2008-12-31) version of driver there is some 
problem, because unlike the hvr-3200 users, I am not able to change dvb-s 
or dvb-s2 channels with vdr-1.7.3. Changing of dvb-t channels works ok.
If I have earlier szapped the correct dvb-s/s2 channel by using the 
szap/szap-s2 and then quitted it with ctrl-c and started vdr-1.7.3, I am 
able to watch that S/S2 channels, but any attempt to switch for 
some other s/s2 channels will fail. Unlike Gregoire Favre who is not able 
to tune any S/S2 channels even from command line, I do not have diseqs 
installed in my system. (hvr-4000 is connected directly via wire to lnb)


Mika

dmesg
-
cx88-mpeg driver manager :03:07.2: PCI INT A -> GSI 21 (level, low) -> IRQ 
21
cx88[1]/2: found at :03:07.2, rev: 5, irq: 21, latency: 32, mmio: 0xf800
cx8800 :03:06.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
cx88[0]/0: found at :03:06.0, rev: 5, irq: 20, latency: 32, mmio: 0xf600
wm8775' 1-001b: chip found @ 0x36 (cx88[0])
wm8775' 2-001b: chip found @ 0x36 (cx88[1])
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
cx8800 :03:07.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
cx88[1]/0: found at :03:07.0, rev: 5, irq: 21, latency: 32, mmio: 0xfa00
cx88[1]/0: registered device video1 [v4l2]
cx88[1]/0: registered device vbi1
cx88[1]/0: registered device radio1
cx88/2: cx2388x dvb driver version 0.0.6 loaded
cx88/2: registering cx8802 driver, type: dvb access: shared
cx88[0]/2: subsystem: 0070:9601, board: Hauppauge WinTV-HVR1300 DVB-T/Hybrid 
MPEG Encoder [card=56]
cx88[0]/2: cx2388x based DVB/ATSC card
BUG: unable to handle kernel NULL pointer dereference at 
IP: [] __mutex_lock_slowpath+0x3d/0xd0
PGD 6a891067 PUD 6a8c8067 PMD 0 
Oops: 0002 [1] SMP 
CPU 1 
Modules linked in: cx88_dvb(+) cx88_vp3054_i2c videobuf_dvb dvb_core wm8775 
snd_seq_dummy snd_seq_oss tuner_simple tuner_types snd_seq_midi_event snd_seq 
tda9887 snd_seq_device tda8290 snd_pcm_oss snd_hda_intel tuner cx8800 cx8802 
cx88_alsa cx88xx snd_pcm ir_common snd_timer snd_page_alloc snd_hwdep 
snd_mixer_oss v4l2_common videodev i2c_algo_bit r8169 ppdev tveeprom 
v4l1_compat ohci1394 pcspkr v4l2_compat_ioctl32 mii thermal parport_pc 
videobuf_dma_sg shpchp ieee1394 videobuf_core i2c_piix4 btcx_risc pci_hotplug 
parport wmi processor k8temp serio_raw rtc_cmos sg button sr_mod i2c_core evdev 
joydev snd lirc_imon lirc_dev soundcore atiixp ide_core pata_atiixp ata_piix 
ahci libata dock sd_mod scsi_mod crc_t10dif ext3 jbd uhci_hcd ohci_hcd ehci_hcd 
usbhid usbcore ff_memless [last unloaded: scsi_wait_scan]
Pid: 1569, comm: modprobe Not tainted 2.6.27.7-1lamikr #1
RIP: 0010:[]  [] 
__mutex_lock_slowpath+0x3d/0xd0
RSP: 0018:88006a861d78  EFLAGS: 00010246
RAX: 88006a861d78 RBX: 88006dd22588 RCX: 
RDX:  RSI: 0001 RDI: 88006dd2258c
RBP: 88006a861dc8 R08:  R09: 0007
R10: 88006a861d48 R11: 8079e7e0 R12: 88006dd2258c
R13: 0001 R14: 88006a8b4290 R15: 88006dd22590
FS:  7f77377ed6f0() GS:88006f802880() knlGS:
CS:  0010 DS:  ES:  CR0: 8005003b
CR2:  CR3: 6a42 CR4: 06e0
DR0:  DR1:  DR2: 
DR3:  DR6: 0ff0 DR7: 0400
Process modprobe (pid: 1569, threadinfo 88006a86, task 88006a8b4290)
Stack:  88006dd22590   88006ec77a20
 88006dd22400 88006dd22588 88006dcda000 0001
 88006dd22588 88006dd22408 88006a861de8 804fd26e
Call Trace:
 [] mutex_lock+0x1e/0x30
 [] videobuf_dvb_get_frontend+0x1d/0x80 [videobuf_dvb]
 [] cx8802_dvb_probe+0x12f/0x1d90 [cx88_dvb]
 [] ? __kmalloc+0xba/0x110
 [] cx8802_register_driver+0x1cd/0x260 [cx8802]
 [] ? dvb_init+0x0/0x30 [cx88_dvb]
 [] dvb_init+0x27/0x30 [cx88_dvb]
 [] _stext+0x3c/0x170
 [] sys_init_module+0xbb/0x1f0
 [] system_call_fastpath+0x16/0x1b


Code: 89 fb 4c 89 e7 4c 8d 7b 08 48 83 ec 28 65 4c 8b 34 25 00 00 00 00 e8 43 
17 00 00 48 8b 53 10 48 8d 45 b0 4c 89 7d b0 48 89 43 10 <48> 89 02 48 89 55 b8 
48 c7 c2 ff ff ff ff 4c