From: pdp7pdp7@gmail.com (Drew Fustini)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kbuild: kselftest error
Date: Sat, 30 Aug 2014 04:18:21 -0500 [thread overview]
Message-ID: <540196DD.1080807@gmail.com> (raw)
Hi - I noticed the kselftest target in the kernel Makefile and decided
to try it out of curiosity:
afustini at lappy486:~/dev/linux/lappy486/git/kernels/mainline$ sudo make
kselftest
Has anyone run kselftest successfully?
I ran into an error that I'm trying to figure out:
== Testing sysctl behavior against /proc/sys/vm/swappiness ==
Writing test file ... ok
Checking sysctl is not set to test value ... ok
Writing sysctl from shell ... ok
Resetting sysctl to original value ... ok
Writing entire sysctl in single write ... ok
Writing middle of sysctl after synchronized seek ... FAIL
Writing beyond end of sysctl ... FAIL
Writing sysctl with multiple long writes ... ok
make[2]: *** [test_num] Error 1
./fw_filesystem.sh: timeout works
./fw_filesystem.sh: filesystem loading works
fw_filesystem: ok
./fw_userhelper.sh: timeout works
./fw_userhelper.sh: firmware interface never appeared
fw_userhelper: [FAIL]
make[2]: *** [fw_userhelper] Error 1
make[1]: *** [run_tests] Error 2
make: *** [kselftest] Error 2
I'm running kernel that I compiled from linus's tree 2 days ago.
After encountering the error, I turned on all the testing config options
I could find under the kernel hacking category. However, I encountered
the same kselftest error with the newly built kernel:
Linux lappy486 3.17.0-lappy486-00040-gff0c57a-dirty #5 SMP PREEMPT Thu
Aug 28 05:08:04 CDT 2014 x86_64 x86_64 x86_64 GNU/Linux
Log files for reference:
make-kselftest-3.17.0-lappy486-00040-gff0c57a-dirty.log:
https://gist.github.com/pdp7/79d511ddf30fa8d0dfee
dmesg-3.17.0-lappy486-00040-gff0c57a-dirty.log:
https://gist.github.com/pdp7/ea3f86dd7dc994189c14
kernel-config-3.17.0-lappy486-00040-gff0c57a-dirty.log:
https://gist.github.com/pdp7/07315ac2aba2ab4c48da
lsmod-3.17.0-lappy486-00040-gff0c57a-dirty.log:
https://gist.github.com/pdp7/c6db7271345afc8a6868
lib-modules-3.17.0-lappy486-00040-gff0c57a-dirty.log:
https://gist.github.com/pdp7/a297c5aa246cd2b1ac9f
find-sys-fs-3.17.0-lappy486-00040-gff0c57a-dirty.log:
https://gist.github.com/pdp7/9238072c1630e0995749
git-status-3.17.0-lappy486-00040-gff0c57a-dirty.log:
https://gist.github.com/pdp7/c300ced047d1fa7fc696
git-diff-3.17.0-lappy486-00040-gff0c57a-dirty.log:
https://gist.github.com/pdp7/686ab164c55a25fcb5f8
thanks,
drew
next reply other threads:[~2014-08-30 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 9:18 Drew Fustini [this message]
2014-08-30 17:16 ` kbuild: kselftest error Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=540196DD.1080807@gmail.com \
--to=pdp7pdp7@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).