Using USB Port Freezes Laptop

, ,

Hi All,
Yesterday, I upgraded to Fedora Plasma 42 (is that the correct way to refer to versions/spins?) from 41 and, frankly, I didn’t notice if the USB port 1 (I’ll call it that, but I have no idea how they’re numbered) was causing issues before the upgrade because I hadn’t tried to use it with FP-41.

However, it was definitely working with AV Linux MX 23, the previous distro I was using. In fact, when I had Windows 10 on this machine, the same port would only charge things, but wouldn’t do data transfers. I was surprised to find that under AV Linux I could use it for USB drives as well.

The Actual Problem
Every time I plug a USB drive into port 1 I get a message saying that the drive has errors and there’s a button saying something like ‘Fix Errors.’ If I click this button, the laptop freezes. No mouse, no keyboard, just a pretty desktop sitting there all useless and unresponsive. A Hard reset is the only thing that brings it back.

As far as I know, this is an up-to-the-minute upgrade of 42. For now, I’ve put tape over the port so I don’t freeze my machine while in the middle of things, but it would be nice to have it back. Is this a known bug? Has it been resolved in Fedora Plasma 43? Is it peculiar to the Plasma Spin or have people noticed this on other variants?

The Laptop
It’s an ASUS ROG G751JY (2016) stock except for a second SATA III SSD. It’s connected to a UPS, so I’m as certain as I can be that there have been no damaging power spikes getting through to the laptop.

Another Odd Thing…
Also the drive activity light is constantly flashing. I’m pretty sure it wasn’t doing that with AVL MX23 because it’s very eye-catching. It also keeps flashing after the laptop freezes up as described above.

There are many thing I like about Fedora, so I’d hate to give it up (considering that it’s taken me three days to learn enough to get this install more-or-less configured the way I want) especially the whole upgrade-in-place feature which I had to use when I found out I’d installed an end-of-life version (41). I don’t know, maybe this feature is more widespread than I’m aware, but it’s a nice time-saver.

Thanks for reading this far.

I have not seen this error before - therefore I assume it is a particular combination of Fedora and your PC.

Have you tried any other USB drives in that port?

To find out what is happening trigger the fault, turn the PC off and then on again. After boot and login run from a command line
journalctl --since "5 minutes ago"
and post that output here in preformatted text (the </> button in the toolbar here)

I should have mentioned that… Yes, I’ve tried three different drives. And they all worked flawlessly in my Windows laptop. I’ll run journalctl and get back to the tread shortly.

I did it twice because behaviour is a tad inconsistent and I ended up with two quite different results.

The first time: Clicking on Mount and Open crashed the system immediately.
The second time: Clicked on Mount and Open, the drive mounted and Dolphin opened. Then it crashed.

The journal control output is far too long to post here, even when I cut it down to three minutes. Can you please give me some idea of what I’m looking for so I can post the relevant parts?

The last 50-100 lines should suffice.

You could grep for USB but I think it is better to see all that is going on and then seach more.

Here are the last 100 lines before the reboot:

To be filled in after some self-edification.

What you provided is just a list list of past boots. Be careful with command-line programs that are new to you. man journalctl is the definitive reference, but you may prefer to start with an introductory tutorial rather than wading through all the options. Fedora has a journalctl introductory document, and there are many others, some good but also a lot of AI nonsense.

Use man journalctl to understand the following example: journalctl --no-hostname -b [N] Add | tail -100 to get the last 100 lines. [N] should be chosen to select a previous boot that froze, e.g., -1 after rebooting from a freeze.

1 Like

Thanks for the warning, George. Here, after some digging, are the last 100 lines without identifying thingies:

Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:23 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:24 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:28 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:28 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:28 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:28 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:28 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:28 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:28 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:28 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 plasmashell[1935]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:350:9: QML QQuickItem (parent or ancestor of QQuickDragAttached): Don't know how to encode variant of type QMetaType() as mime type ""
Nov 03 09:50:29 plasmashell[1935]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:350:9: QML QQuickItem (parent or ancestor of QQuickDragAttached): Don't know how to encode variant of type QMetaType() as mime type "application/x-orgkdeplasmataskmanager_taskbuttonitem"
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:29 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:30 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:30 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:30 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:30 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:30 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:44 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:55 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:50:59 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:05 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:05 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:05 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:05 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:05 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:06 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:07 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:07 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:24 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:24 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:26 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:51:35 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:52:34 systemd[1]: Starting sssd-kcm.service - SSSD Kerberos Cache Manager...
Nov 03 09:52:34 systemd[1]: Started sssd-kcm.service - SSSD Kerberos Cache Manager.
Nov 03 09:52:34 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kcm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 03 09:52:34 sssd_kcm[7411]: Starting up
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 systemd[1459]: app-flatpak-org.kde.kate-2227385176.scope: Consumed 12.174s CPU time, 492.3M memory peak.
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:39 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:40 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:40 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:40 firefox[2707]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Nov 03 09:53:41 kwin_wayland[1755]: kwin_xwl: Could not create a source from 0x55ee3ee10c60 0
Nov 03 09:53:41 systemd[1459]: app-org.mozilla.firefox@257b89d0c4504e3ba0cad23accd64a2e.service: Consumed 11min 36.209s CPU time, 2.7G memory peak.
Nov 03 09:53:42 systemd[1459]: app-org.kde.konsole@5958e09ee51f41a6b69d069fe8da098e.service: Consumed 17.396s CPU time, 1.9G memory peak.
Nov 03 09:53:42 systemd[1459]: app-org.kde.konsole-3526.scope: Consumed 15.520s CPU time, 62.2M memory peak.

These messages are not normal, so should be investigated. Meanwhile, we need to filter them out so we can see messages (if any) associated with the freezes. Try journalctl --no-hostname -b [N] |grep -vF firefox | tail -100.