public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>, Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] Excessive WARN()s in Intel 915 driver
Date: Tue, 14 Jan 2014 14:52:17 +0200	[thread overview]
Message-ID: <8738kqafpa.fsf@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1401131512380.2032-100000@iolanthe.rowland.org>

On Mon, 13 Jan 2014, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Wed, 8 Jan 2014, Daniel Vetter wrote:
>
>> On Wed, Jan 08, 2014 at 01:34:02PM -0500, Alan Stern wrote:
>> > On Wed, 8 Jan 2014, Daniel Vetter wrote:
>> > 
>> > > On Wed, Jan 08, 2014 at 11:08:08AM -0500, Alan Stern wrote:
>> > > > On Tue, 7 Jan 2014, Daniel Vetter wrote:
>> > > > 
>> > > > > I really want users to report these issues, and excessive WARNs seems
>> > > > > to be the only way to get those reports. Please boot with
>> > > > > drm.debug=0xe added to your kernel cmdline and reproduce this issues.
>> > > > > Also, which precise kernel are you running? Testing latest -rc is
>> > > > > always recommended, this state checker code is fairly new and gets
>> > > > > constantly extended and bugs fixed ...
>> > > > 
>> > > > Here you go.  This is the dmesg output after booting with
>> > > > drm.debug=0xe.  Pay no attention to the "AS" suffix in the version
>> > > > string; this is pristine 3.13-rc7.
>> > > 
>> > > That's strange, I've thought we've fixed the last struggling mismatch in
>> > > the lvds borber bits stuff. Can you please try latest drm-intel-nightly
>> > > from
>> > > 
>> > > http://cgit.freedesktop.org/~danvet/drm-intel/
>
> I posted the output from the default branch in that repository last
> week:
>
> 	http://marc.info/?l=linux-kernel&m=138922294308576&w=2
>
> Have you had time to look at the results yet?

I think it might be the time to file this as a new bug on DRM/Intel at
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI

BR,
Jani.


>
> Alan Stern
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center

  parent reply	other threads:[~2014-01-14 12:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 18:50 Excessive WARN()s in Intel 915 driver Alan Stern
2014-01-07 20:12 ` Daniel Vetter
2014-01-08 16:08   ` Alan Stern
2014-01-08 16:17     ` Daniel Vetter
2014-01-08 18:34       ` Alan Stern
2014-01-08 20:21         ` Daniel Vetter
2014-01-08 23:15           ` Alan Stern
2014-01-13 20:16           ` Alan Stern
2014-01-14  9:05             ` Daniel Vetter
2014-01-14 14:43               ` Alan Stern
2014-01-27  9:02                 ` Daniel Vetter
2014-01-27 15:30                   ` Alan Stern
2014-01-27 15:56                     ` Daniel Vetter
2014-01-27 16:05                       ` Alan Stern
2014-01-27 16:36                         ` Daniel Vetter
2014-01-27 17:14                           ` Alan Stern
2014-01-28 16:34                   ` Alan Stern
2014-01-14 12:52             ` Jani Nikula [this message]
2014-01-08 18:43       ` Ville Syrjälä
2014-01-28 17:17         ` Daniel Vetter
2014-01-28 19:42           ` Daniel Vetter
2014-01-30 14:53             ` Alan Stern
2014-01-30 15:22               ` Daniel Vetter
2014-01-30 15:52                 ` Alan Stern
2014-06-25 18:06       ` Regression in i915 driver in 3.16-rc2 Alan Stern
2014-06-25 18:26         ` Ville Syrjälä
2014-06-25 18:50           ` Alan Stern
2014-06-30 10:52             ` Jani Nikula

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=8738kqafpa.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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