linux-kernel - Re: [Intel-gfx] Excessive WARN()s in Intel 915 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140108184323.GL4800@intel.com>
Date:	Wed, 8 Jan 2014 20:43:23 +0200
From:	Ville Syrjälä <ville.syrjala@...ux.intel.com>
To:	Alan Stern <stern@...land.harvard.edu>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [Intel-gfx] Excessive WARN()s in Intel 915 driver

On Wed, Jan 08, 2014 at 05:17:13PM +0100, 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/
> 
> Thanks, Daniel

The log looks fairly clear to me:

1. initially panel fitter is enabled on pipe B, and pipe B is outputting
   to LVDS and VGA. Border is enabled.
2. pipe A gets enabled outputting to LVDS. This will overwrite the
   LVDS border bits
3. pipe B is still active so we do the state check, but as the LVDS
   border bits have been clobbered earlier, the state checker gets
   angry

This actually hits another problem we still have. We've changing the
pipe for the LVDS port w/o shutting the port down in between. That
doesn't sound entirely safe. I wonder if we still have some real
issues preventing this change?

         * intel_modeset_setup_hw_state does not.
         */
        *modeset_pipes &= 1 << intel_crtc->pipe;
-       *prepare_pipes &= 1 << intel_crtc->pipe;
 
        DRM_DEBUG_KMS("set mode pipe masks: modeset: %x, prepare: %x, disable: %x\n",
                      *modeset_pipes, *prepare_pipes, *disable_pipes);

-- 
Ville Syrjälä
Intel OTC
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/