72181 – [v3.13][regression] NULL pointer deref (_nouveau_clock_init)

Bug 72181 - [v3.13][regression] NULL pointer deref (_nouveau_clock_init)

Summary: [v3.13][regression] NULL pointer deref (_nouveau_clock_init)

Status:	RESOLVED FIXED

Alias:	None

Product:	xorg
Classification:	Unclassified
Component:	Driver/nouveau (show other bugs)
Version:	git
Hardware:	Other All

Importance:	medium normal
Assignee:	Nouveau Project
QA Contact:	Xorg Project Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2013-11-30 18:08 UTC by Ronald
Modified:	2013-12-14 07:05 UTC (History)
CC List:	0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Ronald 2013-11-30 18:08:47 UTC

Bug looks like: https://bugs.freedesktop.org/show_bug.cgi?id=71824

Dmesg: http://pastebin.com/raw.php?i=2QyAqsuA

Dmesg with patch mentioned in bug #71824: http://pastebin.com/raw.php?i=fdsLkdK4

Comment 1 Emil Velikov 2013-11-30 18:30:09 UTC

Give this bad boy a try, it should resolve the problem

http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=0397aaaa009092427dc60aea8b3c21c00526d8ba

Comment 2 Ronald 2013-12-01 07:20:44 UTC

Thank you, xexaxo already suggested that patch on IRC. This fixed the bug. Too bad it's not upstream yet :/ .

Comment 3 Ben Skeggs 2013-12-01 21:15:19 UTC

(In reply to comment #2)
> Thank you, xexaxo already suggested that patch on IRC. This fixed the bug.
> Too bad it's not upstream yet :/ .
Technically, Linus's tree is downstream :P But, I'll be sending a fixes tree during the week. 

Ben.

Comment 4 Emil Velikov 2013-12-13 19:42:57 UTC

I wonder who suggested the very same patch as the very same moment :-)

Either way this patch is part of the "drm-fixes-3.13" pull request for Linus, and it should be merged shortly.

Comment 5 Ronald 2013-12-14 07:05:42 UTC

I think it's already there...

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau?id=5b19f4f9bdb69d53f967b5733d6c3273d2397b9c

Thanks!

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.