New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 774738 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

10017.0: kernel_Bootcache fails w/ "device-mapper: reload ioctl on bootcache-testdev failed: Invalid argument"

Project Member Reported by djkurtz@chromium.org, Oct 14 2017

Issue description

Originally reported on kahlee as b/67762873.

Chrome OS Version: 10017.0
Chrome OS Platform: elm, kahlee (maybe others)

Steps To Reproduce:
(1) test_that --fast ${IP} kernel_Bootcache

Expected Result:

Test PASS

Actual Result:

Test FAIL

19:08:56 INFO | autoserv| START	----	----	timestamp=1507939735	localtime=Oct 13 19:08:55
19:08:56 INFO | autoserv| START	kernel_Bootcache	kernel_Bootcache	timestamp=1507939735	localtime=Oct 13 19:08:55
19:08:56 INFO | autoserv| Bundling /build/elm/usr/local/build/autotest/client/site_tests/kernel_Bootcache into test-kernel_Bootcache.tar.bz2
19:08:59 INFO | autoserv| ERROR	kernel_Bootcache	kernel_Bootcache	timestamp=1507939738	localtime=Oct 13 19:08:58	Command </usr/local/opt/punybench/bin/bootcachetest > failed, rc=2, Command returned non-zero exit status
19:08:59 INFO | autoserv| END ERROR	kernel_Bootcache	kernel_Bootcache	timestamp=1507939738	localtime=Oct 13 19:08:58
19:09:00 INFO | autoserv| END GOOD	----	----	timestamp=1507939739	localtime=Oct 13 19:08:59

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

Always

---------------------------------------
Running test manually on DUT has following error messages:

# /usr/local/opt/punybench/bin/bootcachetest

/usr/local/opt/punybench/bin/bootcachetest
|losetup /dev/loop2 /usr/local/xyzzy
device-mapper: reload ioctl on bootcache-testdev failed: Invalid argument
Command failed
Fatal /usr/local/opt/punybench/bin/bootcachetest bootcachetest.c:create_dm_bootcache<789> dmsetup create bootcache-testdev 256
Stack back trace:
        /usr/local/opt/punybench/bin/bootcachetest(stacktrace_err+0x3b) [0x5ae700c6a166]

|dmsetup remove bootcache-testdev
device-mapper: remove ioctl on bootcache-testdev failed: No such device or address
Command failed
Fatal /usr/local/opt/punybench/bin/bootcachetest bootcachetest.c:run<649> dmsetup remove bootcache-testdev:256: No such file or directory<2>
Stack back trace:
        /usr/local/opt/punybench/bin/bootcachetest(stacktrace_err+0x3b) [0x5ae700c6a166]

 
bootcache is only used on spinning disk chromebooks -- early parrot machines which are all on kernel 3.8.  I think we're going to retire these soon, and if so we should probably just delete this test?

otherwise -- we should only run the test on 3.8 kernels
Adding here for posterity: seeing TEST_NA on 4.4 machines (nocturne) with "Applicable to 3.8 Kernel only" message. That's great, wondering if there's a bug to retire the test concurrently with 3.8 EOL.

Sign in to add a comment