On Tue, Nov 27, 2018 at 10:02 AM Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Tue, Nov 27, 2018 at 12:48 AM Dave Hedge <itswag7(a)gmail.com> wrote:
>
> Peter,
>
> Wondering if you have any magical insight in #4. For us this is the main blocker
and something that we would like to wrap soon so that we can progress with testing.
I do. It's an issue as a direct result of adding in the support for
TPM2, I'm trying to get to the bottom of it, it's unclear where the
fix/bug lies and I'm trying to get to the bottom of this so we can get
the release out and we can move on.
I think I have this fixed, or at least worked around in a reasonable
and usable means. I'm just just putting some other pieces in place and
we should have a RC.
P
> Peter
>
> > > 4) The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29
> > >
https://github.com/dracutdevs/dracut/issues/488
> >
> > Dave
> >
> > On Fri, Nov 16, 2018 at 2:07 PM Peter Robinson <pbrobinson(a)gmail.com>
wrote:
> >>
> >> 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
> >> >
https://bugzilla.redhat.com/show_bug.cgi?id=1646568
> >>
> >> There's a fix pending review of this upstream here:
> >>
https://github.com/rhinstaller/anaconda/pull/1692
> >>
> >> > 2) WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
> >> >
https://bugzilla.redhat.com/show_bug.cgi?id=1644873
> >>
> >> 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.
> >>
> >>
https://bugzilla.redhat.com/show_bug.cgi?id=1648112
> >>
> >> > 3) ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) +
#kopen's(0))
> >> >
https://bugzilla.redhat.com/show_bug.cgi?id=1644884
> >>
> >> 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
> >> >
https://github.com/dracutdevs/dracut/issues/488
> >>
> >> 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 and
any
> >> > new issues encountered or anything else we may have missed.
> >>
> >> Does anyone else have anything that might be a blocker here?
> >>
> >> Peter
> >> _______________________________________________
> >> IoT mailing list -- iot(a)lists.fedoraproject.org
> >> To unsubscribe send an email to iot-leave(a)lists.fedoraproject.org
> >> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> >> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> >> List Archives:
https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org
> >
> > _______________________________________________
> > IoT mailing list -- iot(a)lists.fedoraproject.org
> > To unsubscribe send an email to iot-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> > List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org