Bug 722621 - intel_gpu_top: flotimng point segfault
Summary: intel_gpu_top: flotimng point segfault
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:crash]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-15 21:26 UTC by Harald Reindl
Modified: 2018-04-11 16:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 14:44:40 UTC
Type: ---


Attachments (Terms of Use)

Description Harald Reindl 2011-07-15 21:26:44 UTC
the driver works perfectly but the intel-gpu-tools-2.15.0-5.fc15.x86_64 are segfaulting (the same with the previous build), i do not know what they are doing because got them never started and was interested what this is

Gleitkomma-Ausnahme
[root@rh:~]$ dmesg -c
intel_gpu_top[1958] trap divide error ip:401108 sp:7fff660f6580 error:0 in intel_gpu_top[400000+5000]

Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz

00:00.0 Host bridge: Intel Corporation Sandy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Sandy Bridge PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Sandy Bridge Integrated Graphics Controller (rev 09)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b4)
00:1c.4 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 5 (rev b4)
00:1c.6 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 7 (rev b4)
00:1c.7 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 8 (rev b4)
00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
00:1f.0 ISA bridge: Intel Corporation Cougar Point LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Cougar Point 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 04)
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
02:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
03:00.0 Mass storage controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)

Comment 1 Matěj Cepl 2011-07-16 20:11:19 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

Please provide also exact description actions to be taken to reproduce this bug, what did you expect to happen, and what actually happened, so that we can try to reproduce the issue here.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Chad 2011-07-20 13:08:25 UTC

# gdb intel_gpu_top

Program received signal SIGFPE, Arithmetic exception.
0x08048e30 in main (argc=1, argv=0xbffff804) at intel_gpu_top.c:377
377			printf("%30s: %d/%d (%d%%)\n", "ring space",
(gdb)

Comment 3 Matěj Cepl 2011-07-21 14:21:16 UTC
Could you please add as also a full backtrace when this happens, please? (in the situation displayed in the comment 2 run command backtrace)

Also logs requested in the previous comment would be helpful.

Thank you

Comment 4 Harald Reindl 2011-07-21 14:26:32 UTC
this has nothing to do with the xserver because the same happens per SSH-X-Forwarding, this binary seems to be simply broken - have you ever tried to call it somewhere?

Comment 5 Chad 2011-07-21 14:31:31 UTC
Program received signal SIGFPE, Arithmetic exception.
________________________________________________________________________________

 Registers: 
Registers:
   eax:    0x00000000
   ebx:    0x00000064
   ecx:    0x00000000
   edx:    0x00000000
   eflags: 0x00010246
   esi:    0xb7bf6350
   edi:    0x00000058
   esp:    0xbffff6d0
   ebp:    0xbffff758
   eip:    0x08048e30
   cs:     0x0073
   ds:     0x007b
   es:     0x007b
   fs:     0x0000
   gs:     0x0033
   ss:     0x007b

Flags:
   o d I t s Z a P c 

[0x007b:0xbffff6d0]----------------------------------------------------[ STACK ]

BFFFF720 : 01 00 00 00  04 F8 FF BF - 3C D3 5E 00  50 00 00 00 ........<.^.P...
BFFFF710 : 00 00 00 00  00 40 BF B7 - 00 40 BF B7  64 00 00 00 .....@...@..d...
BFFFF700 : 00 00 00 00  04 F8 FF 00 - 02 01 00 00  00 00 00 00 ................
BFFFF6F0 : 00 00 00 00  01 00 00 00 - 48 F2 04 08  10 27 00 00 ........H....'..
BFFFF6E0 : 08 F7 FF BF  6A 1E 51 44 - 00 00 00 00  00 08 10 06 ....j.QD........
BFFFF6D0 : 01 00 00 00  DC B6 04 08 - D1 B6 04 08  64 00 00 00 ............d...


[007B:B7BF6350]-----------------------------------------------------[ DATA ]

B7BF6350 : 00 00 00 00  00 00 00 00 - 00 00 00 00  00 00 00 00 ................
B7BF6360 : 00 00 00 00  00 00 00 00 - 00 00 00 00  00 00 00 00 ................

[0x0073:0x08048e30]-----------------------------------------------------[ CODE ]

=> 0x8048e30 <main+1440>:	divl   0x30(%esp)
   0x8048e34 <main+1444>:	mov    0x30(%esp),%edx
   0x8048e38 <main+1448>:	mov    %edx,0x10(%esp)
   0x8048e3c <main+1452>:	mov    $0x68db8bad,%edx
   0x8048e41 <main+1457>:	mov    %eax,0x14(%esp)
   0x8048e45 <main+1461>:	mov    0x3c(%esp),%eax
   0x8048e49 <main+1465>:	imul   %edx
   0x8048e4b <main+1467>:	sar    $0xc,%edx
   0x8048e4e <main+1470>:	sub    %ecx,%edx
   0x8048e50 <main+1472>:	mov    %edx,0xc(%esp)
   0x8048e54 <main+1476>:	call   0x80487b4 <__printf_chk@plt>
   0x8048e59 <main+1481>:	movl   $0x804b6f0,0xc(%esp)

________________________________________________________________________________

0x08048e30 in main (argc=0x1, argv=0xbffff804) at intel_gpu_top.c:377
377			printf("%30s: %d/%d (%d%%)\n", "ring space",
(gdb) bt f
#0  0x08048e30 in main (argc=0x1, argv=0xbffff804) at intel_gpu_top.c:377
        clear_screen = "\033[H\033[J"
        total_ring_full = 0x0
        ring_idle = 0x2710
        percent = 0x64
        len = <value optimized out>
        ws = {
          ws_row = 0x5e, 
          ws_col = 0x50, 
          ws_xpixel = 0x0, 
          ws_ypixel = 0x0
        }
        j = <value optimized out>
        max_lines = 0x58
        pci_dev = 0x804f248
        ring_size = 0x0
        devid = 0x102
        i = <value optimized out>

Comment 6 Matěj Cepl 2011-07-21 16:06:53 UTC
(In reply to comment #4)
> have you ever tried to call it somewhere?

Of course, works for me.

Comment 7 Fedora End Of Life 2012-08-07 14:44:42 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.