All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walter Lozano <walter.lozano@collabora.com>
To: johannes@sipsolutions.net, linux-um@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: Sjoerd Simons <sjoerd.simons@collabora.com>,
	ritesh sarraf <ritesh.sarraf@collabora.com>
Subject: Occasional hung with UM after enable VMAP_STACK
Date: Tue, 4 Jan 2022 15:10:06 -0300	[thread overview]
Message-ID: <be290dc3-db9c-2940-91bb-c91bf42fd8f6@collabora.com> (raw)

Hi all,

I noticed that after "um: enable VMAP_STACK" [1] I experienced some 
occasional hung in my Gitlab CI jobs that use user-mode-linux to build 
distro images. The configuration use for the building is the one 
available from Debian, see [2] and [3]. Unfortunately I don't have much 
information, when the issue arises the job seems to hang and it is 
cancelled by Gitlab due to a job timeout.

So far I did some bisect to get the commit which introduces the issue 
and a quick check with latest Linux stable branch master to confirm the 
issue is still present. I know this is not a proper bug report but I 
thought it will be better to at least raise a comment.

Thanks in advance,

Walter

[1] http://lists.infradead.org/pipermail/linux-um/2021-August/001657.html

[2] https://packages.debian.org/bookworm/user-mode-linux

[3] https://salsa.debian.org/uml-team/user-mode-linux

-- 
Walter Lozano
Collabora Ltd.


WARNING: multiple messages have this Message-ID (diff)
From: Walter Lozano <walter.lozano@collabora.com>
To: johannes@sipsolutions.net, linux-um@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: Sjoerd Simons <sjoerd.simons@collabora.com>,
	ritesh sarraf <ritesh.sarraf@collabora.com>
Subject: Occasional hung with UM after enable VMAP_STACK
Date: Tue, 4 Jan 2022 15:10:06 -0300	[thread overview]
Message-ID: <be290dc3-db9c-2940-91bb-c91bf42fd8f6@collabora.com> (raw)

Hi all,

I noticed that after "um: enable VMAP_STACK" [1] I experienced some 
occasional hung in my Gitlab CI jobs that use user-mode-linux to build 
distro images. The configuration use for the building is the one 
available from Debian, see [2] and [3]. Unfortunately I don't have much 
information, when the issue arises the job seems to hang and it is 
cancelled by Gitlab due to a job timeout.

So far I did some bisect to get the commit which introduces the issue 
and a quick check with latest Linux stable branch master to confirm the 
issue is still present. I know this is not a proper bug report but I 
thought it will be better to at least raise a comment.

Thanks in advance,

Walter

[1] http://lists.infradead.org/pipermail/linux-um/2021-August/001657.html

[2] https://packages.debian.org/bookworm/user-mode-linux

[3] https://salsa.debian.org/uml-team/user-mode-linux

-- 
Walter Lozano
Collabora Ltd.


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


             reply	other threads:[~2022-01-04 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 18:10 Walter Lozano [this message]
2022-01-04 18:10 ` Occasional hung with UM after enable VMAP_STACK Walter Lozano
2022-01-04 19:04 ` Johannes Berg
2022-01-04 19:04   ` Johannes Berg
2022-01-04 19:26   ` Walter Lozano
2022-01-04 19:26     ` Walter Lozano
2022-01-04 19:49     ` Johannes Berg
2022-01-04 19:49       ` Johannes Berg
2022-01-05 12:58       ` Walter Lozano
2022-01-05 12:58         ` Walter Lozano
2022-01-04 21:39     ` Anton Ivanov
2022-01-04 21:39       ` Anton Ivanov
2022-01-05 12:59       ` Walter Lozano
2022-01-05 12:59         ` Walter Lozano

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=be290dc3-db9c-2940-91bb-c91bf42fd8f6@collabora.com \
    --to=walter.lozano@collabora.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=ritesh.sarraf@collabora.com \
    --cc=sjoerd.simons@collabora.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.