Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm installing mythtv on my laptop. Everything's on, I've managed to get my Hauppauge WinTV Nova-T USB2 Stick installed, configured, and working. Or so I thought.
When I use dvb-utils to scan for channels from my local transponder (Emley moor, uk) it runs for about 30 seconds before I get a hardlock.
I can view tv through xine fine, and because its a hardlock i can't find out what might be the cause.
I've managed to get some output from dmesg by scanning for channels through mythtv. Here's the output:
Code:
Message from syslogd@iyoti at Sat Jan 27 17:45:46 2007 ...
iyoti kernel: [17180473.308000] Oops: 0002 [#1]
Message from syslogd@iyoti at Sat Jan 27 17:45:46 2007 ...
iyoti
Message from syslogd@iyoti at Sat Jan 27 17:45:46 2007 ...
iyoti kernel: [17180473.308000] CPU: 0
Message from syslogd@iyoti at Sat Jan 27 17:45:46 2007 ...
iyoti kernel: [17180473.308000] EIP is at dvb_frontend_release+0x37/0x90 [dvb_core]
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] eax: 00024df7 ebx: e8110031 ecx: f8aaa670 edx: dda36600
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] esi: dda36600 edi: 00000000 ebp: e73e125c esp: cedd9e00
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] ds: 007b es: 007b ss: 0068
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] Process mythtv-setup (pid: 5766, threadinfo=cedd8000 task=ce4c6560)
kernel: [17180473.308000] SMP
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] Stack: 00000000 e73e1384 00000008 dda36600 ecbda8d0 e73e125c c016b95b 00000000
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] ecbda8d0 dfff60c0 e73e125c dda36600 00000000 dfca8240 00000000 c0168b27
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] 00000000 0000003f d8435d00 00000000 c0124458 dfca8240 00000034 dfca8240
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] Call Trace:
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] <c016b95b> __fput+0x9b/0x1a0 <c0168b27> filp_close+0x47/0x80
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] <c0124458> put_files_struct+0x98/0xc0 <c012560c> do_exit+0x11c/0x840
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] <c0125d67> do_group_exit+0x37/0x80 <c012e751> get_signal_to_deliver+0x281/0x3f0
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] <c02dbd00> do_page_fault+0x0/0x6f0 <c010266b> do_notify_resume+0x8b/0x6c0
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] <c0139440> hrtimer_run_queues+0xc0/0x150 <c011cdf8> __wake_up+0x38/0x50
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] <c02dbe02> do_page_fault+0x102/0x6f0 <c02dbd00> do_page_fault+0x0/0x6f0
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] <c01030be> work_notifysig+0x13/0x25
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] Code: 14 89 c5 89 5c 24 08 89 7c 24 10 8b 42 78 8b 58 28 a1 90 8c ab f8 8b bb d8 01 00 00 85 c0 75 44 f6 46 18 03 74 0b a1 00 04 3e c0 <89> 87 c0 01 00 00 8b 8b 08 01 00 00 85 c9 74 06 31 d2 89 d8 ff
Message from syslogd@iyoti at Sat Jan 27 17:45:47 2007 ...
iyoti kernel: [17180473.308000] EIP: [pg0+945874599/1068901376] dvb_frontend_release+0x37/0x90 [dvb_core] SS:ESP 0068:cedd9e00
I've absolutely no idea whether this is helpful or not, but its the only error message i got when it bombed out.
I think I've sorted it. I noticed that when I restarted my laptop, I could do a dvb-utils `scan` once. Second time, I'd get a hardlock.
In mythtv, I told it to use quite a long delay between scans, then after a restart used it to scan for channels. It worked first time, so I saved the changes and its been running fine since.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.