Date: Fri, 21 Jun 2019 05:59:19 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238729] head -r347549 on aorus gaming 7 F12e BIOS (Threadripper 1950X): boot attempts hang (but boots for fedora/Windows 10 Pro) Message-ID: <bug-238729-227-yoE1mD8rEB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238729-227@https.bugs.freebsd.org/bugzilla/> References: <bug-238729-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238729 --- Comment #6 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #5) fwts (a batch run) on fedora may have reported some interesting material. (I've no prior use so I'd not know if some of this is the tool itself.) QUOTE klog: Scan kernel log for errors and warnings. ---------------------------------------------------------------------------= ----- Test 1 of 1: Kernel log error check. FAILED [CRITICAL] KlogAmdIommuNoIVRS: Test 1, CRITICAL Kernel message: [ 0.999781] AMD-Vi: [Firmware Bug]: : IOAPIC[130] not in IVRS table ADVICE: BIOS setup is configured to enable IOMMU, but BIOS lacks IVRS table that is describing which is the address of IOMMU FAILED [HIGH] KlogAcpiBadAmlCode: Test 1, HIGH Kernel message: [ 9.142618] = ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20190215 /utaddress-204) END QUOTE (I ignore examples of DMISerialNumber being 'Unknown'.) There are examples like: FAILED [LOW] DMIStringIndexOutOfRange: Test 2, Out of range string index 0x= 0c while accessing entry 'BIOS Language Information (Type 13)' @ 0x000eb1da, f= ield 'BIOS Language String 12', offset 0x04 There are: cpufreq: CPU frequency scaling tests. ---------------------------------------------------------------------------= ----- Can't access cpufreq info for CPU 0 Failed to parse cpufreq for CPU 0 Aborted test, initialisation failed. . . . apicedge: APIC edge/level test. ---------------------------------------------------------------------------= ----- Test 1 of 1: Legacy and PCI Interrupt Edge/Level trigger tests. FAILED [MEDIUM] LegacyIRQLevelTrig: Test 1, Legacy interrupt 7 is incorrect= ly level triggered. There are various examples reported of: Missing ACPI table 'FACP' and the FACP points to it. Cannot initialise ACPI. Aborted test, initialisation failed. There is: rsdp: RSDP Root System Description Pointer test. ---------------------------------------------------------------------------= ----- Test 1 of 1: RSDP Root System Description Pointer test. PASSED: Test 1, RSDP first checksum is correct FAILED [LOW] RSDPBadOEMId: Test 1, RSDP: oem_id contains non-printable characters. and: osilinux: Disassemble DSDT to check for _OSI("Linux"). ---------------------------------------------------------------------------= ----- Test 1 of 1: Disassemble DSDT to check for _OSI("Linux"). FAILED [MEDIUM] NoDSDT: Test 1, Could not read ACPI DSDT table. and: madt: MADT Multiple APIC Description Table (spec compliant). ---------------------------------------------------------------------------= ----- Cannot read ACPI MADT tables. Aborted test, initialisation failed. and: Test 2 of 4: Test HPET base in HPET table. ACPI table HPET does not exist! Test 3 of 4: Test HPET base in DSDT and/or SSDT. WARNING: Test 3, Test skipped because HPET Device address was not found in = DSDT /SSDT. (But I've generally ignored reports of "ACPI ??? table does not exist, skipping test".) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238729-227-yoE1mD8rEB>