Kworld atsc 110 nxt2004 init

Kworld atsc 110 nxt2004 init

[Jonathan Isom]

Hi
I was looking over my logs and I'm wondering is
"nxt200x: Timeout waiting for nxt2004 to init"
common or is this womething I need to worry about.  I got one shortly before a
lockup(No backtrace).  Nothing was doing other than dvbstreamer sitting idle.
I'll provide further logs if it should be needed.  I would think that
It would need to
only be initialize at module load.  Am I wrong in this thinking?

in kernel  drivers 2.6.28.4

Later

Jonathan

-------------   grep -rn nxt2004 /var/log/messages
------------------------------
103679:Feb 18 11:29:35 ravage [    7.925156] nxt2004: Waiting for
firmware upload (dvb-fe-nxt2004.fw)...
103680:Feb 18 11:29:35 ravage [    7.925166] i2c-adapter i2c-1:
firmware: requesting dvb-fe-nxt2004.fw
103681:Feb 18 11:29:35 ravage [    8.072591] nxt2004: Waiting for
firmware upload(2)...
103692:Feb 18 11:29:35 ravage [    9.256867]  sdc:nxt2004: Firmware
upload complete
103719:Feb 18 11:29:35 ravage [   10.109159] nxt2004: Waiting for
firmware upload (dvb-fe-nxt2004.fw)...
103720:Feb 18 11:29:35 ravage [   10.109169] i2c-adapter i2c-2:
firmware: requesting dvb-fe-nxt2004.fw
103721:Feb 18 11:29:35 ravage [   10.129386] nxt2004: Waiting for
firmware upload(2)...
103734:Feb 18 11:29:35 ravage [   11.495301] nxt2004: Firmware upload complete
103906:Feb 18 14:06:04 ravage [ 9402.688185] nxt200x: Timeout waiting
for nxt2004 to init.
103907:Feb 18 14:06:33 ravage [ 9431.488278] nxt200x: Timeout waiting
for nxt2004 to init.
103908:Feb 18 14:07:19 ravage [ 9478.214280] nxt200x: Timeout waiting
for nxt2004 to init.
103918:Feb 18 14:29:02 ravage [10776.540206] nxt200x: Timeout waiting
for nxt2004 to init.
103922:Feb 18 14:36:28 ravage [11222.734776] nxt200x: Timeout waiting
for nxt2004 to init.
103926:Feb 18 14:41:53 ravage [11547.926210] nxt200x: Timeout waiting
for nxt2004 to init.
103930:Feb 18 14:43:21 ravage [11632.944024] nxt200x: Timeout waiting
for nxt2004 to init.
103939:Feb 18 15:02:17 ravage [12767.392184] nxt200x: Timeout waiting
for nxt2004 to init.
103940:Feb 18 15:02:59 ravage [12809.110280] nxt200x: Timeout waiting
for nxt2004 to init.
103943:Feb 18 15:12:55 ravage [13404.641143] nxt200x: Timeout waiting
for nxt2004 to init.
103964:Feb 18 15:50:57 ravage [15680.490276] nxt200x: Timeout waiting
for nxt2004 to init.
103966:Feb 18 15:52:52 ravage [15795.494281] nxt200x: Timeout waiting
for nxt2004 to init.
103970:Feb 18 15:57:31 ravage [16074.085281] nxt200x: Timeout waiting
for nxt2004 to init.
104026:Feb 18 16:12:33 ravage [16974.415323] nxt200x: Timeout waiting
for nxt2004 to init.
104027:Feb 18 16:13:47 ravage [17047.839276] nxt200x: Timeout waiting
for nxt2004 to init.
104028:Feb 18 16:14:43 ravage [17104.320278] nxt200x: Timeout waiting
for nxt2004 to init.
104030:Feb 18 16:17:04 ravage [17243.163280] nxt200x: Timeout waiting
for nxt2004 to init.
104034:Feb 18 16:23:20 ravage [17618.900281] nxt200x: Timeout waiting
for nxt2004 to init.
104040:Feb 18 16:30:14 ravage [18032.751279] nxt200x: Timeout waiting
for nxt2004 to init.
104043:Feb 18 16:33:09 ravage [18205.866294] nxt200x: Timeout waiting
for nxt2004 to init.
104045:Feb 18 16:39:47 ravage [18603.418279] nxt200x: Timeout waiting
for nxt2004 to init.
104052:Feb 18 16:52:59 ravage [19393.899278] nxt200x: Timeout waiting
for nxt2004 to init.
104055:Feb 18 16:59:10 ravage [19764.901340] nxt200x: Timeout waiting
for nxt2004 to init.
104056:Feb 18 16:59:12 ravage [19765.942278] nxt200x: Timeout waiting
for nxt2004 to init.
104061:Feb 18 17:01:06 ravage [19880.749187] nxt200x: Timeout waiting
for nxt2004 to init.
104063:Feb 18 17:02:52 ravage [19984.340281] nxt200x: Timeout waiting
for nxt2004 to init.
104064:Feb 18 17:03:08 ravage [20000.528331] nxt200x: Timeout waiting
for nxt2004 to init.
104065:Feb 18 17:06:23 ravage [20194.971280] nxt200x: Timeout waiting
for nxt2004 to init.
104066:Feb 18 17:08:17 ravage [20309.528164] nxt200x: Timeout waiting
for nxt2004 to init.
104067:Feb 18 17:09:50 ravage [20401.883279] nxt200x: Timeout waiting
for nxt2004 to init.
104070:Feb 18 17:10:38 ravage [20450.212281] nxt200x: Timeout waiting
for nxt2004 to init.
104072:Feb 18 17:12:44 ravage [20576.170276] nxt200x: Timeout waiting
for nxt2004 to init.
104073:Feb 18 17:12:47 ravage [20579.282277] nxt200x: Timeout waiting
for nxt2004 to init.
104074:Feb 18 17:15:15 ravage [20727.081029] nxt200x: Timeout waiting
for nxt2004 to init.
104075:Feb 18 17:17:15 ravage [20847.849278] nxt200x: Timeout waiting
for nxt2004 to init.
104077:Feb 18 17:19:58 ravage [21008.039030] nxt200x: Timeout waiting
for nxt2004 to init.
104088:Feb 18 17:39:31 ravage [22178.802143] nxt200x: Timeout waiting
for nxt2004 to init.
104095:Feb 18 17:50:18 ravage [22823.847322] nxt200x: Timeout waiting
for nxt2004 to init.
104097:Feb 18 17:54:07 ravage [23053.062140] nxt200x: Timeout waiting
for nxt2004 to init.
104105:Feb 18 18:07:12 ravage [23835.194357] nxt200x: Timeout waiting
for nxt2004 to init.
104108:Feb 18 18:10:15 ravage [24018.519280] nxt200x: Timeout waiting
for nxt2004 to init.
104109:Feb 18 18:11:51 ravage [24114.077230] nxt200x: Timeout waiting
for nxt2004 to init.
104112:Feb 18 18:19:33 ravage [24576.718280] nxt200x: Timeout waiting
for nxt2004 to init.
104115:Feb 18 18:23:16 ravage [24797.646283] nxt200x: Timeout waiting
for nxt2004 to init.
104116:Feb 18 18:23:21 ravage [24802.409279] nxt200x: Timeout waiting
for nxt2004 to init.
104117:Feb 18 18:24:05 ravage [24846.749278] nxt200x: Timeout waiting
for nxt2004 to init.
104120:Feb 18 18:34:16 ravage [25457.200186] nxt200x: Timeout waiting
for nxt2004 to init.
104121:Feb 18 18:35:40 ravage [25541.022144] nxt200x: Timeout waiting
for nxt2004 to init.
104123:Feb 18 18:36:21 ravage [25580.199276] nxt200x: Timeout waiting
for nxt2004 to init.
104126:Feb 18 18:41:33 ravage [25892.056279] nxt200x: Timeout waiting
for nxt2004 to init.
104127:Feb 18 18:42:02 ravage [25920.600323] nxt200x: Timeout waiting
for nxt2004 to init.
104129:Feb 18 18:45:30 ravage [26128.720286] nxt200x: Timeout waiting
for nxt2004 to init.
104131:Feb 18 18:48:22 ravage [26300.799155] nxt200x: Timeout waiting
for nxt2004 to init.
104132:Feb 18 18:48:29 ravage [26308.127280] nxt200x: Timeout waiting
for nxt2004 to init.
104137:Feb 18 18:56:40 ravage [26797.160332] nxt200x: Timeout waiting
for nxt2004 to init.
104146:Feb 18 19:06:03 ravage [27359.499280] nxt200x: Timeout waiting
for nxt2004 to init.
104148:Feb 18 19:09:33 ravage [27568.026286] nxt200x: Timeout waiting
for nxt2004 to init.
104149:Feb 18 19:09:37 ravage [27571.821281] nxt200x: Timeout waiting
for nxt2004 to init.
104152:Feb 18 19:15:37 ravage [27931.659277] nxt200x: Timeout waiting
for nxt2004 to init.
104153:Feb 18 19:19:31 ravage [28165.965284] nxt200x: Timeout waiting
for nxt2004 to init.
104155:Feb 18 19:20:25 ravage [28219.370282] nxt200x: Timeout waiting
for nxt2004 to init.
104162:Feb 18 19:30:05 ravage [28797.528280] nxt200x: Timeout waiting
for nxt2004 to init.
104168:Feb 18 19:38:21 ravage [29290.928346] nxt200x: Timeout waiting
for nxt2004 to init.
104170:Feb 18 19:40:10 ravage [29400.053281] nxt200x: Timeout waiting
for nxt2004 to init.
104171:Feb 18 19:40:14 ravage [29404.195325] nxt200x: Timeout waiting
for nxt2004 to init.
104178:Feb 18 19:48:21 ravage [29891.230014] nxt200x: Timeout waiting
for nxt2004 to init.
----------------------------
--------------------------------------------------------------------
ASUS m3a78 mothorboard
AMD Athlon64 X2 Dual Core Processor 6000+ 3.1Ghz
Gigabyte NVidia 9400gt  Graphics adapter
Kworld ATSC 110 TV Capture Card
Kworld ATSC 115 TV Capture Card
--------------------------------------------------------------------

Re: Kworld atsc 110 nxt2004 init

[CityK]

Jonathan Isom wrote:
> Hi
> I was looking over my logs and I'm wondering is
> "nxt200x: Timeout waiting for nxt2004 to init"
> common 

No its not common

> or is this womething I need to worry about.  I got one shortly before a
> lockup(No backtrace).  Nothing was doing other than dvbstreamer sitting idle.
> I'll provide further logs if it should be needed.  I would think that
> It would need to
> only be initialize at module load.  Am I wrong in this thinking?
>
> in kernel  drivers 2.6.28.4
>
> Later
>
> Jonathan

Quick! Get out of you house now, she's about to blow !!!

Just kidding.  I don't think its anything to worry about.  The timeout
is by design (see the nxt200x.ko module).  I'm not sure why you've run
up against this; it looks to have occurred several hours after
initialization.  Perhaps a quirk in the microcode of the demod caused it.

Re: Kworld atsc 110 nxt2004 init

[Jonathan Isom]

On Sun, Feb 22, 2009 at 2:43 PM, CityK <cityk@rogers.com> wrote:
> Jonathan Isom wrote:
>> Hi
>> I was looking over my logs and I'm wondering is
>> "nxt200x: Timeout waiting for nxt2004 to init"
>> common
>
> No its not common
>
>> or is this womething I need to worry about.  I got one shortly before a
>> lockup(No backtrace).  Nothing was doing other than dvbstreamer sitting idle.
>> I'll provide further logs if it should be needed.  I would think that
>> It would need to
>> only be initialize at module load.  Am I wrong in this thinking?
>>
>> in kernel  drivers 2.6.28.4
Hi
Looking at the logs I found that there was a backtrace. However I believe it
is related to dvbstreamer and the kworld cards.  I cycle thru the channels to
download epg info.  The previous crash I forgot that I was running the script
to cycle them and export the xmltv data.


>From today's lockup.
----------------------------------------------------------------
Feb 22 09:58:05 ravage [53228.039032] BUG: unable to handle kernel
paging request at ffffe2865147d078
Feb 22 09:58:05 ravage [53228.039040] IP: [<ffffffff8108b3ae>]
unmap_vmas+0x4ae/0x8f0
Feb 22 09:58:05 ravage [53228.039047] PGD 0
Feb 22 09:58:05 ravage [53228.039049] Oops: 0000 [#1] SMP
Feb 22 09:58:05 ravage [53228.039050] last sysfs file:
/sys/devices/platform/it87.656/fan3_input
Feb 22 09:58:05 ravage [53228.039052] CPU 0
Feb 22 09:58:05 ravage [53228.039053] Modules linked in: vboxdrv nfsd
exportfs wlan_tkip bridge stp llc tun it87 hwmon_vid tuner_simple
tuner_types nxt200x saa7134_dvb videobuf_d
vb dvb_core tuner wlan_scan_sta ath_rate_sample saa7134 snd_hda_intel
ir_common compat_ioctl32 ath_pci nvidia(P) videodev snd_pcm wlan
v4l1_compat snd_timer v4l2_common ath_hal(P
) videobuf_dma_sg snd videobuf_core tveeprom soundcore snd_page_alloc
k8temp hwmon i2c_piix4 pl2303 usbserial lirc_mceusb2 lirc_dev r8169
mii i2c_core parport_pc parport
Feb 22 09:58:05 ravage [53228.039074] Pid: 30949, comm: cc1plus
Tainted: P           2.6.28.4 #1
Feb 22 09:58:05 ravage [53228.039075] RIP: 0010:[<ffffffff8108b3ae>]
[<ffffffff8108b3ae>] unmap_vmas+0x4ae/0x8f0
Feb 22 09:58:05 ravage [53228.039078] RSP: 0018:ffff88010edfdd48
EFLAGS: 00010246
Feb 22 09:58:05 ravage [53228.039079] RAX: ffff880028025280 RBX:
00002b5197a00000 RCX: 37a926605da94067
Feb 22 09:58:05 ravage [53228.039080] RDX: ffff880028025280 RSI:
00000000fffffff0 RDI: ffff880000015600
Feb 22 09:58:05 ravage [53228.039082] RBP: ffffe2865147d060 R08:
ffff88012fc01040 R09: 0000000000000001
Feb 22 09:58:05 ravage [53228.039083] R10: 0000000000000002 R11:
00000000000001ad R12: 00002b5197917000
Feb 22 09:58:05 ravage [53228.039084] R13: ffff8800706788b8 R14:
00000000000aa000 R15: 0000000000000020
Feb 22 09:58:05 ravage [53228.039086] FS:  00002b519703f0a0(0000)
GS:ffffffff816c8040(0000) knlGS:00000000f6484a10
Feb 22 09:58:05 ravage [53228.039087] CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Feb 22 09:58:05 ravage [53228.039088] CR2: ffffe2865147d078 CR3:
0000000000201000 CR4: 00000000000006a0
Feb 22 09:58:05 ravage [53228.039089] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Feb 22 09:58:05 ravage [53228.039091] DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Feb 22 09:58:05 ravage [53228.039092] Process cc1plus (pid: 30949,
threadinfo ffff88010edfc000, task ffff88011cbcd370)
Feb 22 09:58:05 ravage [53228.039093] Stack:
Feb 22 09:58:05 ravage [53228.039094]  ffff880119e3f460
00002b519b5fffff ffffe20001896a50 0000000000000000
Feb 22 09:58:05 ravage [53228.039096]  ffff88010edfde48
ffffffffffffffff 0000000000000000 ffff8800a9f82b00
Feb 22 09:58:05 ravage [53228.039098]  ffff88010edfde50
0000000196b85190 0000000000000000 00002b519b600000
Feb 22 09:58:05 ravage [53228.039101] Call Trace:
Feb 22 09:58:05 ravage [53228.039102]  [<ffffffff810902ef>] ?
exit_mmap+0x8f/0x150
Feb 22 09:58:05 ravage [53228.039105]  [<ffffffff8103ba55>] ? mmput+0x25/0xb0
Feb 22 09:58:05 ravage [53228.039108]  [<ffffffff8103f99c>] ? exit_mm+0xfc/0x130
Feb 22 09:58:05 ravage [53228.039110]  [<ffffffff81041bb0>] ?
do_exit+0x730/0x930
Feb 22 09:58:05 ravage [53228.039112]  [<ffffffff8109023b>] ?
remove_vma+0x5b/0x80
Feb 22 09:58:05 ravage [53228.039114]  [<ffffffff810915e0>] ?
do_munmap+0x340/0x380
Feb 22 09:58:05 ravage [53228.039116]  [<ffffffff81041de9>] ?
do_group_exit+0x39/0xa0
Feb 22 09:58:05 ravage [53228.039118]  [<ffffffff81041e62>] ?
sys_exit_group+0x12/0x20
Feb 22 09:58:05 ravage [53228.039120]  [<ffffffff8100c1db>] ?
system_call_fastpath+0x16/0x1b
Feb 22 09:58:05 ravage [53228.039122] Code: c7 45 00 00 00 00 00 48 8b
54 24 60 48 85 ed c7 42 0c 01 00 00 00 0f 84 03 ff ff ff 48 83 bc 24
b0 00 00 00 00 0f 85 b2 03 00 00 <f6>
45 18 01 0f 84 a0 01 00 00 ff 8c 24 88 00 00 00 48 8b 74 24
Feb 22 09:58:05 ravage [53228.039137] RIP  [<ffffffff8108b3ae>]
unmap_vmas+0x4ae/0x8f0
Feb 22 09:58:05 ravage [53228.039138]  RSP <ffff88010edfdd48>
Feb 22 09:58:05 ravage [53228.039139] CR2: ffffe2865147d078
Feb 22 09:58:05 ravage [53228.039141] ---[ end trace 8bae73de4732ea2f ]---
Feb 22 09:58:05 ravage [53228.039142] Fixing recursive fault but
reboot is needed!

Re: Kworld atsc 110 nxt2004 init

[Jonathan Isom]

On Sun, Feb 22, 2009 at 8:45 PM, Jonathan Isom <jeisom@gmail.com> wrote:
> On Sun, Feb 22, 2009 at 2:43 PM, CityK <cityk@rogers.com> wrote:
>> Jonathan Isom wrote:
>>> Hi
>>> I was looking over my logs and I'm wondering is
>>> "nxt200x: Timeout waiting for nxt2004 to init"
>>> common

HI all
  I am not sure if this is actually related to my lockups,  however I
think I may have
figured out something. If I boot my system with clocksource equal to
hpet it occurs
right after boot(~8secs in), but if I set it to jiffies I don't see
it(note early testing, may
still end up occuring).  In nxt2004_microcontroller_init there is a
msleep(10) and I'm
wondering if 200 msec(loop)  is long enough.

Any Thoughts?

Jonathan

>> No its not common
>>
>>> or is this womething I need to worry about.  I got one shortly before a
>>> lockup(No backtrace).  Nothing was doing other than dvbstreamer sitting idle.
>>> I'll provide further logs if it should be needed.  I would think that
>>> It would need to
>>> only be initialize at module load.  Am I wrong in this thinking?
>>>
>>> in kernel  drivers 2.6.28.4
> Hi
> Looking at the logs I found that there was a backtrace. However I believe it
> is related to dvbstreamer and the kworld cards.  I cycle thru the channels to
> download epg info.  The previous crash I forgot that I was running the script
> to cycle them and export the xmltv data.