http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbrugger@suse.com, | |mkubecek@suse.com, | |tiwai@suse.com, | |yousaf.kaukab@suse.com --- Comment #1 from Takashi Iwai --- Not sure whether it's arm64-specific issue or net stack problem. Adding people relevant with both to Cc. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c2 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.opensuse.o | |rg/show_bug.cgi?id=1128546 --- Comment #2 from Guillaume GARDET --- Looks like https://bugzilla.opensuse.org/show_bug.cgi?id=1128546 (ignore the unrelated USB trace and comments) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c4 --- Comment #4 from Guillaume GARDET --- (In reply to Fabian Vogt from comment #3)

(In reply to Guillaume GARDET from comment #2)

...

Looks like https://bugzilla.opensuse.org/show_bug.cgi?id=1128546 (ignore the unrelated USB trace and comments)

Yeah, that's the exact same crash - however, that bug report seems to be more about the USB issue now than the iptables one...

Indeed, so keep this one to track this specific issue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schwab@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c7 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #802527|0 |1 is obsolete| | --- Comment #7 from Guillaume GARDET --- Created attachment 802632 --> http://bugzilla.suse.com/attachment.cgi?id=802632&action=edit Decoded trace for kernel-vanilla-5.1.rc4-1.1.g1478096.aarch64 (fixed) Previous version was decoded on x86 and was wrong. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c8 --- Comment #8 from Guillaume GARDET --- For QEMU, if I disable QEMU_VIRTIO_RNG option[1] on aarch64 openQA, the bug is not triggered anymore (at least on 5 tests run in parallel): https://openqa.opensuse.org/tests/908902 https://openqa.opensuse.org/tests/908903 https://openqa.opensuse.org/tests/908904 https://openqa.opensuse.org/tests/908905 https://openqa.opensuse.org/tests/908906 To confirm it, I would need to schedule more tests. Any idea how that would be related? [1]: QEMU_VIRTIO_RNG option in openQA: see https://github.com/os-autoinst/os-autoinst/blob/0cb8a1e041939d12768961f94a03... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c10 --- Comment #10 from Guillaume GARDET --- A workaround is available: boot with 'nokaslr' kernel option to disable Address Space Layout Randomization. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c12 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(schwab@suse.com) | --- Comment #12 from Andreas Schwab --- See the follow-ups. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c14 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(schwab@suse.com) | --- Comment #14 from Andreas Schwab --- I have no idea. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c15 --- Comment #15 from Guillaume GARDET --- Possible fixes to test (merged for 5.2-rc2): * arm64/module: deal with ambiguity in PRELxx relocation ranges: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i... * arm64/kernel: kaslr: reduce module randomization range to 2 GB: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c18 Denis Kirjanov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |denis.kirjanov@suse.com --- Comment #18 from Denis Kirjanov --- Hi Guillaume, please check if it still the issue and if it's not please closer the bug. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1131864 http://bugzilla.suse.com/show_bug.cgi?id=1131864#c19 Guillaume GARDET changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #19 from Guillaume GARDET --- (In reply to Denis Kirjanov from comment #18)

Hi Guillaume,

please check if it still the issue and if it's not please closer the bug.

Thank you.

Backported patch in kernel 5.1.6 fixed this problem on qemu/openQA as well: arm64/kernel: kaslr: reduce module randomization range to 2 GB So, current released Tumbleweed is not affected anymore. -- You are receiving this mail because: You are on the CC list for the bug.