From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 98383] X server is crashing/eats 100% cpu when turning on monitor
Date: Wed, 29 Mar 2017 15:06:13 +0000 [thread overview]
Message-ID: <bug-98383-8800-BwfYQ5v39W@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98383-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1380 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98383
Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|high |medium
Severity|critical |normal
--- Comment #8 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to Mariusz Białończyk from comment #7)
> It is now over a five months from the time when I reported it. Is it really
> so hard to cooperate with me to get rid of this bug? I can try your patches,
> give you additional debug information, I have programming skills.
A few things to consider:
1. nouveau is largely volunteer-driven. Volunteers tend to do the things that
interest them, not the things that interest non-contributors. (Which means that
the end user may have to persuade that their problem is more worthwhile to work
on, and stomping your foot on the ground isn't the best way to achieve that.)
2. You initially filed the bug against a component that no nouveau developer
monitors
3. If you want to get help figuring this out yourself, you may want to try
#nouveau and #dri-devel on freenode.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2853 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2017-03-29 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-98383-8800@http.bugs.freedesktop.org/>
[not found] ` <bug-98383-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-03-29 8:30 ` [Bug 98383] X server is crashing/eats 100% cpu when turning on monitor bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-29 15:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-04-03 15:42 ` 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-98383-8800-BwfYQ5v39W@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.