[Aptitude-devel] Bug#809184: "aptitude changelog" aborts with "Illegal instruction"

[Manuel A. Fernandez Montecelo]

Control: tags -1 - unreproducible + wontfix
Control: close -1


Hi Bjarni,

2015-12-29 23:11 To Bjarni Ingi Gislason:
>2015-12-29 17:48 Bjarni Ingi Gislason:
>>On Mon, Dec 28, 2015 at 10:25:07AM +0800, Paul Wise wrote:
>>>On Mon, 28 Dec 2015 01:57:25 +0000 Bjarni Ingi Gislason wrote:
>>>
>>>>   aptitude changelog apt ...
>>>
>>>Does this always produce the same outcome?
>>>
>>
>> Yes, at least three times.
>>
>>>>   Output was "Illegal instruction" with a return value of 132.
>>>...
>>>> Architecture: i386 (i586)
>>>
>>>There are some things that would help the aptitude maintainers figure
>>>out what the problem is:
>>>
>>>Send the output of this command:
>>>
>>>cat /proc/cpuinfo
>>>
>>
>>processor	: 0
>>vendor_id	: AuthenticAMD
>>cpu family	: 5
>>model		: 8
>>model name	: AMD-K6(tm) 3D processor
>>stepping	: 12
>>cpu MHz		: 331.579
>>cache size	: 64 KB
>>fdiv_bug	: no
>>f00f_bug	: no
>>coma_bug	: no
>>fpu		: yes
>>fpu_exception	: yes
>>cpuid level	: 1
>>wp		: yes
>>flags		: fpu vme de pse tsc msr cx8 pge mmx syscall 3dnow k6_mtrr vmmcall
>>bogomips	: 663.15
>>clflush size	: 32
>>cache_alignment	: 32
>>address sizes	: 32 bits physical, 32 bits virtual
>>power management:
>>[...]
>
>Thanks for the info.
>
>Looks like a problem with Boost, and I've been checking in its BTS and:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794622
>
>The AMD K6 is an i585, or at least not a fully compatible i686, if I
>recall correctly.
>
>
>I've pinged the maintainers of the x32 port to see if they go ahead with
>the NMU (pushing a release with that patch included).  I am not sure if
>we can do much more about it from aptitude's side.

So it was officially announced that these processors will not be
supported and it seems that there will not be a reversal of this
decision:

  https://lists.debian.org/debian-devel-announce/2016/01/msg00001.html

  https://lists.debian.org/debian-devel/2015/09/msg00589.html


It seems that the only solution for you is to use older releases only.

So at this point, I think that we cannot do anything about this from
aptitude's side, sorry.  I am closing the bug report.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>