similar to: Kernel 2.6.32-573.22.1.el6.x86_64, higher than usual load

On Fri, Apr 8, 2016 at 6:32 AM, Johnny Hughes <johnny at centos.org> wrote: > On 04/08/2016 06:50 AM, Johnny Carlsen wrote: > > Hi, > > > > After switching to the 2.6.32-573.22.1.el6.x86_64 kernel (CentOS 6) a > few weeks ago I have noticed that my servers are now reporting a much > higher idle load. > > > > The servers are being monitored with Zabbix,

On 04/08/2016 06:50 AM, Johnny Carlsen wrote: > Hi, > > After switching to the 2.6.32-573.22.1.el6.x86_64 kernel (CentOS 6) a few weeks ago I have noticed that my servers are now reporting a much higher idle load. > > The servers are being monitored with Zabbix, and there is a clear difference between the older kernel 2.6.32-573.12.1 and the newer 2.6.32-573.12.1. > > I can

I did a batch update on a number of Xen vservers, with kernel 2.6.32-573.26.1 being installed. In addition to load averages being high and these #s not being reflected by the individual CPU numbers within top, I now have a spattering of occasional daemon crashes that the vservers have historically never had. Such as, here is the start of a nameserver blowing up in my logs: May 12 04:03:41 XXX

Greetings, Today, I decided to reboot one of my CentOS machines after it had been running for 219 days. In this time, I had done yum updates several times. When I tried rebooting the machine, none of the kernels would work except for the oldest one. Here are the installed kernels: kernel-2.6.32-504.23.4.el6.x86_64 kernel-2.6.32-573.3.1.el6.x86_64 kernel-2.6.32-573.7.1.el6.x86_64

https://bugzilla.samba.org/show_bug.cgi?id=2207 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID Summary|Listing of available sync- |Listing of available sync-

On Wed, 3 Feb 2016, Warren Young wrote: > On Feb 3, 2016, at 12:24 PM, Max Pyziur <pyz at brama.com> wrote: >> >> When I tried rebooting the machine, none of the kernels would work except for the oldest one. > > Define ?would not work?. Post a photo of the error message somewhere if you can?t describe it better than that. You might have to turn off rhgb mode to get a

On Feb 3, 2016, at 12:24 PM, Max Pyziur <pyz at brama.com> wrote: > > When I tried rebooting the machine, none of the kernels would work except for the oldest one. Define ?would not work?. Post a photo of the error message somewhere if you can?t describe it better than that. You might have to turn off rhgb mode to get a useful error message. > Here are the installed kernels:

Hi, I am not sure if this is the right eMail-list to ask questions. I have the problem that with a second connect to a samba share the user is authenticated as guest. The first authentication was right done on my own user account. What i am doing wrong ? Thansk Michael [2013/01/02 11:06:34.964955,? 1] smbd/service.c:1070(make_connection_snum) ? pc-etw-051 (::ffff:172.28.96.114) connect to

On Wed, 29 Aug 2018 at 17:41, Leon Fauster via CentOS <centos at centos.org> wrote: > Since the update from kernel-2.6.32-754.2.1.el6.x86_64 > to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my > KVM guests anymore!? The workstation panics immediately! > > I would not have expected this behavior now (last phase of OS). > It was very robust until now (Optiplex

Leon Fauster via CentOS writes: > Since the update from kernel-2.6.32-754.2.1.el6.x86_64 > to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my > KVM guests anymore!? The workstation panics immediately! > > I would not have expected this behavior now (last phase of OS). > It was very robust until now (Optiplex Workstation). I see some KVM > related lines in the

> Since the update from kernel-2.6.32-754.2.1.el6.x86_64 > to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my > KVM guests anymore!? The workstation panics immediately! > > I would not have expected this behavior now (last phase of OS). > It was very robust until now (Optiplex Workstation). I see some KVM > related lines in the changelog.diff. Before swimming upstream: >

> > Am 30.08.2018 um 10:54 schrieb isdtor <isdtor at gmail.com>: > >> >> Leon Fauster via CentOS writes: >>> Since the update from kernel-2.6.32-754.2.1.el6.x86_64 >>> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my >>> KVM guests anymore!? The workstation panics immediately! >>> >>> I would not have expected this

On Thu, 30 Aug 2018 at 05:41, Leon Fauster via CentOS <centos at centos.org> wrote: > > > > > There goes a cheap and reliable VM dev machine :-/ > > > No way. Should all IT departments trash a big percentage of there hardware > now? > > I am going to say from chip and OEM manufacturers view points: yes. For at least the last 15 years, they have priced out

> Am 30.08.2018 um 06:37 schrieb Simon Matter <simon.matter at invoca.ch>: >> >>> Since the update from kernel-2.6.32-754.2.1.el6.x86_64 >>> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my >>> KVM guests anymore!? The workstation panics immediately! >>> >>> I would not have expected this behavior now (last phase of OS). >>>

Am 30.08.2018 um 20:28 schrieb Simon Matter <simon.matter at invoca.ch>: > Am 30.08.2018 um 12:16 schrieb Leon Fauster <leonfauster at googlemail.com>: >> >> BTW upstream bug report: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1623692 > > Well, I have an account and am logged in, still can not see the bug. It seems that the default bugzilla

> >>> Does some one have problems related to KVM with > >>> kernel-2.6.32-754.3.5.el6.x86_64 ?? > >> > >> Yes, the exact same thing happened here, and I suspect it is related to > >> older cpus that don't get any Spectre/Meltdown updates. > > > > > > Thanks for the feedback. I' was assuming that some kind of > >

> Am 30.08.2018 um 17:24 schrieb Simon Matter <simon.matter at invoca.ch>: > >> Am 30.08.2018 um 06:37 schrieb Simon Matter <simon.matter at invoca.ch>: >>> >>>> Since the update from kernel-2.6.32-754.2.1.el6.x86_64 >>>> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my >>>> KVM guests anymore!? The workstation panics

Am 30.08.2018 um 06:37 schrieb Simon Matter <simon.matter at invoca.ch>: > >> Since the update from kernel-2.6.32-754.2.1.el6.x86_64 >> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my >> KVM guests anymore!? The workstation panics immediately! >> >> I would not have expected this behavior now (last phase of OS). >> It was very robust until now

kernel 2.6.32-279.9.1.el6.x86_64 does not build from the source rpm's using the UNmodified config file and following the directions explicitly. Previous kernels build fine from the same directions. A little help from the developers would be greatly appreciated. while building I get this output: c1: warnings being treated as errors drivers/base/platform.c:621: error:

Is this now fixed in the latest release by updating the hypervisor, the same as CentOS 7? Or does this require something further? I came across https://access.redhat.com/solutions/3312501 which seems to suggest Redhat are working on resolving the issue, so if that's the case then maybe the solution implemented by CentOS is not the best option? Kind Regards, Dan -------------- next part