[g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

Bug #487185 reported by Rusty64bit
66
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Karmic by Bless Sword
Nominated for Lucid by Bless Sword
xserver-xorg-video-intel (Fedora)
Won't Fix
High

Bug Description

Binary package hint: xorg

i'm getting

i915 0000:00:02.0: HDMI Type A-1: no EDID data
[ 1096.497057] i2c-adapter i2c-1: unable to read EDID block.
[ 1096.497061] i915 0000:00:02.0: HDMI Type A-1: no EDID data
[ 1096.501452] i2c-adapter i2c-1: unable to read EDID block.
[ 1096.501455] i915 0000:00:02.0: HDMI Type A-1: no EDID data

in dmesg

sometimes the screen went black, but comes back after 2 or 3 sec.

Swapped the mainboard of my PC from Intel G35 based to Intel G45 based

ProblemType: Bug
Architecture: i386
Date: Mon Nov 23 18:01:11 2009
DistroRelease: Ubuntu 9.10
Package: xorg 1:7.4+3ubuntu7
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=a6332eff-2d47-4a2d-8870-ddabfae24225 ro quiet splash
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xorg
Uname: Linux 2.6.31-14-generic i686
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
dmi.bios.date: 09/27/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: IDG4510H.86A.0117.2009.0927.1107
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DG45ID
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE27729-310
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrIDG4510H.86A.0117.2009.0927.1107:bd09/27/2009:svn:pn:pvr:rvnIntelCorporation:rnDG45ID:rvrAAE27729-310:cvn:ct3:cvr:
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03)
     Subsystem: Intel Corporation Device [8086:5002]

Revision history for this message
In , MartinG (marting-redhat-bugs) wrote :
Download full text (8.2 KiB)

Description of problem:

My system runs into a soft lockup after some time, seemingly at random, but it could be that it only happens after ~30 min of idling.

The display goes blank, the monitor says "No signal", but I can still ssh into the machine. I am not able to wake it up by ctrl-alt-f2 or the like.

"init 3" as root does not work, and I can't seem to kill any running programs (over ssh, as root - the shell never returns)

In /var/log/messages I get:

INFO: task events/0:9 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
events/0 D ffff88012de02024 0 9 2
 ffff88012fb31d60 0000000000000046 0000000000000001 ffffffffa04774eb
 ffff88012fb31cf0 ffffffff81046bf0 ffff88012fb31cf0 000000008604ee9e
 ffff88012fb060e8 000000000000e2e8 ffff88012fb060e8 0000000000012cc0
Call Trace:
 [<ffffffffa04774eb>] ? mantis_query_rc+0x0/0x89 [mantis]
 [<ffffffff81046bf0>] ? dequeue_entity+0x2f/0x1e8
 [<ffffffff810477d8>] ? dequeue_task_fair+0x81/0xa0
 [<ffffffff810108f2>] ? __switch_to+0x19c/0x23c
 [<ffffffff814970e7>] __mutex_lock_common+0x12c/0x1a8
 [<ffffffff8149718f>] __mutex_lock_slowpath+0x2c/0x42
 [<ffffffff81497366>] mutex_lock+0x43/0x71
 [<ffffffffa00682ad>] i915_gem_retire_work_handler+0x40/0x96 [i915]
 [<ffffffffa006826d>] ? i915_gem_retire_work_handler+0x0/0x96 [i915]
 [<ffffffff8106b8b9>] worker_thread+0x1ab/0x25d
 [<ffffffff81070b57>] ? autoremove_wake_function+0x0/0x5f
 [<ffffffff8106b70e>] ? worker_threa...

Read more...

Revision history for this message
In , MartinG (marting-redhat-bugs) wrote :
Revision history for this message
In , Chuck (chuck-redhat-bugs) wrote :

Can you get the output of sysrq-t when that happens? Just ssh in and do:

# echo "t" >/proc/sysrq-trigger

If the lockup messages are being logged that should be make it to the logs too.

Revision history for this message
In , MartinG (marting-redhat-bugs) wrote :

Created attachment 362767
/var/log/messages

Attached /var/log/messages after the display went dark, and I ssh'd into the machine, and issued the command above.

Revision history for this message
In , MartinG (marting-redhat-bugs) wrote :

Contrary to what I stated above, I am in fact able to kill running programs - if I do "killall -9 X" I am able to log in as normal, and things seemingly work as it should. But this is not satisfactory workaround for the livingroom TV... ;)

Revision history for this message
In , MartinG (marting-redhat-bugs) wrote :

Created attachment 362774
/var/log/messages again

It happened again, after I had done "killall -9 X" and ran like normal for a while. The numbers in the log are a bit different, don't know if that could be helpful.

Revision history for this message
In , Mikolaj (mikolaj-redhat-bugs) wrote :

Created attachment 366934
/var/log/messages

I had something similar, but with network device. My setup is:

ifconfig eth0 up
brctl addbr virbr0
brctl addif virbr0 eth0
ifconfig virbr0 172.16.0.1 netmask 255.255.255.0 up

and to that bridge qemu-kvm virtual machines are added:

cat /srv/kvm/qemu-ifup
#!/bin/sh
...
ifconfig "$1" up
brctl addif virbr0 "$1"

I was doing some testing of my new Gigabit switch and I was plugging in and plugging out Ethernet cable to/from eth0 (see my /var/log/messages) and then machine got unresponsive via second interface, wlan0. To bring the box back I've done alt+ctrl+del, as monitor didn't want to turn on. I'm not 100% sure, but that happened on 2.6.30.8-64.fc11.i686.PAE or earlier version.

Revision history for this message
In , Mikolaj (mikolaj-redhat-bugs) wrote :

Created attachment 366935
dmesg

Here is my full dmesg, but with newer version of kernel.

Revision history for this message
Rusty64bit (mirko73) wrote :
Bryce Harrington (bryce)
affects: xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
brjhaverkamp (bert-bertenselena) wrote :

I see this problem too on a G45 machine. The dmesg output continues forever
[ 141.413298] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 142.236246] i2c-adapter i2c-3: unable to read EDID block.
[ 142.236251] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 142.240696] i2c-adapter i2c-3: unable to read EDID block.
[ 142.240700] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 142.937198] i2c-adapter i2c-3: unable to read EDID block.
[ 142.937202] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 142.941687] i2c-adapter i2c-3: unable to read EDID block.
[ 142.941690] i915 0000:00:02.0: HDMI Type A-2: no EDID data

Difference here is that I am unable to run X at all. Last lines in Xorg.0.log are
(II) intel(0): [DRI2] Setup complete
(**) intel(0): Tiling enabled
(**) intel(0): SwapBuffers wait enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.

The screen stays blank.

Bryce Harrington (bryce)
summary: - On Intel G45 unable to read EDID block in Dmesg after move from G35 to
- G45
+ [g45] On Intel G45 unable to read EDID block in Dmesg after move from
+ G35 to G45
Geir Ove Myhr (gomyhr)
tags: added: edid g45 karmic
Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

Strange. The EDID block is contained in both Xorg.0.log and `xrandr --verbose` output (XorgLog.txt and Xrandr.txt), so Xorg is able to read it somehow.

Except for the 2-3 second blanking, is the system working properly?

Revision history for this message
Rusty64bit (mirko73) wrote : Re: [Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45

I had only about two hours to test yet, but it looked stable, means
wasn't crashing within this time.
boots fine and fast and goes straigt to the login.
I had a HDMI to HDMI cable connected first, this was causing the screen
flicker, but with the org. HDMI to DVI cable, that came with the IIyama
LCD, i could not see the flickering screen. maybe just too fast to see it

Geir Ove Myhr schrieb:
> Strange. The EDID block is contained in both Xorg.0.log and `xrandr
> --verbose` output (XorgLog.txt and Xrandr.txt), so Xorg is able to read
> it somehow.
>
> Except for the 2-3 second blanking, is the system working properly?
>
>

Revision history for this message
Havard Sorli (havard-sorli) wrote :

Not sure if this is the same:

The box almost frezze, some about 10-15 sec. after login if I move the mouse. It's possible to login via ssh from another computer.
(worked in Ubuntu 8.10 and 9.4 upgraded to 9.10 and it failed

# tail -n 100 /var/log/messages
Dec 3 19:12:17 hlap kernel: [ 31.031357] i2c-adapter i2c-1: unable to read EDID block.
Dec 3 19:12:17 hlap kernel: [ 31.031364] i915 0000:00:02.0: LVDS-1: no EDID data

Revision history for this message
Havard Sorli (havard-sorli) wrote :

xrandr --verbose gives:

# xrandr --verbose
Xlib: extension "Generic Event Extension" missing on display "localhost:10.0".
 SZ: Pixels Physical Refresh
*0 1920 x 1200 ( 554mm x 342mm ) *60
 1 1600 x 1200 ( 554mm x 342mm ) 61
 2 1280 x 1024 ( 554mm x 342mm ) 76
 3 1024 x 768 ( 554mm x 342mm ) 76
 4 800 x 600 ( 554mm x 342mm ) 73
 5 640 x 480 ( 554mm x 342mm ) 73
Current rotation - normal
Current reflection - none
Rotations possible - normal
Reflections possible - none
Setting size to 0, rotation to normal
Setting reflection on neither axis

Revision history for this message
Havard Sorli (havard-sorli) wrote :

Possible to kill -9 (prosee id) X server (this line in #ps aux ) from ssh login from another computer.
/usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7

Changed in xserver-xorg-video-intel (Fedora):
status: Unknown → Confirmed
Revision history for this message
Rusty64bit (mirko73) wrote :

I did a clean install of 9.10 and mine is stable so far.
updated to the latest bios from Intel, but no change since then.
I tested it on my old Asus G35 board and havn't got the error at all.

Havard Sorli schrieb:
> Not sure if this is the same:
>
> The box almost frezze, some about 10-15 sec. after login if I move the mouse. It's possible to login via ssh from another computer.
> (worked in Ubuntu 8.10 and 9.4 upgraded to 9.10 and it failed
>
> # tail -n 100 /var/log/messages
> Dec 3 19:12:17 hlap kernel: [ 31.031357] i2c-adapter i2c-1: unable to read EDID block.
> Dec 3 19:12:17 hlap kernel: [ 31.031364] i915 0000:00:02.0: LVDS-1: no EDID data
>
>
> ** Attachment added: "X.org.0.log, messages log"
> http://launchpadlibrarian.net/36401642/more-info.txt
>
>

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Avuton Olrich (avuton) wrote :
Download full text (3.7 KiB)

Would like to give something a bit more useful than "me too" but I'm afraid I don't comre with much more than me being in karmic and having the same problems described by the toppost. Stays stable afterwards for a random amount of time then will occur again. Sometimes occurs again after a suspend/resume cycle as well.

--snip--
[ 7.464679] heci driver initialization successful.
[ 7.552847] usb 6-1: configuration #1 chosen from 1 choice
[ 7.560956] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/input/input8
[ 7.561000] generic-usb 0003:046D:C526.0004: input,hidraw3: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1/input0
[ 7.565834] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.1/input/input9
[ 7.565890] generic-usb 0003:046D:C526.0005: input,hiddev96,hidraw4: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1/input1
[ 7.612815] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 7.842740] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 7.842796] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 8.230444] e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
[ 8.281532] e1000e 0000:00:19.0: irq 25 for MSI/MSI-X
[ 8.281894] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 8.293904] usbcore: registered new interface driver snd-usb-audio
[ 8.351171] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input10
[ 9.761938] i2c-adapter i2c-3: unable to read EDID block.
[ 9.761941] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 9.766358] i2c-adapter i2c-3: unable to read EDID block.
[ 9.766360] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 10.475362] i2c-adapter i2c-3: unable to read EDID block.
[ 10.475366] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 10.480687] i2c-adapter i2c-3: unable to read EDID block.
[ 10.480691] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 10.680799] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 10.681261] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 10.801065] ppdev: user-space parallel port driver
[ 12.167592] CPU0 attaching NULL sched-domain.
[ 12.167596] CPU1 attaching NULL sched-domain.
[ 12.201327] CPU0 attaching sched-domain:
[ 12.201331] domain 0: span 0-1 level MC
[ 12.201333] groups: 0 1
[ 12.201338] CPU1 attaching sched-domain:
[ 12.201340] domain 0: span 0-1 level MC
[ 12.201342] groups: 1 0
[ 13.084468] i2c-adapter i2c-3: unable to read EDID block.
[ 13.084471] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 13.088895] i2c-adapter i2c-3: unable to read EDID block.
[ 13.088897] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 13.183734] RPC: Registered udp transport module.
[ 13.183737] RPC: Registered tcp transport module.
[ 13.782651] i2c-adapter i2c-3: unable to read EDID block.
[ 13.782654] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 13.787064] i2c-adapter i2c-3: unable to read EDID block.
[ 13.787065] i915 0000:00:02.0: HDMI Type A-2: no EDID data
[ 13.810214] svc: failed to register lockdv1 RPC service (errno 97).
[ 14.474...

Read more...

Revision history for this message
Maxxer (lorenzo-milesi) wrote :

while not having apparently experience any misbehavior (in 2 days of life), I've seen these messages in my syslog too.
fresh install of 9.10 on Amilo 3655.

Revision history for this message
lmp (lmps) wrote :

I have same situation, bu unfortunately I have problems too.
I have port replicator with connected external monitor.
So this monitor is not detected or just disappears on some random bases. After a while it can be detected again.
Display preferences, Detect monitor - nothing happens (i.e. changes).
Reboot typically helps.
I have Fujitsu Siemens Lifebook.

As from logs, I didn't find anything not listed here.

Revision history for this message
In , MartinG (marting-redhat-bugs) wrote :

This bug report has been silent for a couple of months now, but the bug is still biting me every now and then.
It happened just now, as I was watching a recording from my mediacenter, so it is not happening only when idling.

Any more info I can provide, any tests I can do...? :)

Revision history for this message
In , Matthew (matthew-redhat-bugs) wrote :
Download full text (13.1 KiB)

Hi, I'm also seeing this bug daily in Fedora 12. It seems to duplicate the following bugs reported to LKML and Ubuntu:

http://lkml.org/lkml/2009/1/11/70
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/276476

Note that LKML seems to imply that a patch was incorporated in 2.6.29 while feedback from Ubuntu is that the bug is still present in 2.6.31.

My seeing the bug would seem to confirm that the issue is also still unfixed and present in fedora 12.

Here is some sample output:

Jan 27 00:55:29 hyperion kernel: INFO: task firefox:2624 blocked for more than 120 seconds.
Jan 27 00:55:29 hyperion kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 27 00:55:29 hyperion kernel: firefox D 0000000000000002 0 2624 2062 0x00000000
Jan 27 00:55:29 hyperion kernel: ffff88008f125528 0000000000000086 ffff88008f1254a8 ffff880000000000
Jan 27 00:55:29 hyperion kernel: ffff88008f125498 ffffffff8104039a ffff8801fdce2f38 ffff880028066670
Jan 27 00:55:29 hyperion kernel: ffff8801fdce32c8 000000000000f8f0 ffff8801fdce32c8 0000000000015600
Jan 27 00:55:29 hyperion kernel: Call Trace:
Jan 27 00:55:29 hyperion kernel: [<ffffffff8104039a>] ? account_group_exec_runtime+0x30/0x43
Jan 27 00:55:29 hyperion kernel: [<ffffffff8106e8e3>] ? clocksource_read+0xf/0x11
Jan 27 00:55:29 hyperion kernel: [<ffffffff8106acf2>] ? ktime_get_ts+0x4e/0x53
Jan 27 00:55:29 hyperion kernel: [<ffffffff810c154d>] ? sync_page+0x0/0x4a
Jan 27 00:55:29 hyperion kernel: [<ffffffff8141bf53>] io_schedule+0x31/0x42
Jan 27 00:55:29 hyperion kernel: [<ffffffff810c1593>] sync_page+0x46/0x4a
Jan 27 00:55:29 hyperion kernel: [<ffffffff8141c465>] __wait_on_bit+0x48/0x7b
Jan 27 00:55:29 hyperion kernel: [<ffffffff8141bead>] ? thread_return+0x4e/0xc3 ...

Revision history for this message
T. S. (t.s.) wrote :

I apparently just experienced the same problem, and it crashed my X server. I was writing some e-mails in Thunderbird and suddenly X crashed and restarted. I was running just the laptop screen at the time, but often I use an external screen as well, if that matters.

I have a Fujitsu S7020 with Intel 915GM/GMS/910GML graphics, running Ubuntu 9.10 and kernel 2.6.31-17-generic #54-Ubuntu SMP.

I'm a little confused by the syslog since it appears that Gnome was already dead when the kernel logged the EDID error.

Feb 2 11:40:53 goedel ntpd[2248]: frequency initialized 9.256 PPM from /var/lib/ntp/ntp.drift
Feb 2 11:40:54 goedel kernel: [ 52.956014] eth2: no IPv6 routers present
Feb 2 11:40:57 goedel gdm-simple-greeter[2149]: WARNING: Unable to lookup user name data: Success
Feb 2 11:40:57 goedel gdm-simple-greeter[2149]: WARNING: Unable to parse history: (null) 2#012
Feb 2 11:41:03 goedel wpa_supplicant[1275]: CTRL-EVENT-SCAN-RESULTS
Feb 2 11:41:15 goedel gnome-session[2281]: WARNING: Could not launch application 'at-spi-registryd-wrapper.desktop': Unable to start application: Failed to execute child process "/usr/lib/gnome-session/helpers/at-spi-registryd-wrapper" (No such file or directory)
Feb 2 11:41:15 goedel kernel: [ 73.806724] i2c-adapter i2c-1: unable to read EDID block.
Feb 2 11:41:15 goedel kernel: [ 73.806730] i915 0000:00:02.0: LVDS-1: no EDID data
Feb 2 11:41:15 goedel kernel: [ 73.969558] i2c-adapter i2c-1: unable to read EDID block.
Feb 2 11:41:15 goedel kernel: [ 73.969563] i915 0000:00:02.0: LVDS-1: no EDID data
Feb 2 11:41:15 goedel kernel: [ 74.112981] i2c-adapter i2c-1: unable to read EDID block.
Feb 2 11:41:15 goedel kernel: [ 74.112986] i915 0000:00:02.0: LVDS-1: no EDID data
Feb 2 11:41:21 goedel gnome-session[2281]: WARNING: Could not launch application 'hplip-systray.desktop': Unable to start application: Failed to execute child process "hp-systray" (No such file or directory)
Feb 2 11:41:21 goedel pulseaudio[2334]: module-x11-xsmp.c: X11 session manager not running.

Bryce Harrington (bryce)
description: updated
Revision history for this message
Rusty64bit (mirko73) wrote :

Yesterday i installed the 2.6.32.8 ubuntu mainline kernel on my system and the problem disappered !
No more messages in dmesg

Bryce Harrington (bryce)
summary: - [g45] On Intel G45 unable to read EDID block in Dmesg after move from
- G35 to G45
+ [g45] [g45] On Intel G45 unable to read EDID block in Dmesg after move
+ from G35 to G45
Bryce Harrington (bryce)
summary: - [g45] [g45] On Intel G45 unable to read EDID block in Dmesg after move
- from G35 to G45
+ [g45] On Intel G45 unable to read EDID block in Dmesg after move from
+ G35 to G45
Revision history for this message
Bryce Harrington (bryce) wrote :

Based on Rusty's last comment that this was fixed in the .32 kernel, which we include in lucid, I assume this will no longer be an issue in lucid. Can anyone confirm that?

Meanwhile, since it sounds like this issue needs a kernel fix I'm reassigning to linux.

affects: xserver-xorg-video-intel (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
status: Incomplete → New
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Rusty64bit,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Rusty64bit (mirko73) wrote :

Jeremy,

i'm running 2.6.32.11 mainline a while now and havn't seen the problem
anymore.
started testing with 2.6.32.8

Am 24.04.2010 00:17, schrieb Jeremy Foshee:
> Hi Rusty64bit,
>
> If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

tags: removed: needs-upstream-testing
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Bryce,
    just so I don't close this prematurely, do you think this needs a fix for kernel?

~JFo

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
Arvid Norlander (vorpalblade) wrote :

I have these messages too. Lenovo Thinkpad R500 running lucid with 2.6.31 kernel. Unable to test 2.6.32 kernels due to other bugs (reported elsewhere). Strangest thing is that this system have DisplayPort rather than HDMI. I don't have any external monitor connected, nor any to test with. But the internal display (which xrandr reports is on "LVDS1") works fine.

Revision history for this message
toddq (toddq) wrote :

same problem

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Changed in xserver-xorg-video-intel (Fedora):
importance: Unknown → High
status: Confirmed → Won't Fix
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.