public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dave Airlie <airlied@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Sedat Dilek <sedat.dilek@gmail.com>
Subject: Re: Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ]
Date: Wed, 25 Sep 2013 11:19:13 +0300	[thread overview]
Message-ID: <20130925081913.GB5818@redhat.com> (raw)
In-Reply-To: <20130925075652.GG12663@phenom.ffwll.local>

On Wed, Sep 25, 2013 at 09:56:52AM +0200, Daniel Vetter wrote:
> On Wed, Sep 25, 2013 at 01:17:52PM +1000, Dave Airlie wrote:
> > On Mon, Sep 23, 2013 at 12:14 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > > On Mon, Aug 26, 2013 at 04:05:11PM +0300, Michael S. Tsirkin wrote:
> > >> On Wed, Aug 21, 2013 at 11:22:58AM +0200, Sedat Dilek wrote:
> > >> > [ Re: [Intel-gfx] i915 producing warnings with kernel 3.11-rc5 ]
> > >> >
> > >> > Hi,
> > >> >
> > >> > saw your posting in [1]... can you try the patches below?
> > >> > Not sure if they apply.
> > >> > Did you try v3.11-rc6(+)... or drm-intel-nightly?
> > >> >
> > >> > Regards,
> > >> > - Sedat -
> > >> >
> > >> > [1] http://lists.freedesktop.org/archives/intel-gfx/2013-August/032154.html
> > >>
> > >> Same thing observed with v3.11-rc7.
> > >
> > > I still see this with 3.11.
> > > Following this message, my VGA monitor goes blank and
> > > shows an error suggesting a wrong resolution or frequency are set.
> > > Anyone?
> > 
> > Daniel, Jesse?
> > 
> > still ongoing I think.
> 
> Yeah, I've dismissed it since the original issue in this thread is
> resolved. But it's something else.
> 
> Note to bug reporters: Please don't me-too, but start a new thread/report
> - almost every gfx bug is different, even if it superficially looks the
> same.
> 
> Michael, can you please boot with drm.debug=0xe, reproduce the problem and
> then attach the complete dmesg? Please make sure dmesg contains everything
> since boot-up, if not please increase the dmesg buffer size with
> log_buf_len=4M.
> 
> Also please test the latest drm-intel-fixes release to check that we
> haven't just forgotten to send the patch to stable (there's at least one
> flags mismatch fix already in-flight to 3.11 stable kernels).
> 
> Thanks, Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch


Will do. Holidays starting now so expect some reports
next week.

  reply	other threads:[~2013-09-25  8:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  8:49 linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ] Sedat Dilek
2013-07-01  8:52 ` Daniel Vetter
2013-07-01  9:03   ` Sedat Dilek
2013-07-02  5:31     ` Sedat Dilek
     [not found]       ` <CA+icZUW3K7RyUcfdos7aOkrEOd3To0kSns+G3GSfkPqqwo7z=w@mail.gmail.com>
2013-08-26 13:05         ` Fwd: " Michael S. Tsirkin
2013-08-26 17:28           ` Michael S. Tsirkin
2013-09-22 14:14           ` Fwd: linux-next: Tree for Jul 1 [ drm-intel-next: Several call-traces ] Michael S. Tsirkin
2013-09-25  3:17             ` Dave Airlie
2013-09-25  7:56               ` Daniel Vetter
2013-09-25  8:19                 ` Michael S. Tsirkin [this message]
2013-09-25 15:34                 ` Michael S. Tsirkin
2013-09-25 15:48                   ` [Intel-gfx] " Daniel Vetter
2013-09-29  6:28                     ` Michael S. Tsirkin

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=20130925081913.GB5818@redhat.com \
    --to=mst@redhat.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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