[i915] drm boot error in lucid

Bug #536827 reported by Ritz
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
xf86-video-intel
Fix Released
Medium
linux (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

I get this error while booting my eee1000H with lucid

[ 11.013541] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 11.013555] i915 0000:00:02.0: setting latency timer to 64
[ 11.025318] phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 11.035957] [drm] set up 7M of stolen space
[ 11.164218] composite sync not supported
[ 11.165104] [drm] initialized overlay support
[ 11.609623] [drm:edid_is_valid] *ERROR* EDID checksum is invalid, remainder is 165
[ 11.609641] [drm:edid_is_valid] *ERROR* Raw EDID:
[ 11.609653] <3>00 ff ff ff ff ff ff 00 22 64 e9 03 d0 8a 00 00 ........"d......
[ 11.609660] <3>33 12 01 03 80 16 0d 78 0a 86 26 94 57 51 90 27 3......x..&.WQ.'
[ 11.609666] <3>21 4f 54 00 00 00 01 01 01 01 01 01 01 01 01 01 !OT.............
[ 11.609672] <3>01 01 01 01 01 01 94 11 00 b0 40 58 19 20 35 23 ..........@X. 5#
[ 11.609678] <3>45 00 dc 81 00 00 00 19 16 14 00 d8 40 58 26 20 E...........@X&
[ 11.609684] <3>5d 23 15 04 dc 81 00 00 00 00 00 00 00 fe 00 00 ]#..............
[ 11.609690] <3>00 00 00 00 00 00 ff 00 ff 00 ff 00 ff 00 ff fe ................
[ 11.609695] <3>ff 00 ff 00 ff 00 ff 00 ff 01 ff 00 ff 00 ff ff ................
[ 11.609700]
[ 11.611620] i2c i2c-1: sendbytes: NAK bailout.
[ 11.618165] fb0: inteldrmfb frame buffer device
[ 11.618173] registered panic notifier
[ 11.618192] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cilie 1125 F.... pulseaudio
CRDA:
 country 98:
  (2402 - 2482 @ 40), (N/A, 20)
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043831a,00100004'
   Controls : 12
   Simple ctrls : 7
Date: Wed Mar 10 19:27:00 2010
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=28ff4b10-6be9-4dcf-a1de-34b0bc16c78e
MachineType: ASUSTeK Computer INC. 1000H
Package: linux-image-2.6.32-16-generic 2.6.32-16.25
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=9d1b843a-bcec-49fb-8904-226e2fb80ed3 ro splash vga=769 quiet splash
ProcEnviron:
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.32
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-16-generic i686
dmi.bios.date: 10/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2204
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd10/21/2009:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000H
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

Created an attachment (id=33013)
vbios.dump

Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

Not sure what the bug is here, reassigning to Yakui. Invalid EDIDs can be due to bad timing on the kernel side, flakey hardware or cables, or a real bad EDID in the monitor.

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

It's notebook Sony Vaio VGN-C2S_L, so I suppose it's bad EDID, and not cables ;)

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

(In reply to comment #3)
> It's notebook Sony Vaio VGN-C2S_L, so I suppose it's bad EDID, and not cables
> ;)

Will you please add the boot option of "drm.debug=0x04" and attach the output of dmesg?

Thanks.
   Yakui
>

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

Created an attachment (id=33144)
dmesg with drm.debug=0x04

Here goes dmesg with drm.debug=0x04 option.

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

Created an attachment (id=33189)
Ignore the LVDS edid when it is unavailable or invalid

Will you please try the attached patch and see whether it frequently reports the following similar message?
     >i915 0000:00:02.0: LVDS-1: EDID invalid.

thanks.

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

Now it only reports:

[ 23.903220] [drm] Initialized drm 1.1.0 20060810
[ 23.908682] i915: no symbol version for module_layout
[ 23.932410] i915: no symbol version for module_layout

(no symbol version probably due to my way of compilation).

Does this ignoring LVDS can make some problems or is it safe?

Revision history for this message
In , Bartosz Fenski (fenio) wrote :

Since that change my X.org eats many CPU, and everything is working extremely slow.

At least I'm finally able to run Enemy-territory game, but it works so slow, that I have to try to select proper option to be able to exit from the game.
Before that patch I wasn't able to even run it (signal 11).

Seems there's something wrong with hardware acceleration after that patch.

Is there something else I can provide you to resolve these issues?

regards
fEnIo

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

Created an attachment (id=33484)
try the debug patch that the LVDS edid when it is unavailable or invalid

will you please try the updated patch and see whether it can work for you?

thanks.

Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

(In reply to comment #8)
> Since that change my X.org eats many CPU, and everything is working extremely
> slow.
>
> At least I'm finally able to run Enemy-territory game, but it works so slow,
> that I have to try to select proper option to be able to exit from the game.
> Before that patch I wasn't able to even run it (signal 11).

It seems that the slow issue is not related with this bug. And from the log it seems that the xorg will query the status of every possible outputs periodically.

Can you provide the info of "cat /proc/interrupts"?

Thanks.

>
> Seems there's something wrong with hardware acceleration after that patch.
>
> Is there something else I can provide you to resolve these issues?
>
> regards
> fEnIo
>

Revision history for this message
Ritz (jonas-ritz) wrote : drm boot error in lucid
Download full text (3.5 KiB)

I get this error while booting my eee1000H with lucid

[ 11.013541] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 11.013555] i915 0000:00:02.0: setting latency timer to 64
[ 11.025318] phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 11.035957] [drm] set up 7M of stolen space
[ 11.164218] composite sync not supported
[ 11.165104] [drm] initialized overlay support
[ 11.609623] [drm:edid_is_valid] *ERROR* EDID checksum is invalid, remainder is 165
[ 11.609641] [drm:edid_is_valid] *ERROR* Raw EDID:
[ 11.609653] <3>00 ff ff ff ff ff ff 00 22 64 e9 03 d0 8a 00 00 ........"d......
[ 11.609660] <3>33 12 01 03 80 16 0d 78 0a 86 26 94 57 51 90 27 3......x..&.WQ.'
[ 11.609666] <3>21 4f 54 00 00 00 01 01 01 01 01 01 01 01 01 01 !OT.............
[ 11.609672] <3>01 01 01 01 01 01 94 11 00 b0 40 58 19 20 35 23 ..........@X. 5#
[ 11.609678] <3>45 00 dc 81 00 00 00 19 16 14 00 d8 40 58 26 20 E...........@X&
[ 11.609684] <3>5d 23 15 04 dc 81 00 00 00 00 00 00 00 fe 00 00 ]#..............
[ 11.609690] <3>00 00 00 00 00 00 ff 00 ff 00 ff 00 ff 00 ff fe ................
[ 11.609695] <3>ff 00 ff 00 ff 00 ff 00 ff 01 ff 00 ff 00 ff ff ................
[ 11.609700]
[ 11.611620] i2c i2c-1: sendbytes: NAK bailout.
[ 11.618165] fb0: inteldrmfb frame buffer device
[ 11.618173] registered panic notifier
[ 11.618192] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cilie 1125 F.... pulseaudio
CRDA:
 country 98:
  (2402 - 2482 @ 40), (N/A, 20)
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 16'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043831a,00100004'
   Controls : 12
   Simple ctrls : 7
Date: Wed Mar 10 19:27:00 2010
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=28ff4b10-6be9-4dcf-a1de-34b0bc16c78e
MachineType: ASUSTeK Computer INC. 1000H
Package: linux-image-2.6.32-16-generic 2.6.32-16.25
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=9d1b843a-bcec-49fb-8904-226e2fb80ed3 ro splash vga=769 quiet splash
ProcEnviron:
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.32
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-16-generic i686
dmi.bios.date: 10/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2204
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.cha...

Read more...

Revision history for this message
Ritz (jonas-ritz) wrote :
Revision history for this message
Chase Douglas (chasedouglas) wrote :

It appears that your EDID information from your monitor is incorrect. Is this message present when you boot Karmic?

Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Ritz (jonas-ritz) wrote : Re: [Bug 536827] Re: drm boot error in lucid

Chase Douglas skrev:
> It appears that your EDID information from your monitor is incorrect. Is
> this message present when you boot Karmic?
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
>
Its the build in monitor of my eee 1000H netbook.
I will try with Karmic, and let you know..

Revision history for this message
Ritz (jonas-ritz) wrote : Re: drm boot error in lucid
Download full text (28.0 KiB)

I think it is a regression since Karmic. This bootlog is Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux. Same eee 1000H, and still the same build in display.

When booting, Plymouth is also reported to be crashed in Lucid in maybe 1 out 5 times.
But append will not connect to database, so I can not make an automatic bugreport on that.

[ 0.201836] pci 0000:00:02.0: reg 1c 32bit mmio: [0xf7ec0000-0xf7efffff]
[ 0.201891] pci 0000:00:02.1: reg 10 32bit mmio: [0xf7f80000-0xf7ffffff]
[ 0.202038] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf7eb8000-0xf7ebbfff]
[ 0.202117] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.202125] pci 0000:00:1b.0: PME# disabled
[ 0.202235] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.202243] pci 0000:00:1c.0: PME# disabled
[ 0.202356] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.202364] pci 0000:00:1c.1: PME# disabled
[ 0.202478] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
[ 0.202487] pci 0000:00:1c.3: PME# disabled
[ 0.202573] pci 0000:00:1d.0: reg 20 io port: [0xd400-0xd41f]
[ 0.202658] pci 0000:00:1d.1: reg 20 io port: [0xd480-0xd49f]
[ 0.202743] pci 0000:00:1d.2: reg 20 io port: [0xd800-0xd81f]
[ 0.202828] pci 0000:00:1d.3: reg 20 io port: [0xd880-0xd89f]
[ 0.202919] pci 0000:00:1d.7: reg 10 32bit mmio: [0xf7eb7c00-0xf7eb7fff]
[ 0.203003] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.203011] pci 0000:00:1d.7: PME# disabled
[ 0.203207] pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
[ 0.203216] pci 0000:00:1f.0: quirk: region 0480-04bf claimed by ICH6 GPIO
[ 0.203225] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0380 (mask 0003)
[ 0.203233] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0290 (mask 0007)
[ 0.203242] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 0068 (mask 0003)
[ 0.203325] pci 0000:00:1f.2: reg 10 io port: [0x00-0x07]
[ 0.203338] pci 0000:00:1f.2: reg 14 io port: [0x00-0x03]
[ 0.203351] pci 0000:00:1f.2: reg 18 io port: [0x00-0x07]
[ 0.203363] pci 0000:00:1f.2: reg 1c io port: [0x00-0x03]
[ 0.203376] pci 0000:00:1f.2: reg 20 io port: [0xffa0-0xffaf]
[ 0.203421] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.203429] pci 0000:00:1f.2: PME# disabled
[ 0.203615] pci 0000:03:00.0: reg 10 64bit mmio: [0xfbfc0000-0xfbffffff]
[ 0.203631] pci 0000:03:00.0: reg 18 io port: [0xec00-0xec7f]
[ 0.203726] pci 0000:03:00.0: PME# supported from D3hot D3cold
[ 0.203735] pci 0000:03:00.0: PME# disabled
[ 0.203829] pci 0000:00:1c.1: bridge io port: [0xe000-0xefff]
[ 0.203838] pci 0000:00:1c.1: bridge 32bit mmio: [0xfbf00000-0xfbffffff]
[ 0.203957] pci 0000:01:00.0: reg 10 64bit mmio: [0xfbefe000-0xfbefffff]
[ 0.204098] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[ 0.204109] pci 0000:01:00.0: PME# disabled
[ 0.204212] pci 0000:00:1c.3: bridge 32bit mmio: [0xf8000000-0xfbefffff]
[ 0.204226] pci 0000:00:1c.3: bridge 64bit mmio pref: [0xf0000000-0xf6ffffff]
[ 0.204301] pci 0000:00:1e.0: transparent bridge
[ 0.204350] pci_bus 0000:00: on NUMA...

Revision history for this message
Ritz (jonas-ritz) wrote :

This issue is still present with the new -17 Kernel

Revision history for this message
Florian Apolloner (apollo13) wrote :

Same here, did work in karmic…

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Ritz (jonas-ritz) wrote :

This issue is still present with the new -18 Kernel

Revision history for this message
Konstantin Lavrov (lacosta) wrote :

On my netbook LG X110 with lubuntu I see next strings:

[ 38.807938] [drm:edid_is_valid] *ERROR* EDID checksum is invalid, remainder is 174
[ 38.807950] [drm:edid_is_valid] *ERROR* Raw EDID:
[ 38.807959] <3>00 ff ff ff ff ff ff 00 22 64 e9 03 8e 1f 01 00 ........"d......
[ 38.807967] <3>12 12 01 03 80 16 0d 78 0a 80 36 9a 5e 5d 91 28 .......x..6.^].(
[ 38.807975] <3>20 4f 54 00 00 00 01 01 01 01 01 01 01 01 01 01 OT.............
[ 38.807982] <3>01 01 01 01 01 01 94 11 00 b0 40 58 19 20 35 23 ..........@X. 5#
[ 38.807989] <3>45 00 dc 81 00 00 00 19 00 00 00 fd 00 37 41 22 E............7A"
[ 38.807997] <3>29 05 00 0a 20 20 20 20 20 20 00 00 00 fc 00 48 )... .....H
[ 38.808020] <3>53 44 31 30 30 49 46 57 31 0a 20 20 00 00 00 10 SD100IFW1. ....
[ 38.808028] <3>00 0a 20 20 20 20 20 20 20 20 20 20 20 20 00 81 .. ..
[ 38.808034]
[ 38.808041] i915 0000:00:02.0: LVDS-1: EDID invalid.

$uname -a
Linux lucidtest 2.6.32-18-generic #27-Ubuntu SMP Fri Mar 26 19:51:10 UTC 2010 i686 GNU/Linux

Revision history for this message
Ritz (jonas-ritz) wrote :

Still an issue with -19 kernel. FYI the number after remainder is a random number. Different at every boot

Revision history for this message
Konstantin Lavrov (lacosta) wrote :

In my case after rebooting reminder is 174 - the same

Now with 2.6.32-19-generic too

summary: - drm boot error in lucid
+ [i915] drm boot error in lucid
Revision history for this message
Konstantin Lavrov (lacosta) wrote :

While searching all around find out similar bug 547147 but filed against libdrm and different videocard (radeon)

Though in this bug card is intel.

There is patch: http://lists.freedesktop.org/archives/intel-gfx/2010-March/006066.html

Sound like it must close this issue.

Haw I can test that patch?

affects: linux (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
Bryce Harrington (bryce) wrote :

Konstantin, why did you reassign this to the user-space X driver? The patch you linked to is a kernel patch. Try applying it to your kernel, rebuild, and give it a test?

Revision history for this message
Bryce Harrington (bryce) wrote :

'Checksum invalid' indicates either your monitor generates invalid EDID, or the kernel drm's edid parsing routines are faulty with this hardware. It's likely that this will behave similarly on any video driver.

affects: xserver-xorg-video-intel (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
In , yakuizhao (yakui-zhao) wrote :

Now the corresponding patch is already shipped. And after the patch is applied, it can avoid the warning message of "drm:edid_is_valid" perodically.

commit bfac4d6725baacbfc085c38e231b8582a1b8f62b
Author: Zhao Yakui <email address hidden>
Date: Wed Apr 7 17:11:22 2010 +0800

    drm/i915: Ignore LVDS EDID when it is unavailabe or invalid

So this bug will be marked as resolved.

Thanks.

Revision history for this message
Ritz (jonas-ritz) wrote :

With the latest .32 Kernel it looks like this issue is solved.

cilie@eee:~$ uname -a
Linux eee 2.6.32-20-generic #30-Ubuntu SMP Mon Apr 12 15:19:41 UTC 2010 i686 GNU/Linux

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Ritz,
     Thanks for following up with us on this. I am marking the bug Fix Released. Any other reporters on this bug who are still affected need to open new bugs ti address their issue.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Konstantin Lavrov (lacosta) wrote :

Riz,

  Before I'll file new bug can you please post your output of

dmesg | grep drm

Revision history for this message
Ritz (jonas-ritz) wrote :
Download full text (27.7 KiB)

Linux eee 2.6.32-20-generic #30-Ubuntu SMP Mon Apr 12 15:19:41 UTC 2010 i686 GNU/Linux

0, disabled.
[ 0.271919] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.272284] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.272632] ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 10 11 12 14 15)
[ 0.272963] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.272993] vgaarb: loaded
[ 0.273374] SCSI subsystem initialized
[ 0.273620] libata version 3.00 loaded.
[ 0.273859] usbcore: registered new interface driver usbfs
[ 0.273903] usbcore: registered new interface driver hub
[ 0.273986] usbcore: registered new device driver usb
[ 0.274452] ACPI: WMI: Mapper loaded
[ 0.274459] PCI: Using ACPI for IRQ routing
[ 0.274934] NetLabel: Initializing
[ 0.274942] NetLabel: domain hash size = 128
[ 0.274947] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.274981] NetLabel: unlabeled traffic allowed by default
[ 0.275096] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.275112] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 0.280227] Switching to clocksource tsc
[ 0.284942] AppArmor: AppArmor Filesystem Enabled
[ 0.284982] pnp: PnP ACPI init
[ 0.285024] ACPI: bus type pnp registered
[ 0.290546] pnp: PnP ACPI: found 13 devices
[ 0.290556] ACPI: ACPI bus type pnp unregistered
[ 0.290567] PnPBIOS: Disabled by ACPI PNP
[ 0.290608] system 00:01: iomem range 0xfed13000-0xfed19fff has been reserved
[ 0.290641] system 00:08: ioport range 0x25c-0x25f has been reserved
[ 0.290652] system 00:08: ioport range 0x380-0x383 has been reserved
[ 0.290662] system 00:08: ioport range 0x400-0x41f has been reserved
[ 0.290672] system 00:08: ioport range 0x4d0-0x4d1 has been reserved
[ 0.290682] system 00:08: ioport range 0x800-0x87f has been reserved
[ 0.290693] system 00:08: ioport range 0x480-0x4bf has been reserved
[ 0.290705] system 00:08: iomem range 0x8c000000-0x8c01ffff has been reserved
[ 0.290717] system 00:08: iomem range 0xfed1c000-0xfed1ffff has been reserved
[ 0.290729] system 00:08: iomem range 0xfed20000-0xfed3ffff has been reserved
[ 0.290740] system 00:08: iomem range 0xfed50000-0xfed8ffff has been reserved
[ 0.290750] system 00:08: iomem range 0xffb00000-0xffbfffff has been reserved
[ 0.290761] system 00:08: iomem range 0xfff00000-0xffffffff could not be reserved
[ 0.290785] system 00:0a: iomem range 0xfec00000-0xfec00fff could not be reserved
[ 0.290796] system 00:0a: iomem range 0xfee00000-0xfee00fff has been reserved
[ 0.290815] system 00:0b: iomem range 0xe0000000-0xe3ffffff has been reserved
[ 0.290835] system 00:0c: iomem range 0x0-0x9ffff could not be reserved
[ 0.290845] system 00:0c: iomem range 0xc0000-0xcffff could not be reserved
[ 0.290855] system 00:0c: iomem range 0xe0000-0xfffff could not be reserved
[ 0.290894] system 00:0c: iomem range 0x100000-0x7f7fffff could not be reserved
[ 0.326098] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:04
[ 0.326112] pci 0000:00:1c.0: IO window: 0x1000-0x1fff
[ 0.326125] pci 0...

Revision history for this message
Ritz (jonas-ritz) wrote :
Download full text (27.6 KiB)

..but here it is again

cilie@eee:~$ uname -a
Linux eee 2.6.32-21-generic #31-Ubuntu SMP Tue Apr 13 20:34:00 UTC 2010 i686 GNU/Linux

[ 0.270764] NetLabel: unlabeled traffic allowed by default
[ 0.270881] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.270897] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 0.276107] Switching to clocksource tsc
[ 0.280931] AppArmor: AppArmor Filesystem Enabled
[ 0.280971] pnp: PnP ACPI init
[ 0.281011] ACPI: bus type pnp registered
[ 0.286544] pnp: PnP ACPI: found 13 devices
[ 0.286554] ACPI: ACPI bus type pnp unregistered
[ 0.286564] PnPBIOS: Disabled by ACPI PNP
[ 0.286602] system 00:01: iomem range 0xfed13000-0xfed19fff has been reserved
[ 0.286635] system 00:08: ioport range 0x25c-0x25f has been reserved
[ 0.286647] system 00:08: ioport range 0x380-0x383 has been reserved
[ 0.286659] system 00:08: ioport range 0x400-0x41f has been reserved
[ 0.286671] system 00:08: ioport range 0x4d0-0x4d1 has been reserved
[ 0.286684] system 00:08: ioport range 0x800-0x87f has been reserved
[ 0.286695] system 00:08: ioport range 0x480-0x4bf has been reserved
[ 0.286706] system 00:08: iomem range 0x8c000000-0x8c01ffff has been reserved
[ 0.286717] system 00:08: iomem range 0xfed1c000-0xfed1ffff has been reserved
[ 0.286727] system 00:08: iomem range 0xfed20000-0xfed3ffff has been reserved
[ 0.286738] system 00:08: iomem range 0xfed50000-0xfed8ffff has been reserved
[ 0.286748] system 00:08: iomem range 0xffb00000-0xffbfffff has been reserved
[ 0.286760] system 00:08: iomem range 0xfff00000-0xffffffff could not be reserved
[ 0.286783] system 00:0a: iomem range 0xfec00000-0xfec00fff could not be reserved
[ 0.286793] system 00:0a: iomem range 0xfee00000-0xfee00fff has been reserved
[ 0.286813] system 00:0b: iomem range 0xe0000000-0xe3ffffff has been reserved
[ 0.286832] system 00:0c: iomem range 0x0-0x9ffff could not be reserved
[ 0.286842] system 00:0c: iomem range 0xc0000-0xcffff could not be reserved
[ 0.286852] system 00:0c: iomem range 0xe0000-0xfffff could not be reserved
[ 0.286862] system 00:0c: iomem range 0x100000-0x7f7fffff could not be reserved
[ 0.322110] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:04
[ 0.322125] pci 0000:00:1c.0: IO window: 0x1000-0x1fff
[ 0.322140] pci 0000:00:1c.0: MEM window: 0x80000000-0x801fffff
[ 0.322154] pci 0000:00:1c.0: PREFETCH window: 0x00000080200000-0x000000803fffff
[ 0.322170] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:03
[ 0.322180] pci 0000:00:1c.1: IO window: 0xe000-0xefff
[ 0.322193] pci 0000:00:1c.1: MEM window: 0xfbf00000-0xfbffffff
[ 0.322204] pci 0000:00:1c.1: PREFETCH window: 0x00000080400000-0x000000805fffff
[ 0.322220] pci 0000:00:1c.3: PCI bridge, secondary bus 0000:01
[ 0.322230] pci 0000:00:1c.3: IO window: 0x2000-0x2fff
[ 0.322243] pci 0000:00:1c.3: MEM window: 0xf8000000-0xfbefffff
[ 0.322255] pci 0000:00:1c.3: PREFETCH window: 0x000000f0000000-0x000000f6ffffff
[ 0.322271] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:05
[ 0.322277] pci 0000:00:1e.0: IO window: disabled
[ 0.322289] pci 0000:00:1...

Revision history for this message
Konstantin Lavrov (lacosta) wrote :

So you still have it. But in fact your case not so similiar like mine.

Perhaps it is OK in your case. I mean it just reflects that there is problem with EDID.

In my case this ERROR repeats in dmesg many times.

And I have this: i915 0000:00:02.0: LVDS-1: EDID invalid.

And its happen even with mainline kernel and xorg from edgers.

Revision history for this message
Joonas Saarinen (jza) wrote :

I also have a LG X110 and I'm seeing this (2.6.32-22-generic kernel).

Changed in xserver-xorg-video-intel:
importance: Unknown → Medium
status: Unknown → Fix Released
Changed in xserver-xorg-video-intel:
importance: Medium → Unknown
Changed in xserver-xorg-video-intel:
importance: Unknown → Medium
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.