The 4.5.7-202 kernel update contains a number of important security fixes.
sudo dnf upgrade --advisory=FEDORA-2016-73a733f4d9
This update has been submitted for testing by jforbes.
This update has been pushed to testing.
Works good on x86_64. Memory consumption has increased by 200 MB against 4.4.9.
WFM, Thinkpad X250 i7 (Broadwell, Intel graphics)
works for me
This update has been submitted for stable by bodhi.
Works for me x86_64.
Please note that this kernel version (4.5.7) is EOL
This update has been pushed to stable.
Works for me x86_64 VM.
No stability issues encountered till now.
doesn't boot on Samsung Notebook 9 (skylake, intel gfx) whereas -200 does. No kernel output even after removing 'rhgb quiet' from kernel commandline.
[root@f23 vboxdrv]# make
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vboxhost/vboxdrv SRCROOT=/tmp/vboxhost/vboxdrv CONFIG_MODULE_SIG= -C /lib/modules/4.6.3-200.fc23.x86_64/build modules
make: Entering directory '/usr/src/kernels/4.6.3-200.fc23.x86_64'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
mkdir -p /tmp/vboxhost/vboxdrv/.tmp_versions ; rm -f /tmp/vboxhost/vboxdrv/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/tmp/vboxhost/vboxdrv
make: *** No rule to make target '/tmp/vboxhost/vboxdrv/linux/SUPDrv-linux.o', needed by '/tmp/vboxhost/vboxdrv/vboxdrv.o'. Stop.
Makefile:1433: recipe for target '_module_/tmp/vboxhost/vboxdrv' failed
make: *** [_module_/tmp/vboxhost/vboxdrv] Error 2
make: Leaving directory '/usr/src/kernels/4.6.3-200.fc23.x86_64'
Makefile:298: recipe for target 'vboxdrv' failed
make: *** [vboxdrv] Error 2
CONFIG_HAVE_STACK_VALIDATION=y and no objtool?
Sorry, This is for kernel version is 4.6.3-200.fc23.x86_64.
@anonymous: for the sake of god type "dnf install fedora-easy-karma" so you can't comment the wrong builds and if you are at it realize that vbox is out of scope for Fedora and so you MUST NOT give negative karma (i am also not happy that with 4.6.3 currently vmware modules don't build and the workarounds found are not working but that NOT JUSTIFIES a negative karma for the fedora-kernel)
@hreindl: I was was clicking the wrong kernel version link, OK? That happens when you do several things at once (develop software when the deadline is approaching fast, argue with QA team, submit bug reports, etc.) :-( Not my intention to give negative karma to a perfectly stable kernel. Since I cannot edit/delete my post - there is nothing else I can do but say I'm really, really sorry.
and HENCE use fedora-easy-karma because it only asks for packages which are INSTALLED and in update-testing so you can't overlook anything, especially in cases where a -37 or so build fixes a specific bug and may introduce a regeression not present in the next and previous builds
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.