[mythtv-users] Timestretch causes 'illegal instruction' exit in 0.24

John Pilkington J.Pilk at tesco.net
Wed Dec 8 13:04:20 UTC 2010


Jean-Yves Avenard wrote:
> On 8 December 2010 06:37, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>>  On 12/07/2010 12:16 PM, John Pilkington wrote:
>>> Hi: More exploration after upgrading to 0.24 from ATrpms on my CentOS 5
>>> box.  It's generally competent but old and power-hungry.
>>>
>>> Playback is fine, but enabling timestretch causes an immediate frontend
>>> exit.  'mythfrontend -v playback' shows nothing after hitting the arrow
>>> key except the 'illegal instruction' message.
>>>
>>> I googled this and got a 22-hour old posting
>>> http://ubuntuforums.org/showthread.php?t=1639119
>>>
>>> so it's probably not related to the very new ATrpms build for CentOS.
>>>
>>> What info is needed? Pentium 4, nvidia 96.43.18, GeForce4 Ti 4200 with
>>> AGP8X,
>> Sounds like
>>
>> http://svn.mythtv.org/trac/ticket/8740
> 
> Is it a Prescott P4 ? (e.g. one sold after 2004 with 64bits support)
> 
> then it has SSE3 support too

No, this one's in an Aldi box purchased Jan 2003.  dmesg | grep CPU says 
it's updated to 06042003.  Has occasional booting problems but still 
works well.

dmesg | grep CPU
Initializing CPU#0
CPU 0 irqstacks, hard=c0768000 soft=c0748000
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 
00000400 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 
00000400 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Hyper-Threading is disabled
CPU: After all inits, caps: bfebf3ff 00000000 00000000 00000080 00000400 
00000000 00000000
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU0: Thermal monitoring enabled
CPU0: Intel(R) Pentium(R) 4 CPU 2.66GHz stepping 07
Brought up 1 CPUs
microcode: CPU0 updated from revision 0x24 to 0x37, date = 06042003


I just checked the f12 core2duo machine with Myth 0.24; that does 
timestretch properly, as seemed likely from the lack of reports about 
it.  Main motivation for putting 0.24 on the P4 was to see it in action 
(and try out the CentOS builds) before switching 'production' from 
0.23-fixes.  Dual booting the production box tends to restrict the 
opportunities for experiment, but I think I'm close to switching point now.

I have another old 'office' type box with a Celeron Coppermine core that 
  now also has CentOS and 0.24, and I may be able to get that to work as 
a basic player: but it sounds as if this will be affected by the same 
issue as well as its general lack of speed and memory!

Thanks for the response.

John P


More information about the mythtv-users mailing list