From: Stefan Agner <stefan@agner.ch>
To: Christian Stewart <christian@aperture.us>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/containerd: bump version to v1.6.22
Date: Fri, 08 Sep 2023 08:20:56 +0200 [thread overview]
Message-ID: <23f2b3bd59cb6d860ea52b566eacfdb8@agner.ch> (raw)
In-Reply-To: <CA+h8R2rbhvCt60Fhwi1qGv0PocZsS0rA3fVQoukDP2KhPrkjdQ@mail.gmail.com>
On 2023-09-08 04:03, Christian Stewart wrote:
> Hi Stefan,
>
> On Thu, Sep 7, 2023, 4:51 PM Stefan Agner <stefan@agner.ch> wrote:
>
>> On 8 September 2023 01:28:36 CEST, Christian Stewart <christian@aperture.us> wrote:
>>> Hi Stefan,
>>>
>>> On Thu, Sep 7, 2023 at 4:23 PM Stefan Agner <stefan@agner.ch> wrote:
>>>>
>>>> Hi Christian,
>>>>
>>>> It seems that this version hangs at startup, at least when built with
>>>> Buildroot 2023.02.4.
>>>
>>> I am running 1.7.x on my systems so I can't confirm this currently.
>>
>> I've just tested 1.7.3 as well, it shows the same behavior here. I'll need to do more testing. Ideally I like to see a stack trace (via signal or debugger), but not sure how to archive this with Buildroot and golang.
>>
>> This is on aarch64 platforms.
>
> I hate to say "works on my machine," but with both versions on aarch64 it works for me.
>
> Maybe the filesystem you are using is different? I'm using ext4. Or is the kernel config not set up quite right? Maybe old kernel?
The root file system is a squashfs, but the data is stored on ext4.
We are using the latest vanilla Linux kernel 6.1.52.
It seems to hang here:
WARN[2023-09-08T06:17:38.515218691Z] waiting for response from boltdb
open plugin=bolt
From what I can tell it's some IPC mechanism or similar which is
hanging.
I can also reproduce it on x86-64. I guess it must be unique to our
operating system configuration in some way...
--
Stefan
>
> Best,
> Christian
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-08 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 23:22 [Buildroot] [PATCH v1 1/1] package/containerd: bump version to v1.6.22 Christian Stewart via buildroot
2023-07-28 19:17 ` Thomas Petazzoni via buildroot
2023-08-30 11:04 ` Peter Korsgaard
2023-09-07 23:23 ` Stefan Agner
2023-09-07 23:28 ` Christian Stewart via buildroot
2023-09-07 23:50 ` Stefan Agner
2023-09-08 2:03 ` Christian Stewart via buildroot
2023-09-08 6:20 ` Stefan Agner [this message]
2023-09-15 21:48 ` Christian Stewart via buildroot
2023-09-25 10:08 ` Stefan Agner
2023-09-30 8:03 ` Peter Korsgaard
2023-10-02 18:28 ` Christian Stewart via buildroot
2023-10-04 9:59 ` Stefan Agner
2023-10-04 10:04 ` Christian Stewart via buildroot
2023-10-04 10:08 ` Stefan Agner
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=23f2b3bd59cb6d860ea52b566eacfdb8@agner.ch \
--to=stefan@agner.ch \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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