[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ryzen 6000 (Mobile)
- To: Dylanger Daly <dylangerdaly@xxxxxxxxxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Mon, 15 Aug 2022 18:19:52 +0200
- 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=yzdTEu7s26estwmfSRc7xCggcOp93hzkdIuu/yFAY8g=; b=nh+KTi1sbML+TfT4rid4juLD8urFDi3zE8N7hPMkCRavZQ+CBr+HD36pn4hnQ3fSAGXBg+MYKwQpMQZsIqEWN59H580+C/QVUMVI8rH06LF89lhdipxjsymCJg4C6b4UKuUIu9szo3vVKMWBV4F5yFCn5usKhKJr5ihGcvdAt/8K7U3bMIi0cIrTUDA7SbKu5tkvhKEeBH+hqUytSU/YUgXN2Xi3G/WDqsAbII1ru/tRxRjjZCNLK+AkHFqRFIwpF8MOYXaTQZ2TAOFArhjfLzk+/oT5AOzHYwiCXvpEE2StIBFXPhClFf0u7PE0EWJYXYFmdXAZ/1f0gLBj3sWv/A==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IK+bJLoDov5WVQYimvAhYVEL6eMpxn7eMEMKmiUllRfhpYzNEf9MfqxhaFvq9cQQXsktmpjxj73hVDcCk9PiJ65Enz0f8qXQv9Fxr+TRKQRmwkHgHS5/XhDJpXKPuhWsXhH2lXOBbtXq6NEiTOprF6ysNAssHnhcWgHNyZ72zJMtrSE1RFZk1fiN7d9E8TWxI3X7CJBH/pJF0d506yYhARdvTxHudZj4C8ZXHPFBZSBo3ShXUCxVW1odbw2Ur5S0uoD5XC70MazjlzW08smpF8JMtbRorPxvOJ7AZSWYIWiAE/7t34p0nzKOxC8LppudES3nYMOUzrWI36tQD66AHg==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
- Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>
- Delivery-date: Mon, 15 Aug 2022 16:20:07 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 15.08.2022 17:39, Dylanger Daly wrote:
> Great news! I managed to get it to log the error with your cmdlines
>
> Please see the attached images
>
> The error "BUG: unable to handle page fault for address: ffffc90040639019"
>
> It appears to be a memory violation error?
Yes, there's an attempt to access something which wasn't (successfully)
mapped. I expect there's a log message ahead of the actual crash telling
us what it was that was attempted to be mapped. A wild guess of mine
would be PCI MMCFG space. We may be able to read something out of the
system's ACPI tables, if you could extract them (at least DSDT, maybe
also SSDTs) into files. It would then also be useful to see the
hypervisor and kernel boot messages, at the very least to know where
certain things live in physical address space.
Jan
|
