To: CentOS mailing list <centos@xxxxxxxxxx>
Thema: Re: Nvidia maximum pixel clock issue in
kmod-nvidia-384.98
Dear All,
Start BIOS Configuration and go to Graphic Configuration change On Board
VGA to PCI Express x16
Automatic is VGA on Board
Bis bald
Alexander
Am 09.01.2018 um 13:00 schrieb centos-request@xxxxxxxxxx:
Send CentOS mailing list submissions to
centos@xxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos
or, via email, send a message with subject or body 'help' to
centos-request@xxxxxxxxxx
You can reach the person managing the list at
centos-owner@xxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS digest..."
Today's Topics:
1. Re: CentOS 7.4 fails to boot as Xen PV guest: resurfaces (now
also) with centosplus kernel 693.11.6.el7 (Johnny Hughes)
2. Re: Nvidia maximum pixel clock issue in kmod-nvidia-384.98
(Phil Perry)
3. C6 KPTI cpuinfo flag? (Robert Arkiletian)
4. Re: C6 KPTI cpuinfo flag? (isdtor)
5. Cent OS 7.3 Shared library issue (Aman Sharma)
----------------------------------------------------------------------
Message: 1
Date: Mon, 8 Jan 2018 06:46:31 -0600
From: Johnny Hughes <johnny@xxxxxxxxxx>
To: centos@xxxxxxxxxx
Subject: Re: CentOS 7.4 fails to boot as Xen PV guest:
resurfaces (now also) with centosplus kernel 693.11.6.el7
Message-ID: <dda9a351-3260-647c-b4f0-5c00f6b3bfd5@xxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
On 01/08/2018 12:38 AM, Akemi Yagi wrote:
On Sun, Jan 7, 2018 at 12:07 PM, David Groep <davidg@xxxxxxxxx> 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 maybe in a
different way ...
Thanks to the (great!) quick work on making the plus kernel available
(in #14330, thanks for that!) I was able to test the following
combinations:
- 3.10.0-693.11.6.el7.centos.plus works fine on XenServer 7 HVM guests
- 3.10.0-693.11.1.el7.centos.plus works fine on XenServer 7 XenPV guests
- 3.10.0-693.11.6.el7.centos.plus crashes on boot for XS7 XenPV guests
immediately after the boot stage where the PS/2 drivers are loaded
Crashing does not depend on the amount of VM memory or #cores/sockets.
Also, the tell-tale "mm/vmalloc.c" failure output is no longer present.
The system 'just' crashes (with the kernel log lines as below) around the
time of the i8042 controller probing.
Obviously the stock upstream 3.10.0-693.11.6.el7 crashes as well for
XS7 XenPV guests, but that was to be expected as per 0013763.
It crashes in the same way, around the time of the i8042 probes.
Can anyone (maybe bill_mcgonigle?) reproduce the issue?
Did the KPTI patches break the XenPV fixes in CentOS Plus per 13763?
Or is this a new XenPV issue?
?You may want to be watching the centos-virt mailing list. Xen-related
issues are discussed there.
This thread:
?
https://lists.centos.org/pipermail/centos-virt/2018-January/005716.html
?has a response from Johnny Hughes with a possible solution.
And specifically, this message has links to the 4.9.75 x86_64 kernel
that will boot and run as a Xen PV kernel:
https://lists.centos.org/pipermail/centos-virt/2018-January/005721.html
Also, the latest Xen Dom0 kernel 4.9.75 kernel will also boot a DomU Xen
PV. That kernel is still in testing, and also requires the latest
linux-firmware rpms:
https://buildlogs.centos.org/centos/7/virt/x86_64/
or
https://buildlogs.centos.org/centos/6/virt/x86_64/
(And your xen version ... xen-44/, xen-46/, xen-48/)
Those kernels should be signed released to the main Xen repo sometime
this week.
And as someone has mentioned in another thread (Phil Perry), please read
Greg K-H's (the Kernel.org LTS maintainer, he is in charge of the 4.9.x
LTS tree that we use for the above kernels):
http://www.kroah.com/log/blog/2018/01/06/meltdown-status/
Thanks,
Johnny Hughes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.centos.org/pipermail/centos/attachments/20180108/d7fcd69f/attachment-0001.sig>
------------------------------
Message: 2
Date: Mon, 8 Jan 2018 21:33:44 +0000
From: Phil Perry <pperry@xxxxxxxxxx>
To: centos@xxxxxxxxxx
Subject: Re: Nvidia maximum pixel clock issue in
kmod-nvidia-384.98
Message-ID: <4a6548b4-a8e9-6622-0c93-679e6a454c34@xxxxxxxxxx>
Content-Type: text/plain; charset=utf-8; format=flowed
On 08/01/18 10:22, Danny Smit wrote:
On Sat, Jan 6, 2018 at 2:27 PM, Phil Perry <pperry@xxxxxxxxxx> 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.
Thanks for the feedback Danny - glad we got it resolved.
------------------------------
Message: 3
Date: Mon, 8 Jan 2018 15:03:58 -0800
From: Robert Arkiletian <robark@xxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Subject: C6 KPTI cpuinfo flag?
Message-ID:
<CAN_+rpJQbsNnyEdETOrnFtkSziGTVm0ZwSc5QQBsvqoAv8kjxg@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
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.
------------------------------
Message: 4
Date: Tue, 9 Jan 2018 09:44:16 +0000
From: isdtor <isdtor@xxxxxxxxx>
To: centos@xxxxxxxxxx
Subject: Re: C6 KPTI cpuinfo flag?
Message-ID: <20180109094416.GA72537@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Robert Arkiletian writes:
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.
None that I know of, but check out https://access.redhat.com/articles/3311301.
------------------------------
Message: 5
Date: Tue, 9 Jan 2018 16:14:47 +0530
From: Aman Sharma <amansh.sharma5@xxxxxxxxx>
To: centos@xxxxxxxxxx
Subject: Cent OS 7.3 Shared library issue
Message-ID:
<CAPMH7-_LyGCq5GeqJkTfemggFpNy-w8SMViBELHADN6p04AY1A@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="UTF-8"
Hi Guys,
I am using my native library to run but during runtime, its picking the
default library i.e. /usr/lib/libssl. Due to this, my application crashes.
But after adding the Soft link for my native library, its working fine.
Can anybody Please let me know why its not working without adding softlink
in cent os 7.3.
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
