All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
Date: Sun, 11 Jun 2017 19:33:24 +0000	[thread overview]
Message-ID: <bug-101368-502-eXThUvSlVC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101368-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from Ben Steel <bhs_suse@precisionforesight.com> ---
Created attachment 131881
  --> https://bugs.freedesktop.org/attachment.cgi?id=131881&action=edit
dmesg after rmmod and insmod of nouveau

Tried the command 
  sudo rmmod -v nouveau 
followed by
  sudo insmod
/lib/modules/4.11.3-1-default/kernel/drivers/gpu/drm/nouveau/nouveau.ko 

X was not running and I was on console. In each case stdout and stderr were
redirected, but results were zero-length, so omitted for clarity.
Results of insmod:
Visibly, the four dmesg items from 1763.415095 to 1763.417364 were shown, the
dispay froze up and the fan turned on, blowing very warm air. SSH was very
slow, taking around a minute to get a prompt. Each command typed could take a
similar amount of time. A shutdown command was never able to complete. Dmesg
output during the ssh session after insmod is attached. Hope this helps.

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

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

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-06-11 19:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-10  4:40 [Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot bugzilla-daemon
2017-06-10 11:58 ` bugzilla-daemon
2017-06-10 18:03 ` bugzilla-daemon
2017-06-10 19:55 ` bugzilla-daemon
2017-06-11 19:33 ` bugzilla-daemon [this message]
2017-06-11 23:08 ` bugzilla-daemon
2017-06-13 20:41 ` bugzilla-daemon
2017-06-13 21:07 ` bugzilla-daemon
2017-06-13 23:20 ` bugzilla-daemon
     [not found] <bug-101368-8800@http.bugs.freedesktop.org/>
     [not found] ` <bug-101368-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-06-13 23:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-14  0:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-20 13:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-21 16:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-22 15:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-23  1:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-23 16:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26 11:21   ` 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-101368-502-eXThUvSlVC@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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 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.