[drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1

Bug #1240882 reported by Jagat
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Error log
Oct 17 19:38:00 nanak-P570WM kernel: [ 20.031700] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Oct 17 19:38:00 nanak-P570WM kernel: [ 20.034197] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Oct 17 19:38:00 nanak-P570WM kernel: [ 20.036692] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Oct 17 19:38:00 nanak-P570WM kernel: [ 20.039192] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Oct 17 19:38:00 nanak-P570WM kernel: [ 20.199700] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.202196] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.204688] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.207185] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262737] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 FAULT at 0x418880 [ IBUS ]
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262846] nouveau E[ PIBUS][0000:01:00.0] GPC0: 0x419eb4 0xbadf1000 (0x3800820c)
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262872] nouveau E[ PIBUS][0000:01:00.0] GPC1: 0x419eb4 0xbadf1000 (0x3800820c)
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262905] nouveau E[ PIBUS][0000:01:00.0] GPC2: 0x419eb4 0xbadf1000 (0x3800820c)
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262912] nouveau E[ PIBUS][0000:01:00.0] GPC3: 0x419eb4 0xbadf1000 (0x3800820c)
Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262927] nouveau E[ PBUS][0000:01:00.0] MMIO write of 0xc0000000 FAULT at 0x518824 [ IBUS ]

WORKAROUND: Use the 331 nvidia drivers.

---
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-09-05 (42 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904)
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: saucy
Uname: Linux 3.12.0-999-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Jagat (jagatsingh) wrote :

Graphics card

GK104M [GeForce GTX 780M] driver=nouveau

tags: added: 13.10
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1240882

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc5-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: saucy
Revision history for this message
Jagat (jagatsingh) wrote :

Hi

I updated to latest daily mainline kernel

The error is still exisitng.

Oct 18 15:49:51 nanak-P570WM kernel: [ 49.908482] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1

Thanks

tags: added: apport-collected
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Francis Lamonde (frankebay99) wrote :

I confirm this. Since Kubuntu 12.10 at least. Then 13.04 and now 13.10. Every time I want to use the nouveau driver but I end up trashing it just because of that. The dev team did an awesome job in the past year, the driver works on everything I use, is SMOOTH and FAST, flawless to me. But because it cannot support resuming fro suspend to RAM, I trash it and install the drivers from nvidia, which sometimes cause issues elsewhere.

Nothing's perfect but the nouveau driver in Kubuntu 13.10 is at perfection to me if it wasn't for that. This is a mandatory requirement for me, if it can't suspend and resume in an acceptable way, then it's a total no use for me.

I have an nvidia GeFroce 8400GS, does the same thing with my other GeForce 8600GT.

I wish we can fix this!

Revision history for this message
penalvch (penalvch) wrote :

Jagat, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc6

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
Revision history for this message
Francis Lamonde (frankebay99) wrote :

Jagat,

I still have the problem with the latest 13.10. However I need to upgrade to latest kernel to see if it has or hasn't fixed the issue.

Revision history for this message
penalvch (penalvch) wrote :

Francis Lamonde, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Revision history for this message
Jagat (jagatsingh) wrote :

Hi issue seems with nouveau driver.

I started using Nvidia driver i don't see this now in syslog.

I will still double check this statement and get back to you.

Revision history for this message
Francis Lamonde (frankebay99) wrote :

Jagat, I confirm that, it is with nouveau driver not nvidia proprietary.
I used nouveau and had the issue. Installed only nvidia package, the 331, and issue is gone. I cannot see how it would be related to nouveau driver, so far.

penalvch (penalvch)
tags: added: needs-kernel-logs
Revision history for this message
Jagat (jagatsingh) wrote :

I am also using 331 nvidia and dont have this issue.

penalvch (penalvch)
description: updated
Revision history for this message
Francis Lamonde (frankebay99) wrote :
Download full text (7.8 KiB)

I do not think using a different driver is a true workaround. Like I said, nothing's perfect and it turns out the nVidia drivers are no different; I have other bugs with these and need to patch some of them, but it's always a pain to manage. That is something nVidia will hopefully fix, but what I am saying is beware if you think all your issues will be "worked around" by using another driver. :) They do wake up almost fine from resume, though.

I still get the error with the nouveau drivers on kernel 3.11.0.15, I will try the 3.12.y.z upstream version following the link provided in comment #3 (https://wiki.ubuntu.com/KernelMainlineBuilds). Those are mainlne kernels and comment #8 is asking me to not use a mainline, so not sure what to do. I don't think I am equipped to do more than installing from PPAs.

In the meantime, this is what apport.log tells me:

ERROR: apport (pid 3799) Sat Jan 4 14:56:12 2014: called for pid 1114, signal 6, core limit 18446744073709551615
ERROR: apport (pid 3799) Sat Jan 4 14:56:12 2014: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 3799) Sat Jan 4 14:56:12 2014: executable: /usr/bin/Xorg (command line "/usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 3799) Sat Jan 4 14:56:12 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 3799) Sat Jan 4 14:56:16 2014: wrote report /var/crash/_usr_bin_Xorg.0.crash
ERROR: apport (pid 3799) Sat Jan 4 14:56:16 2014: writing core dump to /etc/X11/core (limit: -1)
ERROR: apport (pid 3799) Sat Jan 4 14:56:19 2014: writing core dump /etc/X11/core of size 70664192

That is about at the time I get these in the kern.log:

Jan 4 14:55:24 Kub1310 kernel: [ 750.848553] PM: Finishing wakeup.
Jan 4 14:55:24 Kub1310 kernel: [ 750.848555] Restarting tasks ... done.
Jan 4 14:55:24 Kub1310 kernel: [ 750.933984] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Jan 4 14:55:24 Kub1310 kernel: [ 750.959558] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Jan 4 14:55:25 Kub1310 kernel: [ 750.985112] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Jan 4 14:55:25 Kub1310 kernel: [ 751.010659] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Jan 4 14:55:25 Kub1310 kernel: [ 751.063348] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Jan 4 14:55:25 Kub1310 kernel: [ 751.088893] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Jan 4 14:55:25 Kub1310 kernel: [ 751.114456] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Jan 4 14:55:25 Kub1310 kernel: [ 751.140022] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
Jan 4 14:56:31 Kub1310 kernel: [ 817.748006] nouveau E[Xorg[1114]] failed to idle channel 0xcccc0000 [Xorg[1114]]
Jan 4 14:56:31 Kub1310 kernel: [ 817.748074] nouveau E[ PFB][0000:01:00.0] trapped read at 0x002001e020 on channel 0x0003fb34 [unknown] SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT
Jan 4 14:56:31 Kub1310 kernel: [ 817.7570...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Francis Lamonde, as it would appear you didn't see this, please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240882/comments/8 .

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.