public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Daniel Vetter" <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] 4.2-rc4 kernel warnings on HSW laptop [regression]
Date: Tue, 13 Oct 2015 15:25:59 +0300	[thread overview]
Message-ID: <87lhb7550o.fsf@intel.com> (raw)
In-Reply-To: <20151013090521.GL26517@intel.com>

On Tue, 13 Oct 2015, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, Oct 13, 2015 at 10:24:58AM +0200, Daniel Vetter wrote:
>> On Mon, Oct 12, 2015 at 02:29:19PM +0200, Takashi Iwai wrote:
>> > On Mon, 12 Oct 2015 09:04:20 +0200,
>> > Daniel Vetter wrote:
>> > > 
>> > > Another pile of regressions for Jairo to track ...
>> > > 
>> > > On Sat, Oct 10, 2015 at 11:46:29AM +0200, Takashi Iwai wrote:
>> > > > Hi,
>> > > > 
>> > > > I noticed that a HSW laptop gets a few new warnings since 4.2-rc
>> > > > kernels.  One error messages pops at each boot time:
>> > > > 
>> > > >  Console: switching to colour dummy device 80x25
>> > > >  [drm] Replacing VGA console driver
>> > > >  [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>> > > >  [drm] Driver supports precise vblank timestamp query.
>> > > >  vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
>> > > >  [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!
>> > > 
>> > > There's patches for this one already, but I accidentally applied them for
>> > > -next, not -fixes. They should land for -rc6.
>> > 
>> > Could you point commit ids?
>> 
>> It was wishful thinking on my side, mixed them up with other patches. I
>> think this one's still open :(
>
> 7f4c628 drm/i915: Assign hwmode after encoder state readout
> 0f64614 drm/i915: Fix clock readout when pipes are enabled w/o ports
>
> not enough?

The relevant bug is [1], everyone please let's track this there.

BR,
Jani.


[1] https://bugs.freedesktop.org/show_bug.cgi?id=91428

>
> -- 
> Ville Syrjälä
> Intel OTC
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-10-13 12:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-10  9:46 4.2-rc4 kernel warnings on HSW laptop Takashi Iwai
2015-10-12  7:04 ` 4.2-rc4 kernel warnings on HSW laptop [regression] Daniel Vetter
2015-10-12 12:29   ` Takashi Iwai
2015-10-12 12:38     ` Takashi Iwai
2015-10-13  8:24     ` [Intel-gfx] " Daniel Vetter
2015-10-13  9:05       ` Ville Syrjälä
2015-10-13 12:25         ` Jani Nikula [this message]
2015-10-14  0:59   ` Miramontes Caton, Jairo Daniel

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=87lhb7550o.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@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