Bug 42876

Summary:	System doesn't boot with GTX 550 Ti
Product:	Drivers	Reporter:	Artyom Kunyov (artkun)
Component:	Video(DRI - non Intel)	Assignee:	drivers_video-dri
Status:	RESOLVED OBSOLETE
Severity:	blocking	CC:	artourter, legia, sergiomartinj, vovan
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	>3.2	Subsystem:
Regression:	Yes	Bisected commit-id:

Description Artyom Kunyov 2012-03-06 14:46:03 UTC

My hardware is:
ASUS P5KPL-AM SE, C2D E8500, GeForce GTX 550 Ti.

The problem is that with kernel newer than 3.2 (including 3.3 in Fedora 17), my system doesn't boot at all. I'm using nouveau and have no proprietary nvidia modules installed.
With 3.2, I'm getting nothing but "Loading initial ramdisk" on the screen, but HDD LED is blinking and when I press the Power button on my PC, the system turns off as it's supposed to.
But with 3.3 (in Fedora 17 and Ubuntu 12.04 with Canonical patched kernel), the system doesn't boot at all. After "Loading initial ramdisk" the monitor turns off, and nothing happens. HDD doesn't do anything.
This happens even without xf86-video-nouveau installed (i've tried Arch).

With kernel 3.1.9, my graphics card still works perfect, with a good 3D acceleration. GNOME 3 works perfect too.

I'm sorry for my English.

Comment 1 Sergio 2012-03-07 21:52:01 UTC

Same problem here.
Same graphic card, and nouveau driver.
I'm using Fedora 16.

With kernel 3.1.10-2 works fine.
With kernels 3.2.x don't work.

Comment 2 legia 2012-03-14 12:31:58 UTC

I have the same problem. No boot with 3.2.x kernel(Debian, Fedora).

C2D
Asus P5Q-E
GeForce 550 Ti

Comment 3 legia 2012-03-15 09:11:59 UTC

(In reply to comment #2)
> I have the same problem. No boot with 3.2.x kernel(Debian, Fedora).
> 
> C2D
> Asus P5Q-E
> GeForce 550 Ti

No problem with parameter acpi=off noapic

Comment 4 Sergio 2012-03-21 20:07:05 UTC

(In reply to comment #3)
> No problem with parameter acpi=off noapic

It worked for me in Fedora 16 with 3.2.10-2 kernel but, don't support for dual screen configuration and GNOME 3 only works in fallback mode.

Comment 5 Artyom Kunyov 2012-03-22 08:25:06 UTC

It worked for me as well with kernel 3.3.0, but with the wrong display resolution, and GNOME Shell was really slow.

Comment 6 ArTourter 2012-03-27 00:31:37 UTC

I have had the same problem with the 3.2 series on Slackware64 (I haven't tried 3.3)
Lenovo T520 laptop
Intel i7 2720QM CPU
Nvidia NVS 4200M

but I am not using the nouveau driver, but the proprietary nvidia driver which I think hasn't got the time to get loaded before the system freezes.

I have tried booting with both nouveau and nvidia blacklisted in console mode and still get the same behaviour.

As mention in comment #4, acpi=off noapic allows normal boot but it is really not practical on a laptop.

3.1.2 works fine (I haven't tried the more recent versions of the 3.1.x series).

Comment 7 Artyom Kunyov 2012-03-27 06:57:00 UTC

(In reply to comment #6)
> I have tried booting with both nouveau and nvidia blacklisted in console mode
> and still get the same behaviour.
> 
> As mention in comment #4, acpi=off noapic allows normal boot but it is really
> not practical on a laptop.

Did you try to install proprietary driver and boot with "rdblacklist=nouveau nouveau.modeset=0"? My system works fine with these boot flags, at least with 3.3

Comment 8 ArTourter 2012-03-29 23:36:40 UTC

(In reply to comment #7)
> (In reply to comment #6)
> > I have tried booting with both nouveau and nvidia blacklisted in console
> mode
> > and still get the same behaviour.
> > 
> > As mention in comment #4, acpi=off noapic allows normal boot but it is
> really
> > not practical on a laptop.
> 
> Did you try to install proprietary driver and boot with "rdblacklist=nouveau
> nouveau.modeset=0"? My system works fine with these boot flags, at least with
> 3.3

Thanks for the suggestion, however it doesn't work for me on 3.2.13. I haven't had the time to compile 3.3 yet.

Comment 9 Vlad 2012-03-30 09:09:26 UTC

I don't think this bug related to this particular card. I use GeForce 8600GT and, most likely, have the same issue with vanilla kernel 3.3 on Gentoo. Almost instantly after I select a menu entry in bootloader I'm getting corrupted/flashing screen and nothing more. Though I didn't try acpi=off and noapic options. One more note, I'm able successfully kexec to 3.3 after initial boot to 3.2.x kernel. After kexec everything works fine with the 3.3 kernel. Hopefully this helps understanding this problem.

Comment 10 Vlad 2012-03-30 09:10:08 UTC

Forgot to mention that I'm using nouveau.

Comment 11 ArTourter 2012-06-25 22:31:03 UTC

I am not sure if this bug report is still live but having just updated my machine to the latest slackware64-current kernel (3.2.21), I am still getting my system to hang half way through the booting sequence. As previously, the only thing that can be done at that point is to hard reset.

My laptop has a dual graphics card and switching to the intel embedded one in the BIOS makes the system boot fine, but switching to the nvidia one makes the system unable to boot unless ACPI is switched off.

I am still able to boot fine with kernels 3.1.x and below.

Comment 12 Sergio 2012-06-25 22:43:30 UTC

ArTourter, for me, in Fedora 18 (Kernel 3.4.2) solves the problem.

Comment 13 ArTourter 2012-06-25 23:34:12 UTC

Hi,

I have just compiled 3.4.4 and I still get exactly the same hang/freeze with ACPI active.

Any clues about how to get sensible error report out of this would be useful.

Comment 14 Vlad 2012-06-26 04:41:55 UTC

I had the same issue again after 3.2 kernel with 3.4.0. However at least vanilla 3.4.3 boots fine again.