[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [BUG] x2apic broken with current AMD hardware


  • To: Elliott Mitchell <ehem+xen@xxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Fri, 10 Mar 2023 09:22:55 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=fj3eC8LdQghUT9ACN0oTSYDwDIzoYa85Ha7YmgJG4yw=; b=isPQC9OXHb1eUdvbYZIzfJUO432K4uJyng6Xc6SqNuJmFKj+QHxqOD/7wg1C0usVgAy5+UxufDKJLmXUbra6fkv0B7PSZ9TJfIC7vKV2sJVo2+RRFGjZ+5agMF7xm/ibcsNf/cz5tstnlD0wyjHhr+2Zns6SLBmK01rGFEk+Au3auZWavMsTiXOR1BBF2l4PHsXEUfKyBF/fzfGpLQFzwMPT9usDbmADi18nENdNM8aqa6D2iThneXCZs2KiMK1rR45ufPMlFAhVcHDtXHvQQ444u8RMalePmdbSZWjTcGPbBfkXndtIDOJd4OkCC/pwXzi31Yp/Xk0zXyud91tDcg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SCWWOIpKsAsCdW7f1m2RU9a6crxROt58tw7qRvEfzo4BRsT/3bdCg2+0B3cufEpkZzjxKgdK3Nkswjm/cOfUkExcUYR7gtU1n9ESO0jHFEh2PnSaiXiCrI0U66FNkR+Eu0E7rMems/Vh5dbjpIM3W8S7Ti3ODs7V84iu9ssFVwx9jPBd/vtc1ZLt3WcQaGR9tqNAij0JwCC4RmQDd9I8NZUuveQUQzkJhz/slTfRhTdh2GGZHJij9xD5baINMuFlMorHWr/k/lXRHvSGTGgSvFIvdiwEynE7SFQrRaJA8erx3TV5BaeeDbN5uI7kLyGmQunAZETventSwsS2oaldbw==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 10 Mar 2023 08:23:25 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 10.03.2023 04:25, Elliott Mitchell wrote:
> On Thu, Mar 09, 2023 at 10:03:23AM +0100, Jan Beulich wrote:
>> On 09.03.2023 00:08, Elliott Mitchell wrote:
>>>
>>> As such I'm less than certain the problem is still in HEAD, though
>>> Neowutran and Co working with 4.16 and the commit log being quiet
>>> suggests there is a good chance.
>>>
>>> More detail, pretty well most things are broken for Domain 0 without
>>> "x2apic=false".  Trying to boot with a 6.1.12 a USB keyboard was
>>> completely unresponsive, on screen the initial ramdisk script output was
>>> indicating problems interacting with storage devices.  Those two together
>>> suggested an interrupt issue and adding "x2apic=false" caused domain 0 to
>>> successfully boot.
>>> A 5.10 kernel similarly requires "x2apic=false" to successfully boot.
>>>
>>> So could be a commit after 4.16 fixed x2apic for current AMD hardware,
>>> but may still be broken.
>>
>> If Dom0 boot is affected, trying a newer hypervisor shouldn't be a problem.
>> You won't need any of the toolstack to match just to see whether Dom0 boots.
>>
>> In any event you will want to collect a serial log at maximum verbosity.
>> It would also be of interest to know whether turning off the IOMMU avoids
>> the issue as well (on the assumption that your system has less than 255
>> CPUs).
> 
> Well, I can now state "x2apic=false" IS required for Xen 4.17.  Since the
> last x2apic commit was about a year ago, I believe this matches HEAD.  I
> missed the logs since the USB-serial adapter decided to bugger when the
> machine rebooted.
> 
> Is it just me or is https://wiki.xenproject.org/wiki/Xen_Serial_Console
> out of date?

Without you being more specific (there are many variants there), from
quickly glancing over it the command line options mentioned look right to
me. There's an oddity like "console=tty0", but that's not affecting serial
(should be "console=vga", if at all - in the specific example the
subsequent "console=com2" overrides the bogus one anyway).

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.