Forum: >>> Magnum BBS <<<

kioworker and CPU

From MERLIN Philippe@21:1/5 to All on Sat Apr 26 12:58:38 2025

This is a multi-part message in MIME format.

--nextPart12652746.O9o76ZdvQC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Hello,
For some time now, I've been having problems with my Debian SID AMD64. I've already reported it to the list about the screen blocking and the mouse becoming
inoperative. The users recommended certain tests to diagnose the cause of the problem. I ran memtest86 overnight without any problems. However, upon further investigation, I noticed that the processor temperatures were very high, approaching 100°C (96.97°C). The fans were operating normally. I thought it was a
thermal paste problem. A technician ran some tests without Linux, and the processor temperatures were normal, even under load, at a maximum of 76°C. He suggested the problem might be with an application. I launched: *top*
and* *I noticed that a kioworker process was constantly using 100% CPU. Why?
Is this the culprit? Where should I look? Kioworker seems to be a KDE process, so I'll
send an email to the KDE list asking for help.
Thanks in advance for your contributions.
Philippe Merlin

--nextPart12652746.O9o76ZdvQC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>Hello,
For some time now, I've been having problems with my Debian SID AMD64. I've already reported it to the list about the screen blocking and the mouse becoming inoperative. The users
recommended certain tests to diagnose the cause of the problem. I ran memtest86 overnight without any problems. However, upon further investigation, I noticed that the processor temperatures were very high, approaching 100°C (96.97°C). The fans were
operating normally. I thought it was a thermal paste problem. A technician ran some tests without Linux, and the processor temperatures were normal, even under load, at a maximum of 76°C. He suggested the problem might be with an application. I launched:
*top*
and* *I noticed that a kioworker process was constantly using 100% CPU. Why?
Is this the culprit? Where should I look? Kioworker seems to be a KDE process, so I'll send an email to the KDE list asking for help.
Thanks in advance for your contributions.
Philippe Merlin
</body>
</html>
--nextPart12652746.O9o76ZdvQC--

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEmq87yX/v2s7XpMbA3VsQlcAxthwFAmgMvF4ACgkQ3VsQlcAx thxJGQf8CZDSM2+1Pbb0DUu/eLQBZBRETn/0iSd6HwhM4JMiXB+hD6BC4gKGlkml XJCYWODbxi95jG/W5SMZd6iB8miHRInG6qVv9CWF7Gsbdz9uI9w2ZnM/bbWStUgI I+n34UPZELXz+eEqibJt7/5EmosmsxR1jt1IqLOitMG0Mz1E9fo0axLoclF4IZYx usFu8ipUWPJpFkiJMLxShdp1SIEjQX856syfP+wE7vvR1hJv4NanGITz+4kVNGlz 50Xkla+5R6vk3NtF55nqJh0Uv4VW0viyD1PTSrQlkl8tWXBKdpOuqZ+c4FQHehnf C8+2+unPMxKLfvTbDkwuGI9SuHIyZg==
=/hjb
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Rongrong@21:1/5 to MERLIN Philippe on Sat Apr 26 20:00:01 2025

Hi Philippe,

I somehow met the same issue before and confirmed that kioworker was unfortunately stuck while generating the thumbnail of a file.

`sudo strace -p <PID>` and `lsof -p <PID>` may help you find the file
that causes the issue. You can then work around the bug by disabling
thumbnail generation for the affected MIME type.

In my case, it was a DOCX file.

$ sudo strace -p <PID>
lseek(11, 5557, SEEK_SET) = 5557
lseek(11, 5557, SEEK_SET) = 5557
lseek(11, 5557, SEEK_SET) = 5557
[...]
$ lsof -p <PID>
kioworker <PID> rongrong 11r REG <DEVICE>
<SIZE/OFF> <NODE> /path/to/a.docx

It is impossible for me to provide a reproducer to the devs, as the
file itself is confidential. Thus, I've never reported the issue. If
you find you are facing the same issue and if the file is not
confidential, please report it to the KDE devs.

Rong

On Sat, 2025-04-26 at 12:58 +0200, MERLIN Philippe wrote:

Hello,
For some time now, I've been having problems with my Debian SID AMD64. I've already reported it to the list about the screen blocking and the mouse becoming
inoperative. The users recommended certain tests to diagnose the cause of the
problem. I ran memtest86 overnight without any problems. However, upon further
investigation, I noticed that the processor temperatures were very high, approaching 100°C (96.97°C). The fans were operating normally. I thought it was a
thermal paste problem. A technician ran some tests without Linux, and the processor temperatures were normal, even under load, at a maximum of 76°C. He
suggested the problem might be with an application. I launched: *top*
and* *I noticed that a kioworker process was constantly using 100% CPU. Why? Is this the culprit? Where should I look? Kioworker seems to be a KDE process, so I'll
send an email to the KDE list asking for help.
Thanks in advance for your contributions.
Philippe Merlin

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From MERLIN Philippe@21:1/5 to All on Mon Apr 28 21:27:33 2025

This is a multi-part message in MIME format.

--nextPart3353854.44csPzL39Z
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Le samedi 26 avril 2025, 19:57:12 heure d’été d’Europe centrale Rongrong a écrit :

Hi Philippe,

I somehow met the same issue before and confirmed that kioworker was unfortunately stuck while generating the thumbnail of a file.

`sudo strace -p <PID>` and `lsof -p <PID>` may help you find the file
that causes the issue. You can then work around the bug by disabling thumbnail generation for the affected MIME type.

In my case, it was a DOCX file.

$ sudo strace -p <PID>
lseek(11, 5557, SEEK_SET) = 5557
lseek(11, 5557, SEEK_SET) = 5557
lseek(11, 5557, SEEK_SET) = 5557
[...]
$ lsof -p <PID>
kioworker <PID> rongrong 11r REG <DEVICE>
<SIZE/OFF> <NODE> /path/to/a.docx

It is impossible for me to provide a reproducer to the devs, as the
file itself is confidential. Thus, I've never reported the issue. If
you find you are facing the same issue and if the file is not
confidential, please report it to the KDE devs.

Rong

Thank you for the method you provide to detect the cause of Kioworker's out-of-control
behavior, which causes processor overheating. In my case, it worked very well; the culprit
was a corrupted .pps file. Deleting this file in the same session didn't make the problem go
away, but upon rebooting, everything returned to normal.
I don't understand why the KDE system is interested in this file if it existed in my home
directory and I hadn't accessed it for a long time.
Should I file a bug report? If so, I don't know how to write one? Is it a Debian or KDE bug?
The offending .pps file is deleted; to find it, I'd have to look for it in my backups.
I also recently had a problem with clamav (clamd), which also used a processor at 100%,
thus increasing the processor temperature. A reboot calmed everything down.

On Sat, 2025-04-26 at 12:58 +0200, MERLIN Philippe wrote:

Hello,
For some time now, I've been having problems with my Debian SID AMD64.
I've
already reported it to the list about the screen blocking and the mouse becoming inoperative. The users recommended certain tests to diagnose the cause of the problem. I ran memtest86 overnight without any problems. However, upon further investigation, I noticed that the processor temperatures were very high, approaching 100°C (96.97°C). The fans were operating normally. I thought it was a thermal paste problem. A
technician ran some tests without Linux, and the processor temperatures were normal, even under load, at a maximum of 76°C. He suggested the problem might be with an application. I launched: *top* and* *I noticed that a kioworker process was constantly using 100% CPU. Why? Is this the culprit? Where should I look? Kioworker seems to be a KDE process, so
I'll send an email to the KDE list asking for help.
Thanks in advance for your contributions.
Philippe Merlin

--nextPart3353854.44csPzL39Z
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>Le samedi 26 avril 2025, 19:57:12 heure d’été d’Europe centrale Rongrong a écrit :
> Hi Philippe,
> > I somehow met the same issue before and confirmed that kioworker was
> unfortunately stuck while generating the thumbnail of a file.
> > `sudo strace -p <PID>` and `lsof -p <PID>` may help you find the file
> that causes the issue. You can then work around the bug by disabling
> thumbnail generation for the affected MIME type.
> > In my case, it was a DOCX file.
> > $ sudo strace -p <PID>
> lseek(11, 5557, SEEK_SET)               = 5557
> lseek(11, 5557, SEEK_SET)               = 5557
> lseek(11, 5557, SEEK_SET)               = 5557
> [...]
> $ lsof -p <PID>
> kioworker <PID> rongrong  11r      REG               <DEVICE>
> <SIZE/OFF>     <NODE> /path/to/a.docx
> > It is impossible for me to provide a reproducer to the devs, as the
> file itself is confidential. Thus, I've never reported the issue. If
> you find you are facing the same issue and if the file is not
> confidential, please report it to the KDE devs.
> > Rong
Thank you for the method you provide to detect the cause of Kioworker's out-of-control behavior, which causes processor overheating. In my case, it worked very well; the culprit was a
corrupted .pps file. Deleting this file in the same session didn't make the problem go away, but upon rebooting, everything returned to normal.
I don't understand why the KDE system is interested in this file if it existed in my home directory and I hadn't accessed it for a long time.
Should I file a bug report? If so, I don't know how to write one? Is it a Debian or KDE bug?
The offending .pps file is deleted; to find it, I'd have to look for it in my backups.
I also recently had a problem with clamav (clamd), which also used a processor at 100%, thus increasing the processor temperature. A reboot calmed everything down.
> > On Sat, 2025-04-26 at 12:58 +0200, MERLIN Philippe wrote:
> > Hello,
> > For some time now, I've been having problems with my Debian SID AMD64.
> > I've
> > already reported it to the list about the screen blocking and the mouse
> > becoming inoperative. The users recommended certain tests to diagnose the
> > cause of the problem. I ran memtest86 overnight without any problems.
> > However, upon further investigation, I noticed that the processor
> > temperatures were very high, approaching 100°C (96.97°C). The fans were
> > operating normally. I thought it was a thermal paste problem. A
> > technician ran some tests without Linux, and the processor temperatures
> > were normal, even under load, at a maximum of 76°C. He suggested the
> > problem might be with an application. I launched: *top* and* *I noticed
> > that a kioworker process was constantly using 100% CPU. Why? Is this the
> > culprit? Where should I look? Kioworker seems to be a KDE process, so
> > I'll send an email to the KDE list asking for help.
> > Thanks in advance for your contributions.
> > Philippe Merlin
 </body>
</html>
--nextPart3353854.44csPzL39Z--

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEmq87yX/v2s7XpMbA3VsQlcAxthwFAmgP1qUACgkQ3VsQlcAx thxv3gf8CGpsrwFdboFdyoDRmLvSx0KsPEW9Iz1RqufCgHzst90et+Ixn+79D0iA BfwmASeq/zLXTlaGrJEzH9W1N/JlQ828PGmB9W19MQYKkBUMdOBTnEQVrL5vunPw lK/CuliPSwVT0TqTjE0F8vgWUsmEOk6qCcNn7uvn0Tr2R5t/+yqlyKE4UUIZjbYg zvaqvgjmauB9Z4iuE1H7Ky14ouMpARm+DvzCxvYZQuKugIE3zXaVq24YJ/q+OaWT 9y6WTbNYyB5zCAbXE65sFQSjNKmPxvMATfEspwBzCzE4WPNtNRJChXGKlppSmz4V D5StVkvxwGjpy7ctOODeHytGTQMbug==
=uMzF
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Soren Stoutner@21:1/5 to All on Mon Apr 28 14:55:38 2025

Copy: phil-deb1.merlin@laposte.net (MERLIN Philippe)

This is a multi-part message in MIME format.

--nextPart10982598.aFP6jjVeTY
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Monday, April 28, 2025 12:27:33 PM Mountain Standard Time MERLIN Philippe wrote:

Thank you for the method you provide to detect the cause of Kioworker's out-of-control behavior, which causes processor overheating. In my case, it worked very well; the culprit was a corrupted .pps file. Deleting this file in the same session didn't make the problem go away, but upon rebooting, everything returned to normal.
I don't understand why the KDE system is interested in this file if it existed
in my home directory and I hadn't accessed it for a long time.

KDE is probably trying to make a thumbnail of the file to display in Dolphin.

Should I file a bug report? If so, I don't know how to write one? Is it a Debian or KDE bug?

It sounds like an upstream bug, so I would file it with KDE.

The offending .pps file is deleted; to find it, I'd have
to look for it in my backups. I also recently had a problem with clamav (clamd), which also used a processor at 100%, thus increasing the processor temperature. A reboot calmed everything down.

It would be very helpful to them if you attached a copy of the .pps file to the bug report.
Otherwise, they don’t have much to go on.

--
Soren Stoutner
soren@debian.org

--nextPart10982598.aFP6jjVeTY
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>On Monday, April 28, 2025 12:27:33 PM Mountain Standard Time MERLIN Philippe wrote:
> Thank you for the method you provide to detect the cause of Kioworker's
> out-of-control behavior, which causes processor overheating. In my case, it
> worked very well; the culprit was a corrupted .pps file. Deleting this file
> in the same session didn't make the problem go away, but upon r

Who's Online
Recent Visitors
- Jack
  Sun Jun 8 06:41:19 2025
  from Mississipi via Telnet
- Centurion
  Sun Jun 8 00:08:04 2025
  from Berea, Ohio via Telnet
- Centurion
  Sat Jun 7 21:52:22 2025
  from Berea, Ohio via Telnet
- Tnmoc
  Sat Jun 7 13:44:20 2025
  from Milton Keynes via Telnet
- Tnmoc
  Sat Jun 7 13:40:01 2025
  from Milton Keynes via Telnet
- Plume
  Sat Jun 7 11:13:29 2025
  from Uk via SSH
- Gwylbert
  Sat Jun 7 08:57:45 2025
  from Sydney, Nsw via Telnet
- Centurion
  Sat Jun 7 04:30:40 2025
  from Berea, Ohio via Telnet

System Info

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	487
Nodes:	16 (2 / 14)
Uptime:	00:34:59
Calls:	9,660
Calls today:	2
Files:	13,709
Messages:	6,166,402

kioworker and CPU

Who's Online

Recent Visitors

System Info