Dear Sean
On 09.03.22 16:54, Sean Whitton wrote:
Dear Dirk,
On Wed 09 Mar 2022 at 12:59pm +01, Dirk Kostrewa wrote:
Personally, I would still prefer a "rename" entry in the alternative
system with util-linux's rename as default, since util-linux is
installed in every Debian
nt on these two
resolutions, but we aren't going to block resolving this bug on hearing
from you.
Thanks both.
--
***
Dirk Kostrewa
Gene Center Munich
Department of Biochemistry, AG Hopfner
Ludwig-Maximilians-Universität M
On 25/01/2022 09:16, Chris Hofstaedtler wrote:
Hi,
* Sean Whitton [220125 00:06]:
On Mon 24 Jan 2022 at 11:33AM +01, Chris Hofstaedtler wrote:
For context, the idea is that /usr/bin/rename should become
src:util-linux' rename implementation.
That seems likely to break a great many scripts,
Meanwhile, I have asked the technical committee for a revision of the
removal of rename.ul from the util-linux package in Debian bug report
#1003653 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003653).
Dirk.
t this
removal will be reversed.
Kind regards,
Dirk Kostrewa.
After changing the Linux distribution from CentOS to Debian "Bullseye"
at an institute of the University of Munich, the removal of rename.ul
from util-linux in Debian "Bullseye" broke one of our scripts used in a
scientific workflow in research. I can't believe that this highly
versatile and si
Bonaccorso:
Hi Dirk,
Thanks for testing that.
On Sat, Aug 29, 2020 at 11:04:43AM +0200, Dirk Kostrewa wrote:
Hi Salvatore,
I have enabled the verbose debugging mode on the command line and have
appended the first 5000 lines of the dmesg output to this e-mail, running
the current kernel from the
57PM +0200, Dirk Kostrewa wrote:
Hi Salvatore,
I just found out, that if none of the two USB ports is connected, there are
two kworker processes with permanently high CPU load, if one USB port is
connected and the other not, there is one such kworker process, and if both
USB ports are connected, t
USB ports with
over-current condition.
Regards,
Dirk.
Am 12.08.20 um 18:05 schrieb Salvatore Bonaccorso:
Hi,
Just commenting on the following:
On Wed, Aug 12, 2020 at 05:53:57PM +0200, Dirk Kostrewa wrote:
[...]
What puzzles me, is that I've observed these oddly behaving kworker
proc
2020 at 05:53:57PM +0200, Dirk Kostrewa wrote:
[...]
What puzzles me, is that I've observed these oddly behaving kworker
processes also with the 5.6 kernel that I've tried from the Buster Backports
repository.
The mentioned commit, is included in the following upstream versions
(relevant f
that I've tried from the Buster
Backports repository.
Cheers,
Dirk.
Am 12.08.20 um 13:02 schrieb Dirk Kostrewa:
Hi Salvatore,
yesterday, I installed the kernel 5.6.0 from the Buster Backports and
saw again a kworker process with high CPU load.
Oddly, this morning, my laptop didn&#x
atore Bonaccorso:
Hi Dirk,
On Tue, Aug 11, 2020 at 12:58:15PM +0200, Dirk Kostrewa wrote:
Hi Salavatore,
as an additional control, I have completely uninstalled the nvidia graphics
driver and repeated the kworker observations using the nouveau graphics
driver with the kernel 4.19.0-10-amd64. This
rk
On Sun, Aug 02, 2020 at 10:00:27AM +0200, Dirk Kostrewa wrote:
Package: src:linux
Version: 4.19.132-1
Severity: normal
Dear Maintainer,
after booting the kernel 4.19.0-10-amd64, there is a kworker process running
with a permanent high CPU load of almost 90% as reported by the "top"
2 schrieb Salvatore Bonaccorso:
Hi Dirk,
On Sun, Aug 02, 2020 at 03:44:09PM +0200, Salvatore Bonaccorso wrote:
Control: tags -1 + moreinfo
Hi Dirk
On Sun, Aug 02, 2020 at 10:00:27AM +0200, Dirk Kostrewa wrote:
Package: src:linux
Version: 4.19.132-1
Severity: normal
Dear Maintainer,
after bo
f
I hope, this was right. If I can give you any more information, please,
let me know.
Regards,
Dirk.
Am 02.08.20 um 15:44 schrieb Salvatore Bonaccorso:
Control: tags -1 + moreinfo
Hi Dirk
On Sun, Aug 02, 2020 at 10:00:27AM +0200, Dirk Kostrewa wrote:
Package: src:linux
Versi
Package: src:linux
Version: 4.19.132-1
Severity: normal
Dear Maintainer,
after booting the kernel 4.19.0-10-amd64, there is a kworker process
running with a permanent high CPU load of almost 90% as reported by the
"top" command:
$ top
top - 09:48:19 up 0 min, 4 users, load average: 1.91, 0
16 matches
Mail list logo
