* Tuning channels with DViCO FusionHDTV7 Dual Express
@ 2011-02-06 22:46 Dave Johansen
2011-02-06 23:08 ` Marc Coevoet
` (2 more replies)
0 siblings, 3 replies; 14+ messages in thread
From: Dave Johansen @ 2011-02-06 22:46 UTC (permalink / raw)
To: v4l-dvb Mailing List
I am trying to resurrect my MythBuntu system with a DViCO FusionHDTV7
Dual Express. I had previously had some issues with trying to get
channels working in MythTV (
http://www.mail-archive.com/linux-media@vger.kernel.org/msg03846.html
), but now it locks up with MythBuntu 10.10 when I scan for channels
in MythTV and also with the scan command line utility.
Here's the output from scan:
scan /usr/share/dvb/atsc/us-ATSC-
center-frequencies-8VSB
scanning us-ATSC-center-frequencies-8VSB
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>>> tune to: 189028615:8VSB
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x1ffb
Any ideas/suggestions on how I can get this to work?
Thanks,
Dave
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-06 22:46 Tuning channels with DViCO FusionHDTV7 Dual Express Dave Johansen
@ 2011-02-06 23:08 ` Marc Coevoet
2011-02-06 23:14 ` Daniel O'Connor
2011-02-06 23:28 ` Mark Zimmerman
2 siblings, 0 replies; 14+ messages in thread
From: Marc Coevoet @ 2011-02-06 23:08 UTC (permalink / raw)
To: Dave Johansen, linux-media
Op 06-02-11 23:46, Dave Johansen schreef:
> I am trying to resurrect my MythBuntu system with a DViCO FusionHDTV7
> Dual Express. I had previously had some issues with trying to get
> channels working in MythTV (
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg03846.html
> ), but now it locks up with MythBuntu 10.10 when I scan for channels
> in MythTV and also with the scan command line utility.
>
> Here's the output from scan:
>
> scan /usr/share/dvb/atsc/us-ATSC-
> center-frequencies-8VSB
> scanning us-ATSC-center-frequencies-8VSB
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>>>> tune to: 189028615:8VSB
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x1ffb
>
> Any ideas/suggestions on how I can get this to work?
>
I've had this kind of problems on a pc with mixed usb1.1 and usb2.0 ports.
Put it on the usb2.0
Marc
--
What's on Shortwave guide: choose an hour, go!
http://shortwave.tk
700+ Radio Stations on SW http://swstations.tk
300+ languages on SW http://radiolanguages.tk
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-06 22:46 Tuning channels with DViCO FusionHDTV7 Dual Express Dave Johansen
2011-02-06 23:08 ` Marc Coevoet
@ 2011-02-06 23:14 ` Daniel O'Connor
2011-02-06 23:28 ` Mark Zimmerman
2 siblings, 0 replies; 14+ messages in thread
From: Daniel O'Connor @ 2011-02-06 23:14 UTC (permalink / raw)
To: Dave Johansen; +Cc: v4l-dvb Mailing List
On 07/02/2011, at 9:16, Dave Johansen wrote:
> Here's the output from scan:
>
> scan /usr/share/dvb/atsc/us-ATSC-
> center-frequencies-8VSB
> scanning us-ATSC-center-frequencies-8VSB
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>>>> tune to: 189028615:8VSB
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x1ffb
>
> Any ideas/suggestions on how I can get this to work?
You could try the latest DVB drivers, although on my DViCo (which looks like the DVB-T version of yours) they aren't any better.
However the drivers in Ubuntu at least work for 1 tuner, if I try and use both in mythtv one tends to lock up after a while :-/
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-06 22:46 Tuning channels with DViCO FusionHDTV7 Dual Express Dave Johansen
2011-02-06 23:08 ` Marc Coevoet
2011-02-06 23:14 ` Daniel O'Connor
@ 2011-02-06 23:28 ` Mark Zimmerman
2011-02-07 3:04 ` Dave Johansen
2 siblings, 1 reply; 14+ messages in thread
From: Mark Zimmerman @ 2011-02-06 23:28 UTC (permalink / raw)
To: Dave Johansen; +Cc: v4l-dvb Mailing List
On Sun, Feb 06, 2011 at 03:46:59PM -0700, Dave Johansen wrote:
> I am trying to resurrect my MythBuntu system with a DViCO FusionHDTV7
> Dual Express. I had previously had some issues with trying to get
> channels working in MythTV (
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg03846.html
> ), but now it locks up with MythBuntu 10.10 when I scan for channels
> in MythTV and also with the scan command line utility.
>
> Here's the output from scan:
>
> scan /usr/share/dvb/atsc/us-ATSC-
> center-frequencies-8VSB
> scanning us-ATSC-center-frequencies-8VSB
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> >>> tune to: 189028615:8VSB
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x1ffb
>
> Any ideas/suggestions on how I can get this to work?
Check your dmesg to see if yout firmware loads.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-06 23:28 ` Mark Zimmerman
@ 2011-02-07 3:04 ` Dave Johansen
2011-02-07 4:10 ` Daniel O'Connor
0 siblings, 1 reply; 14+ messages in thread
From: Dave Johansen @ 2011-02-07 3:04 UTC (permalink / raw)
To: v4l-dvb Mailing List
On Sun, Feb 6, 2011 at 4:14 PM, Daniel O'Connor <darius@dons.net.au> wrote:
>
> You could try the latest DVB drivers, although on my DViCo (which looks like the DVB-T version of yours) they aren't any better.
>
> However the drivers in Ubuntu at least work for 1 tuner, if I try and use both in mythtv one tends to lock up after a while :-/
I actually had the card working and tuning channels about 2 years ago
with Ubuntu 08.10 and 09.04. From what I recall 08.10 required updated
drivers but 09.04 didn't, so I'd imagine that it should at least be
possible for it to work and possibly just out of the box. But do you
think that has a high likelihood of success now?
On Sun, Feb 6, 2011 at 4:28 PM, Mark Zimmerman <markzimm@frii.com> wrote:
> On Sun, Feb 06, 2011 at 03:46:59PM -0700, Dave Johansen wrote:
>> I am trying to resurrect my MythBuntu system with a DViCO FusionHDTV7
>> Dual Express. I had previously had some issues with trying to get
>> channels working in MythTV (
>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg03846.html
>> ), but now it locks up with MythBuntu 10.10 when I scan for channels
>> in MythTV and also with the scan command line utility.
>>
>> Here's the output from scan:
>>
>> scan /usr/share/dvb/atsc/us-ATSC-
>> center-frequencies-8VSB
>> scanning us-ATSC-center-frequencies-8VSB
>> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>> >>> tune to: 189028615:8VSB
>> WARNING: filter timeout pid 0x0000
>> WARNING: filter timeout pid 0x1ffb
>>
>> Any ideas/suggestions on how I can get this to work?
>
> Check your dmesg to see if yout firmware loads.
>
>
>
I checked dmesg and the firmware loads. It doesn't appear to report
any errors either.
Thanks,
Dave
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-07 3:04 ` Dave Johansen
@ 2011-02-07 4:10 ` Daniel O'Connor
2011-02-07 5:18 ` Dave Johansen
0 siblings, 1 reply; 14+ messages in thread
From: Daniel O'Connor @ 2011-02-07 4:10 UTC (permalink / raw)
To: Dave Johansen; +Cc: v4l-dvb Mailing List
On 07/02/2011, at 13:34, Dave Johansen wrote:
>> However the drivers in Ubuntu at least work for 1 tuner, if I try and use both in mythtv one tends to lock up after a while :-/
>
> I actually had the card working and tuning channels about 2 years ago
> with Ubuntu 08.10 and 09.04. From what I recall 08.10 required updated
Yes that's my recollection.
> drivers but 09.04 didn't, so I'd imagine that it should at least be
> possible for it to work and possibly just out of the box. But do you
> think that has a high likelihood of success now?
I would expect at least a single channel and the remote to work since your card seems very similar to mine..
However I don't see any timeouts using mine, at least for 1 channel. Have you looked in dmesg for related parameters?
>
> On Sun, Feb 6, 2011 at 4:28 PM, Mark Zimmerman <markzimm@frii.com> wrote:
>> On Sun, Feb 06, 2011 at 03:46:59PM -0700, Dave Johansen wrote:
>>> I am trying to resurrect my MythBuntu system with a DViCO FusionHDTV7
>>> Dual Express. I had previously had some issues with trying to get
>>> channels working in MythTV (
>>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg03846.html
>>> ), but now it locks up with MythBuntu 10.10 when I scan for channels
>>> in MythTV and also with the scan command line utility.
>>>
>>> Here's the output from scan:
>>>
>>> scan /usr/share/dvb/atsc/us-ATSC-
>>> center-frequencies-8VSB
>>> scanning us-ATSC-center-frequencies-8VSB
>>> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>>>>>> tune to: 189028615:8VSB
>>> WARNING: filter timeout pid 0x0000
>>> WARNING: filter timeout pid 0x1ffb
>>>
>>> Any ideas/suggestions on how I can get this to work?
>>
>> Check your dmesg to see if yout firmware loads.
>>
>>
>>
>
> I checked dmesg and the firmware loads. It doesn't appear to report
> any errors either.
>
> Thanks,
> Dave
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-07 4:10 ` Daniel O'Connor
@ 2011-02-07 5:18 ` Dave Johansen
2011-02-07 23:54 ` Andy Walls
0 siblings, 1 reply; 14+ messages in thread
From: Dave Johansen @ 2011-02-07 5:18 UTC (permalink / raw)
To: v4l-dvb Mailing List
On Sun, Feb 6, 2011 at 9:10 PM, Daniel O'Connor <darius@dons.net.au> wrote:
>
> On 07/02/2011, at 13:34, Dave Johansen wrote:
>>> However the drivers in Ubuntu at least work for 1 tuner, if I try and use both in mythtv one tends to lock up after a while :-/
>>
>> I actually had the card working and tuning channels about 2 years ago
>> with Ubuntu 08.10 and 09.04. From what I recall 08.10 required updated
>
> Yes that's my recollection.
>
>> drivers but 09.04 didn't, so I'd imagine that it should at least be
>> possible for it to work and possibly just out of the box. But do you
>> think that has a high likelihood of success now?
>
> I would expect at least a single channel and the remote to work since your card seems very similar to mine..
>
> However I don't see any timeouts using mine, at least for 1 channel. Have you looked in dmesg for related parameters?
When I use MythTV's channel scan it gets to Channel 9 and says
"Locked" at the top of the screen and then hangs there after printing
"ATSC Channel 9 -- Timed out, no channels".
Here's the output from the terminal:
2011-02-06 21:55:10.545 DiSEqCDevTree, Warning: No device tree for cardid 1
2011-02-06 21:55:10.547 New DB connection, total: 3
2011-02-06 21:55:10.547 Connected to database 'mythconverg' at host: localhost
2011-02-06 21:55:10.550 New DB connection, total: 4
2011-02-06 21:55:10.550 Connected to database 'mythconverg' at host: localhost
2011-02-06 21:55:10.553 DiSEqCDevTree, Warning: No device tree for cardid 2
2011-02-06 21:55:14.472 Skipping channel fetch, you need to scan for
channels first.
Here's the output from dmesg:
[ 1233.984618] xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
[ 1233.986994] xc5000: firmware read 12401 bytes.
[ 1233.986997] xc5000: firmware uploading...
[ 1235.540016] xc5000: firmware upload complete...
[ 1244.872037] BUG: unable to handle kernel paging request at 0000010100000028
[ 1244.872057] IP: [<ffffffffa0034563>] videobuf_dma_unmap+0x43/0xb0
[videobuf_dma_sg]
[ 1244.872074] PGD 0
[ 1244.872087] Oops: 0000 [#1] SMP
[ 1244.872098] last sysfs file:
/sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/firmware/0000:03:00.0/loading
[ 1244.872143] CPU 1
[ 1244.872146] Modules linked in: snd_hda_codec_nvhdmi
snd_hda_codec_realtek nfsd exportfs nfs lockd fscache nfs_acl
auth_rpcgss sunrpc nvidia(P) xc5000 s5h1411 s5h1409 ir_lirc_codec
lirc_dev ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi
snd_seq_midi_event snd_seq ir_nec_decoder cx23885 ir_core snd_timer
cx2341x snd_seq_device video v4l2_common output videodev v4l1_compat
v4l2_compat_ioctl32 videobuf_dma_sg videobuf_dvb snd edac_core psmouse
serio_raw dvb_core videobuf_core btcx_risc tveeprom edac_mce_amd
k8temp shpchp soundcore snd_page_alloc i2c_nforce2 lp parport
dm_raid45 usbhid hid xor forcedeth ahci libahci pata_amd
[ 1244.872478]
[ 1244.872498] Pid: 2119, comm: cx23885[0] dvb Tainted: P
2.6.35-25-generic #44-Ubuntu K9N2GM-FIH(MS-7508)/MS-7508
[ 1244.872544] RIP: 0010:[<ffffffffa0034563>] [<ffffffffa0034563>]
videobuf_dma_unmap+0x43/0xb0 [videobuf_dma_sg]
[ 1244.872593] RSP: 0018:ffff88005c151dc0 EFLAGS: 00010246
[ 1244.872619] RAX: 0000010100000000 RBX: ffff88005ac47ef8 RCX: 0000000000000002
[ 1244.872646] RDX: 0000000000000006 RSI: ffffc90010918000 RDI: ffff88005d7340a0
[ 1244.872673] RBP: ffff88005c151dd0 R08: 0000000000000000 R09: 00000000ffffffff
[ 1244.872700] R10: 00000000ffffffff R11: 0000000000000001 R12: ffff88004e6cc028
[ 1244.872727] R13: ffff88005ac47ef8 R14: ffff88004e6cc028 R15: ffff88005c1816e0
[ 1244.872755] FS: 00007f0f8f1bf7c0(0000) GS:ffff880001e40000(0000)
knlGS:0000000000000000
[ 1244.872797] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 1244.872822] CR2: 0000010100000028 CR3: 000000005da71000 CR4: 00000000000006e0
[ 1244.872849] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 1244.872876] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 1244.872904] Process cx23885[0] dvb (pid: 2119, threadinfo
ffff88005c150000, task ffff88005c1816e0)
[ 1244.872950] Stack:
[ 1244.872968] ffff88005ac47ef8 ffff88005ac47e00 ffff88005c151e00
ffffffffa0b6a11a
[ 1244.872999] <0> ffff88005c151df0 ffff88004e6cc028 ffff88004e6cc028
ffff88004e6cc128
[ 1244.873045] <0> ffff88005c151e10 ffffffffa0b6bd4e ffff88005c151e40
ffffffffa011e457
[ 1244.873106] Call Trace:
[ 1244.873138] [<ffffffffa0b6a11a>] cx23885_free_buffer+0x5a/0xa0 [cx23885]
[ 1244.873170] [<ffffffffa0b6bd4e>] dvb_buf_release+0xe/0x10 [cx23885]
[ 1244.873200] [<ffffffffa011e457>] videobuf_queue_cancel+0xf7/0x120
[videobuf_core]
[ 1244.873244] [<ffffffffa011e4e7>] __videobuf_read_stop+0x17/0x70
[videobuf_core]
[ 1244.873289] [<ffffffffa011e55e>] videobuf_read_stop+0x1e/0x30
[videobuf_core]
[ 1244.873331] [<ffffffffa00138c8>] videobuf_dvb_thread+0x168/0x1e0
[videobuf_dvb]
[ 1244.873373] [<ffffffffa0013760>] ? videobuf_dvb_thread+0x0/0x1e0
[videobuf_dvb]
[ 1244.873416] [<ffffffff8107f266>] kthread+0x96/0xa0
[ 1244.873442] [<ffffffff8100aee4>] kernel_thread_helper+0x4/0x10
[ 1244.873468] [<ffffffff8107f1d0>] ? kthread+0x0/0xa0
[ 1244.873492] [<ffffffff8100aee0>] ? kernel_thread_helper+0x0/0x10
[ 1244.873517] Code: 19 75 6e 8b 53 28 85 d2 74 4b 48 8b 7f 28 8b 4b
30 48 8b 73 20 48 85 ff 74 4e 48 8b 87 e8 01 00 00 48 85 c0 74 42 83
f9 02 77 5d <48> 8b 40 28 48 85 c0 74 0a 45 31 c0 90 ff d0 48 8b 73 20
48 89
[ 1244.873693] RIP [<ffffffffa0034563>] videobuf_dma_unmap+0x43/0xb0
[videobuf_dma_sg]
[ 1244.873736] RSP <ffff88005c151dc0>
[ 1244.873756] CR2: 0000010100000028
[ 1244.874101] ---[ end trace aa715ac226248964 ]---
When I run scan on the command line, here's the output on the terminal:
scanning us-ATSC-center-frequencies-8VSB
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>>> tune to: 57028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 57028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 63028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 63028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 69028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 69028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 79028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 79028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 85028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 85028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 177028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 177028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 183028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 183028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 189028615:8VSB
service is running. Channel number: 9:1. Name: 'KGUN-DT'
service is running. Channel number: 9:2. Name: 'MEXI '
service is running. Channel number: 9:3. Name: 'COOLTV '
>>> tune to: 195028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 195028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 201028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 201028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 207028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 207028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 213028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 213028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 473028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 473028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 479028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 479028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 485028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 485028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 491028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 491028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 497028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 497028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 503028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 503028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 509028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 509028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 515028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 515028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 521028615:8VSB
WARNING: >>> tuning failed!!!
>>> tune to: 521028615:8VSB (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 527028615:8VSB
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x1ffb
Here's the dmesg output from when I run scan:
[ 269.724190] xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
[ 269.726431] xc5000: firmware read 12401 bytes.
[ 269.726435] xc5000: firmware uploading...
[ 271.290017] xc5000: firmware upload complete...
[ 302.280684] BUG: unable to handle kernel paging request at 0000010100000028
[ 302.280820] IP: [<ffffffffa0079563>] videobuf_dma_unmap+0x43/0xb0
[videobuf_dma_sg]
[ 302.280919] PGD 0
[ 302.281001] Oops: 0000 [#1] SMP
[ 302.281124] last sysfs file:
/sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/firmware/0000:03:00.0/loading
[ 302.281207] CPU 1
[ 302.281250] Modules linked in: snd_hda_codec_nvhdmi
snd_hda_codec_realtek nfsd exportfs nfs lockd fscache nfs_acl
auth_rpcgss sunrpc nvidia(P) xc5000 s5h1411 s5h1409 ir_lirc_codec
lirc_dev ir_sony_decoder ir_jvc_decoder ir_rc6_decoder snd_hda_intel
ir_rc5_decoder snd_hda_codec snd_hwdep ir_nec_decoder snd_pcm
snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
snd_seq_device psmouse cx23885 ir_core cx2341x v4l2_common video
output videodev v4l1_compat serio_raw v4l2_compat_ioctl32
videobuf_dma_sg videobuf_dvb edac_core snd dvb_core videobuf_core
k8temp shpchp edac_mce_amd soundcore btcx_risc tveeprom snd_page_alloc
lp i2c_nforce2 parport dm_raid45 xor ahci forcedeth libahci pata_amd
[ 302.284115]
[ 302.284171] Pid: 2034, comm: cx23885[0] dvb Tainted: P
2.6.35-25-generic #44-Ubuntu K9N2GM-FIH(MS-7508)/MS-7508
[ 302.284255] RIP: 0010:[<ffffffffa0079563>] [<ffffffffa0079563>]
videobuf_dma_unmap+0x43/0xb0 [videobuf_dma_sg]
[ 302.284380] RSP: 0018:ffff88004e271dc0 EFLAGS: 00010246
[ 302.284441] RAX: 0000010100000000 RBX: ffff88005a83c0f8 RCX: 0000000000000002
[ 302.284506] RDX: 0000000000000006 RSI: ffffc90000379000 RDI: ffff88005d7340a0
[ 302.284571] RBP: ffff88004e271dd0 R08: ffff88004e270000 R09: 00000000ffffffff
[ 302.284636] R10: 00000000ffffffff R11: 0000000000000001 R12: ffff88004df04828
[ 302.284700] R13: ffff88005a83c0f8 R14: ffff88004df04828 R15: ffff88005d1144a0
[ 302.284766] FS: 00007f8502279740(0000) GS:ffff880001e40000(0000)
knlGS:0000000000000000
[ 302.284845] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 302.284907] CR2: 0000010100000028 CR3: 000000004e20a000 CR4: 00000000000006e0
[ 302.284972] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 302.285037] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 302.285102] Process cx23885[0] dvb (pid: 2034, threadinfo
ffff88004e270000, task ffff88005d1144a0)
[ 302.285182] Stack:
[ 302.285238] ffff88005a83c0f8 ffff88005a83c000 ffff88004e271e00
ffffffffa016311a
[ 302.285420] <0> ffff88004e271df0 ffff88004df04828 ffff88004df04828
ffff88004df04928
[ 302.285694] <0> ffff88004e271e10 ffffffffa0164d4e ffff88004e271e40
ffffffffa0056457
[ 302.286020] Call Trace:
[ 302.286086] [<ffffffffa016311a>] cx23885_free_buffer+0x5a/0xa0 [cx23885]
[ 302.286155] [<ffffffffa0164d4e>] dvb_buf_release+0xe/0x10 [cx23885]
[ 302.286222] [<ffffffffa0056457>] videobuf_queue_cancel+0xf7/0x120
[videobuf_core]
[ 302.286302] [<ffffffffa00564e7>] __videobuf_read_stop+0x17/0x70
[videobuf_core]
[ 302.286382] [<ffffffffa005655e>] videobuf_read_stop+0x1e/0x30
[videobuf_core]
[ 302.286462] [<ffffffffa003d8c8>] videobuf_dvb_thread+0x168/0x1e0
[videobuf_dvb]
[ 302.286541] [<ffffffffa003d760>] ? videobuf_dvb_thread+0x0/0x1e0
[videobuf_dvb]
[ 302.286622] [<ffffffff8107f266>] kthread+0x96/0xa0
[ 302.286685] [<ffffffff8100aee4>] kernel_thread_helper+0x4/0x10
[ 302.286748] [<ffffffff8107f1d0>] ? kthread+0x0/0xa0
[ 302.286810] [<ffffffff8100aee0>] ? kernel_thread_helper+0x0/0x10
[ 302.286873] Code: 19 75 6e 8b 53 28 85 d2 74 4b 48 8b 7f 28 8b 4b
30 48 8b 73 20 48 85 ff 74 4e 48 8b 87 e8 01 00 00 48 85 c0 74 42 83
f9 02 77 5d <48> 8b 40 28 48 85 c0 74 0a 45 31 c0 90 ff d0 48 8b 73 20
48 89
[ 302.289546] RIP [<ffffffffa0079563>] videobuf_dma_unmap+0x43/0xb0
[videobuf_dma_sg]
[ 302.289666] RSP <ffff88004e271dc0>
[ 302.289724] CR2: 0000010100000028
[ 302.289816] ---[ end trace 5c4743a41e045eed ]---
The error output happens after the scanning of 189028615:8VSB. No
additional output is added during or after it locks up at the warning
message that is displayed.
Is there any additional information that I can provide to help debug this issue?
Thanks,
Dave
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-07 5:18 ` Dave Johansen
@ 2011-02-07 23:54 ` Andy Walls
2011-02-08 15:25 ` Mark Zimmerman
2011-02-08 16:39 ` Dave Johansen
0 siblings, 2 replies; 14+ messages in thread
From: Andy Walls @ 2011-02-07 23:54 UTC (permalink / raw)
To: Dave Johansen; +Cc: v4l-dvb Mailing List
On Sun, 2011-02-06 at 22:18 -0700, Dave Johansen wrote:
> On Sun, Feb 6, 2011 at 9:10 PM, Daniel O'Connor <darius@dons.net.au> wrote:
> >
> > On 07/02/2011, at 13:34, Dave Johansen wrote:
> >>> However the drivers in Ubuntu at least work for 1 tuner, if I try and use both in mythtv one tends to lock up after a while :-/
> >>
> >> I actually had the card working and tuning channels about 2 years ago
> >> with Ubuntu 08.10 and 09.04. From what I recall 08.10 required updated
> >
> > Yes that's my recollection.
> >
> >> drivers but 09.04 didn't, so I'd imagine that it should at least be
> >> possible for it to work and possibly just out of the box. But do you
> >> think that has a high likelihood of success now?
> >
> > I would expect at least a single channel and the remote to work since your card seems very similar to mine..
> >
> > However I don't see any timeouts using mine, at least for 1 channel. Have you looked in dmesg for related parameters?
>
> When I use MythTV's channel scan it gets to Channel 9 and says
> "Locked" at the top of the screen and then hangs there after printing
> "ATSC Channel 9 -- Timed out, no channels".
>
> Here's the output from the terminal:
>
> 2011-02-06 21:55:10.545 DiSEqCDevTree, Warning: No device tree for cardid 1
> 2011-02-06 21:55:10.547 New DB connection, total: 3
> 2011-02-06 21:55:10.547 Connected to database 'mythconverg' at host: localhost
> 2011-02-06 21:55:10.550 New DB connection, total: 4
> 2011-02-06 21:55:10.550 Connected to database 'mythconverg' at host: localhost
> 2011-02-06 21:55:10.553 DiSEqCDevTree, Warning: No device tree for cardid 2
> 2011-02-06 21:55:14.472 Skipping channel fetch, you need to scan for
> channels first.
>
> Here's the output from dmesg:
>
> [ 1233.984618] xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
> [ 1233.986994] xc5000: firmware read 12401 bytes.
> [ 1233.986997] xc5000: firmware uploading...
> [ 1235.540016] xc5000: firmware upload complete...
> [ 1244.872037] BUG: unable to handle kernel paging request at 0000010100000028
> [ 1244.872057] IP: [<ffffffffa0034563>] videobuf_dma_unmap+0x43/0xb0
> [videobuf_dma_sg]
> [ 1244.872074] PGD 0
> [ 1244.872087] Oops: 0000 [#1] SMP
> [ 1244.872098] last sysfs file:
> /sys/devices/pci0000:00/0000:00:10.0/0000:03:00.0/firmware/0000:03:00.0/loading
> [ 1244.872143] CPU 1
> [ 1244.872146] Modules linked in: snd_hda_codec_nvhdmi
> snd_hda_codec_realtek nfsd exportfs nfs lockd fscache nfs_acl
> auth_rpcgss sunrpc nvidia(P) xc5000 s5h1411 s5h1409 ir_lirc_codec
> lirc_dev ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder
> snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi
> snd_seq_midi_event snd_seq ir_nec_decoder cx23885 ir_core snd_timer
> cx2341x snd_seq_device video v4l2_common output videodev v4l1_compat
> v4l2_compat_ioctl32 videobuf_dma_sg videobuf_dvb snd edac_core psmouse
> serio_raw dvb_core videobuf_core btcx_risc tveeprom edac_mce_amd
> k8temp shpchp soundcore snd_page_alloc i2c_nforce2 lp parport
> dm_raid45 usbhid hid xor forcedeth ahci libahci pata_amd
> [ 1244.872478]
> [ 1244.872498] Pid: 2119, comm: cx23885[0] dvb Tainted: P
> 2.6.35-25-generic #44-Ubuntu K9N2GM-FIH(MS-7508)/MS-7508
> [ 1244.872544] RIP: 0010:[<ffffffffa0034563>] [<ffffffffa0034563>]
> videobuf_dma_unmap+0x43/0xb0 [videobuf_dma_sg]
> [ 1244.872593] RSP: 0018:ffff88005c151dc0 EFLAGS: 00010246
> [ 1244.872619] RAX: 0000010100000000 RBX: ffff88005ac47ef8 RCX: 0000000000000002
> [ 1244.872646] RDX: 0000000000000006 RSI: ffffc90010918000 RDI: ffff88005d7340a0
> [ 1244.872673] RBP: ffff88005c151dd0 R08: 0000000000000000 R09: 00000000ffffffff
> [ 1244.872700] R10: 00000000ffffffff R11: 0000000000000001 R12: ffff88004e6cc028
> [ 1244.872727] R13: ffff88005ac47ef8 R14: ffff88004e6cc028 R15: ffff88005c1816e0
> [ 1244.872755] FS: 00007f0f8f1bf7c0(0000) GS:ffff880001e40000(0000)
> knlGS:0000000000000000
> [ 1244.872797] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ 1244.872822] CR2: 0000010100000028 CR3: 000000005da71000 CR4: 00000000000006e0
> [ 1244.872849] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 1244.872876] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> [ 1244.872904] Process cx23885[0] dvb (pid: 2119, threadinfo
> ffff88005c150000, task ffff88005c1816e0)
> [ 1244.872950] Stack:
> [ 1244.872968] ffff88005ac47ef8 ffff88005ac47e00 ffff88005c151e00
> ffffffffa0b6a11a
> [ 1244.872999] <0> ffff88005c151df0 ffff88004e6cc028 ffff88004e6cc028
> ffff88004e6cc128
> [ 1244.873045] <0> ffff88005c151e10 ffffffffa0b6bd4e ffff88005c151e40
> ffffffffa011e457
> [ 1244.873106] Call Trace:
> [ 1244.873138] [<ffffffffa0b6a11a>] cx23885_free_buffer+0x5a/0xa0 [cx23885]
> [ 1244.873170] [<ffffffffa0b6bd4e>] dvb_buf_release+0xe/0x10 [cx23885]
> [ 1244.873200] [<ffffffffa011e457>] videobuf_queue_cancel+0xf7/0x120
> [videobuf_core]
> [ 1244.873244] [<ffffffffa011e4e7>] __videobuf_read_stop+0x17/0x70
> [videobuf_core]
> [ 1244.873289] [<ffffffffa011e55e>] videobuf_read_stop+0x1e/0x30
> [videobuf_core]
> [ 1244.873331] [<ffffffffa00138c8>] videobuf_dvb_thread+0x168/0x1e0
> [videobuf_dvb]
> [ 1244.873373] [<ffffffffa0013760>] ? videobuf_dvb_thread+0x0/0x1e0
> [videobuf_dvb]
> [ 1244.873416] [<ffffffff8107f266>] kthread+0x96/0xa0
> [ 1244.873442] [<ffffffff8100aee4>] kernel_thread_helper+0x4/0x10
> [ 1244.873468] [<ffffffff8107f1d0>] ? kthread+0x0/0xa0
> [ 1244.873492] [<ffffffff8100aee0>] ? kernel_thread_helper+0x0/0x10
> [ 1244.873517] Code: 19 75 6e 8b 53 28 85 d2 74 4b 48 8b 7f 28 8b 4b
> 30 48 8b 73 20 48 85 ff 74 4e 48 8b 87 e8 01 00 00 48 85 c0 74 42 83
> f9 02 77 5d <48> 8b 40 28 48 85 c0 74 0a 45 31 c0 90 ff d0 48 8b 73 20
> 48 89
> [ 1244.873693] RIP [<ffffffffa0034563>] videobuf_dma_unmap+0x43/0xb0
> [videobuf_dma_sg]
> [ 1244.873736] RSP <ffff88005c151dc0>
> [ 1244.873756] CR2: 0000010100000028
> [ 1244.874101] ---[ end trace aa715ac226248964 ]---
The cx23885 driver is bombing out in videobuf routines:
http://git.linuxtv.org/media_tree.git?a=blob;f=drivers/media/video/cx23885/cx23885-dvb.c;h=5958cb882e939db4908aa44cdefef8d8cb3948fc;hb=staging/for_v2.6.39#l108
http://git.linuxtv.org/media_tree.git?a=blob;f=drivers/media/video/cx23885/cx23885-core.c;h=359882419b7f588b7c698dbcfb6a39ddb1603301;hb=staging/for_v2.6.39#l1226
http://git.linuxtv.org/media_tree.git?a=blob;f=drivers/media/video/videobuf-dma-sg.c;h=ddb8f4b46c03bacea044ec9395adefdcee69350d;hb=staging/for_v2.6.39#l301
http://git.linuxtv.org/media_tree.git?a=blob;f=include/asm-generic/dma-mapping-common.h;h=0c80bb38773f142ef829dcbc190c60f2cf6ccff8;hb=staging/for_v2.6.39#l66
The local variable "ops" in dma_unmap_sg() is apparently a bad pointer;
it is the value RAX: 0000010100000000. Maybe that is some sort of
"poison" value for memory pointers. Your next BUG has the exact same
bad pointer.
I'm not sure where the actual failure is coming from though.
I never bothered to understand videobuf enough to help further on this
one.
> The error output happens after the scanning of 189028615:8VSB. No
> additional output is added during or after it locks up at the warning
> message that is displayed.
>
> Is there any additional information that I can provide to help debug this issue?
You perhaps could
A. provide the smallest window of known good vs known bad kernel
versions. Maybe someone with time and hardware can 'git bisect' the
issue down to the problem commit. (I'm guessing this problem might be
specific to a particular 64 bit platform IOMMU type, given the bad
dma_ops pointer.)
B. Try the latest drivers and/or bleeding edege kernel to see if the
problem has already been solved. (Back up your current stuff first.)
Regards,
Andy
> Thanks,
> Dave
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-07 23:54 ` Andy Walls
@ 2011-02-08 15:25 ` Mark Zimmerman
2011-02-08 16:51 ` Dave Johansen
2011-02-08 16:39 ` Dave Johansen
1 sibling, 1 reply; 14+ messages in thread
From: Mark Zimmerman @ 2011-02-08 15:25 UTC (permalink / raw)
To: v4l-dvb Mailing List
On Mon, Feb 07, 2011 at 06:54:30PM -0500, Andy Walls wrote:
>
> You perhaps could
>
> A. provide the smallest window of known good vs known bad kernel
> versions. Maybe someone with time and hardware can 'git bisect' the
> issue down to the problem commit. (I'm guessing this problem might be
> specific to a particular 64 bit platform IOMMU type, given the bad
> dma_ops pointer.)
>
FYI: I am on the process of doing a git bisect (10 kernels to go) to
track down this problem:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg25342.html
Which may or may not be related to the problem in this thread.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-07 23:54 ` Andy Walls
2011-02-08 15:25 ` Mark Zimmerman
@ 2011-02-08 16:39 ` Dave Johansen
1 sibling, 0 replies; 14+ messages in thread
From: Dave Johansen @ 2011-02-08 16:39 UTC (permalink / raw)
To: v4l-dvb Mailing List
On Mon, Feb 7, 2011 at 4:54 PM, Andy Walls <awalls@md.metrocast.net> wrote:
> On Sun, 2011-02-06 at 22:18 -0700, Dave Johansen wrote:
>> On Sun, Feb 6, 2011 at 9:10 PM, Daniel O'Connor <darius@dons.net.au> wrote:
>> The error output happens after the scanning of 189028615:8VSB. No
>> additional output is added during or after it locks up at the warning
>> message that is displayed.
>>
>> Is there any additional information that I can provide to help debug this issue?
>
> You perhaps could
>
> A. provide the smallest window of known good vs known bad kernel
> versions. Maybe someone with time and hardware can 'git bisect' the
> issue down to the problem commit. (I'm guessing this problem might be
> specific to a particular 64 bit platform IOMMU type, given the bad
> dma_ops pointer.)
>
> B. Try the latest drivers and/or bleeding edege kernel to see if the
> problem has already been solved. (Back up your current stuff first.)
>
> Regards,
> Andy
>
>> Thanks,
>> Dave
>
>
>
Is there some sort of instructions out there on how to do this sort of
testing to isolate where the problem started? Also, is it possible to
do it in a virtual machine or something to that effect to make the
deployment of the various systems easier?
Thanks,
Dave
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-08 15:25 ` Mark Zimmerman
@ 2011-02-08 16:51 ` Dave Johansen
2011-02-09 5:41 ` Dave Johansen
0 siblings, 1 reply; 14+ messages in thread
From: Dave Johansen @ 2011-02-08 16:51 UTC (permalink / raw)
To: v4l-dvb Mailing List
On Tue, Feb 8, 2011 at 8:25 AM, Mark Zimmerman <markzimm@frii.com> wrote:
> On Mon, Feb 07, 2011 at 06:54:30PM -0500, Andy Walls wrote:
>>
>> You perhaps could
>>
>> A. provide the smallest window of known good vs known bad kernel
>> versions. Maybe someone with time and hardware can 'git bisect' the
>> issue down to the problem commit. (I'm guessing this problem might be
>> specific to a particular 64 bit platform IOMMU type, given the bad
>> dma_ops pointer.)
>>
>
> FYI: I am on the process of doing a git bisect (10 kernels to go) to
> track down this problem:
>
> http://www.mail-archive.com/linux-media@vger.kernel.org/msg25342.html
>
> Which may or may not be related to the problem in this thread.
>
I'm using Mythbuntu 10.10 x64, which I believe uses 2.6.35 but I will
check tonight, so if the issue you're tracking down really is related
to 2.6.36, then I imagine that my problem wouldn't be caused by what
you're looking into. Plus, every time I've looked at dmesg the
firmware has loaded properly, so I'm guessing I'm on 2.6.35 and being
affected by a different issue.
Thanks for the heads up,
Dave
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-08 16:51 ` Dave Johansen
@ 2011-02-09 5:41 ` Dave Johansen
2011-02-10 1:25 ` Andy Walls
0 siblings, 1 reply; 14+ messages in thread
From: Dave Johansen @ 2011-02-09 5:41 UTC (permalink / raw)
To: v4l-dvb Mailing List
On Tue, Feb 8, 2011 at 9:51 AM, Dave Johansen <davejohansen@gmail.com> wrote:
> On Tue, Feb 8, 2011 at 8:25 AM, Mark Zimmerman <markzimm@frii.com> wrote:
>> On Mon, Feb 07, 2011 at 06:54:30PM -0500, Andy Walls wrote:
>>>
>>> You perhaps could
>>>
>>> A. provide the smallest window of known good vs known bad kernel
>>> versions. Maybe someone with time and hardware can 'git bisect' the
>>> issue down to the problem commit. (I'm guessing this problem might be
>>> specific to a particular 64 bit platform IOMMU type, given the bad
>>> dma_ops pointer.)
>>>
>>
>> FYI: I am on the process of doing a git bisect (10 kernels to go) to
>> track down this problem:
>>
>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg25342.html
>>
>> Which may or may not be related to the problem in this thread.
>>
>
> I'm using Mythbuntu 10.10 x64, which I believe uses 2.6.35 but I will
> check tonight, so if the issue you're tracking down really is related
> to 2.6.36, then I imagine that my problem wouldn't be caused by what
> you're looking into. Plus, every time I've looked at dmesg the
> firmware has loaded properly, so I'm guessing I'm on 2.6.35 and being
> affected by a different issue.
>
> Thanks for the heads up,
> Dave
>
So I don't know how useful this is, but I tried Mythbuntu 10.10 x86
and it works like a charm. So the issue appears to be isolated to the
x64 build. If there's anything I can do to help figure out what the
cause of this issue is in the x64 build, then please let me know and
I'll do my best to help out.
Thanks for all the help,
Dave
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-09 5:41 ` Dave Johansen
@ 2011-02-10 1:25 ` Andy Walls
2011-02-10 15:49 ` Mark Zimmerman
0 siblings, 1 reply; 14+ messages in thread
From: Andy Walls @ 2011-02-10 1:25 UTC (permalink / raw)
To: Dave Johansen; +Cc: v4l-dvb Mailing List
On Tue, 2011-02-08 at 22:41 -0700, Dave Johansen wrote:
> On Tue, Feb 8, 2011 at 9:51 AM, Dave Johansen <davejohansen@gmail.com> wrote:
> > On Tue, Feb 8, 2011 at 8:25 AM, Mark Zimmerman <markzimm@frii.com> wrote:
> >> On Mon, Feb 07, 2011 at 06:54:30PM -0500, Andy Walls wrote:
> >>>
> >>> You perhaps could
> >>>
> >>> A. provide the smallest window of known good vs known bad kernel
> >>> versions. Maybe someone with time and hardware can 'git bisect' the
> >>> issue down to the problem commit. (I'm guessing this problem might be
> >>> specific to a particular 64 bit platform IOMMU type, given the bad
> >>> dma_ops pointer.)
> >>>
> >>
> >> FYI: I am on the process of doing a git bisect (10 kernels to go) to
> >> track down this problem:
> >>
> >> http://www.mail-archive.com/linux-media@vger.kernel.org/msg25342.html
> >>
> >> Which may or may not be related to the problem in this thread.
> >>
> >
> > I'm using Mythbuntu 10.10 x64, which I believe uses 2.6.35 but I will
> > check tonight, so if the issue you're tracking down really is related
> > to 2.6.36, then I imagine that my problem wouldn't be caused by what
> > you're looking into. Plus, every time I've looked at dmesg the
> > firmware has loaded properly, so I'm guessing I'm on 2.6.35 and being
> > affected by a different issue.
> >
> > Thanks for the heads up,
> > Dave
> >
>
> So I don't know how useful this is, but I tried Mythbuntu 10.10 x86
> and it works like a charm. So the issue appears to be isolated to the
> x64 build.
You validated my guess. :)
> If there's anything I can do to help figure out what the
> cause of this issue is in the x64 build, then please let me know and
> I'll do my best to help out.
So this increases the likelyhood that this is a kernel problem
introduced outside of the drivers/media directory.
To find it, someone needs to clone out the kernel with git; start a git
bisect using the lastest known good and earliest known bad kernel
versions; and build, install, and test kernels until the problem is
found, as outlined here:
http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/
http://manpages.ubuntu.com/manpages/maverick/man1/git-bisect.1.html
The "build, install and test kernels" step is the pain. Let's say it
takes a 2 core AMD64 machine about 17 minutes to build a minimal kernel.
The number of kernels that need to be tested will be roughly log2(Number
of commits between known good and bad kernels). So 30,000 commits will
require roughly 15 kernel builds to narrow the problem. If it takes 20
minutes per iteration, that's 5 hours to find the problem.
That someone also needs 64 bit hardware and a board supported by the
cx23885 driver that also exhibits the problem. I have an HVR-1850 and a
64-bit machine, but I haven't tested it yet. I do not have 5 hours
free. Sorry.
Regards,
Andy
> Thanks for all the help,
> Dave
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Tuning channels with DViCO FusionHDTV7 Dual Express
2011-02-10 1:25 ` Andy Walls
@ 2011-02-10 15:49 ` Mark Zimmerman
0 siblings, 0 replies; 14+ messages in thread
From: Mark Zimmerman @ 2011-02-10 15:49 UTC (permalink / raw)
To: v4l-dvb Mailing List
On Wed, Feb 09, 2011 at 08:25:32PM -0500, Andy Walls wrote:
> On Tue, 2011-02-08 at 22:41 -0700, Dave Johansen wrote:
> > On Tue, Feb 8, 2011 at 9:51 AM, Dave Johansen <davejohansen@gmail.com> wrote:
> > > On Tue, Feb 8, 2011 at 8:25 AM, Mark Zimmerman <markzimm@frii.com> wrote:
> > >> On Mon, Feb 07, 2011 at 06:54:30PM -0500, Andy Walls wrote:
> > >>>
> > >>> You perhaps could
> > >>>
> > >>> A. provide the smallest window of known good vs known bad kernel
> > >>> versions. Maybe someone with time and hardware can 'git bisect' the
> > >>> issue down to the problem commit. (I'm guessing this problem might be
> > >>> specific to a particular 64 bit platform IOMMU type, given the bad
> > >>> dma_ops pointer.)
> > >>>
> > >>
> > >> FYI: I am on the process of doing a git bisect (10 kernels to go) to
> > >> track down this problem:
> > >>
> > >> http://www.mail-archive.com/linux-media@vger.kernel.org/msg25342.html
> > >>
> > >> Which may or may not be related to the problem in this thread.
> > >>
> > >
> > > I'm using Mythbuntu 10.10 x64, which I believe uses 2.6.35 but I will
> > > check tonight, so if the issue you're tracking down really is related
> > > to 2.6.36, then I imagine that my problem wouldn't be caused by what
> > > you're looking into. Plus, every time I've looked at dmesg the
> > > firmware has loaded properly, so I'm guessing I'm on 2.6.35 and being
> > > affected by a different issue.
> > >
> > > Thanks for the heads up,
> > > Dave
> > >
> >
> > So I don't know how useful this is, but I tried Mythbuntu 10.10 x86
> > and it works like a charm. So the issue appears to be isolated to the
> > x64 build.
>
> You validated my guess. :)
>
>
> > If there's anything I can do to help figure out what the
> > cause of this issue is in the x64 build, then please let me know and
> > I'll do my best to help out.
>
> So this increases the likelyhood that this is a kernel problem
> introduced outside of the drivers/media directory.
>
> To find it, someone needs to clone out the kernel with git; start a git
> bisect using the lastest known good and earliest known bad kernel
> versions; and build, install, and test kernels until the problem is
> found, as outlined here:
>
> http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/
> http://manpages.ubuntu.com/manpages/maverick/man1/git-bisect.1.html
>
>
>
> The "build, install and test kernels" step is the pain. Let's say it
> takes a 2 core AMD64 machine about 17 minutes to build a minimal kernel.
> The number of kernels that need to be tested will be roughly log2(Number
> of commits between known good and bad kernels). So 30,000 commits will
> require roughly 15 kernel builds to narrow the problem. If it takes 20
> minutes per iteration, that's 5 hours to find the problem.
>
> That someone also needs 64 bit hardware and a board supported by the
> cx23885 driver that also exhibits the problem. I have an HVR-1850 and a
> 64-bit machine, but I haven't tested it yet. I do not have 5 hours
> free. Sorry.
>
The slowest part of the process for me was deciding to start. After
that, the 'install, test, and reboot back into a good kernel' cycle
takes about 10 minutes, then I start the next build and walk away. By
squeezing in one cycle in the morning before leaving for work, and one
or two in the evening, I have gotten this far:
Bisecting: 37 revisions left to test after this (roughly 5 steps)
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2011-02-10 15:49 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-06 22:46 Tuning channels with DViCO FusionHDTV7 Dual Express Dave Johansen
2011-02-06 23:08 ` Marc Coevoet
2011-02-06 23:14 ` Daniel O'Connor
2011-02-06 23:28 ` Mark Zimmerman
2011-02-07 3:04 ` Dave Johansen
2011-02-07 4:10 ` Daniel O'Connor
2011-02-07 5:18 ` Dave Johansen
2011-02-07 23:54 ` Andy Walls
2011-02-08 15:25 ` Mark Zimmerman
2011-02-08 16:51 ` Dave Johansen
2011-02-09 5:41 ` Dave Johansen
2011-02-10 1:25 ` Andy Walls
2011-02-10 15:49 ` Mark Zimmerman
2011-02-08 16:39 ` Dave Johansen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.