Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1107330
| From | Paul Gevers <elbrus@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204! |
| Date | 2022-06-22 22:10 +0200 |
| Message-ID | <EBePL-6yjO-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <DpTHb-7Db-3@gated-at.bofh.it> <EASPf-6kXQ-3@gated-at.bofh.it> <EATBE-6lu4-7@gated-at.bofh.it> <DpTHb-7Db-3@gated-at.bofh.it> <EATBE-6lu4-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
Hi Diederik, On 21-06-2022 23:19, Diederik de Haas wrote: > I think that the install logs aren't that important (anymore) as the issue/ > symptoms appear to be the same: > - some swap action resulting in some failure > - CPU gets stuck > - watchdog triggers a reboot If the reboot would actually happen/finish, I wouldn't have problems of the hanging host. The issues I spotted required a manual reboot (and that's why I spotted them). > How is swap configured on these devices? https://salsa.debian.org/ci-team/debian-ci-config/-/blob/master/cookbooks/basics/default.rb#L3 until line 11 > Yeah, I _assumed_ as such, but assumptions can be dangerous ;-) Total ACK. > Normally I scroll (hard) by the hardware listings as that rarely says anything > to me. And I did that before too, but just now I made an important discovery. > > I *assumed* it was running on arm64 (native) hardware and was about to ask > specifics about it and then I noticed this: > Host bridge [0600]: Red Hat, Inc. QEMU PCIe Host bridge [1b36:0008] > > Qemu. Quite likely unrelated, but a while back I had an issue with qemu in > building arm64 images: https://bugs.debian.org/988174 hmm, OK, right (I forgot that I knew this). > I think it would be useful to know which qemu version(s) were used. Is there any way to know from inside the VM? > If the issue does occur again, I think it would be useful to bring 'upstream' > into the conversation. They likely can bring much more useful input into this > then (f.e.) I could. Also, if upstream is made aware there is an issue (even > infrequent), then they can make the most informed choice what to do with it. Ack. Paul
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204! Diederik de Haas <didi.debian@cknow.org> - 2022-06-21 22:10 +0200
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204! Paul Gevers <elbrus@debian.org> - 2022-06-21 22:40 +0200
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204! Paul Gevers <elbrus@debian.org> - 2022-06-22 22:10 +0200
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204! Diederik de Haas <didi.debian@cknow.org> - 2022-06-22 23:20 +0200
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204! Diederik de Haas <didi.debian@cknow.org> - 2022-06-22 23:30 +0200
Bug#1001001: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204! Paul Gevers <elbrus@debian.org> - 2022-06-23 10:50 +0200
csiph-web