Opened 14 months ago
Last modified 2 months ago
#18593 new bug
Issues in virtual machines related to SSE2+ usage following GCC 13 upgrade — at Initial Version
Reported by: | waddlesplash | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta6 |
Component: | System/Kernel | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | #17233, #18541, #18562 | Blocking: | |
Platform: | All |
Description
This is a meta-ticket created to encompass the various symptoms which seem to have implicit SSE2 usage from GCC 13 optimizations as a common cause.
In summary:
- QEMU/KVM: Hangs on rocket during network device initialization, "emulation failure" in console (#18541), sometimes reports as "paused" (#18562)
- VMware: READ/WRITE FAULT on KDL backtraces into userland,
area contains
, and a bunch of other KDL commands (seen in #17233.)
The issues in QEMU/KVM do not occur in VMware and vice versa. Compiling the kernel and drivers with -mno-sse2
(i.e. leaving SSE(1) enabled for standard floating-point usage) seems to resolve the problems.
Note:
See TracTickets
for help on using tickets.