Ubuntu 17.10 - Kernel 4.13.0 - dkms does not build

[drohm]

Upgraded my Ubuntu Budgie 17.04 system to Ubuntu Budgie 17.10, which has updated kernel 4.13.0-16. I had to add veeamsnap via dkms and it's failing on build (sudo dkms build -m veeamsnap -v 1.0.1.364). Log output is below:

Code: Select all

DKMS make.log for veeamsnap-1.0.1.364 for kernel 4.13.0-16-generic (x86_64)
Sun Oct 22 18:15:17 EDT 2017
make: Entering directory '/usr/src/linux-headers-4.13.0-16-generic'
  AR      /var/lib/dkms/veeamsnap/1.0.1.364/build/built-in.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_array_1lv.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_bitmap.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/container.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/container_spinlocking.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/queue_spinlocking.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/bitmap_sync.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/log.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/page_array.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/rangeset.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/rangelist.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/cbt_map.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/rangevector.o
  CC [M]  /var/lib/dkms/veeamsnap/1.0.1.364/build/defer_io.o
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c: In function ‘dbg_kmalloc_huge’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c:138:55: error: ‘__GFP_REPEAT’ undeclared (first use in this function); did you mean ‘__GFP_RECLAIM’?
   ptr = dbg_kmalloc( max_size, flags | __GFP_NOWARN | __GFP_REPEAT);
                                                       ^~~~~~~~~~~~
                                                       __GFP_RECLAIM
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c:138:55: note: each undeclared identifier is reported only once for each function it appears in
In file included from /var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.c:7:0:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.h: In function ‘blk_bio_end’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.h:77:7: error: ‘struct bio’ has no member named ‘bi_error’; did you mean ‘bi_iter’?
  bio->bi_error = err;
       ^~~~~~~~
       bi_iter
/var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.c: In function ‘dio_bioset_create’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.c:113:16: error: too few arguments to function ‘bioset_create’
  dio_bio_set = bioset_create( 64, sizeof( dio_bio_complete_t ) );
                ^~~~~~~~~~~~~
In file included from ./include/linux/blkdev.h:20:0,
                 from /var/lib/dkms/veeamsnap/1.0.1.364/build/stdafx.h:10,
                 from /var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.c:1:
./include/linux/bio.h:390:24: note: declared here
 extern struct bio_set *bioset_create(unsigned int, unsigned int, int flags);
                        ^~~~~~~~~~~~~
/var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.c: In function ‘dio_bio_end_io’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.c:170:20: error: ‘struct bio’ has no member named ‘bi_error’; did you mean ‘bi_iter’?
   local_err = bio->bi_error;
                    ^~~~~~~~
                    bi_iter
scripts/Makefile.build:302: recipe for target '/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o' failed
make[1]: *** [/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o] Error 1
make[1]: *** Waiting for unfinished jobs....
In file included from /var/lib/dkms/veeamsnap/1.0.1.364/build/defer_io.c:9:0:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.h: In function ‘blk_bio_end’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.h:77:7: error: ‘struct bio’ has no member named ‘bi_error’; did you mean ‘bi_iter’?
  bio->bi_error = err;
       ^~~~~~~~
       bi_iter
scripts/Makefile.build:302: recipe for target '/var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.o' failed
make[1]: *** [/var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.o] Error 1
scripts/Makefile.build:302: recipe for target '/var/lib/dkms/veeamsnap/1.0.1.364/build/defer_io.o' failed
make[1]: *** [/var/lib/dkms/veeamsnap/1.0.1.364/build/defer_io.o] Error 1
In file included from /var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.c:4:0:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.h: In function ‘blk_bio_end’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.h:77:7: error: ‘struct bio’ has no member named ‘bi_error’; did you mean ‘bi_iter’?
  bio->bi_error = err;
       ^~~~~~~~
       bi_iter
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.c: In function ‘blk_bioset_create’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.c:11:16: error: too few arguments to function ‘bioset_create’
  blk_bio_set = bioset_create( 64, sizeof( tracking_bio_complete_t ) );
                ^~~~~~~~~~~~~
In file included from ./include/linux/blkdev.h:20:0,
                 from /var/lib/dkms/veeamsnap/1.0.1.364/build/stdafx.h:10,
                 from /var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.c:1:
./include/linux/bio.h:390:24: note: declared here
 extern struct bio_set *bioset_create(unsigned int, unsigned int, int flags);
                        ^~~~~~~~~~~~~
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.c: In function ‘tracking_bio_end_io’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.c:43:26: error: ‘struct bio’ has no member named ‘bi_error’; did you mean ‘bi_iter’?
   bio_compl->error = bb->bi_error;
                          ^~~~~~~~
                          bi_iter
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.c: In function ‘tracking_redirect_bio_endio’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.c:267:17: error: ‘struct bio’ has no member named ‘bi_error’; did you mean ‘bi_iter’?
   int err = bb->bi_error;
                 ^~~~~~~~
                 bi_iter
scripts/Makefile.build:302: recipe for target '/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.o' failed
make[1]: *** [/var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.o] Error 1
Makefile:1546: recipe for target '_module_/var/lib/dkms/veeamsnap/1.0.1.364/build' failed
make: *** [_module_/var/lib/dkms/veeamsnap/1.0.1.364/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.13.0-16-generic'

[PTide]

Hi and welcome to the community.

Unfortunately Ubuntu 17.10 is not supported in the current version. We consider adding the new kernel support in the upcoming release.

Thanks

[drohm]

Is there a rough timeline for the next release?

[PTide]

It is going to happen this year.

[drohm]

Awesome, thanks very much for the info.

[bkc]

I also need 4.13 kernel support to backup my Dell XPS 13 (since 4.13 was required to get suspend to work, I have been running betas of this kernel for a while, but could not get veeam backups to work)

[PTide]

I also need 4.13 kernel support to backup my Dell XPS 13

If your distro is in the supported list then kindly contact our support team for the fix.

Thanks

[drohm]

PTide,
So there is a fix for the 4.13.0 kernel that I can apply to get around this?

[PTide]

So there is a fix for the 4.13.0 kernel that I can apply to get around this?

Yes, there is a fix for veeamsnap kernel module, you can contact our support team and request the fix. Please note that Ubuntu 17.10 is not supported by current VAL version (1.0.1.364) which means it's not guaranteed that there will be no other non-driver-related issues on your system. If there will be any then we won't be able to help you until the next version is released.

Thanks

[marius roma]

I have the same problem. How can I contact the support team to get the fix?
Regards
marius

[PTide]

Hi Mario,

You need to open a case via veeam.com portal.

Thanks

[marius roma]

Can I open a case even for the free version installed on a private PC?
Regards
marius

[PTide]

Yes, FREE version users are also eligible for support, however there is no SLA, so support is provided on the best effort basis.

Thanks