frontend dies with illegal instruction

[Brian May]

Binary package hint: mythtv

After watching TV, mythtv frequently crashes.

The logged messages are:

2009-05-17 15:00:32.841 TV: Attempting to change from WatchingLiveTV to None
Illegal instruction

This only happened after upgrading from Intrepid to Jaunty.

Brian May

[Mario Limonciello (superm1)]

Can you post /proc/cpuinfo? It's possible your CPU doesn't support the
minimum optimizations.

On Sun, May 17, 2009 at 00:08, Brian May <email address hidden>wrote:

> Public bug reported:
>
> Binary package hint: mythtv
>
> After watching TV, mythtv frequently crashes.
>
> The logged messages are:
>
> 2009-05-17 15:00:32.841 TV: Attempting to change from WatchingLiveTV to
> None
> Illegal instruction
>
> This only happened after upgrading from Intrepid to Jaunty.
>
> Brian May
>
> ** Affects: mythtv (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> frontend dies with illegal instruction
> https://bugs.launchpad.net/bugs/377489
> You received this bug notification because you are a member of MythTV
> Ubuntu Maintainers, which is subscribed to mythtv in ubuntu.
>

--
Mario Limonciello
<email address hidden>

[Brian May (brian-microcomaustralia)]

root@oncilla:/tmp# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
stepping : 11
cpu MHz : 2659.869
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5319.73
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
stepping : 11
cpu MHz : 2659.869
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5319.90
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
stepping : 11
cpu MHz : 2659.869
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5319.93
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
stepping : 11
cpu MHz : 2659.869
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
bogomips : 5319.94
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

[Mario Limonciello (superm1)]

Well that CPU should certainly be able to do this. Does that illegal
instruction happen *every* time?

On Sun, May 17, 2009 at 01:55, Brian May <email address hidden>wrote:

> root@oncilla:/tmp# cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
> stepping : 11
> cpu MHz : 2659.869
> cache size : 4096 KB
> physical id : 0
> siblings : 4
> core id : 0
> cpu cores : 4
> apicid : 0
> initial apicid : 0
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
> constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx
> est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5319.73
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
> stepping : 11
> cpu MHz : 2659.869
> cache size : 4096 KB
> physical id : 0
> siblings : 4
> core id : 1
> cpu cores : 4
> apicid : 1
> initial apicid : 1
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
> constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx
> est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5319.90
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 2
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
> stepping : 11
> cpu MHz : 2659.869
> cache size : 4096 KB
> physical id : 0
> siblings : 4
> core id : 2
> cpu cores : 4
> apicid : 2
> initial apicid : 2
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
> constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx
> est tm2 ssse3 cx16 xtpr pdcm lahf_lm tpr_shadow vnmi flexpriority
> bogomips : 5319.93
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> processor : 3
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
> stepping : 11
> cpu MHz ...

[Brian May (brian-microcomaustralia)]

Most of the time it has crashed I haven't looked at the log file. Two out of two times when I looked, there was this error at the end.

Sometimes it will crash multiple times repeatedly, then it will work multiple times repeatedly. At one point I thought I had fixed the problem, then it started crashing again.

It seems to happen when exiting an application {live tv, recorded tv, image gallery} and go back to the menu.

I changed the .xsession so I won't lose details if/when it happens again:

=== cut ===
#!/bin/sh
xset +dpms
while true
do
 mythfrontend > "/tmp/mythtv-`date +%Y%m%d_%H%M%S`.log" 2>&1
done
=== cut ===

Brian May

[MarcRandolph (mrand)]

Howdy Brian. Did you ever resolve this? If so, how? If not, you might try to verify aspects of your hardware, including checking your CPU temperature during load, and running a memory test.

[Brian May (brian-microcomaustralia)]

No, I didn't resolve it.

It happens on two completely different computers (one is a factory made Dell, the other is home assembled), in different parts of the house, so I would be surprised if it is a hardware issue. I sometimes wonder if maybe it is a 64bit issue...

It always happens at the same point, when exiting to the main menu.

Brian May

[MarcRandolph (mrand)]

Howdy, and thank you for helping to improve Mythbuntu by opening this ticket. Unfortunately, this backtrace attached is not useful to the developers. Could you please open a new ticket after following the "basic backtrace" directions outlined here:

http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages

The above process will result in new tickets being opened, so I'm going to close this one. Please ignore the "Invalid" wording - that is simply unfortunate wording.

[Brian May (brian-microcomaustralia)]

Hello,

Since upgrading to Karmic this problem has gone. I haven't had any more crashes of this nature.

Thanks,

Brian May