similar to: high kworker CPU usage in 3.10.0-957 w/ Xorg nouveau driver?

Folks I have two USB connected drives, configured as a mirrored-pair in ZFS. It's been working fine UNTIL I updated Centos from 3.10.0-862.14.4.el7.x86_64 to 3.10.0-957.1.3.el7.x86_64 The import of the pools didn't happen at boot. When I tried executing: zpool list I got the diagnostic suggesting I do /sbin/modprobe zfs And that command claimed the module didn't exist. YUM

On Dec 6, 2018, at 17:45, david <david at daku.org> wrote: > > Folks > > I have two USB connected drives, configured as a mirrored-pair in ZFS. It's been working fine UNTIL I updated Centos > from 3.10.0-862.14.4.el7.x86_64 > to 3.10.0-957.1.3.el7.x86_64 > > The import of the pools didn't happen at boot. When I tried executing: > zpool list > I got

Hi, I'm new to this list (and R), but my impression is that this question is more appropriate here than R-help. I hope that is right. I'm having several issues with the performance of an R script. Occasionally it crashes with the well-known 'Error: cannot allocate vector of size X' (this past time it was 4.8 Gb). When it doesn't crash, CPU usage frequently drops quite low

On Mon, Apr 20, 2015 at 09:00:07AM -0400, Martes wrote: > Greetings again everyone. > > Can someone please respond to this? You just posted yesterday... Anyway, you didn't give much context. I can see from a google search why you provided the interrupts output, but judging from what you posted, that's not the problem. Perhaps you have a CPU task that's running at 100%?

Greetings Johnathan. Thank you for the reply. I have run top, and iftop, etc... The only process that is listed is as follows: Tasks: 272 total, 2 running, 270 sleeping, 0 stopped, 0 zombie %Cpu(s): 7.1 us, 18.3 sy, 0.0 ni, 73.8 id, 0.7 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 32679644 total, 402520 free, 9889728 used, 22387396 buff/cache KiB Swap: 0 total, 0 free,

On Mon, Apr 20, 2015 at 11:03:43AM -0400, Martes wrote: > Tasks: 272 total, 2 running, 270 sleeping, 0 stopped, 0 zombie > %Cpu(s): 7.1 us, 18.3 sy, 0.0 ni, 73.8 id, 0.7 wa, 0.0 hi, 0.1 si, 0.0 st > KiB Mem : 32679644 total, 402520 free, 9889728 used, 22387396 buff/cache > KiB Swap: 0 total, 0 free, 0 used. 21951812 avail Mem > > PID USER

No problemos with x86_64, however on i686 kworker/u16:57: page allocation failure: order:0, mode:0x284000 CPU: 0 PID: 1425 Comm: kworker/u16:57 Not tainted 3.18.0-0.rc5.git0.1.fc22.i686+debug #1 Workqueue: events_unbound async_run_entry_fn Call Trace: [<c0b2b55a>] dump_stack+0x48/0x60 [<c056f3d4>] warn_alloc_failed+0xd4/0x110 [<c0571ade>] __alloc_pages_nodemask+0x81e/0xc30

Greetings again everyone. Can someone please respond to this? I am not sure what is causing this issue, however, others seem to have experienced it in the past. Could this be caused by the processor being damaged? Nothing has changed on the system, except for the heat warning shutoff when the water cooler died, and the system was not restarted until the new one was installed. Any input

https://bugs.freedesktop.org/show_bug.cgi?id=77073 Priority: medium Bug ID: 77073 Assignee: nouveau at lists.freedesktop.org Summary: [nouveaun NVE0] Attaching displayport spawns kworker taking up 100% cpu QA Contact: xorg-team at lists.x.org Severity: critical Classification: Unclassified OS:

Greetings everyone. I am experiencing the kworker issue where a kworker is using 100% of a given core. This behavior was only observed after having installed a new water cooler, to replace a cooler that had died. (Sealed closed loop device from Corsair) The processor is staying around 40 degrees celsius as reported by the MB UEFI interface. (ksysguard shows between 29 degrees and 30 degrees,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 2018-11-20 at 13:32 +0000, lejeczek via CentOS wrote: > hi guys > > I've one box where I just yesterday upgraded Centos. I > wonder if that kernel upgrade process might somewhat > troublesome. > After that upgrade UEFI boot fails with: > > Failed to set MokListRT: Invalid Parameter > Something has gone

On 11/20/18 8:45 AM, Phil Wyett wrote: > On Tue, 2018-11-20 at 13:42 +0000, Phil Wyett wrote: > > On Tue, 2018-11-20 at 13:32 +0000, lejeczek via CentOS wrote: > >> hi guys > >> > >> I've one box where I just yesterday upgraded Centos. I > >> wonder if that kernel upgrade process might somewhat > >> troublesome. > >> After that

On Tue, Nov 20, 2018 at 01:32:44PM +0000, lejeczek via CentOS wrote: > > hi guys > > I've one box where I just yesterday upgraded Centos. I wonder if that kernel > upgrade process might somewhat troublesome. > After that upgrade UEFI boot fails with: > > Failed to set MokListRT: Invalid Parameter > Something has gone seriously wrong: import_mok_state() failed >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 2018-11-20 at 13:42 +0000, Phil Wyett wrote: > On Tue, 2018-11-20 at 13:32 +0000, lejeczek via CentOS wrote: > > hi guys > > > > I've one box where I just yesterday upgraded Centos. I > > wonder if that kernel upgrade process might somewhat > > troublesome. > > After that upgrade UEFI boot fails

Hi list, today I tried to update my centos workstation (7.6.1810). My problem concerns kmod-nvidia update. Nvidia driver where installed by elrepo. During running yum update I get: kmod-nvidia.x86_64 430.40-2.el7_7.elrepo elrepo and I also get several statements like this: Errore: Pacchetto: kmod-nvidia-430.40-2.el7_7.elrepo.x86_64 (elrepo) Richiede:

hi guys I've one box where I just yesterday upgraded Centos. I wonder if that kernel upgrade process might somewhat troublesome. After that upgrade UEFI boot fails with: Failed to set MokListRT: Invalid Parameter Something has gone seriously wrong: import_mok_state() failed : Invalid Parameter Has anybody seen that? And maybe know to fix it? many thanks, L.

On 27/08/2019 11:35, Alessandro Baggi wrote: > Hi list, > today I tried to update my centos workstation (7.6.1810). > My problem concerns kmod-nvidia update. Nvidia driver where installed by > elrepo. > During running yum update I get: > > > kmod-nvidia.x86_64 430.40-2.el7_7.elrepo ????????? elrepo > > and I also get several statements like this: > >

CentOS Errata and Security Advisory 2018:2748 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2748 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 2b3829724eb95e3c6692d2759d242c0b0f59204f060752c7c2b519116abb6179 kernel-3.10.0-862.14.4.el7.x86_64.rpm

CentOS Errata and Security Advisory 2018:3651 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2018:3651 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3c969bb6961aea21258bcec9bb5d143b3e84c1fa1506f3068e3271b51a7aeffc bpftool-3.10.0-957.1.3.el7.x86_64.rpm

Hello! I'm writing to report a crash in the QXL / DRM code in the Linux kernel. I originally filed the issue on LaunchPad and more details can be found there, although I doubt whether these details are useful. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813620 I first experienced these issues with: * Ubuntu 18.04 (probably kernel 4.15.something) * Ubuntu 18.10 (kernel