[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1002873: marked as done (reportbug: prints "Illegal instruction")



Your message dated Thu, 30 Dec 2021 18:16:40 +0100
with message-id <2c4e9f9c-8abb-fb43-2e2b-85197f036523@web.de>
and subject line Re: Bug#1002873: reportbug: prints "Illegal instruction"
has caused the Debian Bug report #1002873,
regarding reportbug: prints "Illegal instruction"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1002873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002873
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 11.1.0
Severity: normal
X-Debbugs-Cc: karogyoker2+debbug@gmail.com

Dear Maintainer,

I was submitting a bug regarding a different, unrelated package (libgl1-mesa-
dri).
Before the screen where I can type the message, a black console area appeared.
I was able to see "Illegal instruction" twice, but the whole console area
disappeared
automatically and brought me to the page where I can type the message.

I suspect that some command tried to run which required SSE2, what my CPU lacks
of.

cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 10
model name      : AMD Athlon(tm)
stepping        : 0
cpu MHz         : 1143.835
cache size      : 512 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
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 pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow cpuid 3dnowprefetch
vmmcall
bugs            : fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2
spec_store_bypass
bogomips        : 2287.67
clflush size    : 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts

It shows some weird info due to the fact that I have downclocked the
CPU to be more stable, it is an Athlon XP 2600+ (Barton).



-- Package-specific info:
** Environment settings:
INTERFACE="gtk"

** /home/user/.reportbugrc:
reportbug_version "11.1.0"
mode standard
ui gtk
realname "NoSSE2"
email "karogyoker2+debbug@gmail.com"
no-cc
list-cc-me
smtphost reportbug.debian.org

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 5.15.0-2-686-pae (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug depends on:
ii  apt                2.3.13
ii  python3            3.9.7-1
ii  python3-reportbug  11.1.0
ii  sensible-utils     0.0.17

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                            <none>
ii  debconf                                               1.5.79
pn  debsums                                               <none>
pn  default-mta | postfix | exim4 | mail-transport-agent  <none>
pn  dlocate                                               <none>
pn  emacs-bin-common                                      <none>
ii  file                                                  1:5.41-2
ii  gnupg                                                 2.2.27-2
pn  python3-urwid                                         <none>
pn  reportbug-gtk                                         <none>
ii  xdg-utils                                             1.1.3-4.1

Versions of packages python3-reportbug depends on:
ii  apt                2.3.13
ii  file               1:5.41-2
ii  python3            3.9.7-1
ii  python3-apt        2.3.0+b1
ii  python3-debian     0.1.42
ii  python3-debianbts  3.2.0
ii  python3-requests   2.25.1+dfsg-2
ii  sensible-utils     0.0.17

python3-reportbug suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
> I was submitting a bug regarding a different, unrelated package
> (libgl1-mesa-dri). Before the screen where I can type the message, a
> black console area appeared. I was able to see "Illegal instruction"
> twice, but the whole console area disappeared automatically and
> brought me to the page where I can type the message.
> 
> I suspect that some command tried to run which required SSE2, what my
> CPU lacks of.
The black console area you were seeing is where the bug script of the
libgl1-mesa-dri package was executed. The black console area is
necessary because package bug scripts can be interactive. The output you
were seeing was generated by the bug script, not by reportbug.
You can find the bug scripts installed on your system in /usr/share/bug/
if you are interested in finding out what it did.

Hope this helps. I'm closing this bug since there is no evidence of a
related problem with reportbug.

--- End Message ---

Reply to: