Bug 774508

Summary:	Graphics freeze up after Plymouth bootsplash to desktop
Product:	[openSUSE] openSUSE 12.2	Reporter:	Roman Bysh <rb03884>
Component:	Basesystem	Assignee:	Forgotten User sM9JzehKpy <forgotten_sM9JzehKpy>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P3 - Medium	CC:	alinm.elena, cwh, fbourdonnec, julioeep, pieris89, rb03884, suse, swyear, zaitor
Version:	RC 2
Target Milestone:	RC 2
Hardware:	x86-64
OS:	openSUSE 12.2
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	plymouth.debug log

Description Roman Bysh 2012-08-04 00:20:37 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1

Every time I boot up the graphics on my screen freeze up right after the Plymouth bootsplash.

Reproducible: Always

Steps to Reproduce:
1. Start the computer
2. Watch the Plymouth bootsplash after the progress bar reaches about 75%
3. Entire screen freezes up
Actual Results:  
The green Plymouth bootsplash progress bar reaches about 75% and the screen freezes up. Cannot see the desktop.
I have to use CNTRL+ALT+Backspace to exit desktop. I then login and the desktop appears okay.

Expected Results:  
The green Plymouth bootsplash should boot up and fade out while desktop fades in smoothly. It should never switch to a black screen then desktop. 

It behaves the same as when openSUSE used splashy.

Comment 1 Stanley Miller 2012-08-04 05:40:53 UTC

I am seeing the same thing on my system with an Nvidia Quadro FX580. Killing X is working for me for now.

Comment 2 Stanley Miller 2012-08-05 00:04:32 UTC

I removed "splash-silent" from the boot loader options and the screen isn't getting corrupted.

Also hitting ESC while booting to see the console messages also eliminates the corrupt screen issue.

Comment 3 Ray chen 2012-08-08 00:30:48 UTC

I have the same problem
see video captured with my phone-cam:
http://dl.dropbox.com/u/6331820/2012-08-06%2008.26.32.mp4
after the screen corruption, press Ctrl-Alt+Backspacex2 can go in the login screen
see the dmesg message can find:
[   26.650999] [drm] nouveau 0000:01:00.0: fail set_domain
[   26.651049] [drm] nouveau 0000:01:00.0: validate vram_list
[   26.651055] [drm] nouveau 0000:01:00.0: validate: -22
[   26.651076] [drm] nouveau 0000:01:00.0: fail set_domain
[   26.651078] [drm] nouveau 0000:01:00.0: validate vram_list
[   26.651081] [drm] nouveau 0000:01:00.0: validate: -22
[   26.682301] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0200 Data 0x000000cf
[   26.682326] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0204 Data 0x00000000
[   26.682351] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0208 Data 0x00000040
[   26.682374] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x020c Data 0x00000001
[   26.682398] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0210 Data 0x00000000
[   26.682421] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0218 Data 0x00000500
[   26.682446] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x021c Data 0x00000320
[   26.682463] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0220 Data 0x00000000
...a lot of PFIFO_CACHE_ERROR

but if boot without plymouth (press Esc before the screen corruption)
above message will disappear

hope this message can help to solve the problem

Comment 4 Forgotten User sM9JzehKpy 2012-08-08 06:37:10 UTC

@Roman and @Ray: Did you try to boot with the option indicated in comment #2 ? 

@Ray: Can you describe a little more about the hardware you are running on and which kernel you are using? Is this a Xen boot ??  The reason why I am asking about Xen is that I found a bug report on Debian describing the PFIFO_CACHE_ERROR with Nouveau and this seems to be an kernel-issue. But it only appeared when booting as Xen. 

Also I would like to ask you to update to the latest available versions. 

Thanks

Comment 5 Ray chen 2012-08-08 06:59:52 UTC

I'm running openSUSE 12.2 rc2 on my laptop with nvidia GeForce 9300M G graphic card
installed with openSUSE-DVD-x86_640091 downloaded from software.opensuse.org
I don't think it's a kernel-relative bug
plymouth even can run on the same laptop when openSUSE 12.2 beta1
I have video:
http://dl.dropbox.com/u/6331820/2012-06-08%2004.34.50.mp4

however, my kernel and hardware info:

uname -a
Linux linux-wtrh.site 3.4.6-1.1-desktop #1 SMP PREEMPT Thu Jul 26 09:36:26 UTC 2012 (641c197) x86_64 x86_64 x86_64 GNU/Linux

lspci 
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 03)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03)
01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 9300M G] (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
06:00.0 SATA controller: JMicron Technology Corp. JMB360 AHCI Controller (rev 02)

if need any more info , I'll happy to provide
Thanks

Comment 6 Ray chen 2012-08-08 08:52:35 UTC

After testing nvidia driver,
I found a workaround,
add nomodeset as kernel option 
or set NO_KMS_IN_INITRD="yes" in /etc/sysconfig/kernel
then I can boot into kde

Comment 7 Stanley Miller 2012-08-08 13:39:08 UTC

I'm using the latest x64 RC2 here, standard desktop kernel and the default nv/nouveau nvidia driver.

Comment 8 Alin M Elena 2012-08-09 10:23:17 UTC

some findings... on my machine NO_KMS is already set
[alin@abbaton:~]: grep NO_KMS /etc/sysconfig/kernel 
NO_KMS_IN_INITRD="yes"

nomodeset at boot time fixes the corrupted screen but brings other issues.
I use my laptop in a dual display setup... and with nomodeset the external display is not detected anymore...

[alin@abbaton:~]: dmesg | grep nouveau
[   13.962400] nouveau 0000:04:00.0: enabling device (0006 -> 0007)
[   13.962989] nouveau 0000:04:00.0: setting latency timer to 64
[   13.963041] [drm] nouveau 0000:04:00.0: Detected an NV50 generation card (0x0af000a2)
[   13.964290] fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing generic driver
[   13.969241] [drm] nouveau 0000:04:00.0: Checking PRAMIN for VBIOS
[   14.026539] [drm] nouveau 0000:04:00.0: ... appears to be valid
[   14.026541] [drm] nouveau 0000:04:00.0: Using VBIOS from PRAMIN
[   14.026544] [drm] nouveau 0000:04:00.0: BIT BIOS found
[   14.026546] [drm] nouveau 0000:04:00.0: Bios version 70.89.02.00
[   14.026549] [drm] nouveau 0000:04:00.0: TMDS table version 2.0
[   14.026758] [drm] nouveau 0000:04:00.0: MXM: no VBIOS data, nothing to do
[   14.026760] [drm] nouveau 0000:04:00.0: DCB version 4.0
[   14.026762] [drm] nouveau 0000:04:00.0: DCB outp 00: 01800113 00010030
[   14.026763] [drm] nouveau 0000:04:00.0: DCB outp 01: 020112a6 0f220010
[   14.026765] [drm] nouveau 0000:04:00.0: DCB outp 02: 02011262 00020010
[   14.026766] [drm] nouveau 0000:04:00.0: DCB conn 00: 00000040
[   14.026768] [drm] nouveau 0000:04:00.0: DCB conn 01: 00101146
[   14.026773] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 0 at offset 0x694E
[   14.149863] [drm] nouveau 0000:04:00.0: 0x6BCC: Condition still not met after 20ms, skipping following opcodes
[   14.149885] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 1 at offset 0x6D81
[   14.149887] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 2 at offset 0x6D83
[   14.149894] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 3 at offset 0x6DB8
[   14.149905] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 4 at offset 0x6EB0
[   14.149906] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x6F15
[   14.169910] [drm] nouveau 0000:04:00.0: 0x6F15: Condition still not met after 20ms, skipping following opcodes
[   14.339081] [drm] nouveau 0000:04:00.0: Detected 256MiB VRAM (DDR1)
[   14.339083] [drm] nouveau 0000:04:00.0: Stolen system memory at: 0x00af000000
[   14.340570] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
[   14.425478] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00202106c0 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.425518] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00203e8890 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.425564] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00204068a0 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.425610] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00204208c0 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.425657] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x002043e8c0 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.425702] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00203e4800 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.425743] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00203ea864 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.427850] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00202146c0 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.427897] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x002021e740 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.427944] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x002022a700 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.427989] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x0020236700 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428037] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x0020242740 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428086] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x0020250700 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428136] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00202407ac on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428182] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x0020262700 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428227] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x0020270780 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428271] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x0020280700 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428318] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x002028e700 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428361] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00202a0700 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   14.428406] [drm] nouveau 0000:04:00.0: VM: trapped write at 0x00202ae700 on ch 0 [0x00000050] BAR/PFIFO_WRITE/FB reason: PT_NOT_PRESENT
[   15.757880] [drm] nouveau 0000:04:00.0: 4 available performance level(s)
[   15.757886] [drm] nouveau 0000:04:00.0: 0: core 405MHz shader 405MHz memory 405MHz voltage 900mV
[   15.757889] [drm] nouveau 0000:04:00.0: 1: core 450MHz shader 810MHz memory 450MHz voltage 900mV
[   15.757891] [drm] nouveau 0000:04:00.0: 2: core 450MHz shader 810MHz memory 450MHz voltage 900mV
[   15.757894] [drm] nouveau 0000:04:00.0: 3: core 450MHz shader 950MHz memory 450MHz voltage 900mV
[   15.757896] [drm] nouveau 0000:04:00.0: c: core 405MHz shader 810MHz
[   15.770030] [drm] nouveau 0000:04:00.0: MM: using COPY for buffer copies
[   15.863730] [drm] nouveau 0000:04:00.0: allocated 1920x1080 fb: 0x2a0000, bo ffff88013608f800
[   15.863821] fbcon: nouveaufb (fb0) is primary device
[   15.863877] fb0: nouveaufb frame buffer device
[   15.863884] [drm] Initialized nouveau 1.0.0 20120316 for 0000:04:00.0 on minor 0
[   38.908301] nouveau_ratelimit: 717 callbacks suppressed
[   38.908306] [drm] nouveau 0000:04:00.0: PGRAPH - DATA_ERROR INVALID_VALUE
[   38.908309] [drm] nouveau 0000:04:00.0: PGRAPH - DATA_ERROR
[   38.908312] [drm] nouveau 0000:04:00.0: PGRAPH - ch 2 (0x0000bf9000) subc 7 class 0x8697 mthd 0x16b0 data 0x00000000

[alin@abbaton:~]: uname -a 
Linux abbaton.ucd.ie 3.5.0-1-desktop #1 SMP PREEMPT Mon Jul 30 21:41:12 UTC 2012 (6d995bc) x86_64 x86_64 x86_64 GNU/Linux

[alin@abbaton:~]: zypper se -is nouveau 
Loading repository data...
Reading installed packages...

S | Name                          | Type    | Version                     | Arch   | Repository          
--+-------------------------------+---------+-----------------------------+--------+---------------------
i | libXvMC_nouveau               | package | 8.0.4-22.2                  | x86_64 | openSUSE-Factory-Oss
i | libdrm_nouveau1               | package | 2.4.33-6.3                  | x86_64 | openSUSE-Factory-Oss
i | libvdpau_nouveau              | package | 8.0.4-22.2                  | x86_64 | openSUSE-Factory-Oss
i | xorg-x11-driver-video-nouveau | package | 0.0.16_20120321_ab7291d-5.3 | x86_64 | openSUSE-Factory-Oss
[alin@abbaton:~]: zypper se -is grub2
Loading repository data...
Reading installed packages...

S | Name                    | Type    | Version    | Arch   | Repository                                              
--+-------------------------+---------+------------+--------+---------------------------------------------------------
i | grub2                   | package | 2.00-6.1   | x86_64 | openSUSE-Factory-Oss                                    
i | grub2-branding-openSUSE | package | 12.2-133.1 | noarch | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | grub2-efi               | package | 2.00-6.1   | x86_64 | openSUSE-Factory-Oss                                    
[alin@abbaton:~]: zypper se -is plymouth
Loading repository data...
Reading installed packages...

S | Name                          | Type    | Version     | Arch   | Repository                                              
--+-------------------------------+---------+-------------+--------+---------------------------------------------------------
i | plymouth                      | package | 0.8.6.1-3.1 | x86_64 | openSUSE-Factory-Oss                                    
i | plymouth-branding-openSUSE    | package | 12.2-133.1  | noarch | home:rwooninck:UNSTABLE_KDE4 (KDE_Qt48_openSUSE_Factory)
i | plymouth-plugin-fade-throbber | package | 0.8.6.1-3.1 | x86_64 | openSUSE-Factory-Oss                                    
i | plymouth-plugin-label         | package | 0.8.6.1-3.1 | x86_64 | openSUSE-Factory-Oss                                    
i | plymouth-plugin-script        | package | 0.8.6.1-3.1 | x86_64 | openSUSE-Factory-Oss                                    
i | plymouth-plugin-space-flares  | package | 0.8.6.1-3.1 | x86_64 | openSUSE-Factory-Oss                                    
i | plymouth-plugin-throbgress    | package | 0.8.6.1-3.1 | x86_64 | openSUSE-Factory-Oss                                    
i | plymouth-plugin-two-step      | package | 0.8.6.1-3.1 | x86_64 | openSUSE-Factory-Oss                                    
i | plymouth-scripts              | package | 0.8.6.1-3.1 | noarch | openSUSE-Factory-Oss                                    
i | plymouth-theme-script         | package | 0.8.6.1-3.1 | noarch | openSUSE-Factory-Oss                                    
i | plymouth-utils                | package | 0.8.6.1-3.1 | x86_64 | openSUSE-Factory-Oss 

Alin

Comment 9 Alin M Elena 2012-08-09 15:30:41 UTC

As Raymond suggested...

1. hitting esc when screen corrupted lets me with a clean console... hitting esc again I get a corrupted screen.

I also added the plymouth debug log

Alin

Comment 10 Alin M Elena 2012-08-09 15:33:46 UTC

Created attachment 501823 [details]
plymouth.debug log

Comment 11 Roman Bysh 2012-08-11 16:03:13 UTC

I have no problems after installing nVidia driver.

Comment 12 Franck Bourdonnec 2012-08-13 10:19:27 UTC

same bug here : 775489, 771392

remove "splah=silent" from grub

Franck

Comment 13 Alin M Elena 2012-08-13 10:54:44 UTC

let us summarize few things... 
*the bug is about screen corruption, garbage on the plymouth screen...
*it happens only with the nouveau driver... and we are interested actually only in that here...
*removing splash=silent does not solve the problem.. just minimises it...
without it... you get a text console booting mode... the screeen gets corrupted at some moment, though on a small area of the screeen, and self clears itself few moments later, giving the impression of a clean boot...

what we want is not a workaround... we want to be able to boot with plymouth, nouveau and grub2 without corruption of the screen.

Alin

Comment 14 Stanley Miller 2012-08-15 01:34:25 UTC

Look at this another way: A new user downloads OpenSuse and tries to install it. Their screen goes to confetti mode. They give up, download Ubuntu or whatever and they are lost to our community.

I'd rather see the release late than this go unfixed. I agree with the MAJOR classification above but the MEDIUM priority is worrisome.

Comment 15 Alin M Elena 2012-08-30 20:13:47 UTC

just to clear this...

I have installed a clean 12.2RC2 on a machine with nvidia... and plymouth was fine.. then the login screen was full of rubbish...put the password and gnome had the screen full of rubish too..

I have checked and I had NO_KMS_... set to no... I have set it to yes... 
mkinitrd 
and reboot

this times I got garbage on the plymouth screen at some moment...  but the login screen was fine... and gnome screen was fine too..

Alin

Comment 16 Criss Peress 2012-09-05 16:58:57 UTC

I have the same problem on the stable release. Just installed from kde live cd and once installed updated trough zypper. After that I can't get to kdm to work fine but I get a lot of artifacts on the screen.

Comment 17 Alin M Elena 2012-09-05 17:03:10 UTC

can you see to what is set this variable NO_KMS_IN_INITRD in 
/etc/sysconfig/kernel

Alin

Comment 18 Criss Peress 2012-09-05 17:33:57 UTC

It's set to "no" which I think is the default one  as I've done nothing in /etc/sysconfig

Comment 19 Alin M Elena 2012-09-05 17:39:23 UTC

the solution is to set it you "yes" and then
mkinitrd
reboot and things shall be better.

Alin

Comment 20 Criss Peress 2012-09-05 18:19:40 UTC

Disabling kms for me is not a solution but some sort of workaround.
I mean with that option set Plymouth works and so do kdm, but plymouth is just ugly as it uses a completely wrong resolution.
I hope a bugfix will be released soon as it's an annoyng bug, for the moment I prefer to remove the splash option from the kernel line.

Comment 21 Alin M Elena 2012-09-05 18:23:17 UTC

not a solution of course... a workaround... 
I got right resolution on a system with using efi...  so if you can use efi... you may be a little bit better...


Alin

Comment 22 Roman Bysh 2013-11-17 17:50:04 UTC

Fixed in the final release