hung task on host kernel when running crostini tast tests |
||
Issue descriptionR71-11151.6.0 - nami - vm.CrostiniStartEverything https://stainless.corp.google.com/browse/chromeos-autotest-results/249720163-chromeos-test/ Oddly this is only showing up on the 71 branch as far as I can tell.
,
Oct 25
I can take a look, but at first glance, this looks like it is a (host) kernel bug of some kind, so I'm not sure I am the best equipped to diagnose it. :) The crash in the ramoops is in the host 4.4 kernel. At this level, crosvm is just another user-mode process doing I/O operations through the normal read()/write()/fsync() interfaces. If we can hang the system using these syscalls, there's definitely something wrong in kernel-land. The kernel stacks in the oops seem to have several processors waiting on ext4 and jbd2 calls; maybe we are somehow hitting a deadlock? If this has reproduced more than once, it would be good to get some more data points (e.g. are they all on the same host kernel version?) and try to narrow it down some more.
,
Nov 2
I'm unassigning myself from this, since I'm not actively looking at it. Have we seen any more of these in recent tests? |
||
►
Sign in to add a comment |
||
Comment 1 by jkardatzke@chromium.org
, Oct 24Status: Assigned (was: Untriaged)