similar to: possible issue with nvidia and new patches?

Displaying 20 results from an estimated 110 matches similar to: "possible issue with nvidia and new patches?"

2018 Jan 04
0
possible issue with nvidia and new patches?
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" >
2018 Jan 07
2
CentOS 7.4 fails to boot as Xen PV guest: resurfaces (now also) with centosplus kernel 693.11.6.el7
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,
2018 Jan 04
2
CentOS-virt - Kernel Side-Channel Attacks
On 01/04/2018 10:49 AM, Akemi Yagi wrote: > On Thu, Jan 4, 2018 at 9:51 AM, <rikske at deds.nl> wrote: > >> Please patch the CentOS-virt Kernel to fix the >> Kernel Side-Channel Attacks vulnerabilities. >> >> The latest CentOS-virt kernel was released in November, as seen below. >> >> kernel-4.9.63-29.el7.x86_64.rpm 2017-11-21 13:30 >>
2019 Mar 08
2
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
On Thu, Mar 07, 2019 at 10:16:00PM -0500, Michael S. Tsirkin wrote: > On Thu, Mar 07, 2019 at 09:55:39PM -0500, Jerome Glisse wrote: > > On Thu, Mar 07, 2019 at 09:21:03PM -0500, Michael S. Tsirkin wrote: > > > On Thu, Mar 07, 2019 at 02:17:20PM -0500, Jerome Glisse wrote: > > > > > It's because of all these issues that I preferred just accessing > > >
2019 Mar 08
2
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
On Thu, Mar 07, 2019 at 10:16:00PM -0500, Michael S. Tsirkin wrote: > On Thu, Mar 07, 2019 at 09:55:39PM -0500, Jerome Glisse wrote: > > On Thu, Mar 07, 2019 at 09:21:03PM -0500, Michael S. Tsirkin wrote: > > > On Thu, Mar 07, 2019 at 02:17:20PM -0500, Jerome Glisse wrote: > > > > > It's because of all these issues that I preferred just accessing > > >
2018 Jan 06
3
PEM file opened without DIRECT I/O which makes private key readable by attacker exploiting MELTDOWN
On Sat, Jan 6, 2018 at 5:38 PM, Philipp Marek <philipp at marek.priv.at> wrote: > I think we are possibly interested in switching to DIRECT IO (given that it >> bypasses any caching system including page cache) when reading *.PEM file >> > Sorry, but this makes no sense. > The data could just as well be read from the SSH process > memory space. > I think
2013 Apr 05
2
ClassicUpgrade => EpicFail
ClassicUpgrade of my samba3 data to samba4 fails, with this error: ERROR(<class 'passdb.error'>): uncaught exception - Unable to get id for sid Full log of the classicupgrade is at the end of this email. Project member on this list, Andrew Barlett, wrote that the issue is probably that my Samba 3 passdb was passable in an NT 4 DC mode, but is actually 'invalid' :
2018 Jan 08
1
C6 KPTI cpuinfo flag?
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.
2019 Jul 08
3
[PATCH v8 00/11] x86: PIE support to extend KASLR randomization
Splitting the previous serie in two. This part contains assembly code changes required for PIE but without any direct dependencies with the rest of the patchset. Changes: - patch v8 (assembly): - Fix issues in crypto changes (thanks to Eric Biggers). - Remove unnecessary jump table change. - Change author and signoff to chromium email address. - patch v7 (assembly): - Split patchset
2019 Jul 08
3
[PATCH v8 00/11] x86: PIE support to extend KASLR randomization
Splitting the previous serie in two. This part contains assembly code changes required for PIE but without any direct dependencies with the rest of the patchset. Changes: - patch v8 (assembly): - Fix issues in crypto changes (thanks to Eric Biggers). - Remove unnecessary jump table change. - Change author and signoff to chromium email address. - patch v7 (assembly): - Split patchset
2018 Jan 06
1
CentOS-virt - Kernel Side-Channel Attacks
On 01/05/2018 06:33 AM, George Dunlap wrote: > On Thu, Jan 4, 2018 at 7:12 PM, Sarah Newman <srn at prgmr.com> wrote: >> On 01/04/2018 10:49 AM, Akemi Yagi wrote: >>> On Thu, Jan 4, 2018 at 9:51 AM, <rikske at deds.nl> wrote: >>> >>>> Please patch the CentOS-virt Kernel to fix the >>>> Kernel Side-Channel Attacks vulnerabilities.
2019 Mar 08
1
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
On Thu, Mar 07, 2019 at 10:43:12PM -0500, Michael S. Tsirkin wrote: > On Thu, Mar 07, 2019 at 10:40:53PM -0500, Jerome Glisse wrote: > > On Thu, Mar 07, 2019 at 10:16:00PM -0500, Michael S. Tsirkin wrote: > > > On Thu, Mar 07, 2019 at 09:55:39PM -0500, Jerome Glisse wrote: > > > > On Thu, Mar 07, 2019 at 09:21:03PM -0500, Michael S. Tsirkin wrote: > > > >
2019 Mar 08
1
[RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
On Thu, Mar 07, 2019 at 10:43:12PM -0500, Michael S. Tsirkin wrote: > On Thu, Mar 07, 2019 at 10:40:53PM -0500, Jerome Glisse wrote: > > On Thu, Mar 07, 2019 at 10:16:00PM -0500, Michael S. Tsirkin wrote: > > > On Thu, Mar 07, 2019 at 09:55:39PM -0500, Jerome Glisse wrote: > > > > On Thu, Mar 07, 2019 at 09:21:03PM -0500, Michael S. Tsirkin wrote: > > > >
2018 Feb 07
5
Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
On 07.02.2018 16:31, Kashyap Chamarthy wrote: > [Cc: KVM upstream list.] > > On Tue, Feb 06, 2018 at 04:11:46PM +0100, Florian Haas wrote: >> Hi everyone, >> >> I hope this is the correct list to discuss this issue; please feel >> free to redirect me otherwise. >> >> I have a nested virtualization setup that looks as follows: >> >> - Host:
2017 Nov 06
6
Nvidia error
I am getting this error on CentOS 7.4 kernel: NVRM: API mismatch: the client has the version 384.98, but#012NVRM: this kernel module has the version 384.90. Please#012NVRM: make sure that this kernel module and all NVIDIA driver#012NVRM: components have the same version nvidia-detect -v Probing for supported NVIDIA devices... [10de:1288] NVIDIA Corporation GK208 [GeForce GT 720] This device
2018 Feb 08
5
Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
>> In short: there is no (live) migration support for nested VMX yet. So as >> soon as your guest is using VMX itself ("nVMX"), this is not expected to >> work. > > Hi David, thanks for getting back to us on this. Hi Florian, (sombeody please correct me if I'm wrong) > > I see your point, except the issue Kashyap and I are describing does > not
2018 Jan 09
3
CentOS Linux 7 (1708) AltArch i386 Kernel
Red Hat no longer maintains the i386 kernel for RHEL 7.4.? We have been using a modified kernel until this latest meltdown / spectre? release (*kernel-3.10.0-693.11.6.el7*). This latest release does not build on i386/i686 and we can't figure out how to make it work.? Build try: https://buildlogs.centos.org/c7.1708.u.i386/kernel/20180109171431/3.10.0-693.11.6.el7.centos.plus.i386/ SRPM:
2018 Jan 03
3
Nvidia maximum pixel clock issue in kmod-nvidia-384.98
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
2018 Jan 06
2
Nvidia maximum pixel clock issue in kmod-nvidia-384.98
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
2018 Jan 12
1
Is kernel-3.10.0-693.11.6.el7 tested with old hardware?
Today we tried to update machines w/ Core2 Duo E6750 from 3.10.0-693.11.1.el7.centos.plus to 3.10.0-693.11.6.el7.centos.plus and the machines did not boot due to a kernel panic. Before we dig any further I wanted to know if the 11.6 kernel has been tested on old hardware, too, or if the problem is well known but not documented (yet). Thank you in advance! Gerhard Schneider -- Gerhard