From: Jason Wessel <jason.wessel@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] serial-getty@.service: Allow device to fast fail if it does not exist
Date: Wed, 28 Aug 2019 22:03:59 -0500 [thread overview]
Message-ID: <1747485c-6e3b-4acf-81bb-89d4d6e80009@windriver.com> (raw)
In-Reply-To: <e125a759ceaca090562af688aad68eaec89f7da2.camel@linuxfoundation.org>
On 8/28/19 5:41 PM, Richard Purdie wrote:
> On Wed, 2019-08-28 at 15:24 -0500, Jason Wessel wrote:
>> On 8/27/19 7:15 PM, richard.purdie@linuxfoundation.org wrote:
>>> On Tue, 2019-08-27 at 19:03 -0500, Jason Wessel wrote:
>>>> On 8/27/19 5:58 PM, Richard Purdie wrote:
>>>>> Hi Jason,
>>>>> Somehow this change is responsible for this build failure:
>>>>>
>>>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/976
>>>>>
>>>>> (steps 5c and 7c so failure during testimage).
>>>>>
>>>>> I have bisected it to this change, I haven't looked into why.
>>>> Thanks for tracking it down. I am sure how to try an duplicate
>>>> this. I clicked around to try and find out a bit about what it
>>>> is
>>>> running for these phases of the build but it is not very obvious.
>>>>
>>>> Is there a local.conf I can try along with what ever commands it
>>>> ran?
>>> The configuration its using is shown in
>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/978/steps/8/logs/stdio
>>> for each step.
>>>
>> I tried the configuration on my system but it seems to work fine, see
>> below. Is there a way to get complete log file of the boot on the
>> broken host? I am also curious if it fails every time or not.
>>
>> /home/pokybuild/yocto-worker/qa-
>> extras2/build/build/tmp/work/qemux86_64-poky-linux/core-image-
>> sato/1.0-r0/testimage/qemu_boot_log.20190827200002
>>
>> I am not sure it will tell us anything further or not, but it
>> certainly looks like the system didn't boot correctly in the first
>> place.
> I've rerun it as
> https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/983
>
>
I'll take a further look at it tomorrow. I have no idea why systemd emitted this message:
[ 4.750194] systemd[1]: Unnecessary job for /dev/ttyS1 was removed.
[ 4.751666] systemd[1]: Unnecessary job for /dev/ttyS0 was removed.
[ OK ] Started Serial Getty on ttyS0.
Stopping Serial Getty on ttyS0...
I have an image now with the problem so, I'll make a copy of it in case the problem "goes away" again. It will be interesting to see what the deal is with this corner case.
Cheers,
Jason.
prev parent reply other threads:[~2019-08-29 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 0:27 [PATCH] serial-getty@.service: Allow device to fast fail if it does not exist Jason Wessel
2019-08-27 22:58 ` Richard Purdie
2019-08-28 0:03 ` Jason Wessel
2019-08-28 0:15 ` richard.purdie
2019-08-28 20:24 ` Jason Wessel
2019-08-28 22:24 ` richard.purdie
2019-08-28 22:41 ` Richard Purdie
2019-08-29 3:03 ` Jason Wessel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1747485c-6e3b-4acf-81bb-89d4d6e80009@windriver.com \
--to=jason.wessel@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox