Announcement

Collapse
No announcement yet.

Consistent but random fatal crashes requiring a hard reset

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    [KDE] Consistent but random fatal crashes requiring a hard reset

    Hello!

    My Kubuntu18.04.1 machine fatally crashes at random times.

    Computer stays on (can hear the fan running), display/screen black and doesn't 'wake' after keyboard press, keyboard locks up (caps lock light not toggling), mouse non-responsive, power button does nothing.

    This happens at random intervals during gaming, internet browser use, no use at all (even when just sitting at the login screen). At first I thought it was the CPU/GPUs over-heating, so I began monitoring them, but it happens when they're both hot and 'cold'.

    Possibly my GPUs/CPU/thunderbolt display aren't fully-supported, and randomly crash when doing specific registering jobs, etc. I can recreate the behaviour/symptoms by suspending the system to RAM. It refuses to wake, and the same display/keyboard/mouse symptoms show. Syslog shows different issues, depending on if the bug/crash happens during a RAM suspension, or during a random crash. If I suspend to RAM, it doesn't show errors (simply says "starting suspend to ram..." etc. If it's a crash, syslog has some error output (attached below).

    See attached what syslog spits out just before the random crash, and when I boot kubuntu back up. Note, hot-plugging an HDMI display during this version of the crash/bug doesn't give me any display/control: randomcrashSyslog[Jan25].txt
    Here's a short version from a random crash at a different time (same type) which I believe holds the key errors: randomcrashSHORTSyslog[Jan26].txt

    See attached the syslog when the system is manually suspended to RAM:

    See attached a syslog when I left the system at the login screen for an hour or so. Screen did go black, and I could not wake it, however the keyboard seemed responsive (caps lock light toggles, etc.). This - to me - seems good evidence that it's either the thunderbolt bus which my display is attached to is not "waking up" right, or the graphics drivers are unable to process the display wake-up process, or both! Logged in successfully with a black screen and used init 6 to reboot: loginscreenblackdisplaySyslog[Jan26].txt

    Update: Swapped my thunderbolt display for an HDMI one. Suspend to RAM and the wake-up process works! SO 18.04 doesn't like thunderbolt displays. I'm going to try and reproduce the random crash on the HDMI-display. Just have to leave it on for a while and wait.

    Update update: Continues to crash randomly with HDMI display. Here's the syslog: randomcrashHDMIsyslog[Jan26].txt

    Same symptoms, different syslog output. The first 'random crash' syslog is most likely the most telling/is of most importance. Nothing seems harmful in syslog just before suspending to RAM.

    The system stops logging due to the suspension, but seems to keep logging once the screen goes black on a random crash, so that probably means it's some kind of driver failure instead of a kernel panic or something? I think the suspension not waking and the random crash are two separate, but very similar issues. I have a feeling there's just little support for my RAM/GPU/CPU/Motherboard. I've also attached my system profile. If you need more info, let me know.

    Anyways, hopefully someone will have some insight into this, or will be able to point me in the direction of where to make this known to some developers!

    Brief Profile

    Mac Pro Late 2013 - https://support.apple.com/kb/SP697?locale=en_US
    Weird, I know, but I've also got macOS and Windows installed for a triple-boot setup. Super fun, and testing its capabilities!
    Processor - Intel Xeon E5 with 25MB L3 cache and Turbo Boost up to 3.9GHz - 3.0GHz 8-Core
    Memory - DDR3 ECC memory 3.0GHz 8-Core 64GB (four 16GB)
    Graphics - Dual AMD FirePro D300 graphics processors with 2GB of GDDR5 VRAM each - 3.7GHz Quad-Core

    System Profile according to command "inxi -Fxz" and "System Profiler and Benchmark" on KDE Discover:

    profile[Jan25].txt

    Syslog events during random bug/crash with thunderbolt display. Glaring errors here. I think I even cut off it's logging after a couple of minutes of it being black by hard resetting. Next time I'll let it run longer:

    randomcrashSyslog[Jan25].txt

    The same type of crash, at a different time. Shortened syslog which I believe holds the errors which could help solve the issue:

    randomcrashSHORTSyslog[Jan26].txt

    The same type of crash, but with only an HDMI display connected.

    randomcrashHDMIsyslog[Jan26].txt

    Syslog events when screen goes black at login window after a while with thunderbolt display connected. Keyboard was responsive but the display didn't wake. Logged in with black screen and issued init 6 to reboot.

    loginscreenblackdisplaySyslog[Jan26].txt
    Last edited by ymgenesis; Jan 26, 2019, 04:28 PM. Reason: HDMI suspend to RAM and wake works! Thunderbolt display is the issue? Added a shorter syslog with the key errors.
    Tags: crash, drivers, kubuntu, plasma, thunderbolt
    • Top
    • Bottom
    #2
    Can't see either one of your .txt files. Did you upload them to KFN?
    The next brick house on the left
    Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic
    ​
    ​
    ​
    ​
    • Top
    • Bottom

    Comment

      #3
      Both are there at the bottom of his post. I can click on them and view them. You can't?
      Windows no longer obstructs my view.
      Using Kubuntu Linux since March 23, 2007.
      "It is a capital mistake to theorize before one has data." - Sherlock Holmes​
      • Top
      • Bottom

      Comment

        #4
        Updated the post with a new random crash syslog file. Before it was just the syslog when I suspended it to RAM. The crash syslog file has some glaring radeon, pce, etc. errors.
        • Top
        • Bottom

        Comment

          #5
          Originally posted by Snowhog View Post
          Both are there at the bottom of his post. I can click on them and view them. You can't?
          No, but that may be due to the computer I'm on right now. It tries to find and open a text (.txt) file on disk. I can open the support.apple.com link with no problem. I'll try it at home later.
          The next brick house on the left
          Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic
          ​
          ​
          ​
          ​
          • Top
          • Bottom

          Comment

            #6
            I can get to the linked files now - by playing, neither here nor there.

            The last entries listed are consistently network related.

            Would the OP enter this into a konsole:
            Code:
            inxi -Fxz
            and post the results in a CODE box.
            The next brick house on the left
            Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic
            ​
            ​
            ​
            ​
            • Top
            • Bottom

            Comment

              #7
              In the text file randomcrashSHORTSyslog[Jan26].txt there seems to be lots of errors relating to the GPUs (radeon and amdgpu drivers). Not sure if a network issue could cause a crash that cripples the system entirely? My network seems to be running fine on the surface. I've had issues before with open graphics drivers and these stupid proprietary GPUs AMD and Apple put out for this MacPro 2013.

              Are you referring to these errors?

              Code:
              kubuntu18 kernel: [16986.833189] [UFW BLOCK] IN=enp11s0 OUT= MAC=xxxxx SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
              Seems UFW is just blocking a multicast address (224.0.0.1). Not sure if that is an issue... or if it's even what you're referring to.

              Unless this pcieport error during the random crashes mentioning a broadcast error has anything to do with that?

              Code:
              Jan 26 13:28:39 kubuntu18 kernel: [ 1830.789369] pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: id=0018
Jan 26 13:28:39 kubuntu18 kernel: [ 1830.789377] pcieport 0000:00:03.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0018(Requester ID)
Jan 26 13:28:39 kubuntu18 kernel: [ 1830.789382] pcieport 0000:00:03.0:   device [8086:0e08] error status/mask=00004000/00000000
Jan 26 13:28:39 kubuntu18 kernel: [ 1830.789385] pcieport 0000:00:03.0:    [14] Completion Timeout     (First)
Jan 26 13:28:39 kubuntu18 kernel: [ 1830.789390] pcieport 0000:00:03.0: broadcast error_detected message
Jan 26 13:28:39 kubuntu18 kernel: [ 1830.806855] pcieport 0000:00:03.0: AER: Device recovery failed
              Then again, I'm not the expert!

              Installed inxi. Really cool tool! Output of inxi -Fxz:

              Code:
              System:    Host: kubuntu18 Kernel: 4.15.0-43-generic x86_64 bits: 64 gcc: 7.3.0
Desktop: KDE Plasma 5.12.7 (Qt 5.9.5) Distro: Ubuntu 18.04.1 LTS
Machine:   Device: unknown System: Apple product: MacPro6 1 v: 1.0 serial: N/A
Mobo: Apple model: Mac-F60DEB81FF30ACF6 v: MacPro6 1 serial: N/A
UEFI: Apple v: 127.0.0.0.0 date: 09/17/2018
CPU:       Quad core Intel Xeon E5-1620 v2 (-MT-MCP-) arch: Ivy Bridge rev.4 cache: 10240 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 29602
clock speeds: max: 3900 MHz 1: 1724 MHz 2: 1534 MHz 3: 1823 MHz 4: 1857 MHz 5: 1927 MHz 6: 1654 MHz
7: 1725 MHz 8: 1726 MHz
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X]
bus-ID: 02:00.0
Card-2: Advanced Micro Devices [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X]
bus-ID: 06:00.0
Display Server: x11 (X.Org 1.19.6 ) drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
Resolution: 2560x1440@59.95hz
OpenGL: renderer: AMD PITCAIRN (DRM 2.50.0 / 4.15.0-43-generic, LLVM 6.0.0)
version: 4.5 Mesa 18.0.5 Direct Render: Yes
Audio:     Card-1 Intel C600/X79 series High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
Card-2 2x Advanced Micro Devices [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
driver: snd_hda_intelsnd_hda_intel bus-ID: 06:00.1
Card-3 Apple Thunderbolt Display Audio driver: USB Audio usb-ID: 002-005
Card-4 Focusrite-Novation Scarlett 18i8 driver: USB Audio usb-ID: 005-002
Sound: Advanced Linux Sound Architecture v: k4.15.0-43-generic
Network:   Card-1: Broadcom Limited NetXtreme BCM57762 Gigabit Ethernet PCIe driver: tg3 v: 3.137 bus-ID: 0b:00.0
IF: enp11s0 state: up speed: 100 Mbps duplex: half mac: <filter>
Card-2: Broadcom Limited NetXtreme BCM57762 Gigabit Ethernet PCIe driver: tg3 v: 3.137 bus-ID: 0c:00.0
IF: enp12s0 state: down mac: <filter>
Card-3: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter driver: wl bus-ID: 0d:00.0
IF: wlp13s0 state: down mac: <filter>
Card-4: Broadcom Limited NetXtreme BCM57761 Gigabit Ethernet PCIe driver: tg3 v: 3.137 bus-ID: 63:00.0
IF: enp99s0 state: down mac: <filter>
Drives:    HDD Total Size: 1000.6GB (3.5% used)
ID-1: /dev/sda model: APPLE_SSD_SM1024 size: 1000.6GB temp: 50C
Partition: ID-1: / size: 47G used: 33G (75%) fs: ext4 dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 52.0C mobo: N/A gpu: 48.0,46.0
Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 228 Uptime: 7 min Memory: 1872.3/64392.7MB Init: systemd runlevel: 5 Gcc sys: 7.3.0
Client: Shell (bash 4.4.191) inxi: 2.3.56
              Also I posted an update in the main post. My keyboard/mouse were plugged in to the USB slots on the back of my thunderbolt display. I swapped the display for an HDMI display, plugged the keyboard/mouse in to the tower, and the suspend to RAM worked! Maybe the issue is thunderbolt-related? Not re-initializing the thunderbolt display/ports properly? I can tell you that hot-plugging the thunderbolt display doesn't work. Some white noise comes from it to suggest audio might work, but no display pops up. Not sure how this would affect the random crash, though, so this might only solves the 'suspend to RAM' issue. Going to leave it on this display for a while to see if the 'random crash' happens, and will post a syslog if it does.

              Also, according to inxi -Fxz, one of my audio cards is bus-ID: 06:00.1. This error is in the crash syslog:

              Code:
              Jan 26 13:28:39 kubuntu18 kernel: [ 1830.976277] pci 0000:06:00.1: device has no driver
              Maybe the motherboard itself is panicking, causing everything to crash. Who knows... there seems to be so many errors popping up in the syslog text I mentioned at the top of my comment. Can't tell which one is the culprit.
              Last edited by ymgenesis; Jan 26, 2019, 01:17 PM.
              • Top
              • Bottom

              Comment

                #8
                You seem to have a fairly complex hardware setup with multiple cards. But you also have 64GB or RAM that doesn't seem to be stressed, so suspend to RAM should not be a problem.

                You might try by removing some cards - one at a time - to see if there may be a culprit. Start with the "driverless" audio card. It shouldn't matter, but there could be MB issues, as you noted.

                Also, could try another CLI entry:
                Code:
                lsblk
                and post the results again in a CODE BOX.
                The next brick house on the left
                Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic
                ​
                ​
                ​
                ​
                • Top
                • Bottom

                Comment

                  #9
                  Hello,

                  Unfortunately due to the nature of the Mac Pro 2013's setup, I can't actually take out any cards form the tower. Ridiculous, I know.

                  The thunderbolt display I was using seemed to be the issue for the suspend to RAM. The feature works when I use an HDMI display, which is good.

                  However, the random crashes still happen with the HDMI connected. This leads me to believe that I guess my CPU or GPU isn't fully supported in Ubuntu 18.04. I might try submitting a bug to ubuntu. Here's what syslog spits out when the crash happens:

                  Code:
                  Jan 26 16:41:37 kubuntu18 kernel: [10812.430479] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Non-Fatal) error received: id=0018
Jan 26 16:41:37 kubuntu18 kernel: [10812.445121] pciehp 0000:00:03.0:pcie004: Slot(5-3): Link Down
Jan 26 16:41:37 kubuntu18 kernel: [10812.445149] pcieport 0000:00:03.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0018(Requester ID)
Jan 26 16:41:37 kubuntu18 kernel: [10812.445152] pcieport 0000:00:03.0:   device [8086:0e08] error status/mask=00004020/00000000
Jan 26 16:41:37 kubuntu18 kernel: [10812.445154] pcieport 0000:00:03.0:    [ 5] Surprise Down Error   
Jan 26 16:41:37 kubuntu18 kernel: [10812.445156] pcieport 0000:00:03.0:    [14] Completion Timeout     (First)
Jan 26 16:41:37 kubuntu18 kernel: [10812.445159] pcieport 0000:00:03.0: broadcast error_detected message
Jan 26 16:41:37 kubuntu18 acpid: input device has been disconnected, fd 14
Jan 26 16:41:37 kubuntu18 kernel: [10812.455347] pciehp 0000:00:03.0:pcie004: Slot(5-3): Link Up
Jan 26 16:41:37 kubuntu18 acpid: input device has been disconnected, fd 13
Jan 26 16:41:37 kubuntu18 acpid: input device has been disconnected, fd 10
Jan 26 16:41:37 kubuntu18 acpid: input device has been disconnected, fd 9
Jan 26 16:41:37 kubuntu18 acpid: input device has been disconnected, fd 8
Jan 26 16:41:37 kubuntu18 acpid: input device has been disconnected, fd 7
Jan 26 16:41:37 kubuntu18 kernel: [10812.599012] pcieport 0000:00:03.0: AER: Device recovery failed
Jan 26 16:41:37 kubuntu18 kernel: [10812.599021] pcieport 0000:00:03.0: AER: Multiple Uncorrected (Fatal) error received: id=0018
Jan 26 16:41:37 kubuntu18 kernel: [10812.599034] pcieport 0000:00:03.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, id=0018(Requester ID)
Jan 26 16:41:37 kubuntu18 kernel: [10812.599044] pcieport 0000:00:03.0:   device [8086:0e08] error status/mask=00004020/00000000
Jan 26 16:41:37 kubuntu18 kernel: [10812.599053] pcieport 0000:00:03.0:    [ 5] Surprise Down Error   
Jan 26 16:41:37 kubuntu18 kernel: [10812.599062] pcieport 0000:00:03.0:    [14] Completion Timeout     (First)
Jan 26 16:41:37 kubuntu18 kernel: [10812.599067] pcieport 0000:00:03.0: broadcast error_detected message
Jan 26 16:41:47 kubuntu18 kernel: [10822.865130] radeon 0000:06:00.0: ring 3 stalled for more than 10240msec
Jan 26 16:41:47 kubuntu18 kernel: [10822.865134] radeon 0000:06:00.0: ring 0 stalled for more than 10420msec
Jan 26 16:41:47 kubuntu18 kernel: [10822.865140] radeon 0000:06:00.0: GPU lockup (current fence id 0x0000000000041435 last fence id 0x000000000004143a on ring 0)
Jan 26 16:41:47 kubuntu18 kernel: [10822.865147] radeon 0000:06:00.0: GPU lockup (current fence id 0x00000000000b034b last fence id 0x00000000000b0354 on ring 3)
Jan 26 16:41:47 kubuntu18 kernel: [10822.869394] Console: switching to colour dummy device 80x25
Jan 26 16:41:48 kubuntu18 kernel: [10823.314054] radeon 0000:06:00.0: Saved 308 dwords of commands on ring 0.
Jan 26 16:41:48 kubuntu18 kernel: [10823.314104] radeon 0000:06:00.0: GPU softreset: 0x0000004D
Jan 26 16:41:48 kubuntu18 kernel: [10823.314107] radeon 0000:06:00.0:   GRBM_STATUS               = 0xF5D01028
Jan 26 16:41:48 kubuntu18 kernel: [10823.314110] radeon 0000:06:00.0:   GRBM_STATUS_SE0           = 0x08000002
Jan 26 16:41:48 kubuntu18 kernel: [10823.314112] radeon 0000:06:00.0:   GRBM_STATUS_SE1           = 0xEC400002
Jan 26 16:41:48 kubuntu18 kernel: [10823.314115] radeon 0000:06:00.0:   SRBM_STATUS               = 0x200000C0
Jan 26 16:41:48 kubuntu18 kernel: [10823.314153] radeon 0000:06:00.0:   SRBM_STATUS2              = 0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.314156] radeon 0000:06:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.314158] radeon 0000:06:00.0:   R_008678_CP_STALLED_STAT2 = 0x40000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.314161] radeon 0000:06:00.0:   R_00867C_CP_BUSY_STAT     = 0x00408002
Jan 26 16:41:48 kubuntu18 kernel: [10823.314163] radeon 0000:06:00.0:   R_008680_CP_STAT          = 0x84228647
Jan 26 16:41:48 kubuntu18 kernel: [10823.314166] radeon 0000:06:00.0:   R_00D034_DMA_STATUS_REG   = 0x44483146
Jan 26 16:41:48 kubuntu18 kernel: [10823.314168] radeon 0000:06:00.0:   R_00D834_DMA_STATUS_REG   = 0x44C83D57
Jan 26 16:41:48 kubuntu18 kernel: [10823.314171] radeon 0000:06:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.314173] radeon 0000:06:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.754095] radeon 0000:06:00.0: GRBM_SOFT_RESET=0x0000DDFF
Jan 26 16:41:48 kubuntu18 kernel: [10823.754150] radeon 0000:06:00.0: SRBM_SOFT_RESET=0x00100100
Jan 26 16:41:48 kubuntu18 kernel: [10823.755300] radeon 0000:06:00.0:   GRBM_STATUS               = 0x00003028
Jan 26 16:41:48 kubuntu18 kernel: [10823.755302] radeon 0000:06:00.0:   GRBM_STATUS_SE0           = 0x00000006
Jan 26 16:41:48 kubuntu18 kernel: [10823.755305] radeon 0000:06:00.0:   GRBM_STATUS_SE1           = 0x00000006
Jan 26 16:41:48 kubuntu18 kernel: [10823.755308] radeon 0000:06:00.0:   SRBM_STATUS               = 0x200000C0
Jan 26 16:41:48 kubuntu18 kernel: [10823.755347] radeon 0000:06:00.0:   SRBM_STATUS2              = 0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.755350] radeon 0000:06:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.755352] radeon 0000:06:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.755355] radeon 0000:06:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.755358] radeon 0000:06:00.0:   R_008680_CP_STAT          = 0x00000000
Jan 26 16:41:48 kubuntu18 kernel: [10823.755361] radeon 0000:06:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
Jan 26 16:41:48 kubuntu18 kernel: [10823.755363] radeon 0000:06:00.0:   R_00D834_DMA_STATUS_REG   = 0x44C83D57
Jan 26 16:41:48 kubuntu18 kernel: [10823.755452] radeon 0000:06:00.0: GPU reset succeeded, trying to resume
Jan 26 16:41:48 kubuntu18 kernel: [10823.771983] [drm] probing gen 2 caps for device 8086:e08 = 37a7d03/e
Jan 26 16:41:48 kubuntu18 kernel: [10823.771986] [drm] PCIE gen 3 link speeds already enabled
Jan 26 16:41:48 kubuntu18 kernel: [10823.787769] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
Jan 26 16:41:48 kubuntu18 kernel: [10823.787917] radeon 0000:06:00.0: WB enabled
Jan 26 16:41:48 kubuntu18 kernel: [10823.787925] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x000000003a9fe4a8
Jan 26 16:41:48 kubuntu18 kernel: [10823.787930] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x00000000d8245dc8
Jan 26 16:41:48 kubuntu18 kernel: [10823.787935] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x000000004585da30
Jan 26 16:41:48 kubuntu18 kernel: [10823.787939] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x00000000f0a5aade
Jan 26 16:41:48 kubuntu18 kernel: [10823.787944] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x00000000edfc4d94
Jan 26 16:41:48 kubuntu18 kernel: [10823.788249] radeon 0000:06:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x00000000be9517c4
Jan 26 16:41:48 kubuntu18 kernel: [10823.798430] radeon 0000:06:00.0: failed VCE resume (-22).
Jan 26 16:41:48 kubuntu18 kernel: [10823.949784] [drm] ring test on 0 succeeded in 1 usecs
Jan 26 16:41:48 kubuntu18 kernel: [10823.949789] [drm] ring test on 1 succeeded in 1 usecs
Jan 26 16:41:48 kubuntu18 kernel: [10823.949793] [drm] ring test on 2 succeeded in 1 usecs
Jan 26 16:41:48 kubuntu18 kernel: [10823.949802] [drm] ring test on 3 succeeded in 3 usecs
Jan 26 16:41:48 kubuntu18 kernel: [10823.949809] [drm] ring test on 4 succeeded in 3 usecs
Jan 26 16:41:49 kubuntu18 kernel: [10824.125536] [drm] ring test on 5 succeeded in 1 usecs
Jan 26 16:41:49 kubuntu18 kernel: [10824.125541] [drm] UVD initialized successfully.
Jan 26 16:41:50 kubuntu18 kernel: [10825.137242] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
Jan 26 16:41:50 kubuntu18 kernel: [10825.137290] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-110).
Jan 26 16:41:50 kubuntu18 kernel: [10825.584341] radeon 0000:06:00.0: GPU softreset: 0x00000048
Jan 26 16:41:50 kubuntu18 kernel: [10825.584346] radeon 0000:06:00.0:   GRBM_STATUS               = 0xA0003028
Jan 26 16:41:50 kubuntu18 kernel: [10825.584349] radeon 0000:06:00.0:   GRBM_STATUS_SE0           = 0x00000006
Jan 26 16:41:50 kubuntu18 kernel: [10825.584351] radeon 0000:06:00.0:   GRBM_STATUS_SE1           = 0x00000006
Jan 26 16:41:50 kubuntu18 kernel: [10825.584354] radeon 0000:06:00.0:   SRBM_STATUS               = 0x200000C0
Jan 26 16:41:50 kubuntu18 kernel: [10825.584393] radeon 0000:06:00.0:   SRBM_STATUS2              = 0x00000000
Jan 26 16:41:50 kubuntu18 kernel: [10825.584396] radeon 0000:06:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Jan 26 16:41:50 kubuntu18 kernel: [10825.584399] radeon 0000:06:00.0:   R_008678_CP_STALLED_STAT2 = 0x00010000
Jan 26 16:41:50 kubuntu18 kernel: [10825.584402] radeon 0000:06:00.0:   R_00867C_CP_BUSY_STAT     = 0x00400002
Jan 26 16:41:50 kubuntu18 kernel: [10825.584404] radeon 0000:06:00.0:   R_008680_CP_STAT          = 0x84010243
Jan 26 16:41:50 kubuntu18 kernel: [10825.584407] radeon 0000:06:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
Jan 26 16:41:50 kubuntu18 kernel: [10825.584410] radeon 0000:06:00.0:   R_00D834_DMA_STATUS_REG   = 0x44C83D57
Jan 26 16:41:50 kubuntu18 kernel: [10825.584413] radeon 0000:06:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
Jan 26 16:41:50 kubuntu18 kernel: [10825.584416] radeon 0000:06:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
Jan 26 16:41:51 kubuntu18 kernel: [10826.023490] radeon 0000:06:00.0: GRBM_SOFT_RESET=0x0000DDFF
Jan 26 16:41:51 kubuntu18 kernel: [10826.023545] radeon 0000:06:00.0: SRBM_SOFT_RESET=0x00000100
Jan 26 16:41:51 kubuntu18 kernel: [10826.024694] radeon 0000:06:00.0:   GRBM_STATUS               = 0x00003028
Jan 26 16:41:51 kubuntu18 kernel: [10826.024697] radeon 0000:06:00.0:   GRBM_STATUS_SE0           = 0x00000006
Jan 26 16:41:51 kubuntu18 kernel: [10826.024700] radeon 0000:06:00.0:   GRBM_STATUS_SE1           = 0x00000006
Jan 26 16:41:51 kubuntu18 kernel: [10826.024702] radeon 0000:06:00.0:   SRBM_STATUS               = 0x200000C0
Jan 26 16:41:51 kubuntu18 kernel: [10826.024741] radeon 0000:06:00.0:   SRBM_STATUS2              = 0x00000000
Jan 26 16:41:51 kubuntu18 kernel: [10826.024744] radeon 0000:06:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
Jan 26 16:41:51 kubuntu18 kernel: [10826.024747] radeon 0000:06:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
Jan 26 16:41:51 kubuntu18 kernel: [10826.024750] radeon 0000:06:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
Jan 26 16:41:51 kubuntu18 kernel: [10826.024752] radeon 0000:06:00.0:   R_008680_CP_STAT          = 0x00000000
Jan 26 16:41:51 kubuntu18 kernel: [10826.024755] radeon 0000:06:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
Jan 26 16:41:51 kubuntu18 kernel: [10826.024758] radeon 0000:06:00.0:   R_00D834_DMA_STATUS_REG   = 0x44C83D57
Jan 26 16:41:51 kubuntu18 kernel: [10826.024847] radeon 0000:06:00.0: GPU reset succeeded, trying to resume
Jan 26 16:41:51 kubuntu18 kernel: [10826.040849] [drm] probing gen 2 caps for device 8086:e08 = 37a7d03/e
Jan 26 16:41:51 kubuntu18 kernel: [10826.040852] [drm] PCIE gen 3 link speeds already enabled
Jan 26 16:41:51 kubuntu18 kernel: [10826.057273] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
Jan 26 16:41:51 kubuntu18 kernel: [10826.057419] radeon 0000:06:00.0: WB enabled
Jan 26 16:41:51 kubuntu18 kernel: [10826.057425] radeon 0000:06:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0x000000003a9fe4a8
Jan 26 16:41:51 kubuntu18 kernel: [10826.057428] radeon 0000:06:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0x00000000d8245dc8
Jan 26 16:41:51 kubuntu18 kernel: [10826.057431] radeon 0000:06:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0x000000004585da30
Jan 26 16:41:51 kubuntu18 kernel: [10826.057434] radeon 0000:06:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0x00000000f0a5aade
Jan 26 16:41:51 kubuntu18 kernel: [10826.057438] radeon 0000:06:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0x00000000edfc4d94
Jan 26 16:41:51 kubuntu18 kernel: [10826.057738] radeon 0000:06:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0x00000000be9517c4
Jan 26 16:41:51 kubuntu18 kernel: [10826.067915] radeon 0000:06:00.0: failed VCE resume (-22).
Jan 26 16:41:51 kubuntu18 kernel: [10826.219238] [drm] ring test on 0 succeeded in 1 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.219242] [drm] ring test on 1 succeeded in 1 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.219247] [drm] ring test on 2 succeeded in 1 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.219255] [drm] ring test on 3 succeeded in 3 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.219262] [drm] ring test on 4 succeeded in 3 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.394990] [drm] ring test on 5 succeeded in 1 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.394994] [drm] UVD initialized successfully.
Jan 26 16:41:51 kubuntu18 kernel: [10826.396016] [drm] ib test on ring 0 succeeded in 0 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.396049] [drm] ib test on ring 1 succeeded in 0 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.396079] [drm] ib test on ring 2 succeeded in 0 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.396111] [drm] ib test on ring 3 succeeded in 0 usecs
Jan 26 16:41:51 kubuntu18 kernel: [10826.396141] [drm] ib test on ring 4 succeeded in 0 usecs
Jan 26 16:41:52 kubuntu18 kernel: [10827.573385] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait timed out.
Jan 26 16:41:52 kubuntu18 kernel: [10827.573418] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-110).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573426] radeon 0000:06:00.0: scheduling IB failed (-12).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573450] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573473] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573495] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 6 (-12).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573499] radeon 0000:06:00.0: scheduling IB failed (-12).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573521] [drm:radeon_vce_get_create_msg [radeon]] *ERROR* radeon: failed to schedule ib (-12).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573542] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: failed to get create msg (-12).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573563] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 7 (-12).
Jan 26 16:41:52 kubuntu18 kernel: [10827.573621] BUG: unable to handle kernel NULL pointer dereference at 00000000000001b0
Jan 26 16:41:52 kubuntu18 kernel: [10827.573631] IP: _raw_spin_lock_irqsave+0x22/0x40
Jan 26 16:41:52 kubuntu18 kernel: [10827.573634] PGD 0 P4D 0 
Jan 26 16:41:52 kubuntu18 kernel: [10827.573639] Oops: 0002 [#1] SMP PTI
Jan 26 16:41:52 kubuntu18 kernel: [10827.573642] Modules linked in: iptable_raw iptable_mangle iptable_nat nf_nat_ipv4 binfmt_misc rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt cmac bnep nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype nls_iso8859_1 wl(POE) nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate btusb btrtl btbcm btintel bluetooth ecdh_generic applesmc input_polldev input_leds intel_rapl_perf snd_usb_audio snd_usbmidi_lib joydev lpc_ich snd_hda_codec_cirrus
Jan 26 16:41:52 kubuntu18 kernel: [10827.573700]  snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq_midi cfg80211 snd_seq_midi_event snd_pcm ip6table_filter snd_rawmidi ip6_tables apple_gmux snd_seq nf_conntrack_netbios_ns mei_me snd_seq_device snd_timer nf_conntrack_broadcast apple_bl snd mei ioatdma nf_nat_ftp soundcore dca shpchp video nf_nat nf_conntrack_ftp nf_conntrack libcrc32c mac_hid sch_fq_codel iptable_filter parport_pc ppdev lp parport ip_tables x_tables autofs4 amdkfd amd_iommu_v2 amdgpu chash hid_generic usbhid hid tg3 ptp radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops libahci i2c_i801 drm pps_core thunderbolt
Jan 26 16:41:52 kubuntu18 kernel: [10827.573756] CPU: 2 PID: 497 Comm: kworker/2:1H Tainted: P        W  OE    4.15.0-43-generic #46-Ubuntu
Jan 26 16:41:52 kubuntu18 kernel: [10827.573758] Hardware name: Apple Inc. MacPro6,1/Mac-F60DEB81FF30ACF6, BIOS 127.0.0.0.0 09/17/2018
Jan 26 16:41:52 kubuntu18 kernel: [10827.573782] Workqueue: radeon-crtc radeon_flip_work_func [radeon]
Jan 26 16:41:52 kubuntu18 kernel: [10827.573788] RIP: 0010:_raw_spin_lock_irqsave+0x22/0x40
Jan 26 16:41:52 kubuntu18 kernel: [10827.573790] RSP: 0018:ffffb02747a3be18 EFLAGS: 00010046
Jan 26 16:41:52 kubuntu18 kernel: [10827.573793] RAX: 0000000000000000 RBX: 0000000000000246 RCX: 0000000000000000
Jan 26 16:41:52 kubuntu18 kernel: [10827.573795] RDX: 0000000000000001 RSI: 0000000000000092 RDI: 00000000000001b0
Jan 26 16:41:52 kubuntu18 kernel: [10827.573798] RBP: ffffb02747a3be20 R08: 0000000000000000 R09: 0000000000000872
Jan 26 16:41:52 kubuntu18 kernel: [10827.573800] R10: fffffaff7c4b8bc0 R11: ffffffffa4b5380d R12: ffff91d0a9094180
Jan 26 16:41:52 kubuntu18 kernel: [10827.573802] R13: ffff91d0b8780800 R14: ffff91d0b8274000 R15: ffff91d0ac6b0000
Jan 26 16:41:52 kubuntu18 kernel: [10827.573805] FS:  0000000000000000(0000) GS:ffff91d0bf080000(0000) knlGS:0000000000000000
Jan 26 16:41:52 kubuntu18 kernel: [10827.573808] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 26 16:41:52 kubuntu18 kernel: [10827.573810] CR2: 00000000000001b0 CR3: 000000093fa0a004 CR4: 00000000001606e0
Jan 26 16:41:52 kubuntu18 kernel: [10827.573813] Call Trace:
Jan 26 16:41:52 kubuntu18 kernel: [10827.573836]  radeon_flip_work_func+0x138/0x230 [radeon]
Jan 26 16:41:52 kubuntu18 kernel: [10827.573842]  process_one_work+0x1de/0x410
Jan 26 16:41:52 kubuntu18 kernel: [10827.573846]  worker_thread+0x32/0x410
Jan 26 16:41:52 kubuntu18 kernel: [10827.573851]  kthread+0x121/0x140
Jan 26 16:41:52 kubuntu18 kernel: [10827.573854]  ? process_one_work+0x410/0x410
Jan 26 16:41:52 kubuntu18 kernel: [10827.573858]  ? kthread_create_worker_on_cpu+0x70/0x70
Jan 26 16:41:52 kubuntu18 kernel: [10827.573863]  ? do_syscall_64+0x73/0x130
Jan 26 16:41:52 kubuntu18 kernel: [10827.573867]  ? SyS_exit_group+0x14/0x20
Jan 26 16:41:52 kubuntu18 kernel: [10827.573871]  ret_from_fork+0x35/0x40
Jan 26 16:41:52 kubuntu18 kernel: [10827.573874] Code: 48 6f ff 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 53 9c 58 0f 1f 44 00 00 48 89 c3 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 <f0> 0f b1 17 85 c0 75 06 48 89 d8 5b 5d c3 89 c6 e8 99 ff 73 ff 
Jan 26 16:41:52 kubuntu18 kernel: [10827.573945] RIP: _raw_spin_lock_irqsave+0x22/0x40 RSP: ffffb02747a3be18
Jan 26 16:41:52 kubuntu18 kernel: [10827.573947] CR2: 00000000000001b0
Jan 26 16:41:52 kubuntu18 kernel: [10827.573952] ---[ end trace 3bcf59b616e3f5ec ]---
Jan 26 16:42:21 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:21 AEAD Decrypt error: bad packet ID (may be a replay): [ #536314 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:21 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:21 AEAD Decrypt error: bad packet ID (may be a replay): [ #536315 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:21 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:21 AEAD Decrypt error: bad packet ID (may be a replay): [ #536320 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:21 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:21 AEAD Decrypt error: bad packet ID (may be a replay): [ #536327 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:21 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:21 AEAD Decrypt error: bad packet ID (may be a replay): [ #536330 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:21 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:21 AEAD Decrypt error: bad packet ID (may be a replay): [ #536331 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:58 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:58 AEAD Decrypt error: bad packet ID (may be a replay): [ #635792 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:58 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:58 AEAD Decrypt error: bad packet ID (may be a replay): [ #635793 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:58 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:58 AEAD Decrypt error: bad packet ID (may be a replay): [ #635839 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:42:58 kubuntu18 nordvpnd[1231]: 2019/01/26 16:42:58 AEAD Decrypt error: bad packet ID (may be a replay): [ #635840 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jan 26 16:44:22 kubuntu18 dbus-daemon[901]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.89' (uid=1000 pid=3578 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper)
Jan 26 16:44:22 kubuntu18 org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Jan 26 16:44:22 kubuntu18 org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Jan 26 16:44:22 kubuntu18 dbus-daemon[901]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Jan 26 16:45:37 kubuntu18 dbus-daemon[901]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.89' (uid=1000 pid=3578 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper)
Jan 26 16:45:37 kubuntu18 org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Jan 26 16:45:37 kubuntu18 org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Jan 26 16:45:37 kubuntu18 dbus-daemon[901]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Jan 26 16:46:52 kubuntu18 dbus-daemon[901]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.89' (uid=1000 pid=3578 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev" label="unconfined") (using servicehelper)
Jan 26 16:46:52 kubuntu18 org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Jan 26 16:46:52 kubuntu18 org.kde.powerdevil.backlighthelper: message repeated 2 times: [ QDBusArgument: read from a write-only object]
Jan 26 16:46:52 kubuntu18 dbus-daemon[901]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
                  Here's lsblk

                  Code:
                  NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.9G  0 disk 
├─sda1   8:1    0   200M  0 part /boot/efi
├─sda2   8:2    0 604.7G  0 part 
├─sda3   8:3    0  47.8G  0 part /
└─sda4   8:4    0 279.1G  0 part
                  sda2 = macOS, sda3 = Kubuntu, sda4 = Windows
                  Last edited by ymgenesis; Jan 27, 2019, 09:18 AM.
                  • Top
                  • Bottom

                  Comment

                    #10
                    I've made a post in the Ubuntu forums, as well, to see if I can get more eyes on this very frustrating issue:
                    https://ubuntuforums.org/showthread....2#post13833702
                    • Top
                    • Bottom

                    Comment

                    Previous template Next
                    Working...
                    X