All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [drm:i915_driver_irq_handler] *ERROR* EIR stuck: 0x00000010, masking
Date: Mon, 27 Jul 2009 12:53:56 -0700	[thread overview]
Message-ID: <4A6E05D4.5060308@gmail.com> (raw)
In-Reply-To: <20090727104335.0a9a1556@jbarnes-g45>

Jesse Barnes wrote:
> On Mon, 27 Jul 2009 10:37:04 -0700
> "Justin P. Mattock"<justinmattock@gmail.com>  wrote:
>
>    
>> Jesse Barnes wrote:
>>      
>>> On Sun, 26 Jul 2009 21:12:49 -0400
>>> Justin Mattock<justinmattock@gmail.com>   wrote:
>>>
>>>
>>>        
>>>> to my surprise this machine still works...
>>>> (dell inspiron 1200)
>>>> Anyways in dmesg I see:
>>>>
>>>> [   10.188083] b43-pci-bridge 0000:03:00.0: setting latency timer
>>>> to 64 [   10.191947] ssb: Sonics Silicon Backplane found on PCI
>>>> device 0000:03:00.0 [   10.220248] fb: conflicting fb hw usage
>>>> inteldrmfb vs VESA VGA - removing generic driver
>>>> [   10.222343] Console: switching to colour dummy device 80x25
>>>> [   10.225625] Console: switching to colour frame buffer device
>>>> 128x48 [   10.278714] render error detected, EIR: 0x00000010
>>>> [   10.278717] page table error
>>>> [   10.278720]   PGTBL_ER: 0x00000100
>>>> [   10.278725] [drm:i915_driver_irq_handler] *ERROR* EIR stuck:
>>>> 0x00000010, masking
>>>> [   10.278742] render error detected, EIR: 0x00000010
>>>> [   10.278745] page table error
>>>> [   10.278747]   PGTBL_ER: 0x00000100
>>>> [   10.290087] [drm] LVDS-8: set mode 1024x768 c
>>>> [   10.640403] [drm] fb0: inteldrmfb frame buffer device
>>>> [   10.640597] [drm] Initialized i915 1.6.0 20080730 for
>>>> 0000:00:02.0 on minor 0 [   10.679818] b43-phy0: Broadcom 4306
>>>> WLAN found (core revision 5)
>>>>
>>>> direct rendering still seems to be intact,
>>>> suspend not sure(test in a moment).
>>>>
>>>>          
>>> Sounds like a dupe of the issue Frans reported.  We report errors
>>> like this now rather than silently ignoring them.  This one must be
>>> harmless or your machine wouldn't ever have worked. :)
>>>
>>>
>>>        
>> Seems harmless to me, one thing I see is
>> during the boot process Ill see the boot messages, then once
>> init/udev starts up, and loads i915 the screen will go black
>> for a tenth or so of a second, then goes back to normal. Now keep in
>> mind this might be something suse does during the boot process.
>> (I can try loading ubuntu/debian to see if the affects are the same
>> once I get a chance).
>>      
>
> Yeah that's probably just the i915 driver probing the outputs.  It
> shuts everything off to avoid showing any ugly load detect patterns or
> flicker.
>
>    
Alright,
Then that's pretty much everything, other than
a message that's been there, but now finally is showing itself.

Justin P. Mattock

      reply	other threads:[~2009-07-27 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27  1:12 [drm:i915_driver_irq_handler] *ERROR* EIR stuck: 0x00000010, masking Justin Mattock
2009-07-27 17:15 ` Jesse Barnes
2009-07-27 17:37   ` Justin P. Mattock
2009-07-27 17:43     ` Jesse Barnes
2009-07-27 19:53       ` Justin P. Mattock [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=4A6E05D4.5060308@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.