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 101322] GM108/NV118: 0 MiB DDR3 and boot crash in gf100_ltc_oneinit_tag_ram
Date: Wed, 18 Oct 2017 08:00:04 +0000	[thread overview]
Message-ID: <bug-101322-8800-OCUhO2P19G@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101322-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #11 from Daniel Drake <dan-LrsmPHowOvpd3aXB8m+yKQ@public.gmane.org> ---
Sent partial dump from nvidia proprietary driver to mmio.dumps address:


I loaded the module and then started an empty X session.
Unfortunately with tracing enabled, this results in an instant hard hang
upon starting X, before it has rendered the black screen.

However I managed to capture these messages over the network up until
the point of hang.

Captured on Linux 4.13. No external displays connected. The all-in-one PC
has one internal LCD display.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2017-10-18  8:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 20:30 [Bug 101322] New: GM108/NV118: 0 MiB DDR3 and boot crash in gf100_ltc_oneinit_tag_ram bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-101322-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-06-06 20:52   ` [Bug 101322] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-07 13:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-07 13:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-07 13:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-08 14:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-13 15:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-14  0:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-17  8:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-12  8:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-12 20:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-18  8:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-10-18 19:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-20  8:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:28   ` 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-101322-8800-OCUhO2P19G@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.