Bug 862925

Fails for example the following criteria ( and every desktop related one for alpha/beta )

"It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments. The web browser must be able to download files, load extensions, and log into FAS"

Removing set gfxpayload=keep from grub while keeping quiet works around this issue as well

Provide at least:

# lspci -nn | grep VGA

Also add drm.debug=0x04 to the kernel command line, restart computer, and
attach (if possible):

* 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)

After that, try to reproduce the issue again and also attach again the logs.

# lspci -nn | grep VGA
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712]

Created attachment 621200 [details]
dmesg with drm.debug

Created attachment 621201 [details]
Xorg.0.log

* your X server config file (/etc/X11/xorg.conf, if available)
By default there is none and has not been since somewhere around F10

* system log (/var/log/messages)

Nothing gets written in messages in F18 want me to provide you with the full output from the journal instead? 
( I would expect there would not be anything relevant there that is not already in dmesg and the Xorg log )

Created attachment 621202 [details]
journal output

output from journalctl -a -b -o short-monotonic --no-pager > journal.txt 

I can make this more verbose if required...

Is this correct ?

DMI: Hewlett-Packard HP Pavilion dm1 Notebook PC/148B, BIOS F.15 09/15/2010

There is a F.16 bios version. 

Otherwise this will print your motherboard and bios version:

# cat /sys/devices/virtual/dmi/id/board_name 

# cat /sys/devices/virtual/dmi/id/bios_version

I'm perfectly well aware that there is a newer bios version and I will be happy to upgrade my firmware for you as long as you can provide me with an alternative method to do so that does not require me to install Microsoft Windows first to do so or somehow burn it on a disk.

And just to reiterate this does not happen with kernels <rc7 including the releases that have the debug turned off.

Discussed at 2012-10-04 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-04/f18-beta-blocker-review-2.1.2012-10-04-16.00.log.txt . 

As this looks like a single-system X showstopper, we reject it as a blocker by established precedent (X bugs that affect only a single system or small range of systems are not considered to be wide enough to be blockers; we don't have the development capacity to commit to fixing all such bugs). If it turns out to affect a wider range of systems, it can be re-proposed as a blocker.

Dave, maybe this bug has enough info to give some insight into the lockup?

Note that this does not happen with 3.7.0-0.rc4 kernel

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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