Kernel – ‘Urgent’? 4.13 Update Released – 4.13.7..

Kernel 4.13.6 has only been out for two days, but there has just been another update – 4.13.7 – with the following changes:  https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.13.7

If you are running 4.13.6, then update is – presumably – recommended ASAP!

Robert Gadsdon.   October 14, 2017.


Comments

Kernel – ‘Urgent’? 4.13 Update Released – 4.13.7.. — 1 Comment

  1. This might be OBE, but a quick search did not turn it up, so I had to figure it on my own. If it’s already been posted, my apologies for the noise.

    archlinux with kernel 4.13.7-1, vmware workstation pro 12.5.7, I’m getting a warning that turns into an error:

    CC [M] /tmp/modconfig-xNswE2/vmnet-only/userif.o
    /tmp/modconfig-xNswE2/vmnet-only/userif.c: In function ‘VNetUserIfRead’:
    /tmp/modconfig-xNswE2/vmnet-only/userif.c:744:11: error: implicit declaration of function ‘signal_pending’; did you mean ‘timer_pending’? [-Werror=implicit-function-declaration]
    if (signal_pending(current)) {
    ^~~~~~~~~~~~~~
    timer_pending
    cc1: some warnings being treated as errors

    There’s a signal_pending() in build/include/linux/sched/signal.h, so I edited an include into userif.c, and modconfig goes to completion.

    I also had to edit vm_device_version.h to set:

    PCI_VENDOR_ID_VMWARE -> 0x15ad

    and

    PCI_DEVICE_ID_VMWARE_VMXNET3 -> 0x07b0

    because the compiler insists that 0x15AD redefines 0x15ad etc.

    Now the GUI starts, but when I try to resume the VM, the GUI pops up an error panel telling me to increase the amount of memory for all VMs to 2304M (or sumpthin’). Considering that I’ve reserved 16384M for all virtual machines (this is the only VM I’m trying to run), and 4M for *this* VM – a *32b* Win7SP1 VM – this does not seem intuitive.

    Mebbe this is the vmmon, uh, feature I see talked about.

    grrr.

Leave a Reply

Your email address will not be published. Required fields are marked *