search for: kabi

I?m trying to build a 2.6.18-128.1.6.el5 kernel without kabichk. I have downloaded the sources, installed the compiler, etc and ran the following command rpmbuild -bb --target=`uname -m` --without kabichk --with baseonly --without debug \ --without debuginfo kernel-2.6.spec. I had modified the .SPEC file according to the WIKI page http://wiki.centos...

...; http://centos.toracat.org/kmods/CentOS-4/xfs/SRPMS/ >> >> Please discard the obsoleted ones (I did not bump the version/release >> number). ?Let me know when your binaries are ready for testing. >> > rebuilds and uploaded. * Downloaded from http://people.centos.org/tru/kABI/4/RPMS/ and did some test installs. First, installed the kernel version specific kmod-xfs-0.4-1.el4.2.6.9_78.0.22 to the test box and then installed the current kABI-tracking kmod-xfs-0.4-2.el4. It successfully replaced the xfs.ko installed by the former and created symlinks to other installed ke...

...ta and Enhancement Advisory 2013:0485 Upstream details at : https://rhn.redhat.com/errata/RHEA-2013-0485.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 38fc59ea17e6fb9838ef53e5e16a7ea67e3c575ff210d01dc29ecedf4602b900 kabi-whitelists-20130129-1.el6.centos.noarch.rpm 9d4970d5a6c0ceeeef7e11068afd04f61477d30038b5da333ecd3b7898a50fd1 ksc-20130129-1.el6.centos.noarch.rpm x86_64: 38fc59ea17e6fb9838ef53e5e16a7ea67e3c575ff210d01dc29ecedf4602b900 kabi-whitelists-20130129-1.el6.centos.noarch.rpm 9d4970d5a6c0ceeeef7e11068afd...

On Tue, Jan 1, 2019 at 5:30 PM Jan Vlietland <j.vlietland at nisi.nl> wrote: > > Hi Ilia, many thanks for answering my mail. > > Tonight I tried to see what happens if I generate a xorg.conf file and place it in /etc/X11/xorg.conf, as described here: > https://askubuntu.com/questions/4662/where-is-the-x-org-config-file-how-do-i-configure-x-there > > When I do that X

Hi Ilia, many thanks for answering my mail. Tonight I tried to see what happens if I generate a xorg.conf file and place it in /etc/X11/xorg.conf, as described here: https://askubuntu.com/questions/4662/where-is-the-x-org-config-file-how-do-i-configure-x-there When I do that X starts without the framebuffer error. X starts with a backtrace list in the shell and then stops with the error:

...and it gave me: Wrote: ~/kend/rpmbuild/SRPMS/kvm-kmod-36-1.2.6.18_194.11.4.el5.1.x64.src.rpm I guess it all comes down to experience. Being not to familiar with rpmbuild I did not know you could do that. Thanks for the tip! >kmod-kvm is built from kvm and it is kernel version independent, >kABI-tracking. This means that, if your custom kernel is kABI >compatible with the distro kernel, the kvm module will continue to >work. I wish that was better documented. So as long as I have kABI checking enabled when I build my custom I should be golden? I apparently did not fully understand...

Hi, I'm having a problem compiling the kernel as a normal user (don't know if not being root is the problem or not). What is ABI? I can compile with the flag --without kabichk, but I don't know if really is that the solution or not. The package build stops at this point: + echo '**** kABI checking is enabled in kernel SPEC file. ****' **** kABI checking is enabled in kernel SPEC file. **** + chmod 0755 /home/samueldg/rpmbuild/SOURCES/check-kabi + '[&...

...lib/modules/2.6.18- 53.el5.nx + make -s ARCH=x86_64 INSTALL_MOD_PATH=/var/tmp/kernel-2.6.18-53.el5.nx-rootmodules_install KERNELRELEASE= 2.6.18-53.el5.nx + echo '**** GENERATING kernel ABI metadata ****' **** GENERATING kernel ABI metadata **** + gzip -c9 + chmod 0755 /home/rpmbuild/SOURCES/kabitool + '[' '!' -e /home/rpmbuild/SOURCES/kabi_whitelist_x86_64 ']' + cp /home/rpmbuild/SOURCES/kabi_whitelist_x86_64 /var/tmp/kernel- 2.6.18-53.el5.nx-root/kabi_whitelist + rm -f /var/tmp/kernel-2.6.18-53.el5.nx-kabideps + /home/rpmbuild/SOURCES/kabitool -b . -d /var/tmp/kern...

On Tue, Jan 1, 2019 at 4:06 PM Jan Vlietland <j.vlietland at nisi.nl> wrote: > > Hi Ben, David and Daniel , > > First of all happy new year. Based on advice of Greg K-H herewith a mail > about a number of Nouveau issues with my laptop. > > I installed various Kali linux versions up to Linux 4.20.0-rc7 > (downloaded, compiled and installed) on a Samsung NP900X5N laptop

I got a new laptop as my old one died: an HP Probook 470 G4.? I installed Centos 7 1511. The laptop has a Kaby Lake i5 CPU and an? 01:00.0 3D controller: NVIDIA Corporation Device 134e (rev a2).? Fedora recognizes it as a GM108M/930MX. This may give some hints, but it is not that the standard kernel does not support it, this output comes from the 4.8.7 mainline kernel which should support this

Hi Ben, David and Daniel , First of all happy new year. Based on advice of Greg K-H herewith a mail about a number of Nouveau issues with my laptop. I installed various Kali linux versions up to Linux 4.20.0-rc7 (downloaded, compiled and installed) on a Samsung NP900X5N laptop and have an issue with the driver after loading. My configuration: - i7 7500 - 16 gb / 256 gb ssd - nvidia 940MX

On Sat, 2016-11-12 at 15:34 -0500, Fred Smith wrote: > On Sat, Nov 12, 2016 at 09:15:22PM +0100, Louis Lagendijk wrote: > > > > I got a new laptop as my old one died: an HP Probook 470 G4.? > > I installed Centos 7 1511. > > The laptop has a Kaby Lake i5 CPU and an? > > 01:00.0 3D controller: NVIDIA Corporation Device 134e (rev a2).? > > Fedora recognizes it

Hi, the topic is an excerpt of the 5.4 release notes and raises a question. I have a i386 server here, that has been running for nearly two years with xfs module from extras repo. When lookin at the module it was build against 2.6.18-92.1.13.el5. Question is, is it still safe to use this module with 5.4? Or should I switch back to a CentosPlus kmod and an older kernel? Rainer

...s get added to new kernels. What's the correct way to get this device added to the kernel? Do I submit my patch to the CentOS dev team, to the kernel.org folks, or both? What's the timeline (if accepted) to actually seeing this in a production kernel? On the CentOS kernel build how-to, the kABI fixes won't make it into CentOS until 5.4, and 5.3 hasn't been released yet. Thanks in advance... Regards, Chris

On Mon, 2016-11-14 at 06:48 -0600, Johnny Hughes wrote: > On 11/12/2016 02:39 PM, Louis Lagendijk wrote: > > > > On Sat, 2016-11-12 at 15:34 -0500, Fred Smith wrote: > > > > > > On Sat, Nov 12, 2016 at 09:15:22PM +0100, Louis Lagendijk wrote: > > > > > > > > > > > > I got a new laptop as my old one died: an HP Probook 470

Hi, I would like to announce a set of OCFS2 kABI-tracking kernel module packages for RHEL5, Scientific Linux 5 and CentOS-5 and kernels. These packages have been introduced into the ELRepo testing repository (http://elrepo.org/). You can find these packages at: http://elrepo.org/linux/testing/el5/ The ELRepo project is a community projec...

Hi, I would like to announce a set of OCFS2 kABI-tracking kernel module packages for RHEL5, Scientific Linux 5 and CentOS-5 and kernels. These packages have been introduced into the ELRepo testing repository (http://elrepo.org/). You can find these packages at: http://elrepo.org/linux/testing/el5/ The ELRepo project is a community projec...

On Mon, Sep 09, 2019 at 03:19:55PM +0800, Jason Wang wrote: > > On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: > > iovec addresses coming from vhost are assumed to be > > pre-validated, but in fact can be speculated to a value > > out of range. > > > > Userspace address are later validated with array_index_nospec so we can > > be sure kernel info does not

On Mon, Sep 09, 2019 at 03:19:55PM +0800, Jason Wang wrote: > > On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: > > iovec addresses coming from vhost are assumed to be > > pre-validated, but in fact can be speculated to a value > > out of range. > > > > Userspace address are later validated with array_index_nospec so we can > > be sure kernel info does not

https://bugzilla.mindrot.org/show_bug.cgi?id=3194 Bug ID: 3194 Summary: Please consider lowering chacha20-poly1305 at openssh.com cipher priority on AES-NI capable CPU Product: Portable OpenSSH Version: 8.3p1 Hardware: amd64 OS: Linux Status: NEW Severity: enhancement