Summary: | NVA0 KMS: kernel NULL pointer dereference | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Peter Sääf <peter.saaf> | ||||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | normal | ||||||||||
Priority: | medium | ||||||||||
Version: | unspecified | ||||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Comment on attachment 29219 [details]
kernel log
It's not a binary blob, it's text.
Created attachment 29647 [details]
kernel log with highmem disabled
Created attachment 29648 [details]
kernel config
It might be a good idea to write things down here and not just mention it on irc. I have tested for this bug with a few different cards I have access to with the following results. NVA0 (GTX 275) Crash NV92 (8800 GTS) Crash NV92 (9800 GT) Crash NV4B (7600 GT) Works So it seems only NV50 is affected. And there is some suspicion that this is only in combination with a 32bit kernel. Also, bugs #23847 and #29593 is probably the same as this one. Fixed as of 7798546495c04a810db86be34ba1f39e370fd325 From: Marcin Kościelnicki <koriakin@0x04.net> Date: Tue, 29 Sep 2009 21:50:16 +0000 Subject: drm/nouveau: fix missized allocation for ttm_bo_global struct |
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.
Created attachment 29219 [details] kernel log I have been getting this NULL pointer dereference since drm-next was merged to nouvuea/linux-2.6 master on August 21. The card is a GeForce GTX 275 (NVA0) The dereference does not happen in the following circumstances. 1. kernel has CONFIG_DEBUG_INFO=y 2. booting with kms disabled and then reloading the module with modeset=1 What other information should I provide to help figure this out? bisecting is difficult due to the drm-next merge. The attached trace is with current master (e02aed2)