698872 – segfault in libnvidia-glcore.so

Bug 698872 - segfault in libnvidia-glcore.so [NEEDINFO]

Summary: segfault in libnvidia-glcore.so

Keywords:
Status:	CLOSED CANTFIX
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	gnome-shell
Sub Component:
Version:	15
Hardware:	i686
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Assignee:	Owen Taylor
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:	abrt_hash:c2b841989bce6d4ad3eb516392d...
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2011-04-22 05:38 UTC by Sriram Ramkrishna
Modified:	2023-09-29 03:16 UTC (History)
CC List:	11 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2011-05-04 13:33:38 UTC
Type:	---
Embargoed:
Dependent Products:
Flags:	ferdnyc: needinfo? (otaylor)

Attachments	(Terms of Use)
File: event_log (22.01 KB, text/plain) 2011-04-22 05:39 UTC, Sriram Ramkrishna	no flags	Details
File: build_ids (5.45 KB, text/plain) 2011-04-22 05:39 UTC, Sriram Ramkrishna	no flags	Details
File: dsos (32.41 KB, text/plain) 2011-04-22 05:39 UTC, Sriram Ramkrishna	no flags	Details
File: maps (36.55 KB, text/plain) 2011-04-22 05:39 UTC, Sriram Ramkrishna	no flags	Details
File: backtrace (21.00 KB, text/plain) 2011-04-22 05:39 UTC, Sriram Ramkrishna	no flags	Details
backtrace (574.02 KB, text/plain) 2023-05-12 10:19 UTC, Mikhail	no flags	Details
View All

Description Sriram Ramkrishna 2011-04-22 05:38:57 UTC

abrt version: 2.0.1
comment: I wasn't doing anything in particular - I had Impress running, web browser, and rhythmbox, teh browser was pointed at gmail and live.gnome.org
executable: /usr/bin/gnome-shell
cmdline: /usr/bin/gnome-shell
component: gnome-shell
reported_to: file: /tmp/abrt.log
uid: 500
kernel: 2.6.38.2-9.fc15.i686
architecture: i686
reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
package: gnome-shell-3.0.0.2-2.fc15
username: sramkris
rating: 0
time: 1303368793
os_release: Fedora release 15 (Lovelock)

Text file: event_log, 22542 bytes
Binary file: smaps, 215057 bytes
Text file: build_ids, 5578 bytes
Binary file: coredump, 249917440 bytes
Text file: dsos, 33191 bytes
Text file: maps, 37425 bytes
Text file: backtrace, 21505 bytes

Comment 1 Sriram Ramkrishna 2011-04-22 05:39:00 UTC

Created attachment 494065 [details]
File: event_log

Comment 2 Sriram Ramkrishna 2011-04-22 05:39:06 UTC

Created attachment 494066 [details]
File: build_ids

Comment 3 Sriram Ramkrishna 2011-04-22 05:39:08 UTC

Created attachment 494067 [details]
File: dsos

Comment 4 Sriram Ramkrishna 2011-04-22 05:39:10 UTC

Created attachment 494068 [details]
File: maps

Comment 5 Sriram Ramkrishna 2011-04-22 05:39:12 UTC

Created attachment 494069 [details]
File: backtrace

Comment 6 Owen Taylor 2011-04-23 19:58:17 UTC

This is a segfault inside the nvidia proprietary driver. Since that driver is compiled without frame pointers, we don't even get a backtrace that might indicate what part of our code might be triggering the problem.

Comment 7 Sriram Ramkrishna 2011-04-23 23:19:12 UTC

Ah, such as it is then.  Since it is an nvidia proprietary driver,  I'll have to wait for the next version or something to see if it is going away.

Thanks for looking into the backtrace, much appreciated.

Comment 8 Elad Alfassa 2011-05-04 13:33:38 UTC

Closing.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 9 Mikhail 2023-05-12 10:19:35 UTC

Created attachment 1964186 [details]
backtrace

Thats odd but abrt leaded me to this report (I am amdgpu user)

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Generating backtrace
Backtrace is generated and saved, 29230 bytes

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#698872' was found
abrt-action-find-bodhi-update [ERROR] abrt-bodhi does not support product version 'Rawhide'

Comment 10 randall 2023-06-06 18:29:13 UTC

This is not just an Nvidia bug. I have AMD and as far as I can tell running only the items available via the default installation with third party enabled. I haven't added any additional repositories outside of what is added during the installation. In fact, this installation is clean, I only installed and updated today.


--- Running report_uReport ---
('report_uReport' completed successfully)

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Generating backtrace
Backtrace is generated and saved, 47771 bytes

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#698872' was found
Searching for updates
No updates for this package found

Comment 11 Jonathan Haas 2023-08-30 06:43:01 UTC

I've also just got a crash like this, but I've got an Intel GPU.

--- Running report_uReport ---
(»report_uReport« erfolgreich abgeschlossen)

--- Überspringe collect_GConf ---
Für diesen Event wurden keine passenden Aktionen gefunden.

--- Überspringe collect_xsession_errors ---
Für diesen Event wurden keine passenden Aktionen gefunden.

--- Überspringe collect_vimrc_user ---
Für diesen Event wurden keine passenden Aktionen gefunden.

--- Überspringe collect_vimrc_system ---
Für diesen Event wurden keine passenden Aktionen gefunden.

--- Running analyze_CCpp ---
Ablaufverfolgung erstellen
Ablaufverfolgung wurde erstellt und gespeichert, 26552 Byte

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#698872' was found
Searching for updates
No updates for this package found


See https://retrace.fedoraproject.org/faf/reports/652495/

Comment 12 Filip Bartmann 2023-09-18 10:27:10 UTC

I have this bug on Intel GPU too.

Comment 13 "FeRD" (Frank Dana) 2023-09-29 02:53:56 UTC

Just came up as a duplicate for me as well, after a crash in Nouveau.

I understand that the original report can't be addressed as it involves the Nvidia proprietary driver, but is there anything that can be done to stop Abrt detecting this bug as a duplicate of so many other crashes, and preventing valid reports from being opened?

(Also, in the more immediate term, is there any way I can force Abrt to ignore this bug and open a new one, while I still have the crash data on my system?)

Comment 14 "FeRD" (Frank Dana) 2023-09-29 03:16:42 UTC

Ah, I just noticed the "Reporting is disabled because the generated backtrace has low informational value" message at the top of the Abrt log window, so maybe it's not this bug that's preventing reporting after all.

(Still, as I said I'm running Nouveau. If a useful backtrace can't be collected from that then something seems very off, it's a fully open-source driver.)

Anyway, the retrace server report is here:

https://retrace.fedoraproject.org/faf/reports/748391/


And the /var/log/messages dump from Nouveau showed:

User Logs:
--Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: kernel rejected pushbuf: No such device
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: krec 0 pushes 1 bufs 12 relocs 0
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000000 00000012 00000004 00000004 00000000 0x7f851c152000 0xc00000 0x80000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000001 00000006 00000004 00000000 00000004 0x7f8529454000 0x218000 0x1000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000002 00000045 00000004 00000004 00000000 0x7f851fe02000 0x53a0000 0x20000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000003 00000226 00000002 00000002 00000002 (nil) 0x3460000 0x20000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000004 00000008 00000002 00000002 00000002 (nil) 0x2e0000 0xe0000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000005 00000195 00000002 00000002 00000000 (nil) 0x5180000 0x80000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000006 0000000b 00000002 00000002 00000000 (nil) 0x8e0000 0x20000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000007 0000000a 00000002 00000002 00000002 (nil) 0x7e0000 0x100000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000008 00000007 00000002 00000002 00000000 (nil) 0x260000 0x80000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 00000009 00000016 00000002 00000000 00000002 (nil) 0xd00000 0x960000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 0000000a 00000017 00000002 00000000 00000002 (nil) 0x1660000 0x960000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: buf 0000000b 00000085 00000004 00000004 00000000 0x7f84c41f9000 0x55c0000 0x400000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau: ch5: psh 00000000 0000007728 0000007a8c
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20048100
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x053a0000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x03478000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20018106
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00001f00
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x200180c0
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000186
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x200203fd
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x07800000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x04b00000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20090200
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00d00000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000780
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x000004b0
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x000000e6
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000040
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000001
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x200503f8
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x01660000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000016
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000040
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x2001054e
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000001
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x2003048a
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000780
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x000004b0
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00010001
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x200105e7
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20010487
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x0fac6881
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x80000574
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x80000671
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x800004b9
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x80000e04
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x800103e4
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20010680
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x2001054f
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x800004b3
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x8000066f
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x200504e0
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000001
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00001e01
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00001e01
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00001e01
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000207
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x200204e6
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x000000ff
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000003
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x80000565
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x800004bb
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x800105a1
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x800005a2
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x80000980
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x200104ea
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x8000054d
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x8000055c
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x200104ed
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x8000059b
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x80000644
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20010546
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20010581
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000004
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x80000548
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x80000596
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20010e06
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00001b02
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20010e08
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00001b02
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x8000036d
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x20030646
Jul 20 20:31:40 teevey gnome-shell[1467312]: nouveau:         0x00000000
--

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