freeze/crash

freeze/crash

[James]

I have this: http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1250
I have kernel-3.0.4 and the daily media tree from 2011-10-13.

CIII-HD:85000000:8VSB:49:52:1
OTTAWA CBOFT-DT:189000000:8VSB:49:53:3
CJOH:213000000:8VSB:49:51:1
TVO    :533000000:8VSB:49:52:1
OTTAWA  CBOT-DT:539000000:8VSB:49:52:3
Télé-Québec_HD:569000000:8VSB:49:52:3
CHOT:629000000:8VSB:49:52:3

zap -channels channels.conf "CJOH'
Using frontend "Samsung 5H1409 QAM/8VSB Frontend", type ATSC
status | signal 000c | snr 000c | ber 00000000 | unc 00000000 |
crash

azap -c channels_X.conf "CJOH"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 213000000 Hz
video pid 0x0031 audio pid 0x0033
crash

It always crashes when I access the hardware but the place it crashes is 
random.

It could be the hardware but it is brand new.

Re: freeze/crash

[semiRocket]

On Fri, 14 Oct 2011 01:51:37 +0200, James <bjlockie@lockie.ca> wrote:

> It always crashes when I access the hardware but the place it crashes is  
> random.

Maybe you would want to pass those crash logs for debugging purposes :)

It's possible for developers to track from them where the crash occurs in  
driver.

Re: freeze/crash

[James]

On 10/14/11 07:10, semiRocket wrote:
> On Fri, 14 Oct 2011 01:51:37 +0200, James <bjlockie@lockie.ca> wrote:
>
>> It always crashes when I access the hardware but the place it crashes
>> is random.
>
> Maybe you would want to pass those crash logs for debugging purposes :)
What crash logs?
The kernel locks up, is there a log somewhere?
>
> It's possible for developers to track from them where the crash occurs
> in driver.

It occurred to me to try the mythbuntu livedvd. :-)

That didn't work so I tried my other PCIe slot (I had to disconnect 
stuff to make it fit :-() and it works now.

Re: freeze/crash

[semiRocket]

On Fri, 14 Oct 2011 20:38:46 +0200, James <bjlockie@lockie.ca> wrote:

> On 10/14/11 07:10, semiRocket wrote:
> On Fri, 14 Oct 2011 01:51:37 +0200, James <bjlockie@lockie.ca> wrote:
>  It always crashes when I access the hardware but the place it crashes
> is random.
>  Maybe you would want to pass those crash logs for debugging purposes  
> What crash logs?
> The kernel locks up, is there a log somewhere?


System log under /var/log/messages
or command dmesg

Also, if you keep your terminal window open crash should pop-up by itself  
so called "kernel oops". For example see first post in the following link:
	http://stackoverflow.com/questions/316131/how-do-you-diagnose-a-kernel-oops

Re: freeze/crash

[James]

On 10/14/11 17:53, semiRocket wrote:
> On Fri, 14 Oct 2011 20:38:46 +0200, James <bjlockie@lockie.ca> wrote:
>
>> On 10/14/11 07:10, semiRocket wrote:
>> On Fri, 14 Oct 2011 01:51:37 +0200, James <bjlockie@lockie.ca> wrote:
>>  It always crashes when I access the hardware but the place it crashes
>> is random.
>>  Maybe you would want to pass those crash logs for debugging purposes 
>> What crash logs?
>> The kernel locks up, is there a log somewhere?
>
>
> System log under /var/log/messages
> or command dmesg
>
> Also, if you keep your terminal window open crash should pop-up by 
> itself so called "kernel oops". For example see first post in the 
> following link:
>     http://stackoverflow.com/questions/316131/how-do-you-diagnose-a-kernel-oops
There was no kernel oops, everything just froze.
dmesg seems to clear when I reboot.

Re: freeze/crash

[semiRocket]

On Sat, 15 Oct 2011 09:35:13 +0200, James <bjlockie@lockie.ca> wrote:

> On 10/14/11 17:53, semiRocket wrote:
>> On Fri, 14 Oct 2011 20:38:46 +0200, James <bjlockie@lockie.ca> wrote:
>>
>>> On 10/14/11 07:10, semiRocket wrote:
>>> On Fri, 14 Oct 2011 01:51:37 +0200, James <bjlockie@lockie.ca> wrote:
>>>  It always crashes when I access the hardware but the place it crashes
>>> is random.
>>>  Maybe you would want to pass those crash logs for debugging purposes  
>>> What crash logs?
>>> The kernel locks up, is there a log somewhere?
>>
>>
>> System log under /var/log/messages
>> or command dmesg
>>
>> Also, if you keep your terminal window open crash should pop-up by  
>> itself so called "kernel oops". For example see first post in the  
>> following link:
>>     http://stackoverflow.com/questions/316131/how-do-you-diagnose-a-kernel-oops
> There was no kernel oops, everything just froze.
> dmesg seems to clear when I reboot.

Yes, log is regenerated with reboot.

If everything just froze those pci slot swap seems like a good solution :)
It sounds to me like some hardware problem (maybe dust preventing a good  
contact in slot).