Seemingly log entries from hardware issues

I say seemingly because I am not actually sure if this is a kernel bug or something else.

In any case my specs are:

  • Asus X99E WS motherboard (the best motherboard I have ever had - it’s awesome!)
  • OpenSuSE 13.2
  • 32 GB of DDR4 RAM
  • SSD drive in RAID 1 for OS
  • 3 x 4TB HDDs in RAID5 for rest (several RAID 5’s)
  • (All RAIDs are Linux RAIDs, not hardware)
  • Eye Infinity 6 display card.
  • ~Not~ setup as a VM
  • ~No~ proprietary driver for the video card

I’ve been getting these errors for a few months. At first I thought to just ignore it because the motherboard was quite new but I thought such errors would have been addressed by now so I thought I would ask the community if you have any ideas on what’s happening and a solution. These errors are constant by the way. If I do “journalctl -f” there will be a screen full of these in less than 10 secs.

Any help appreciated.

The errors:

– Logs begin at Wed 2015-05-20 08:49:46 MST. –
Jul 20 12:24:57 quark kernel: radeon 0000:06:00.0: ffff880805332400 pin failed
Jul 20 12:24:57 quark kernel: [drm:radeon_crtc_page_flip] ERROR failed to pin new rbo buffer before flip
Jul 20 12:25:00 quark kernel: radeon 0000:06:00.0: ffff880805332400 pin failed
Jul 20 12:25:00 quark kernel: [drm:radeon_crtc_page_flip] ERROR failed to pin new rbo buffer before flip
Jul 20 12:25:04 quark sudo[13124]: reg : TTY=pts/6 ; PWD=/home/reg ; USER=root ; COMMAND=/bin/bash
Jul 20 12:25:04 quark sudo[13124]: pam_unix(sudo:session): session opened for user root by reg(uid=0)
Jul 20 12:25:05 quark kernel: pcieport 0000:00:03.0: AER: Corrected error received: id=0018
Jul 20 12:25:05 quark kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
Jul 20 12:25:05 quark kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00000001/00002000
Jul 20 12:25:05 quark kernel: pcieport 0000:00:03.0: 0] Receiver Error (First)
Jul 20 12:25:15 quark kernel: pcieport 0000:00:03.0: AER: Corrected error received: id=0018
Jul 20 12:25:15 quark kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
Jul 20 12:25:15 quark kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00000001/00002000
Jul 20 12:25:15 quark kernel: pcieport 0000:00:03.0: 0] Receiver Error (First)
Jul 20 12:25:19 quark kernel: radeon 0000:06:00.0: ffff880805332400 pin failed
Jul 20 12:25:19 quark kernel: [drm:radeon_crtc_page_flip] ERROR failed to pin new rbo buffer before flip
Jul 20 12:25:20 quark kernel: pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
Jul 20 12:25:20 quark kernel: pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
Jul 20 12:25:20 quark kernel: pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00000001/00002000
Jul 20 12:25:20 quark kernel: pcieport 0000:00:03.0: 0] Receiver Error (First)

Googling for

ERROR failed to pin new rbo buffer before flip

First hit is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703370;att=0;msg=31 from 2013, so perhaps too old, but then, you asked for any help…

Solution could be increase UMA buffer https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=703370;filename=130319193059.BMP;msg=31

Or UEFI/BIOS update?

That setting doesn’t exist in this BIOS. I looked everywhere but it is a very new BIOS. I did however see that since last time I updated it there were BIOS updates so I applied them, no difference unfortunately. :frowning:

I think I’ll try Asus support but I don’t hold out much hope there.

Did you try the proprietary driver that is a fairly hot card and may require it.

Guys, sorry I didn’t get back sooner but I guess someone fixed something recently in an update as it finally went away.

Oops. It looks like it is still there. I am not sure for sure but think when what happens that I asked about on this thread weird display problem then this error goes away. It’s only a hypothesis at this point but I think a sound one.

No I hadn’t tried the proprietary drivers yet. I am trying to avoid them because last time I did (many years ago when they were the only ones that worked) and then asked for help I got the reply “we don’t support when…” you get the idea. Obviously I will when all else fails but as a programmer I used to diagnosing until I actually know what’s going on so I’m trying to get a real answer. The problem is I work on technologies that are far removed from this stuff (PHP these days) so my background as programmer doesn’t help all that much.

I just saw that I have the previous kernel I can boot from as well and saw someone fixed this by adding radeon.dpm=1 to the kernel boot up so I’m going to try both of those options and see what happens.

Adding radeon.dpm=1 seems to have solved those error messages, finally.

My weird display problem (in the previous thread) is still there unfortunately.