dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65771] New: Oops after starting nouveau with NVAA / NV50 (Nvidia 8200)
Date: Mon, 25 Nov 2013 17:34:57 +0000	[thread overview]
Message-ID: <bug-65771-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=65771

            Bug ID: 65771
           Summary: Oops after starting nouveau with NVAA / NV50 (Nvidia
                    8200)
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.13-rc1
          Hardware: i386
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: dirk.neukirchen@student.hu-berlin.de
        Regression: Yes

Created attachment 115981
  --> https://bugzilla.kernel.org/attachment.cgi?id=115981&action=edit
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

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2013-11-25 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 17:34 bugzilla-daemon [this message]
2013-11-25 17:37 ` [Bug 65771] Oops after starting nouveau with NVAA / NV50 (Nvidia 8200) bugzilla-daemon
2013-11-25 17:44 ` bugzilla-daemon
2013-12-07 10:04 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-65771-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox