It may be my fault.  I'll take a look.  Thanks.

I made some changes to these packages: crosh, debugd, and swap-init.  With those changes at ToT, I cannot reproduce the problem.  I am now resyncing everything and will check if there are interferences.  If you give me the IP address of your device I can take a look there.  Thanks!

Cannot repro even with a full ToT build, so I need to look at your device.

There is some problem in the way your kernel and /lib/modules were built.  I see this in the syslog:


2017-03-21T21:58:38.351191-07:00 NOTICE swap[1529]: modprobe zram failed (compiled?)

and when I try to load the module I see this error:

localhost ~ # modprobe zram
modprobe: ERROR: could not insert 'zram': Exec format error

but that's strange because the time stamp in the file is similar to that of the kernel build:

localhost ~ # file /lib/modules/3.8.11/kernel/drivers/staging/zram/zram.ko 
/lib/modules/3.8.11/kernel/drivers/staging/zram/zram.ko: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), BuildID[sha1]=017b819f8a1425e5101a7eb2f14ba09f6c2563bd, not stripped
localhost ~ # uname -a
Linux localhost 3.8.11 #18 SMP Mon Mar 20 23:40:01 PDT 2017 x86_64 Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz GenuineIntel GNU/Linux
localhost ~ # find /lib/modules -name *zram* | xargs ls -l
-rw-r--r-- 1 root root 24176 Mar 20 23:40 /lib/modules/3.8.11/kernel/drivers/staging/zram/zram.ko

/lib/modules/3.8.11/kernel/drivers/staging/zram:
total 24
-rw-r--r-- 1 root root 24176 Mar 20 23:40 zram.ko
localhost ~ # 

Really not sure what went wrong here.  Did you manually dump a new kernel in /dev/sda2?

@4: I didn't dump a new kernel there, but now that you mention it, I think I might have had some issues with update_kernel yesterday.

I can't reinstall right now since I'm running a long-term experiment, but if you think it's my error (and inability to load zram.ko would point at that) then let's punt.

Maybe update_kernel got interrupted halfway, or something.  This is the most likely explanation.  Safe to close.