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

Bug#157725: marked as done (xserver-xfree86: [glint] SIGFPE running ygraph client on Permedia 2 rev 1)

Your message dated Thu, 26 Apr 2007 18:35:28 +0200
with message-id <4630D4D0.6020304@ens-lyon.org>
and subject line Bug#157725: xserver-xfree86: [glint] SIGFPE running ygraph client on Permedia 2 rev 1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xserver-xfree86
Version: 4.1.0-16
Severity: important

Hi,

first my thanks for the work on Debian.

I am running XFree on an Alpha (first two lines of dmesg):
Linux version 2.4.18 (root@gnork) (gcc version 2.95.4 20011002 (Debian prerelease)) #12 Wed Jun 26 15:43:24 CEST 2002 Booting GENERIC on Tsunami variation Monet using machine vector Monet from SRM
Using a selfwritten tool (not by me, but I know the author), I can cause X to crash. There may be an error in the application, but it should never cause to affect X in such a way, at least I think so. (X crashes, but restarts showing the gdm-login screen.)
To confirm this, you could get the tool I used (it is for visualisation of data): 

home  : http://www.aei.mpg.de/~pollney/ygraph/
source: http://www.aei.mpg.de/~pollney/ygraph/src/ygraph-0.14.tar.gz
binary: http://www.aei.mpg.de/~knarf/ygraph/alpha_linux/ygraph
 (alpha version + striped)

Then you might want to get one data file:
http://www.aei.mpg.de/~knarf/xfree_bug/alp_3D_diagonal.xg

if you then start it with
  ygraph -x15.5,16 -y0.913,0.915 alp_3D_diagonal.xg
it should crash your X-server. The options -x and -y are for setting the ranges of the display, if you start without, you will see some sort of graph.
You can see my XFree86.vt01.log (there X was running from 'startx', but the problem was the same) and my /etc/X11/XF86Config here: 

http://www.aei.mpg.de/~knarf/xfree_bug/XFree86.vt01.log
http://www.aei.mpg.de/~knarf/xfree_bug/XF86Config
(I hope it is ok not to include this here, I can add it later, if this would be better than the link.)
Thanks for looking into this. Please let me know, if you need more information. 

  Frank Loeffler


lspci shows:

00:07.0 ISA bridge: Contaq Microsystems 82c693
00:07.1 IDE interface: Contaq Microsystems 82c693
00:07.2 IDE interface: Contaq Microsystems 82c693
00:07.3 USB Controller: Contaq Microsystems 82c693
00:0c.0 SCSI storage controller: LSI Logic / Symbios Logic (formerly NCR) 53c895 (rev 02) 
00:0d.0 Display controller: Texas Instruments TVP4020 [Permedia 2] (rev 01)
01:03.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41) 01:06.0 SCSI storage controller: QLogic Corp. ISP1020 Fast-wide SCSI (rev 06) 
01:08.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)

scanpci:

pci bus 0x0 cardnum 0x07 function 0x0000: vendor 0x1080 device 0xc693
 Contaq 82C693

pci bus 0x0 cardnum 0x07 function 0x0001: vendor 0x1080 device 0xc693
 Contaq 82C693

pci bus 0x0 cardnum 0x07 function 0x0002: vendor 0x1080 device 0xc693
 Contaq 82C693

pci bus 0x0 cardnum 0x07 function 0x0003: vendor 0x1080 device 0xc693
 Contaq 82C693

pci bus 0x0 cardnum 0x0c function 0x0000: vendor 0x1000 device 0x000c
 NCR 53c895

pci bus 0x0 cardnum 0x0d function 0x0000: vendor 0x104c device 0x3d07
 Texas Instruments Permedia 2

pci bus 0x1 cardnum 0x03 function 0x0000: vendor 0x1011 device 0x0019
 Digital DC21142 10/100 Mb/s Ethernet

pci bus 0x1 cardnum 0x06 function 0x0000: vendor 0x1077 device 0x1020
 QLogic ISP1020

pci bus 0x1 cardnum 0x08 function 0x0000: vendor 0x1011 device 0x0024
 Digital DC21152

--- End Message ---
--- Begin Message --- 
Closing, as suggested by the submitter, since he does not have the
hardware anymore.
If anybody ever reproduces this problem, feel free to reopen.

Brice

--- End Message ---
Reply to: