similar to: Nvidia maximum pixel clock issue in, , kmod-nvidia-384.98

On Sun, Jan 7, 2018 at 12:07 PM, David Groep <davidg at nikhef.nl> wrote: > Dear all, > > Maybe I'm the only one - so before filing it as a bug: it appears that > the latest set of kernel patches in 3.10.0-693.11.6.el7 makes issue > 0013763 "CentOS 7.4 kernel (3.10.0-693*) fails to boot as Xen PV guest" > re-surface *also* with the CentOS PLUS kernel. But

Dear all, Maybe I'm the only one - so before filing it as a bug: it appears that the latest set of kernel patches in 3.10.0-693.11.6.el7 makes issue 0013763 "CentOS 7.4 kernel (3.10.0-693*) fails to boot as Xen PV guest" re-surface *also* with the CentOS PLUS kernel. But maybe in a different way ... Thanks to the (great!) quick work on making the plus kernel available (in #14330,

Noticed C6 had a kernel update on Friday. 2.6.32-696.18.7.el6.x86_64 What is the flag in /proc/cpuinfo that indicates the KPTI patch for Meltdown CVE-2017-5754 for C6? Some distros are using "kaiser" some like Fedora are using "pti". Also noticed some (like Fedora) are displaying "cpu_insecure" under the bugs: heading of cpuinfo.

On 06/01/18 12:00, Zube wrote: > On Sat Jan 06 12:27:22 PM, Danny Smit wrote: > >> I normally certainly prefer the stability of the long-lived releases. >> I noticed an update was just released of the long-lived release: >> 384.111. The notes for this release say: >> >> Fixed a regression that prevented displays connected via some >> types

On Sat Jan 06 12:27:22 PM, Danny Smit wrote: > I normally certainly prefer the stability of the long-lived releases. > I noticed an update was just released of the long-lived release: > 384.111. The notes for this release say: > > Fixed a regression that prevented displays connected via some > types of passive adapters (e.g. DMS-59 to VGA or DVI) from working >

On Thu, Jan 4, 2018 at 9:40 PM, Phil Perry <pperry at elrepo.org> wrote: > Normally elrepo only releases the long term branch for Enterprise Linux, on > the assumption EL users will welcome the implied stability over more > frequent and potentially buggy releases. > In this case I had built the current short lived release as a user requested > it for compatibility with the

On Sat, Jan 6, 2018 at 2:27 PM, Phil Perry <pperry at elrepo.org> wrote: > > I've just built and released 384.111 to the elrepo main repository, so it > should show up on the mirrors shortly. As expected, the 384.111 also solves the problem in my case. Thanks for the support everyone. Regards, Danny

On 03/01/18 20:14, Zube wrote: > On Wed Jan 03 07:43:04 PM, Phil Perry wrote: > >>> On CentOS 7 I'm running into an issue with the latest nvidia driver >>> from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 >>> This driver version seem to introduce issue in detecting video modes >>> when a monitor is connected using DVI. As soon as the machine

On Thu, Jan 4, 2018 at 5:22 AM, Phil Perry <pperry at elrepo.org> wrote: > On 03/01/18 20:14, Zube wrote: >> >> I can confirm that this happens with the driver downloaded from NVIDIA. >> I had to fall back to the .90 driver to get it to work for all my >> NVS 315s (with dual DVI) running on 7.4 / 6.9. Thanks. For reference, I did the same test. With the driver

On 03/01/18 15:45, Danny Smit wrote: > Hi everyone, > > On CentOS 7 I'm running into an issue with the latest nvidia driver > from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 > This driver version seem to introduce issue in detecting video modes > when a monitor is connected using DVI. As soon as the machine attempts > to start X, nothing happens and the monitor goes

On Wed Jan 03 07:43:04 PM, Phil Perry wrote: > > On CentOS 7 I'm running into an issue with the latest nvidia driver > > from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 > > This driver version seem to introduce issue in detecting video modes > > when a monitor is connected using DVI. As soon as the machine attempts > > to start X, nothing happens and the

On 04/01/18 09:12, Danny Smit wrote: > On Thu, Jan 4, 2018 at 5:22 AM, Phil Perry <pperry at elrepo.org> wrote: >> On 03/01/18 20:14, Zube wrote: >>> >>> I can confirm that this happens with the driver downloaded from NVIDIA. >>> I had to fall back to the .90 driver to get it to work for all my >>> NVS 315s (with dual DVI) running on 7.4 / 6.9.

Hi everyone, On CentOS 7 I'm running into an issue with the latest nvidia driver from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 This driver version seem to introduce issue in detecting video modes when a monitor is connected using DVI. As soon as the machine attempts to start X, nothing happens and the monitor goes into sleep mode reporting that it has 'no signal'. It is

On Thu, 4 Jan 2018, Zube wrote: > Twitter user stintel, in this thread: > > https://twitter.com/stintel/status/948499157282623488 > > mentions a possible problem with the new patches and the > nvidia driver: > > "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver > incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" >

Twitter user stintel, in this thread: https://twitter.com/stintel/status/948499157282623488 mentions a possible problem with the new patches and the nvidia driver: "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" Also: https://twitter.com/tomasz_gwozdz/status/948590364679655429

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

Hi, Me and another sysadmin has independently been researching a problem where DomU randomly locks (Can’t reach it via xl console, no ping / SSH connection, shown as stuck in running-state in xentop) on two of our separate machines (installed completely independently): Dom0: Debian 7.0 with Xen version: 4.1.4 and xen-utils 4.1.4-3+deb7u1 Debian 7.1 with Xen version: 4.1 DomU: 7.0 7.1(.3)

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://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

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19