public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Dave Airlie <airlied@redhat.com>, Zhao Yakui <yakui.zhao@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [ERROR] drm:edid;  Unexpected error messages in syslog
Date: Tue, 06 Oct 2009 16:37:06 +1000	[thread overview]
Message-ID: <4ACAE592.8030307@bigpond.net.au> (raw)

I've started getting the following messages on recent kernels:

Oct  5 16:50:40 mudlark kernel: [drm:edid_is_valid] *ERROR* EDID 
checksum is invalid, remainder is 16
Oct  5 16:50:40 mudlark kernel: [drm:edid_is_valid] *ERROR* Raw EDID:
Oct  5 16:50:40 mudlark kernel:
Oct  5 16:50:40 mudlark kernel: i915 0000:00:02.0: VGA-1: EDID invalid.
Oct  5 16:50:40 mudlark kernel: [drm:edid_is_valid] *ERROR* EDID 
checksum is invalid, remainder is 16
Oct  5 16:50:40 mudlark kernel: [drm:edid_is_valid] *ERROR* Raw EDID:
Oct  5 16:50:40 mudlark kernel:
Oct  5 16:50:40 mudlark kernel: i915 0000:00:02.0: VGA-1: EDID invalid.
Oct  5 16:50:41 mudlark kernel: [drm] DAC-6: set mode 1600x1200 16
Oct  5 16:50:45 mudlark kernel: [drm:edid_is_valid] *ERROR* EDID 
checksum is invalid, remainder is 16
Oct  5 16:50:45 mudlark kernel: [drm:edid_is_valid] *ERROR* Raw EDID:
Oct  5 16:50:45 mudlark kernel:
Oct  5 16:50:45 mudlark kernel: i915 0000:00:02.0: VGA-1: EDID invalid.
Oct  5 16:50:45 mudlark kernel: [drm:edid_is_valid] *ERROR* EDID 
checksum is invalid, remainder is 16
Oct  5 16:50:45 mudlark kernel: [drm:edid_is_valid] *ERROR* Raw EDID:
Oct  5 16:50:45 mudlark kernel:
Oct  5 16:50:45 mudlark kernel: i915 0000:00:02.0: VGA-1: EDID invalid.
Oct  5 16:50:45 mudlark kernel: [drm:edid_is_valid] *ERROR* EDID 
checksum is invalid, remainder is 16
Oct  5 16:50:45 mudlark kernel: [drm:edid_is_valid] *ERROR* Raw EDID:
Oct  5 16:50:45 mudlark kernel:
Oct  5 16:50:45 mudlark kernel: i915 0000:00:02.0: VGA-1: EDID invalid.
Oct  5 16:51:00 mudlark kernel: [drm:edid_is_valid] *ERROR* EDID 
checksum is invalid, remainder is 16
Oct  5 16:51:00 mudlark kernel: [drm:edid_is_valid] *ERROR* Raw EDID:
Oct  5 16:51:00 mudlark kernel:
Oct  5 16:51:00 mudlark kernel: i915 0000:00:02.0: VGA-1: EDID invalid.
Oct  5 16:51:00 mudlark kernel: [drm:edid_is_valid] *ERROR* EDID 
checksum is invalid, remainder is 16
Oct  5 16:51:00 mudlark kernel: [drm:edid_is_valid] *ERROR* Raw EDID:
Oct  5 16:51:00 mudlark kernel:
Oct  5 16:51:00 mudlark kernel: i915 0000:00:02.0: VGA-1: EDID invalid.
Oct  5 16:51:00 mudlark kernel: [drm:edid_is_valid] *ERROR* EDID 
checksum is invalid, remainder is 16
Oct  5 16:51:00 mudlark kernel: [drm:edid_is_valid] *ERROR* Raw EDID:
Oct  5 16:51:00 mudlark kernel:
Oct  5 16:51:00 mudlark kernel: i915 0000:00:02.0: VGA-1: EDID invalid.

Should I worry about these?  There's no other noticeable problem with 
the system.

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

             reply	other threads:[~2009-10-06  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  6:37 Peter Williams [this message]
2009-10-09  5:17 ` [ERROR] drm:edid; Unexpected error messages in syslog ykzhao
2009-10-10  0:56   ` Peter Williams

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=4ACAE592.8030307@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=airlied@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yakui.zhao@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