Bug 199133 - nouveau_mem_host+0x47/0x1b0 [nouveau]: NULL pointer dereference at 0000000000000040
Summary: nouveau_mem_host+0x47/0x1b0 [nouveau]: NULL pointer dereference at 0000000000...
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: drivers_video-dri
URL:
Keywords:
: 198853 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-03-17 10:27 UTC by Hector Cavalcanti Saavedra
Modified: 2018-03-18 10:50 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.15.8-300.fc27.x86_64
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
Details on the kernel oops. (4.45 KB, text/plain)
2018-03-17 10:27 UTC, Hector Cavalcanti Saavedra 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Hector Cavalcanti Saavedra 2018-03-17 10:27:21 UTC 
Created attachment 274787 [details]
Details on the kernel oops.

The nouveau driver causes kernel oops after the new DRM changes. I can reproduce by using my system for a few minutes, mainly when using Chromium or opening a PDF file (on Evince or on Chromium).
Comment 1 Hector Cavalcanti Saavedra 2018-03-17 10:28:41 UTC 
*** Bug 198853 has been marked as a duplicate of this bug. ***
Comment 2 Pierre Moreau 2018-03-17 14:36:52 UTC 
Could you please try with the patch mentioned in https://bugs.freedesktop.org/show_bug.cgi?id=105174 (which was submitted along other drm-fixes this week)?

Also, fyi, the Nouveau bugs are reported at https://bugs.freedesktop.org; see https://nouveau.freedesktop.org/wiki/Bugs/ for more details.
Comment 3 Hector Cavalcanti Saavedra 2018-03-18 10:50:31 UTC 
(In reply to Pierre Moreau from comment #2)
> Could you please try with the patch mentioned in
> https://bugs.freedesktop.org/show_bug.cgi?id=105174 (which was submitted
> along other drm-fixes this week)?
> 
> Also, fyi, the Nouveau bugs are reported at https://bugs.freedesktop.org;
> see https://nouveau.freedesktop.org/wiki/Bugs/ for more details.

Oops, my bad. Thank you for the patch, I'm going to try it and close this bug.
Note You need to log in before you can comment on or make changes to this bug.