Bug 681248

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

The system is really unstable after login. System freezes when clicking anything. Switching to VT also results to complete freeze. I have no idea how to get those infos as you required. :( Any help is welcomed.

Another thing I would like to add is that just seconds before Plymouth starts, two lines of error appear on screen. From the photo I tried my best to capture, they read:

[0.002366] /proc/device-tree: can't find root
[0.328454] pci_root PNP0A08:00: address space collision: host bridge win(...)
(...)em 0x000cc000-0x000cffff] conflicts with Video ROM [mem 0x000c000-0x000ce(...)


(...) is the part which did not get clear from the photo.

There are three possible lines of attack:

a) When you get to the kernel boot menu (the one which says “Boot/Boot (Basic Video)/Verify and Boot/…”) if you leave the cursor on “Boot” and press key ‘a’ you can edit kernel command line. If you add there string “nomodeset” (without quote obviously) your system will start without loading kernel graphic modules with different mode. It may (but doesn't have to) help. Does it?
b) Again, on the kernel command line you can number 3 to it and removing words “rhgb quiet” … that starts system in the text mode (also without graphical boot), but with the kernel drivers. If you run (as normal user, not root; login is liveuser and it has no password) command startx what happens? If it crashes do you get back to the command line? If yes, it is the ideal case ... store output of the command dmesg (i.e., using dmesg >dmesg-log.txt) and /var/log/Xorg.0.log and /var/log/messages somewhere (USB thumb drive, somewhere on the Internet via scp or ftp, via email ... that would be probably difficult to configure for you) and attach them to this bug as separate uncompressed attachments.
c) of course, you can combine these two .. both nomodeset and 3 could be applied together, if nothing else works.

Thank you very much.

Thanks for your guides, here's my result:

a) the Plymouth falls back to simple blue progress bar. However, it hung at roughly 75% and left only a blinking prompter.

b) It went on OK until a line started with "[drm]" appears. Then the old rendering corruption happened again.:(

c) Better than b), at least this time I could capture something with my camera on screen. http://picplz.com/cfvF Those errors rapidly scrolled and had no response to the "Pause Break" key.

I wish I could provide more infos. So let me know if there's any other ways to get the infos you guys needed. Thanks.

Do you still experience this with lastest alpha ?

(In reply to comment #5)
> Do you still experience this with lastest alpha ?

Tested with latest Fedora 15 Beta TC1, no rendering corruption was observed.

However, it hung at entry to gdm.
Booting with nomdeset kernel option resulted the identical error as captured in http://picplz.com/cfvF

(In reply to comment #5)
> Do you still experience this with lastest alpha ?

Just tried Fedora 15 Beta. Reaching GDM take uncommonly long time and immediately
 crash after hitting any GDM item.

Booting by removing 'rhgb' and 'quiet' from kernel parameters showed the following ever-lasting ACPI Error 
http://picplz.com/2K7x

It read:

[Time Stamp]No handler or method for GPE09, disabling event (20110112/evgpe-753)

Let me know if there's sth I can do to locate the bug.

Thanks,

Do you still have this issue (acpi or video one) with lastest f15 if so what is still an issue ?

The error message before Plymouth still presents.

Other issues seem to be gone and the system is on a stable status, even with GNOME 3 running.