Bug 33969

Summary: "unable to handle kernel paging request" crash after playing tuxracer for a few seconds
Product: DRI Reporter: Adam Rak <adam.rak>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Full dmesg after the crash none

Description Adam Rak 2011-02-06 09:32:00 UTC 
Created attachment 42998 [details] [review]
Full dmesg after the crash

Hardware is Fusion Zacate APU (HD6310)
Mesa is commit ec96b0ecdbe723f4664188010c7f86d5d7f41d82 checkout
ddx is commit a4899db96029acde6cd400fc0541693a487898e7 checkout
linux kernel is 2.6.38-rc3 commit 44f2c5c841da1b1e0864d768197ab1497b5c2cc1
X.Org X Server 1.7.7 (debian squeeze)

Running nexuiz crashes the X when entering play mode. (no apparent error log)

Running(and playing) extremetuxracer produces a kernel oops after a few seconds, the dmesg is in the attachment.
Comment 2 Adam Rak 2011-05-05 11:20:26 UTC 
I compiled a new kernel snapshot which had the patch, and nexuiz works fine, colors are good, brightness is good (even in ultra mode), and it didn't crash (so far).

only problem is this in kernel logs:
[  154.143277] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
[  167.311647] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
[  238.150304] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
[  239.764641] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
[  265.227673] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
[  267.913187] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!

but it still works.
Comment 3 Martin Peres 2019-11-19 08:17:43 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/drm/amd/issues/176.

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.