l time out
<ogra_> sigh
<ogra_> so i guess no wlan on pi3 for the RC image then
<ppisati> ogra_: can you ssh in and check if the wlan is there?
<ogra_> well, i can probably set up wired, lets see ... though usually if console-conf had one error you can forget about the whole thing
<ppisati> ogra_: right, it usually loses its mind after a failed network config
<ogra_> yep
<ogra_> well, we still have two weeks :P
<ogra_> ppisati, in general the kernel seems to be a lot better though ... something at least ... all oopses gone
<ogra_> oh my
<ogra_> now cosole-conf just crashed ... drops me back to "please press enter" and if i do that it prints python tracebacks
<ppisati> ogra_: so, for the BBB panic bug, i tried to install console-conf on classic, reproduce the 'first boot' snappy boot environment and work from there
<ppisati> ogra_: might be a strategy to debug this
<ogra_> i did set BBB to verification-done for the sru kernel yesterday already
<ogra_> ppisati, was the kernel from bug 1627643 the one in proposed ?
<mup> Bug #1627643: oops on pi3 (seemingly wlan related) <Snappy:New> <linux-raspi2 (Ubuntu):New for p-pisati> <https://launchpad.net/bugs/1627643>
<ppisati> ogra_: or we punch a hole in the dev image so we can login via the serial console and check what's really going on
<ppisati> ogra_: yes
<ogra_> well, i wanted to play with systemd console but didnt have time for that yet
<ogra_> \o/
<ogra_> something at least ... that kernel looks fine
<ppisati> ogra_: good to know
<ogra_> do you have an SRU bug that i can tag verification-done ?
<ogra_> (though i need to test pi2 still)
<ppisati> ogra_: let me find it
<ogra_> ogra@localhost:~$ cat /proc/net/dev
<ogra_> Inter-|   Receive                                                |  Transmit
<ogra_>  face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
<ogra_>   sit0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
<ogra_>     lo