From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91738] New: xf86-video-nouveau 1.0.11 will not allow X to start
Date: Sun, 23 Aug 2015 19:00:34 +0000 [thread overview]
Message-ID: <bug-91738-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1293 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91738
Bug ID: 91738
Summary: xf86-video-nouveau 1.0.11 will not allow X to start
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: ryan.q-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 117881
--> https://bugs.freedesktop.org/attachment.cgi?id=117881&action=edit
dmesg_before_startx
Host machine is Slackware64-current.
- xf86-video-nouveau 1.0.11
- xorg-server 1.17.2
- Linux 4.1.6
X is unable to start from what appears to be a block by nouveau. Blacklisting
nouveau in /etc/modprobe.d/nouveau.conf like so:
blacklist nouveau
results in a kernel panic. See attached dmesg and Xorg.0.log. Forgive me if I
am reporting this bug in the wrong place.
Thank you.
dmesg:
http://sprunge.us/fNHi
Xorg.0.log
http://sprunge.us/XhRO
dmesg after startx:
http://sprunge.us/gEdV
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2752 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-08-23 19:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 19:00 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-91738-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-08-23 19:00 ` [Bug 91738] xf86-video-nouveau 1.0.11 will not allow X to start bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-23 19:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-23 19:08 ` [Bug 91738] [VN117] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-23 19:08 ` [Bug 91738] [NV117] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-23 21:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-23 22:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 2:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 2:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 3:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 3:08 ` [Bug 91738] [NV117] NULL deref in nvkm_i2c_try_acquire_pad, kernel 4.1 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 3:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 3:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 3:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 3:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 4:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 4:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-25 5:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-19 1:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-22 20:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-22 20:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-22 21:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-28 2:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-28 2:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-25 17:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-20 18:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-21 0:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-21 0:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:03 ` 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-91738-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.