From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 90390] New: [NV98] Modesetting causes blank screen because of INVALID_STATE [UNK0B] chid 1 mthd 0x0080 data 0x00000000
Date: Sun, 10 May 2015 19:53:30 +0000 [thread overview]
Message-ID: <bug-90390-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1526 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90390
Bug ID: 90390
Summary: [NV98] Modesetting causes blank screen because of
INVALID_STATE [UNK0B] chid 1 mthd 0x0080 data
0x00000000
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: analizer-o+MxOtu4lMCHXe+LvDLADg@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Environment:
Video card: GeForce 9300M GS (laptop)
Kernel: 4.0.2-gentoo
Steps to reproduce:
1. Boot
2. modprobe drm_kms_heloper
3. modprobe nouveau
Expected result:
Framebuffer initialization
Actually after dozen attempts I had framebuffer initialized once, background
was red, foreground was black and I never was able to achieve this again.
Actual result:
Blank screen. Still able to process keyboard input, so kernel log can be
gathered and system can be safely rebooted.
Results with various parameters:
With `nouveau.noaccel=1` I'm getting black screen instead of blank screen and
system is not responsive to keyboard input.
With `nouveau.modeset=0` nothing happens after `modprobe nouveau`, this makes
me think this is a modesetting issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2758 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-05-10 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 19:53 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-90390-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-05-10 19:54 ` [Bug 90390] [NV98] Modesetting causes blank screen because of INVALID_STATE [UNK0B] chid 1 mthd 0x0080 data 0x00000000 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-10 19:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-10 19:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-10 19:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-10 19:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-10 20:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-10 21:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:59 ` 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-90390-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.