[mythtv-users] Playback freeze/lockup + kernel panic

[Ian Clark]

On 2 February 2010 01:26, steve <networks1 at cox.net> wrote:

> >Better to look at the vmcore using crash rather than using gdb directly,
> btw.
>
> OK I got it working,and right you are.  The whole thing is too big to post.
> But the important part seems to be:
>
> NVRM: Xid (0001:00): 26, Ch 00000003 M 00000304 D 00000001 intr 00400000
> NVRM: Xid (0001:00): 26, Ch 00000003 M 00000858 D 00000000 intr 04c00000
> NVRM: Xid (0001:00): 26, Ch 00000003 M 00000858 D 00000000 intr 00400000
> NVRM: Xid (0001:00): 26, Ch 00000003 M 00000858 D 00000000 intr 00c00000
> NVRM: Xid (0001:00): 26, Ch 00000003 M 00000858 D 00000000 intr 00400000
> NVRM: Xid (0001:00): 26, Ch 00000003 M 00000858 D 00000000 intr 00c00000
> NVRM: Xid (0001:00): 26, Ch 00000003 M 00000858 D 00000000 intr 00400000
> NVRM: Xid (0001:00): 26, Ch 00000003 M 00000858 D 00000000 intr 00c00000
> BUG: unable to handle kernel paging request at ffffc9000a180000
> IP: [<ffffffffa054e643>] os_mem_set+0x11/0x18 [nvidia]
> PGD 12fc07067 PUD 12fc18067 PMD 12a4f2067 PTE 0
> Thread overran stack, or stack corrupted
> Oops: 0002 [#1] SMP
> last sysfs file: /sys/kernel/kexec_crash_loaded
>
> Indicating that it is some kind of nvidia problem.  Any idea if this
> indicates a hardware fault vs. a driver problem?
>
> If it always crashes at the same address/function then it's likely a
software issue, if the crash is more random, then hardware is more likely at
fault.

If you can reproduce it with the same file and you get the same result time
after time that's almost 100% software.

Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20100202/0f15ac88/attachment.htm>