public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Felix Miata <mrmazda@earthlink.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: 845G - call trace every boot
Date: Fri, 11 Oct 2013 07:00:46 -0400	[thread overview]
Message-ID: <5257DA5E.2040605@earthlink.net> (raw)
In-Reply-To: <20131011100015.GS13047@intel.com>

On 2013-10-11 13:00 (GMT+0300) Ville Syrjälä composed:

> On Fri, Oct 11, 2013 at 12:24:04AM -0400, Felix Miata wrote:

>> Are these happening to everyone using recent kernels and 845G? openSUSE only?

>> 2013-10-11T00:05:50.929822-04:00 gx260 kernel: [    2.621885]
>> ------------[ cut here ]------------
>> WARNING: CPU: 0 PID: 107 at /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.3/linux-3.11/drivers/gpu/drm/i915/intel_display.c:1074 assert_pipe+0x80/0xe0 [i915]()
>> pipe A assertion failure (expected on, current off)

> Already fixed:

> commit 67c72a12254101d4e8d9b9f3a02646ba0be84a2d
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Tue Sep 24 11:46:14 2013 +0200

>      drm/i915: preserve pipe A quirk in i9xx_set_pipeconf

> and

> commit a4945f9522d27e1e6d64a02ad055e83768cb0896
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Tue Oct 8 11:16:59 2013 +0100

>      drm/i915: Undo the PIPEA quirk for i845

Where do these show up in some bug tracker? Kernel? Freedesktop? Other? What 
bug #?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

      reply	other threads:[~2013-10-11 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11  4:24 845G - call trace every boot Felix Miata
2013-10-11 10:00 ` Ville Syrjälä
2013-10-11 11:00   ` Felix Miata [this message]

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=5257DA5E.2040605@earthlink.net \
    --to=mrmazda@earthlink.net \
    --cc=intel-gfx@lists.freedesktop.org \
    /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