Bug 1251802
Summary: | .xsession-errors shows the message "nouveau: kernel reject pushbuf", desktop is unresponsive | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paulo Fessel <pfessel> |
Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | airlied, ajax, bskeggs, hardy.heroin, mwc, omarth, pall.valmundsson, rockowitz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-19 19:16:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paulo Fessel
2015-08-10 02:22:01 UTC
When issuing systemctl restart kdm.service, I got the following on /var/log/messages: [100642.184685] nouveau E[kwin_x11[2588]] failed to idle channel 0xcccc0000 [kwin_x11[2588]] [100642.184863] nouveau E[ PFIFO][0000:02:00.0] read fault at 0x0000013000 [PAGE_NOT_PRESENT] from PFIFO/BAR_READ on channel 0x003f9ca000 [unknown] [100657.198323] nouveau E[abrt-applet[2640]] failed to idle channel 0xcccc0000 [abrt-applet[2640]] [100672.189980] nouveau E[abrt-applet[2640]] failed to idle channel 0xcccc0000 [abrt-applet[2640]] Screen is still frozen, only cure will be a reboot it seems. I just wanted to add that I recognize the symptoms, even though I am currently running openSUSE. I ran into the same problem running Fedora 23, thought it had to do something specific with Fedora and switched to openSUSE LEAP 42.1 but I still have the same issue (random lockups of Plasma 5 while still being able to SSH into the system). When it happens I see error messages like this: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: GPPTR SIGNATURE nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 14 [kdesu[6410]] subc 0 mthd 0x0000 data 0x00000000 nouveau E[ PFIFO][0000:01:00.0] PBDMA0: SIGNATURE nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 14 [kdesu[6410]] subc 0 mthd 0x0000 data 0x00000000 nouveau E[ PFIFO][0000:01:00.0] PBDMA0: SIGNATURE nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 14 [kdesu[6410]] subc 0 mthd 0x0000 data 0x00000000 nouveau E[ PFIFO][0000:01:00.0] read fault at 0x0000000000 [PDE] from PBDMA0/HOST on channel 0x007ed4c000 [unknown] nouveau E[y2base[6398]] failed to idle channel 0xcccc0000 [y2base[6398]] nouveau E[y2base[6398]] failed to idle channel 0xcccc0000 [y2base[6398]] nouveau E[ X[1163]] failed to idle channel 0xcccc0002 [X[1163]] nouveau E[ X[1163]] failed to idle channel 0xcccc0002 [X[1163]] And if I leave the system up for some days my logs fill up with nothing but repeating lines like this: kernel: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ACQUIRE kernel: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 2 [X[2425]] subc 0 mthd 0x001c data 0x00001004 kernel: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ACQUIRE kernel: nouveau E[ PFIFO][0000:01:00.0] PBDMA0: ch 8 [plasmashell[2633]] subc 0 mthd 0x001c data 0x00001004 Just wanted to let you know that you are not alone in this Paulo. I gave up on Fedora altogether, since KDE was never their graphical desktop of choice and things on FC22 got really messed up. It's been two months I'm running openSUSE Leap 42.1, and at least on my computer, these problems have vanished as long you run the latest and greatest Plasma 5.5, which is a default update for Leap since last December if I'm not mistaken. I also turned the switch on my wife's notebook this weekend, since her Fedora was already EOL'ed in that environment (fc20). No regrets at all, I feel the road is much less bumpy since then. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. |