-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kernel 4.4.0-64-generic :( #3
Comments
Yep can do, will have a look and reply when done. |
@fullmoon4465 could you put your /var/lib/dkms/iomemory-vsl/3.2.10/build/make.log in http://pastebin.com/ and post the link ? just to make sure I'm not seeing something else than you are. |
@fullmoon4465 looking at my results it seems like a test concurrency/order issue in the make process, am investigating. |
I'm actually using Miratnis Fuel 9.0, then upgraded to 9.2 which is where the new kernel came in to play with the bootstrap image you build. I can probably try it again tomorrow. After you use the bootstrap though (live disk), I don't think it will do what I need it to do without a reboot on the server, meaning I can't do what I wanted pre install of the OS openstack. I can however compile just fine after fuel has deployed openstack "Mitaka on Ubuntu 14.04". Then use ceph to add the osd's after this driver's installed. TMI but notes for my self. will get back |
@fullmoon4465 Ah! thanks for the context there! (am familiar with Fuel) Am having varying results myself (scrap my pre-edited remark). I'm out of juice for now, will continue tomorrow. Are you in the bay area per chance ? (need to figure out private messaging hahaha) |
Nah midwest. But we all work remote anyway until hardware is needed lol |
Haha cool, too bad you're not closer or I would have hopped by! :) |
Issue #3 is a result from the timeout for a test triggering. This is mostly seen on low CPU resource compile environments, as the original kfio_config.sh script would start a background test for each test and monitor the tests for the timeout value (default 120s). The easiest fix would be to up the timeout, but this could still trigger the issue. Instead of changing the timeout rate limiting has been applied, based on the amount of CPUs instead of a stampede of tests.
@fullmoon4465 sorry for the delay, had some things to take care of in the meantime. Problem should be fixed, I'll close the ticket for now, and thanks for filing the bug! If the problem persist please re-open :) |
Any way to get this working with newer kernel?
Building module:
cleaning build area....
'make' DKMS_KERNEL_VERSION=4.4.0-64-generic............(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.4.0-64-generic (x86_64)
Consult /var/lib/dkms/iomemory-vsl/3.2.10/build/make.log for more information.
The text was updated successfully, but these errors were encountered: