dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66281] New: DRI_PRIME=1 glxinfo crashes and causes session to restart
Date: Sun, 01 Dec 2013 21:01:17 +0000	[thread overview]
Message-ID: <bug-66281-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 66281
           Summary: DRI_PRIME=1 glxinfo crashes and causes session to
                    restart
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.13 rc2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: mortem.dei@gmail.com
        Regression: No

I have a new laptop but the secondary GPU can't be accessed by the system
(neither with Nouveau nor bumblebee). With the kernel 3.12 the output of xrandr
didn't even show the card, but with the new one I do get the following output:


xrandr --listproviders

Providers: number : 2
Provider 0: id: 0x66 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs:
4 outputs: 3 associated providers: 1 name:Intel
Provider 1: id: 0x3f cap: 0x5, Source Output, Source Offload crtcs: 0 outputs:
0 associated providers: 1 name:nouveau

However, when I try to run anything with DRI_PRIME=1 glxinfo the system crashes
and I have to restart the session.

OS: Ubuntu 13.10
Laptop: Lenovo Ideapad u430p

Hardware: See lspci:

09:00.0 3D controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1)
    Subsystem: Lenovo Device 3800
    Flags: bus master, fast devsel, latency 0, IRQ 68
    Memory at b3000000 (32-bit, non-prefetchable) [size=16M]
    Memory at a0000000 (64-bit, prefetchable) [size=256M]
    Memory at b0000000 (64-bit, prefetchable) [size=32M]
    I/O ports at 3000 [size=128]
    Expansion ROM at <ignored> [disabled]
    Capabilities: [60] Power Management version 3
    Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [78] Express Endpoint, MSI 00
    Capabilities: [100] Virtual Channel
    Capabilities: [128] Power Budgeting <?>
    Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
    Kernel driver in use: nouveau

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

             reply	other threads:[~2013-12-01 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-01 21:01 bugzilla-daemon [this message]
2013-12-01 21:03 ` [Bug 66281] DRI_PRIME=1 glxinfo crashes and causes session to restart bugzilla-daemon
2014-05-09 17:11 ` bugzilla-daemon
2014-05-09 17:27 ` bugzilla-daemon
2014-05-09 17:45 ` bugzilla-daemon
2014-05-09 18:02 ` bugzilla-daemon
2014-05-12  8:24 ` bugzilla-daemon
2014-05-12 10:53 ` bugzilla-daemon
2014-07-26 13:26 ` 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-66281-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;
as well as URLs for NNTP newsgroup(s).