dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Zumbiehl <florz@florz.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@intel.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: i915 ERRORs and WARN_ON()s
Date: Fri, 29 Apr 2016 04:27:08 +0200	[thread overview]
Message-ID: <20160429022708.GL26959@florz.florz.de> (raw)
In-Reply-To: <871t5rji14.fsf@intel.com>

Hi,

> The Bugzilla at https://bugs.freedesktop.org is our tool of choice for
> tracking bugs in drm/i915. It's your choice to not create an account
> there, but please, don't expect us to work as a proxy between you and
> bugzilla either. It's a much bigger and unscalable inconvenience for us
> than it is for you to create that account.

Hu? I don't quite get it. Communicating via email is an unscalable
inconvenience? So, if I asked you to create an account with my todo tracker
instead, would that be more scalable and convenient? Using everyone's
software of choice instead of my own most certainly is neither scalable nor
convenient for me at all.

> > You mean the ones I reported a month ago should be fixed? Should I try a
> > newer nightly to check?
> 
> Yes, please.
> 
> I'd also like to get a full dmesg from you, with drm.debug=14 module
> parameter set, all the way from boot to the problem.

http://rain.dyn.florz.de/drm-intel-nightly_1101e5fcc_dmesg.txt

Doesn't look much different than the one from a month ago (except much more
verbose, obviously), unfortunately, and the Xv stuttering also persists.

> However, personally I find it a bit obnoxious to send big logs by mail
> to hundreds or thousands of other people on the lists who really aren't
> at all interested in them. Maybe you don't mind bothering them? It's
> also not good to hide it away in my private inbox alone, because there
> are other developers who will be interested. It has also proven to be
> problematic to upload files to pastebins etc. where they expire at some
> point in time, usually when we'd like to have a look.
> 
> Again, the obvious solution to the above is to file that bug and attach
> the dmesg there, at the unfortunate slight inconvenience of you creating
> an account there.

The obvious solution is to have a bug tracker that interfaces to email? I
mean, it's essentially a messaging system with per-thread group membership
(plus some management functionality that's mostly irrelevant to me), just
with its own account system and user interface instead of a standardized
SMTP interface so I can use the MUA of my choice. It's like if I were to
ask you to write replies to me into a web form I host somewhere instead of
using the reply function of your MUA, plus you'd first have to create an
account, of course.

Regards, Florian
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-04-29  2:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-26 11:21 blank screen on boot with i915/DRM_FBDEV_EMULATION Florian Zumbiehl
2016-03-29 12:01 ` Daniel Vetter
2016-03-29 16:44   ` Florian Zumbiehl
2016-03-30  6:29     ` Daniel Vetter
2016-03-30 23:14       ` i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION) Florian Zumbiehl
2016-04-12  1:23         ` Florian Zumbiehl
2016-04-27 10:03           ` Marius Vlad
2016-04-27 12:40             ` [Intel-gfx] " Florian Zumbiehl
2016-04-27 13:30               ` Jani Nikula
2016-04-29  2:27                 ` Florian Zumbiehl [this message]
2016-04-29 10:30                   ` [Intel-gfx] i915 ERRORs and WARN_ON()s David Weinehall
2016-05-01  0:11                     ` Florian Zumbiehl
2016-05-01  9:37                       ` Daniel Vetter
2016-05-02  0:35                         ` Florian Zumbiehl

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=20160429022708.GL26959@florz.florz.de \
    --to=florz@florz.de \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox