On Wed, Nov 14, 2018 at 4:14 PM Paul Whalen <pwhalen(a)redhat.com> wrote:
Good morning all,
Apologies, there was a miscommunication about the IoT meeting this week
and we missed our allotted time in #fedora-meeting.
We wanted to go over the list of blockers for Fedora 29 IoT and to check
on testing results. The list currently includes:
1) initial-setup hangs during boot after IoT installation
There's a fix pending review of this upstream here:
2) WARNING at
I've not managed to recreate this one, I also believe it's actually
closely related to this one which Tim bought up on the thread too. Tim
can you confirm that if you see this error it also causes issues with
"rpm-ostree install" on the SD cards? There's been a few issues
reported upstream around MMC stability on the bcm2835 driver and I
wonder if there's something special happening with the way rpm-ostree
hits the HW that is making this more likely to trigger. I also wonder
if it's improved with v4.19.x kernel.
3) ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) +
This is fixed, it was the console=ttyAMA0 option we had enabled which
cause it to fight with bluetooth over who owned the serial device.
4) The 35network-legacy is still used even if network-scripts
isn't installed in Fedora 29
I've been traveling this week so I've not had time to dig further on
this, hoping to catch up on the weekend.
It would be great to get some feedback on the most recent composes
new issues encountered or anything else we may have missed.
Does anyone else have anything that might be a blocker here?