All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 64774] New: nouveau GF108 kernel crash in optimus mode when enabling external display output
Date: Sun, 19 May 2013 20:54:37 +0000	[thread overview]
Message-ID: <bug-64774-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2490 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=64774

          Priority: medium
            Bug ID: 64774
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: nouveau GF108 kernel crash in optimus mode when
                    enabling external display output
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: major
    Classification: Unclassified
                OS: All
          Reporter: pasik-X3B1VOXEql0@public.gmane.org
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Created attachment 79549
  --> https://bugs.freedesktop.org/attachment.cgi?id=79549&action=edit
dmesg Linux 3.8.11 nouveau optimus before the kernel crash

I'm using Lenovo T430 laptop with intel+nvidia hybrid graphics, optimus is
enabled in BIOS:

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [Quadro NVS 5400M]
(rev a1)

$ uname -a
Linux localhost.localdomain 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I boot up the system with only laptop internal LVDS active on intel gpu, and
when in X session, I enable the second display on nouveau gpu connected to the
dock DP2/DVI connector. 
At this point the kernel crashes immediately.

Screenshots of the kernel crash/stacktrace here:
http://pasik.reaktio.net/nouveau/debug/nouveau-kernel-crash01.jpg
http://pasik.reaktio.net/nouveau/debug/nouveau-kernel-crash02.jpg

hand-written bits from the kernel crash:

Pid: 1208, comm: Xorg Not tainted 3.8.11-200.fc18.x86_64 #1 LENOVO
2349H2G/2349H2G
RIP: 0010:[<ffffffffa01abb7e>] [<ffffffffa01abb7e>] nvc0_vm_map_sg+0x8e/0x110
[nouveau]
RSP: 0018:ffff8803298357c8 EFLAGS: 00010206
..
Process Xorg (pid: 1208,..)
..
Call Trace:
.. nouveau_vm_map_sg+0xc2/0x130 [nouveau]
.. nouveau_vma_getmap.isra.11+0x68/0xa0 [nouveau]
.. nouveau_bo_move_m2mf.isra.12+0x85/0x140 [nouveau]
.. ? nouveau_vm_map_at+0x153/0x1c0 [nouveau]
.. nouveau_bo_move+0xa5/0x400 [nouveau]
.. ttm_bo_handle_move_mem+0x245/0x610 [ttm]

More info from the screenshots above (also attached)..

Kernel dmesg from before the crash attached.
I also tried with Linux kernel 3.9.2 and there the system crashes hard aswell.

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

[-- Attachment #1.2: Type: text/html, Size: 4179 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-05-19 20:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 20:54 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-64774-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-05-19 20:55   ` [Bug 64774] nouveau GF108 kernel crash in optimus mode when enabling external display output bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 21:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 21:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 12:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-21 10:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 18:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 20:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 16:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 17:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 17:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-01 16:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-02  0:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-02  1:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-06 16:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-64774-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.