[RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled (Needs DVI quirk)

Bug #561301 reported by Thomas Orgis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-ati

It is tricky to determine if this issue is the same as one reported in the several bugs about freezes / black screens, so I'm making a new one...

I installed a amd64 ubuntu lucid lynx beta1 system on a box with a Foxconn mainboard that features integrated radeon graphics, namely RS690. The system has all current updates as of last saturday.
I notice some things, possible related to the final freeze/crash/whatever:

1. Multiple flickering on startup, sortof in intervals of about a second. This includes the plymouth splash screen and the desktop after it appeared (automatic login) for some time. Annoying but not fatal as such, as it seems to stop, generally (maybe reappears once on certain actions, like starting a video player).

2. There is only a VGA connector and there the monitor is connected. The radeon driver complains about bad EDID data for the DVI port, multiple times. Well, there is no physical DVI port.

3. After some undetermined time of usage, the screen suddenty goes black, and I am unable to reach a console. I need to have a second computer to get debugging, I guess. The machine is not frozen, but the screen is gone.

This persists with a self-built 2.6.33.2-rt13 kernel (since this is supposed to be an audio workstation) in the same manner, with the linux-rt kernel it was a bit different (for example, I needed to fix the resolution in xorg.conf because with that kernel a wrong one is detected), I did not spend enough time with it to trigger that black screen ... or indeed it does not happen there.

I'll try starting with nomodeset ... then examine if there are still options like switching back to XAA (that worked in the past for the buggy intel drivers) ... or resort to VESA. I actually have no time to debug Xorg issues on that box, but well... do I have a choice? With another non-ubuntu system (older Xorg at least, kernel version about the same), this never occured. So it might have to do with the recent enable of KMS, or acceleration architecture updates.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/seq: musiker 1797 F.... qjackctl.bin
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe7f8000 irq 16'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,105b0c8c,00100002'
   Controls : 28
   Simple ctrls : 17
DistroRelease: Ubuntu 10.04
Frequency: I don't know.
HibernationDevice: RESUME=UUID=fe1f2b79-1cb9-4b0a-87c3-cd2aecac0d67
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 ppp0 no wireless extensions.
MachineType: FOXCONN RS690M2MA
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=1ffb8723-173a-4118-9350-13115ffe0b04 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=C
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.34
Reproducible: No
RfKill:

Tags: lucid graphics regression-release needs-upstream-testing
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare video
dmi.bios.date: 05/26/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: A690GM2MA/A690VM2MA
dmi.board.vendor: FOXCONN
dmi.board.version: 0A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd05/26/2008:svnFOXCONN:pnRS690M2MA:pvr0A:rvnFOXCONN:rnA690GM2MA/A690VM2MA:rvr0A:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: RS690M2MA
dmi.product.version: 0A
dmi.sys.vendor: FOXCONN

Revision history for this message
Thomas Orgis (thomas-forum) wrote :
Bryce Harrington (bryce)
tags: added: lucid
Revision history for this message
Thomas Orgis (thomas-forum) wrote :

nomodeset kernel option does nothing (at least on my kernel build), but radeon.modeset=0 does help. Worked an evening on the box with disabled modesetting now and didn't see a freeze/crash.
Only the mode detection is suboptimal... I have seen that in comparison to another Linux system I have on that box.. the image looked more crisp, less smearing on the LCD (that also covers the mode set using kernel modesetting). After manually fixing ip some tuned mode with slightly increased refresh rate (not 59.9 but rather 61 Hz or so) this is improved.

Main message: DIsabling kernel modesetting for RS690 _seems_ to be a good idea so far.

Bryce Harrington (bryce)
summary: [RV690] flicker on startup, dead black screen after some time with lucid
+ if KMS enabled
Revision history for this message
Bryce Harrington (bryce) wrote : Re: [RV690] flicker on startup, dead black screen after some time with lucid if KMS enabled

Weird, I'm not sure how you got that file out of apport, but it's not the right format of stuff... it just has all the files we need concatenated together. Our tools expect to have the individual files uploaded as separate attachments. Ah well.

Btw, thanks for doing all the troubleshooting in filing this defect report, it helps a lot.

Anyway, something is really loused up bad with your monitor EDID:

 [ 28.220068] [drm:edid_is_valid] *ERROR* Raw EDID:
 [ 28.220109] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.220111] <3>00 00 00 00 00 00 00 00 00 00 00 00 1f 00 00 00 ................
 [ 28.220113] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0f ................
 [ 28.220114] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.220116] <3>00 00 00 3f 00 00 00 00 00 00 00 00 00 00 00 00 ...?............
 [ 28.220118] <3>00 00 00 07 07 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.220120] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.220122] <3>7f 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 ................
 [ 28.220123]
 [ 28.242499] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
 [ 28.279284] [drm:edid_is_valid] *ERROR* Raw EDID:
 [ 28.279325] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.279327] <3>00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.279329] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.279331] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.279333] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.279334] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.279336] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 [ 28.279338] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

That probably goes along with your observation #2.

It's quite interesting that disabling KMS makes it work. That suggests there is an error in the EDID handling code in the kernel, at least for this specific gfx card and monitor combination. I don't think we should shut off KMS for this, because I think the issue is particular to your specific graphics card.

Issue #1 sounds like X trying to probe for EDID, and getting confused by the non-existence of the phantom DVI port.

#3 sounds like it might be a power management issue. Possibly it's unrelated to the above, but my money would be that PM is getting confused by the non-existent DVI port as well. That might need a separate fix, but lets see if it disappears once the phantom DVI issue is sorted.

I'm refiling to the kernel since this will need a DVI quirk in the kernel drm code. Since disabling KMS lets you work around the issue, it seems there is not an X task to do here.

affects: xserver-xorg-video-ati (Ubuntu) → linux (Ubuntu)
summary: [RV690] flicker on startup, dead black screen after some time with lucid
- if KMS enabled
+ if KMS enabled (Needs DVI quirk)
Revision history for this message
Thomas Orgis (thomas-forum) wrote :

About my mad monitor EDID ... are you talking about the existing LCD connected to VGA or the non-existing DVI? The physical monitor shouldn't be all that bad since it works without pain using an slightly older Xorg (perhaps about a year or so) without KMS. Should really be the hardware to blame? I hope it's possible to have the KMS code fixed up to work like the old code used to work... and also without KMS, Xorg now detects a sub-optimal mode. This might be due to some well-intended improvements, probably.

Oh, and a side note: The splash screen business looks rather pointless in the current setup... after the boot manager menu, there is a delay where nothing happens visually and just a cursor on the top left of a black screen is shown... disk starts clattering in the background... at some time, the ubuntu splash screen comes up, but is replaced by the actual desktop very quickly.
Same for shutdown ... it takes some moments to kill the desktop... and then the machine is off after very briefly offering a glimpse on the splash screen. So, some stuff is perhaps too fast (the actual work) ... though I am not sure what the delay at the beginning is about (should re-test with stock kernel and initrd... but I think it was the same there). But then... this is off-topic, just on my mind because of the flickering also hurting the perceived smoothness of the bootup.

tags: added: kj-triage
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Thomas,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux 561301

Also, if you could 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-kernel-logs
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Thomas Orgis (thomas-forum) wrote :

To make it clear: You suggest booting the final release ISO of ubuntu (29th of april)? I don't see ISOs of a "development" release.

I cannot promise much in the way of testing things... I am working with the machine only at certain intervals, and then it's usually more important to produce something with it. When I come around to test how a new kernel release works, I'll update the bug report -- in the end, people report that the 2.6.33 I am running now might not be the best for firewire audio.

Revision history for this message
Thomas Orgis (thomas-forum) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Thomas Orgis (thomas-forum) wrote : AplayDevices.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : ArecordDevices.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : BootDmesg.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : Card0.Codecs.codec.3.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : Lspci.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : Lsusb.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : PciMultimedia.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : ProcModules.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : UdevDb.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : UdevLog.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : UserAsoundrc.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote : WifiSyslog.txt

apport information

Revision history for this message
Thomas Orgis (thomas-forum) wrote :

The current ubuntu kernel still flickers around with KMS enabled... the splash screen comes very late and flickers.
I didn't wait if a freeze / black screen occurs... need to work now.
Maybe the apport info helps.

tags: added: kernel-graphics
Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
penalvch (penalvch) wrote :

Thomas Orgis, 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>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. 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.11.1

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):
status: Triaged → Incomplete
Revision history for this message
Thomas Orgis (thomas-forum) wrote :

The concerned Hardware is gone, so testing is not possible for me anymore. I guess the bug has to be closed ... I don't remember it occuring on other machines, also with integrated Radeon, but different chips.

Revision history for this message
penalvch (penalvch) wrote :

Thomas Orgis, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/561301/comments/26 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.