Bug 104237

Summary: nouveau-related kmail crash
Product: xorg Reporter: Agostino Sarubbo <ago>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
kmail-debug
none
double-free none

Description Agostino Sarubbo 2017-12-13 08:33:44 UTC
Created attachment 136131 [details]
kmail-debug

I have a stable gentoo system, so atm I run:
mesa-17.1.10
libdrm-2.4.82
xf86-video-nouveau-1.0.15

I tested also:
mesa-17.3.0
libdrm-2.4.88

When I run kmail, it crashes and in dmesg I see:
[ 3514.679879] nouveau 0000:03:00.0: gr: TRAP ch 5 [003fb74000 kmail[23649]]
[ 3514.679889] nouveau 0000:03:00.0: gr: GPC0/TPC0/TEX: 80000041
[ 3514.679893] nouveau 0000:03:00.0: gr: GPC0/TPC1/TEX: 80000041
[ 3514.679904] nouveau 0000:03:00.0: fifo: read fault at 0002430000 engine 00 [PGRAPH] client 04 [GPC0/] reason 02 [PAGE_NOT_PRESENT] on channel 5 [003fb74000 kmail[23649]]
[ 3514.679906] nouveau 0000:03:00.0: fifo: gr engine fault on channel 5, recovering...
[ 3514.680191] nouveau 0000:03:00.0: kmail[23649]: channel 5 killed!


If I compile kmail with the debug stuff I get what is in the kmail-debug attachment.

If I compile also libdrm with the debug stuff I get a double-free which is in the double-free attachment.
Comment 1 Agostino Sarubbo 2017-12-13 08:34:07 UTC
Created attachment 136132 [details]
double-free
Comment 2 Martin Peres 2019-12-04 09:34:36 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/391.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.