Bug 65771 - Oops after starting nouveau with NVAA / NV50 (Nvidia 8200)
Summary: Oops after starting nouveau with NVAA / NV50 (Nvidia 8200)
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: i386 Linux
: P1 high
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-25 17:34 UTC by dirkneukirchen
Modified: 2013-12-07 10:04 UTC (History)
0 users

See Also:
Kernel Version: 3.13-rc1
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
3.13-rc1 debug kernel log recv. via netconsole (15.23 KB, text/plain)
2013-11-25 17:34 UTC, dirkneukirchen 		Details
acpidump output; just in case (178.03 KB, text/plain)
2013-11-25 17:37 UTC, dirkneukirchen 		Details
dmesg of successfull boot of 3.12.1 (24.66 KB, text/plain)
2013-11-25 17:44 UTC, dirkneukirchen 		Details
Add an attachment (proposed patch, testcase, etc.)

Description dirkneukirchen 2013-11-25 17:34:57 UTC 
Created attachment 115981 [details]
3.13-rc1 debug kernel log recv. via netconsole

Desktop didn't come up after updating Kernel from 3.12.0 to 3.13-rc1.
Screen remains black.

A netconsole log showed the messages possibly responsable for the Oops:
[   11.132842] nouveau E[     CLK][0000:02:00.0] 17 freq unknown
[   11.132901] nouveau E[     CLK][0000:02:00.0] init failed, -22
[   11.132966] nouveau E[     DRM] failed to create 0x80000080, -22
[   11.133734] nouveau: probe of 0000:02:00.0 failed with error -22

System:
- Linux Mint 15 with vanilla kernel 3.13-rc1
- dual screen
Comment 1 dirkneukirchen 2013-11-25 17:37:57 UTC 
Created attachment 115991 [details]
acpidump output; just in case
Comment 2 dirkneukirchen 2013-11-25 17:44:18 UTC 
Created attachment 116001 [details]
dmesg of successfull boot of 3.12.1
Comment 3 dirkneukirchen 2013-12-07 10:04:29 UTC 
the card does come up after adding

drm/nouveau/clk: Add support for NVAA/NVAC

http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=drm-nouveau-next&id=a7e4201f0f7d47e03b851f06f8987856e8d33083
Note You need to log in before you can comment on or make changes to this bug.