Your message dated Tue, 8 Apr 2008 22:17:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: SIGILL in libGLcore.so.1 from nvidia-glx 169.07-2 due to
SSE instructions
has caused the Debian Bug report #462429,
regarding SIGILL in libGLcore.so.1 from nvidia-glx 169.07-2 due to SSE
instructions
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 [EMAIL PROTECTED]
immediately.)
--
462429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462429
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: nvidia-glx
Version: 169.07-2
Severity: grave
Justification: renders package unusable
Hi.
libGLcore.so.169.07 seems to be compiled with SSE instructions enabled.
$ gdb glxgears
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/glxgears
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGILL, Illegal instruction.
0xb7978840 in ?? () from /usr/lib/libGLcore.so.1
(gdb) disass 0xb7978840 0xb7978848
Dump of assembler code from 0xb7978840 to 0xb7978848:
0xb7978840: movups (%ecx),%xmm0
0xb7978843: movups 0x10(%ecx),%xmm1
0xb7978847: movups 0x20(%ecx),%xmm2
End of assembler dump.
(gdb)
This makes it unusable on older hardware without SSE support like mine:
$ grep ^flags /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat
pse36 mmx fxsr syscall mmxext 3dnowext 3dnow up
-- Package-specific info:
uname -r:
Linux dom 2.6.23.1-my2 #1 SMP Wed Oct 17 01:10:33 CEST 2007 i686 GNU/Linux
/proc/version:
Linux version 2.6.23.1-my2 ([EMAIL PROTECTED]) (gcc version 4.2.1 (Debian
4.2.1-6)) #1 SMP Wed Oct 17 01:10:33 CEST 2007
/proc/driver/nvidia/version:
01:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev
a1)
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.23.1-my2 (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages nvidia-glx depends on:
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libgl1-mesa-glx [l 7.0.2-4 A free implementation of the OpenG
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar
ii nvidia-kernel-2.6. 169.07-2+2.6.23+my2 NVIDIA binary kernel module for Li
ii x11-common 1:7.3+10 X Window System (X.Org) infrastruc
ii xlibmesa-gl 1:7.3+10 transitional package for Debian et
ii xserver-xorg-core 2:1.4.1~git20080118-1 Xorg X server - core server
nvidia-glx recommends no packages.
-- no debconf information
----------------------------------------------------------------------
Nadchodzi galaktyczna wojna!
Sprawdz >> http://link.interia.pl/f1ce0
--- End Message ---
--- Begin Message ---
Hi,
2008/4/8, Bruno Kleinert <[EMAIL PROTECTED]>:
> environment variable, nvidia's libGL implementation accepts to disable
> the use of processor extensions. it's documented
> in /usr/share/doc/nvidia-glx/README.txt.gz, chapter 11D.
Indeed there is such variable. I guess I should check docs before
filing bug report ...
I'm closing this bug.
Thanks,
A.
--- End Message ---
