On Sat, 15 Oct 2011 09:35:13 +0200, James wrote:
On 10/14/11 17:53, semiRocket wrote:
On Fri, 14 Oct 2011 20:38:46 +0200, James wrote:
On 10/14/11 07:10, semiRocket wrote:
On Fri, 14 Oct 2011 01:51:37 +0200, James wrote:
It always crashes when I access the hardware but the place it crashe
On 10/14/11 17:53, semiRocket wrote:
On Fri, 14 Oct 2011 20:38:46 +0200, James wrote:
On 10/14/11 07:10, semiRocket wrote:
On Fri, 14 Oct 2011 01:51:37 +0200, James wrote:
It always crashes when I access the hardware but the place it crashes
is random.
Maybe you would want to pass those cra
On Fri, 14 Oct 2011 20:38:46 +0200, James wrote:
On 10/14/11 07:10, semiRocket wrote:
On Fri, 14 Oct 2011 01:51:37 +0200, James 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
On 10/14/11 07:10, semiRocket wrote:
On Fri, 14 Oct 2011 01:51:37 +0200, James 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
On Fri, 14 Oct 2011 01:51:37 +0200, James 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.
--
T
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:8500:8VSB:49:52:1
OTTAWA CBOFT-DT:18900:8VSB:49:53:3
CJOH:21300:8VSB:49:51:1
TVO:53300:8VSB:49:52:1
OTTAWA CBOT-DT:53900:8VSB:49:
