00:26 <vagrantc> hrm.

00:27 <vagrantc> can't seem to make a bootable sd card image for the veyron-speedy anymore...

00:27 <vagrantc> wonder if upgrading cgpt and vboot* is causing issues

00:28 <vagrantc> nope, was able to create a working image with the currently booting kernel.

00:46 <mmind00> vagrantc: maybe also https://lkml.org/lkml/2016/12/28/173 ?

00:47 <vagrantc> it's even an issue with different versions of 4.8.x

00:48 <vagrantc> 4.8.5 works, 4.8.11 doesn't ...

00:48 <vagrantc> i guess if the reverted patch was backported...

00:54 <mmind00> vagrantc: my pinky netbooted sucessfully with 4.10-rc1, so there doesn't seem to be some "catastrohic" issue at least

00:57 <phh> vagrantc: what's your issue when doing bootable sdcard?

00:57 <phh> beep from bootloader?

00:57 <vagrantc> phh: no, it loads, but then just a white screen, no output

00:58 <phh> vagrantc: with fbcon enabled?

00:58 <vagrantc> with a modularized debian config, fwiw

01:00 <phh> something I've observed on veyron-speedy on 4.9-rcX, is that the boot on SD is flaky... sometimes I can boot for 10 times straight, then it won't boot, and boot again. and sometimes 4 tries in a row won't make it boot. and in this case, it is freezing at root detection

01:00 <phh> though I've never been able to boot debian kernel, because initramfs is too big for coreboot

01:02 <vagrantc> i've also never successfully booted with rootfs on USB or sd ...

01:02 <phh> where is your rootfs then? network or emmc?

01:02 <vagrantc> emmc

01:02 <vagrantc> phh: that sounds pretty similar to the behavior i observed

01:03 <vagrantc> phh: i submitted a patch that seems to fix the issue with eMMC rootfs, but apparently it makes it worse for others...

01:03 <phh> vagrantc: the 1v8 one?

01:04 <vagrantc> https://patchwork.kernel.org/patch/9352915/

01:04 <phh> yup this one

01:04 <phh> the behaviour I have on sdcard is different than this emmc issue

01:05 <phh> on emmc I see that sometimes it fails during probe

01:05 <phh> but for sdcard, I see that everything works well, the partition table is properly read, it's just that the kernel keeps waiting on... something...

01:06 <vagrantc> regarding initramfs size, i'm using modules=dep for initramfs-tools/initramfs.conf, which makes a ~4MB initrd ... initrd+initramfs ~7MB

01:07 <vagrantc> when debugging, i enabled the USB-serial console option (forget what it's called) ... but obviously can't get that enabled in a debian kernel (which boots an arbitrary number of devices)

01:07 <phh> ok, I'll probably switch to that when I get vpu to build as a module

01:09 <vagrantc> i should probably try to figure out how to get the initramfs to load the appropriate video and keyboard modules

01:20 <vagrantc> why on earth did i not think of this before

01:21 <vagrantc> mmcblk0: error -110 sending status command, retrying

01:21 <vagrantc> mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0x900

01:22 <vagrantc> mmcblk0: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0

01:22 <vagrantc> and then it waits

01:26 <vagrantc> so i enabled a debug shell in initramfs, and that time it worked.

01:27 <vagrantc> reboot failed again ...

01:27 <vagrantc> whew.

01:33 <vagrantc> does the microSD slot uses a different driver than the eMMC?

16:03 <phh> diego71: is there a regulator in your dts? is it properly probed?

16:14 <diego71> phh: defined:yes. Probed no. But I'm quite ignorant about dt stuff, so I don't know when or what should be probed. I suspect some missing modules....

16:24 <phh> Well your regulator's driver is loaded?

16:30 <diego71> I thought so, but i'm not sure.

16:30 <diego71> At the moment I found, that the non-working kernel miss the i2c_rk3x module, compared to a working one...

16:34 <phh> yeah, a regulator is most probably on i2c bus

16:34 <phh> so that makes sense

23:56 <rperier> Happy new year !

23:56 <rperier> ;)