Bug 679583 - [G96] nouveau boot failure on Macbook Pro
Summary: [G96] nouveau boot failure on Macbook Pro
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 15
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
: 694503 816695 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2011-02-22 22:12 UTC by Ralph Giles
Modified: 2018-04-11 17:22 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-08-07 19:29:00 UTC
Type: ---

Attachments (Terms of Use)
VESA livecd boot Xorg.0.log (62.39 KB, text/plain)
2011-03-21 23:23 UTC, Ralph Giles
no flags Details
VESA livecd boot /var/log/messages (179.24 KB, text/plain)
2011-03-21 23:24 UTC, Ralph Giles
no flags Details
screen capture of dmesg from warm reboot (153.69 KB, image/jpeg)
2011-07-07 13:54 UTC, Alex Murray
no flags Details
screen capture of dmesg from cold boot back into Fedora 15 (147.94 KB, image/jpeg)
2011-07-07 13:56 UTC, Alex Murray
no flags Details
kmsg dump including dump_stack() output when loading the driver manually (9.45 KB, text/x-log)
2011-10-20 19:54 UTC, Rolf Offermanns
no flags Details

Description Ralph Giles 2011-02-22 22:12:38 UTC
Description of problem:

gfx test day live cd fails to boot on Macbook Pro

Version-Release number of selected component (if applicable):


How reproducible:

Tried with both cold and warm boots with the same result.

Steps to Reproduce:
1. download gfx_test_week_20110221_x86-64.iso aka 'graphics_test_week_20'
2. burn to cd
3. insert cd
4. shut down machine
5. start machine
6. hold down 'c' briefly to boot from the cd-rom
Actual results:

CD drive spins up, bios-y underscore cursor appears for a fraction of a second, then fedora bootloader screen appears and counts down. Screen turns light gray, some dark horizontal bars flicker briefly, and then following lines are printed at the top of the screen, gray text on black:

[    2.101533] [drm] nouveau 0000:02:00.0: DCB I2C entry invalid
[    3.849383] [drm] nouveau 0000:02:00.0: PRAMIN flush timeout
[    5.469452] [drm] nouveau 0000:02:00.0: PRAMIN flush timeout

Machine is locked hard and shutdown must be forced by holding down the power button for 5 seconds.

Expected results:

Boot to LiveCD desktop.

Additional info:

Under MacOS, 'System Profiler' says the machine is:

MacBookPro5,1 Intel Core 2 Duo 2.4 GHz 4 GB ram

NVidia GeForce 9400M (device 10de:0863 rev 0x00b1 rom 3437 256 MB PCI)
NVidia GeForce 9600M GT (device 10de:0647 rev 0x00a1 rom 3437 256 MB PCIe/x16)
native display is 1440x900 LCD

Booting with 'basic video' (vesa driver) and running smoltSendProfile generated

Comment 1 Matěj Cepl 2011-03-07 15:36:39 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information especially concerning your hardware we require that will be helpful in our diagnosis of this issue.

If the anaconda crashes during the switching to the graphic mode, most likely the problem lies in Xorg support for your graphics chip. There are couple of options how we can obtain information necessary for resolving the issue.

If the computer is not completely frozen when installation fails, switch to the console (Ctrl+Alt+F2) and copy /tmp/X* and /var/log/anaconda.xlog to some other place -- USB stick, some other computer via network, somewhere on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

If the computer is completely useless after installation fails, you can also install Fedora with a VESA mode driver (see http://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/
for more information on that). Then after successful installation you can collect /var/log/anaconda.xlog, /var/log/Xorg.0.log, and the output of the program dmesg instead.

Or you can install Fedora in a text mode completely, and then start X after that. If it fails, still /var/log/Xorg.0.log and the output of dmesg program from the failed attempt to start X would be useful.

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

Thank you very much in advance.

Comment 2 Ralph Giles 2011-03-21 23:22:02 UTC
I tried again with 'Fedora-15-Alpha-i686-Live-Desktop.iso' downloaded today.

The machine hangs hard at while starting up. Booting in 'basic video' mode it completes and shows the gnome2 fallback.

I wasn't installing, just trying the live cd, so I don't know if the attached logs are helpful. FWIW, here they are.

Comment 3 Ralph Giles 2011-03-21 23:23:07 UTC
Created attachment 486702 [details]
VESA livecd boot Xorg.0.log

Comment 4 Ralph Giles 2011-03-21 23:24:02 UTC
Created attachment 486703 [details]
VESA livecd boot /var/log/messages

Comment 6 Ben Skeggs 2011-04-07 23:36:01 UTC
*** Bug 694503 has been marked as a duplicate of this bug. ***

Comment 7 Ben Skeggs 2011-04-07 23:36:53 UTC
Okay, I have only one theory of what could be happening here so far.  Do either of you guys have an actual install so that you could try a test kernel for me?

Comment 8 Ralph Giles 2011-04-08 01:02:29 UTC
I don't have an install (not my machine) but I can probably hack up a live image.

Comment 9 Ben Skeggs 2011-04-08 05:14:31 UTC
Okay, I've done a scratch kernel build that's available here: http://koji.fedoraproject.org/koji/taskinfo?taskID=2983210

I'll leave NEEDINFO set until someone has tested it :)

Comment 10 Seth Doty 2011-04-08 15:33:40 UTC
I went ahead and did a full install on my macbook this morning.  Pulled down all available updates, installed your kernel build, rebooted, and still the same message for me.

Comment 11 Ralph Giles 2011-04-08 17:05:36 UTC
I spend some time trying to hack something this morning, but didn't succeed in the allotted time.

In case it's relevant, I also tried the April 7 boot.iso, sha256sum

14d8ce7d72430d9a387ddb3fc48b13c88191e91697be861992df8ae979270216  boot.iso

And got as far as starting anaconda in text mode before it hung on 'waiting for hardware to initialize'.

Comment 12 Ben Skeggs 2011-04-10 23:59:25 UTC
(In reply to comment #10)
> I went ahead and did a full install on my macbook this morning.  Pulled down
> all available updates, installed your kernel build, rebooted, and still the
> same message for me.

Can I get your dmesg output from after it's failed?

Comment 13 Alex Murray 2011-07-06 23:57:49 UTC
Ben - I've posted a mmiotrace https://bugs.freedesktop.org/show_bug.cgi?id=27501#c9 of the nvidia binary driver on the upstream corresponding bug if thats any help - basically simply modprobing nouveau on latest Fedora / Ubuntu is enough to get this hang on my MacBook Pro 5,1 - ie. the modprobe doesn't even succeed - yet it is fine with the binary driver - the mmiotrace output is quite short though so hopefully it can help. Unfortunately the screen becomes corrupted after trying to modprobe nouveau so I can't see the dmesg output.

Comment 14 Alex Murray 2011-07-07 13:54:04 UTC
Created attachment 511713 [details]
screen capture of dmesg from warm reboot

Captured this after rebooting from my Ubuntu desktop with the NVIDIA driver loaded into the Fedora 15 Desktop ISO.

Comment 15 Alex Murray 2011-07-07 13:56:30 UTC
Created attachment 511715 [details]
screen capture of dmesg from cold boot back into Fedora 15

I then hard powered off my machine and cold booted into the Fedora 15 ISO and got this shorter dump - in both cases the machine was hard locked at the point of capture. I am guessing the reason the first one is longer is the warm reboot left the card better initialised from the NVIDIA driver beforehand whereas on this cold boot nouveau did a worse job. Ben anything helpful here? Anything more I can try and get for you? Would love to see this get fixed.

Comment 16 Rolf Offermanns 2011-08-28 07:35:41 UTC
Any news on this bug?

I have the same problem with my MBP (5,2) and the F16 alpha release (3.1.0-0.rc3.git0.0.fc16.i686).

Comment 17 Rolf Offermanns 2011-10-19 11:07:58 UTC
Still present in F16b1 + updates (3.1.0-0.rc9.git0.0.fc16.x86_64).

Is there anything I can do to help?

Comment 18 Rolf Offermanns 2011-10-20 19:54:05 UTC
Created attachment 529374 [details]
kmsg dump including dump_stack() output when loading the driver manually

I inserted a dump_stack() call to the nv84_instmem_flush routine using kernel 3.1.0-0.rc10.git0. Don't know if it helps...

Comment 19 buttr1a 2012-04-04 02:23:15 UTC
Had the same problem on my MacBook pro with Ubuntu. Try temporarily changing the kernel boot option to " nomodeset" to boot, then change it permanently in the grub config file.  Instructions here:

Comment 20 Dave Jones 2012-04-26 18:14:46 UTC
*** Bug 816695 has been marked as a duplicate of this bug. ***

Comment 21 Fedora End Of Life 2012-08-07 19:29:04 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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:

Note You need to log in before you can comment on or make changes to this bug.