-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Debian Jessie build from source is hanging #1434
Comments
I see this:chdir(/lib/modules/4.14.0-rc7/build): No such file or directory ===== |
Thanks for the quick reply. |
On Mon, Nov 6, 2017 at 1:33 PM, AndrewAday ***@***.***> wrote:
Thanks for the quick reply.
What is the kernel-devel package equivalent for Debian?
Is it the linux-headers-<version> and linux-image-<version> package?
Try linux-headers-*
…
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I had the same problems AndrewAday'd had above. While there is no build errors, it seems to hang on test #15 and #16 (py_test_brb and py_test_brb2): Kernel: 4.9.0-0.bpo.3-amd64 (on Debian 8.9)
|
Does the initial |
no warnings as far as I know: -- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Latest recognized Git tag is v0.4.0
-- Git HEAD is 06c0528417be48415cd22cd1cd25b498132bffbd
-- Revision is 0.4.0-06c05284
-- Performing Test HAVE_NO_PIE_FLAG
-- Performing Test HAVE_NO_PIE_FLAG - Failed
-- Found BISON: /usr/bin/bison (found version "3.0.2")
-- Found FLEX: /usr/bin/flex (found version "2.5.39")
-- Found LLVM: /usr/lib/llvm-3.8/include 3.8.1
-- Found LibElf: /usr/lib/x86_64-linux-gnu/libelf.so
-- Performing Test ELF_GETSHDRSTRNDX
-- Performing Test ELF_GETSHDRSTRNDX - Success
-- Using static-libstdc++
-- Found LuaJIT: /usr/lib/x86_64-linux-gnu/libluajit-5.1.a;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libm.so
-- Configuring done
-- Generating done
-- Build files have been written to: /var/tmp/bcc/build and all three tools are also available:
|
I've retried using 4.9 Kernel and like Smun I am now hanging on test 15: py_test_brb.
Any ideas why? |
Looks like the test is causing deadlock:
|
@4ast @yonghong-song This looks like a more serious issue |
I can reproduce the issue with latest net-next. I will take a deep look on this. |
I did not see the deadlock message on default 4.9.
I will look at this separately. At least the system is healthy even I saw this during boot time. Through some experiment, it looks like the following patch is responsible for the failure.
Revert this patch can fix the issue. |
Regarding to my above deadlock warning reported by kernel lockdep, it is a false positive. The issue has been fixed in 4.14 and latest net-next. |
I'm experiencing the same issue. I have tried reverting commit 97a0cac and deadlock in test 15 was indeed resolved, however build fails anyway because of tests 3, 27, 28, 29, 30, 31 not passed. I'm on Debian Stretch, kernel version 4.14.13. Build log attached. |
Maybe test_libbcc related to Could you help debug further on these test failures? Thanks! |
Looks like test_brb failed? There are few possibilities: The command format to run the test itself
Test wrapper is at |
I'm experiencing the same issue,any idea what's wrong? |
I roughly remember that the following hack can fix the issue?
Could you give a try? If this is the case, we will need to figure out the reason reason... |
Yes, this can fix the issue,thank you! But three other tests failed:
VrtualBox6.0 |
Right. That is why we have not fixed this issue yet :-(. |
Hi, I am also having the same issue. |
I am facing the same error and hanging issue I tried all of the suggestions in the post and verifying the dependencies. |
I have hoped somebody working on debian issue can help debug why the above mentioned workaround fixed the issue while it had an opposite impact on some other systems... |
For @kmahmou1 -- check that your linux-headers package version exactly matches your linux-image version. If you just do "apt-get install linux-headers-$(uname -r)" you'll get linux-headers-4.9.0-8-amd64=4.9.144-3.1 which won't work with that 4.9.110-3+deb9u6 kernel. If they don't match, either remove the linux-headers packages and do:
or upgrade linux-image to the matching 4.9.144-3.1 package. |
When you build on a clean machine, the python module does not exist yet. So it can't be imported by the tests. So to build the first time you can use the workaround below, to skip the tests to build packages. DEB_BUILD_OPTIONS=nocheck debuild -b -uc -us -i |
I am following this guide: https://github.com/iovisor/bcc/blob/master/INSTALL.md?utf8=%E2%9C%93#debian---source
I had to modify
CMakeLists.txt
to include the -std=c++11 option so it would build at all. But when runningdebuild -b -uc -us
, numerous tests fail with the exception "Exception: Failed to compile BPF module", and debuild hangs on test "Start 29: py_test_tools_memleak"Any idea what's wrong? I am running a 4-14-rc7 kernel on debian version 8.9.
Attached is my build output.
bcc_0.4.0-1_amd64.build.txt
The text was updated successfully, but these errors were encountered: