similar to: Updating microcode_ctl froze Centos7

Displaying 20 results from an estimated 9000 matches similar to: "Updating microcode_ctl froze Centos7"

2020 Jun 17
1
Updating microcode_ctl froze Centos7
On Mon, 2020-06-15 at 22:25 +0200, Robin Lee wrote: > On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > > Today when I ran yum update two packages came up microcode_ctl > > and unbound-libs. The updating process went fine until it > > outputted > > > > Running transaction > > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > > > then
2020 Jun 14
0
Updating microcode_ctl froze Centos7
On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > then it just froze. I could no longer ssh to the machine and the > console was just blank. I had to
2020 Jun 14
1
Updating microcode_ctl froze Centos7
On 14/06/2020 17:09, Robin Lee wrote: > On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: >> Today when I ran yum update two packages came up microcode_ctl >> and unbound-libs. The updating process went fine until it outputted >> >> Running transaction >> Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 >> >> then it just froze. I could no longer
2020 Jun 15
0
Updating microcode_ctl froze Centos7
On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > then it just froze. I could no longer ssh to the machine and the > console was just blank. I had to
2020 Jun 12
0
Updating microcode_ctl froze Centos7
On Fri, Jun 12, 2020 at 09:20:34AM +0200, Robin Lee wrote: > Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > then it just froze. I could no longer ssh to the machine and the > console was just blank. I had
2020 Jun 10
0
CESA-2020:2432 Moderate CentOS 7 microcode_ctl Security Update
CentOS Errata and Security Advisory 2020:2432 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:2432 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e60f84fe58d8f960f14241fc1c21ad0053213bad8ba294fc3c5f727d37076e4c microcode_ctl-2.1-61.6.el7_8.x86_64.rpm Source:
2006 Nov 29
5
microcode_ctl
i'm running on vmware system and HP proliant DL360 G5 servers on wmware, on boot i have the following message: ----------------------------- Applying Intel Microcode update: don't know to make device "cpu/microcode" [OK] ----------------------------- and on a HP proliant DL360 G5 server , on boot i have too the following message: ----------------------------- Applying
2007 Dec 12
6
ssh terminal froze once in a while
Hello My ssh terminal froze some times, and I was thinking it might be related to centos , but now I found that even ubuntu users experiencing the same problem. does ssh logs any where, and what do you suggest for finding the cause. Thanks
2017 Jan 04
1
microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs
Thanks for the breakdown Paul - I've had to learn all my sysadmin stuff through organic interactions like this. Still though - someone manages the default repositories - so my question is, who decides when a package gets an update from whatever CentOS ships with default to a newer version? How does that process take place, and, can I affect it by adding microcode_ctl-2.1-18 ? On Wed, Jan 4,
2020 Jun 25
0
CEEA-2020:2743 CentOS 7 microcode_ctl Enhancement Update
CentOS Errata and Enhancement Advisory 2020:2743 Upstream details at : https://access.redhat.com/errata/RHEA-2020:2743 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3f199ac1b15b6e30cc81d6c399aaa04c2b71869b8fefbb9a689b95a796004805 microcode_ctl-2.1-61.10.el7_8.x86_64.rpm Source:
2017 Jan 04
2
microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs
Hello all! I'm brand new to the mailing list, and I've encountered an issue with the microcode_ctl package version 2.1-16 being installed during the CentOS 7.3 upgrade. It causes my servers to hard stop and they need to be forcibly powered off and back on again with the power button to continue. This RedHat thread https://bugzilla.redhat.com/show_bug.cgi?id=1398698 details the issue,
2019 Dec 25
0
CEEA-2019:4161 CentOS 7 microcode_ctl-2.1-53.7.el7_7.x86_64 update vs Dell Precision 7530
Hello, this update freshly announced (not available since days, like 2 weeks) seemed to completely break my CentOS 7 system running on a Dell Precision 7530. when I applied it days ago. Once the new microcode has been applied during the yum update transaction, with other updates like nss, system suddently froze, and no way to reboot. I could boot from a flashdrive and give a look at the boot
2020 Jul 15
3
Samba upload from windows restricted to 1KB
Hi Samba users, Out recently setup samba share from Linux box to a windows machine resulted in every upload restricted to 1KB in size regardless of the original file size. However uploading from other Linux using SMB has no issues. We have turned on samba log level 3. Any idea what going on here? Thanks Anand
2020 Jul 01
3
Samba-4.10.4 strange behaviour
Hello All, I'm new to the list and I don't have much of experience with samba. I have a test setup on CentOS 7.8 with samba-4.10.4 and samba-vfs-glusterfs . When my client mounts the samba share via vers=1.0 , the user sees the share properly (uid,gid,mode are just like on gluster). When the share is mounted with vers=2.0 or not specified (anything higher) the files are owned by
2018 Sep 19
1
how to update ucode with xen
it is working thx a lot... but it has included the GenuineIntel.bin only in actually used kernel... do I need to reinstall microcode_ctl every time I update the kernel? And second question, I quess I still need the ucode = scan as xen parameter right? Am 2018-09-19 20:08, schrieb Kevin Stange: > On 9/19/18 1:55 AM, Christoph wrote: >> >> Hi >> >> can someone say me
2018 Sep 19
4
how to update ucode with xen
Hi can someone say me how to update the ?code of the cpu with xen? I have added the ucode=scan parameter to xen but it does not seem to work... the ?code version of my xeon is really old :/ model name : Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz microcode : 0x10 -- ------ Greetz
2020 Jun 11
0
CentOS-announce Digest, Vol 184, Issue 4
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2020 Sep 01
2
Unable to create subdirectories/files in samba mount when using vfs objects = glusterfs
Hi Team, I am trying to setup a samba CTDB cluster to export gluster volme as samba share. While CTDB cluster works well, I ran into an issue with creating subdirectories and also creating files/directories within subdictories when accessing the share from both linux and windows servers. Setup details : We have a three node cluster with nodes snode1, snode2 and snode3. I have a
2019 Aug 04
4
browsers slowing Centos 7 installation to a crawl
My video problems mentioned in a previous thread are gone, though I do not know why. Now my problem is that whenever I have a browser open and an internet connection, my Centos 7 slows to a crawl. Chromium seems to be the least bad. Sometimes it slows to the point that I cannot even move the mouse. Even switching between virtual terminals takes a while sometimes. When I get there, top generally
2018 Jan 18
3
/lib/firmware/microcode.dat update on CentOS 6
On 01/18/18 11:31, Matthew Miller wrote: > On Thu, Jan 18, 2018 at 11:01:18AM -0500, Pete Geenhuizen wrote: >> Do we update the microcode now or do we wait until the latest >> microcode_ctl rpm is available and then tackle this issue? > Check with your hardware vendor for BIOS/EFI firmware updates. Apply > those. > > > Thanks for the reply, but you missed what I was