779447 – On first boot no usabel graphical display; in syslog PFIFO_CACHE_ERROR from nouveau

Bug 779447 - On first boot no usabel graphical display; in syslog PFIFO_CACHE_ERROR from nouveau

Summary: On first boot no usabel graphical display; in syslog PFIFO_CACHE_ERROR from n...

Status:	RESOLVED DUPLICATE of bug 771392

Alias:	None

Product:	openSUSE 12.2
Classification:	openSUSE
Component:	Other (show other bugs)
Version:	Final
Hardware:	x86-64 openSUSE 12.2

Priority:	P5 - None Severity: Critical (vote)
Target Milestone:	---
Assignee:	Forgotten User Wum0mkMcd8
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2012-09-09 18:52 UTC by Jogchum Reitsma
Modified:	2012-09-14 22:34 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Output of dmesg (993.60 KB, text/plain) 2012-09-14 10:59 UTC, Jogchum Reitsma	Details
Output of dmesg after setting log_buf_len=2M (482.11 KB, text/plain) 2012-09-14 13:33 UTC, Jogchum Reitsma	Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

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

Description Jogchum Reitsma 2012-09-09 18:52:16 UTC

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

I upgraded my wife's system from 12.1 to 12.2 final. On boot after a while a totally messed up graphical screen appears. After loggin in on a tty-console and doing a shutdown -r now, the system mostly - but not always - comes up correctly.

the systems messages are flooded with messages like
Sep  8 09:14:00 linux-xao5 kernel: [  185.087003] [drm] nouveau 0000:01:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x02ac Data 0x00000003 


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Forgotten User Q_jroExIGN 2012-09-13 22:27:01 UTC

Please add "log_buf_len=1M" to boot parameters,
press Crtl-Alt-Backspace-Backspace immediately when the garbled screen occurs (the log buffer is very fast full),
then you should be able to login and please add full output of "dmesg" here.

I want to collect as much information as possible to file a bug report upstream.

Comment 2 Jogchum Reitsma 2012-09-14 10:59:01 UTC

Created attachment 505815 [details]
Output of dmesg

Output of dmesg after setting boot parameter log_buf_len=1M, hitting Ctrl-Alt-Backspace Backspace at garbled screen, and logging in.

Comment 3 Forgotten User Q_jroExIGN 2012-09-14 12:03:19 UTC

Thanks. But you were to slow with Crtl-Alt-Backspace-Backspace.
I need a log file similiar to this (up to line 880 or so): http://pastebin.com/RYGxj2XT

The log files I saw the switch from plymouth to X happens at ~ 25 to 40 seconds.

Comment 4 Jogchum Reitsma 2012-09-14 12:41:38 UTC

I'm not sure I can do it faster - it took less than half a second. But I'll give it a try.

I take it the 1M in the bootparam is the amount of memory the buffer uses - would it help to increase that?

Comment 5 Jogchum Reitsma 2012-09-14 13:33:43 UTC

Created attachment 505844 [details]
Output of dmesg after setting log_buf_len=2M

After several tries, I decided to increase log_buf_len to 2M, and now I have a better result I think.

Comment 6 Forgotten User Q_jroExIGN 2012-09-14 22:34:49 UTC

Thanks.

Duplicate of bug 771392.

*** This bug has been marked as a duplicate of bug 771392 ***