Control: reassign -1 src:linux 5.10.120-1 Control: tag -1 upstream moreinfo On Tuesday, 5 July 2022 12:09:00 CEST Michael wrote: > package: linux-image-5.10.0-15-arm64 > version: 5.10.120-1 > > i am running virtualbox 6.1.34 from the virtualbox.org repo on a debian > 11.3 host. the guest also runs debian 11.3. > > when both host and guest run the latest stable kernel 5.10.0-15 > (5.10.120-1) i get random process crashes in the guest when having > significant i/o for longer than a few seconds on the host. > > and eventually guest processes start to randomly crash, e.g.: > > Jun 30 20:17:01 vmguest kernel: traps: sh[250946] general protection fault > ip:7fb0c341708e sp:7ffec3154378 error:0 in > libc-2.31.so[7fb0c33a6000+14b000] > Jul 01 00:00:02 vmguest kernel: traps: hostname[253617] general protection > fault ip:7f905f2b24a6 sp:7fff44a30e30 error:0 in > libc-2.31.so[7f905f299000+14b000] > Jul 01 00:53:01 vmguest kernel: traps: wget[254290] general protection > fault ip:7f934bc23fda sp:7ffd716954d0 error:0 in > libtasn1.so.6.6.0[7f934bc1a000+c000] > > if i switch to kernel 5.10.0-14 (5.10.113-1) on the host (the guest kernel > remains 5.10.0-15), then the random process crashes in the guest disappear, > although the complaints from hrtimer and clocksource still remain, but > significantly less often. This indeed looks like an upstream regression between 5.10.113 and 5.10.120. What surprises me are the time gaps between those GPF messages, ~3.5h and 50m, but not within the same second/minute. What happens between those time stamps? If there are more messages around those GPF messages, it would be useful to share those as well. In Stable-Proposed-Updates there is a 5.10.127-1 version and it would be useful to test whether the issue happens with that version too.
Attachment:
signature.asc
Description: This is a digitally signed message part.