On 20.07.2022 06:48, ChrisD wrote: > So, you think it's a problem with fc36?
Well, if that's where the binary came from, then yes. And btw please don't top-post and please don't send html mail (see the almost unreadable stuff below that was how your mail came through when read as plain-text). Jan > -------- Original message --------From: Andrew Cooper > <[email protected]> Date: 7/18/22 6:25 PM (GMT-05:00) To: > [email protected], [email protected] Cc: Jan Beulich > <[email protected]>, Michael Young <[email protected]> Subject: Re: > Panic on CPU 0: FATAL TRAP: vec 7, #NM[0000] On 18/07/2022 22:31, > [email protected] wrote:> I am trying to run Xen-4.16.1-4.fc36 on Fedora 36 > on a brand new Lenovo> ThinkStation p620, but I keep getting the following > error booting the> Xen kernel.> > Panic on CPU 0:> FATAL TRAP: vec 7, > #NM[0000]>> Version info:> Name : xen> Version : 4.16.1> Release > : 4.fc36So https://koji.fedoraproject.org/koji/buildinfo?buildID=1991182 > shouldbe the binary build in use, and looking at the debug syms, it > reallydoes have:ffff82d040439c80 <amd_iommu_init>:...ffff82d04043a00c: > 0f 6e c2 movd %edx,%mm0ffff82d04043a00f: 0f 62 c0 > punpckldq %mm0,%mm0ffff82d04043a012: 49 89 87 c0 00 00 00 > mov %rax,0xc0(%r15)ffff82d04043a019: 41 0f 7f 87 d0 00 00 movq > %mm0,0xd0(%r15)ffff82d04043a020: 00So hardware is correct - this build > of Xen is nonsense.The binary is also full of .annobin_ stuff which appears > to be some kindof GCC plugin for watermarking.Michael: Any idea what's going > on here? Something has caused GCC toemit some MMX logic which is ultimately > why things exploded, but thisprobably means that some of the build CFLAGS got > dropped.Thanks,~Andrew
