coreboot

coreboot@coreboot.org

6 participants
39686 discussions

[coreboot - Bug #386] (New) ASUS P8Z77-V LX2 - Raminit issue at second boot with two 8GiB DIMMs - bootloop
by gzz5f gzz5f 15 Jan '23

15 Jan '23

Issue #386 has been reported by gzz5f gzz5f. ---------------------------------------- Bug #386: ASUS P8Z77-V LX2 - Raminit issue at second boot with two 8GiB DIMMs - bootloop https://ticket.coreboot.org/issues/386 * Author: gzz5f gzz5f * Status: New * Priority: High * Category: board support * Target version: master * Start date: 2022-06-05 * Affected versions: master * Needs backport to: none * Affected hardware: ASUS P8Z77-V LX2 * Affected OS: all ---------------------------------------- I build coreboot today for the ASUS P8Z77-V LX2 and used the latest coreboot master code. The 2 8GiB DIMMs are working fine at first boot. You can start computer, install from a live media the OS and so on. But at the second boot it failes boot forever and its bootooping. It does not make a change if i boot for a second until SeaBIOS output and then turn off the computer or use the computer for longer time. The second boot is always broken. Workaround 1: Remove one of the two 8GiB DIMMs. Then the computer also starts fine after a reboot. Workaround 2: Install two 4GiB DIMMs instead of two 8GiB DIMMs. Then the computer also starts fine after reboot. Workaround 3: At every boot boot for a second with one DIMM. Turn off the computer, insert the second DIMM and start it again. kmalkki told me to rebuid the image with DEBUG_RAM_SETUP=y I then build a second image, with DEBUG_RAM_SETUP=y. The logfile contains the first successfull boot (created with Workaround 3), the poweroff and the poweron with the bootloop. I have let it bootloop few times before turned off the PSU. ---Files-------------------------------- coreboot_logfie.txt (197 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

3 3

[coreboot - Bug #343] (Resolved) Fails to load GRUB payload: CPU Index 0 - APIC 0 Unexpected Exception:6 @ 10:00009016 - Halting
by Martin Roth 15 Jan '23

15 Jan '23

Issue #343 has been updated by Martin Roth. Status changed from New to Resolved The patch https://review.coreboot.org/c/coreboot/+/64235 which was said to fix the issue was merged on 2022-11-02. Please reopen if the issue is still seen. ---------------------------------------- Bug #343: Fails to load GRUB payload: CPU Index 0 - APIC 0 Unexpected Exception:6 @ 10:00009016 - Halting https://ticket.coreboot.org/issues/343#change-1359 * Author: Paul Menzel * Status: Resolved * Priority: Normal * Start date: 2022-03-30 ---------------------------------------- coreboot emulation/qemu-i440fx is unable to load GRUB payload. It works with SeaBIOS. ``` FMAP REGION: COREBOOT Name Offset Type Size Comp cbfs master header 0x0 cbfs header 32 none fallback/romstage 0x80 stage 21944 none fallback/ramstage 0x56c0 stage 62048 LZMA (139536 decompressed) config 0x14980 raw 428 none revision 0x14b80 raw 716 none build_info 0x14e80 raw 112 none fallback/dsdt.aml 0x14f40 raw 4044 none cmos_layout.bin 0x15f40 cmos_layout 640 none fallback/postcar 0x16200 stage 23328 none fallback/payload 0x1bd80 simple elf 460906 none (empty) 0x8c640 null 3603556 none bootblock 0x3fc2c0 bootblock 15104 none ``` ``` […] [NOTE ] coreboot-4.16-415-ga84c00c9ce Wed Mar 30 01:18:14 UTC 2022 ramstage starting (log level: 7)... […] [INFO ] Timestamp - selfboot jump: 965162845 [EMERG] CPU Index 0 - APIC 0 Unexpected Exception:6 @ 10:00009016 - Halting [EMERG] Code: 0 eflags: 00010002 cr2: 00000000 [EMERG] eax: 00000000 ebx: 3ffbdc18 ecx: 0001ac27 edx: 000000ff [EMERG] edi: 3ffbdc00 esi: 3ffbdbf0 ebp: 000001e4 esp: 3ffc3fbc [EMERG] 0x00008fd0: 00 00 00 00 00 00 00 00 [EMERG] 0x00008fd8: 00 00 00 00 00 00 00 00 [EMERG] 0x00008fe0: 00 00 00 00 00 00 00 00 [EMERG] 0x00008fe8: 00 00 00 00 00 00 00 00 [EMERG] 0x00008ff0: 00 00 00 00 00 00 00 00 [EMERG] 0x00008ff8: 00 00 00 00 00 00 00 00 [EMERG] 0x00009000: 52 52 68 27 ac 01 00 6a [EMERG] 0x00009008: 0b e8 5e cd 00 00 83 c4 [EMERG] 0x00009010: 10 a0 00 00 00 00 0f 0b [EMERG] 0x00009018: 51 51 68 6a a2 01 00 6a [EMERG] 0x00009020: 0b e8 46 cd 00 00 83 c4 [EMERG] 0x00009028: 10 eb e6 90 bc f0 ff 07 [EMERG] 0x00009030: 00 e9 c7 d7 00 00 66 90 [EMERG] 0x00009038: 02 b0 ad 1b 02 00 00 00 [EMERG] 0x00009040: fc 4f 52 e4 55 57 56 53 [EMERG] 0x00009048: 83 ec 1c 8b 5c 24 30 8b [EMERG] 0x3ffc4038: 0x00000002 [EMERG] 0x3ffc4034: 0x00000003 [EMERG] 0x3ffc4030: 0x00000000 [EMERG] 0x3ffc402c: 0x00000000 [EMERG] 0x3ffc4028: 0x00000000 [EMERG] 0x3ffc4024: 0x00000000 [EMERG] 0x3ffc4020: 0x00000000 [EMERG] 0x3ffc401c: 0x00000000 [EMERG] 0x3ffc4018: 0x00000000 [EMERG] 0x3ffc4014: 0x00000000 [EMERG] 0x3ffc4010: 0x00000000 [EMERG] 0x3ffc400c: 0x00000000 [EMERG] 0x3ffc4008: 0x00000000 [EMERG] 0x3ffc4004: 0x00000000 [EMERG] 0x3ffc4000: 0x00000000 [EMERG] 0x3ffc3ffc: 0x00000000 [EMERG] 0x3ffc3ff8: 0x3ffbd4e8 [EMERG] 0x3ffc3ff4: 0xdeadbeef [EMERG] 0x3ffc3ff0: 0xdeadbeef [EMERG] 0x3ffc3fec: 0x3ff9e061 [EMERG] 0x3ffc3fe8: 0x3ffa1f19 [EMERG] 0x3ffc3fe4: 0x00018f20 [EMERG] 0x3ffc3fe0: 0x3ffdcfd4 [EMERG] 0x3ffc3fdc: 0x3ffc4000 [EMERG] 0x3ffc3fd8: 0x3ffd63ac [EMERG] 0x3ffc3fd4: 0x00000000 [EMERG] 0x3ffc3fd0: 0x3ffa1fe5 [EMERG] 0x3ffc3fcc: 0x3ffa2139 [EMERG] 0x3ffc3fc8: 0x3ffbdc24 [EMERG] 0x3ffc3fc4: 0x3ffa4303 [EMERG] 0x3ffc3fc0: 0x3ff95000 [EMERG] 0x3ffc3fbc: 0x3ffac8e4 <-esp ``` ---Files-------------------------------- coreboot.log (17.2 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

[coreboot - Bug #443] (New) acpica distfile changed
by Fabian Groffen 15 Jan '23

15 Jan '23

Issue #443 has been reported by Fabian Groffen. ---------------------------------------- Bug #443: acpica distfile changed https://ticket.coreboot.org/issues/443 * Author: Fabian Groffen * Status: New * Priority: Normal * Target version: none * Start date: 2022-12-04 ---------------------------------------- commit 58c79bc2537e408db2a8b5ce7723ed6dd0145652 (HEAD -> acpica-distfile-fix) Author: Fabian Groffen <grobian(a)gentoo.org> Date: Sun Dec 4 21:13:28 2022 +0100 crossgcc: fix distfile for acpica For some reason this distfile was changed into something odd. But update it. Signed-off-by: Fabian Groffen <grobian(a)gentoo.org> diff --git a/util/crossgcc/buildgcc b/util/crossgcc/buildgcc index 0d349f2dfe..d9f7b73766 100755 --- a/util/crossgcc/buildgcc +++ b/util/crossgcc/buildgcc @@ -52,7 +52,7 @@ MPFR_ARCHIVE="https://ftpmirror.gnu.org/mpfr/mpfr-${MPFR_VERSION}.tar.xz" MPC_ARCHIVE="https://ftpmirror.gnu.org/mpc/mpc-${MPC_VERSION}.tar.gz" GCC_ARCHIVE="https://ftpmirror.gnu.org/gcc/gcc-${GCC_VERSION}/gcc-${GCC_VERSION}.tar.xz" BINUTILS_ARCHIVE="https://ftpmirror.gnu.org/binutils/binutils-${BINUTILS_VERSION}.tar.xz" -IASL_ARCHIVE="https://acpica.org/sites/acpica/files/acpica-unix2-${IASL_VERSION}.tar.gz" +IASL_ARCHIVE="https://acpica.org/sites/acpica/files/acpica-unix2-${IASL_VERSION}.tar_0.gz" # CLANG toolchain archive locations LLVM_ARCHIVE="https://github.com/llvm/llvm-project/releases/download/llvmorg-${CLANG_VERS…" CLANG_ARCHIVE="https://github.com/llvm/llvm-project/releases/download/llvmorg-${CLANG_VERS…" diff --git a/util/crossgcc/sum/acpica-unix2-20221020.tar.gz.cksum b/util/crossgcc/sum/acpica-unix2-20221020.tar_0.gz.cksum similarity index 100% rename from util/crossgcc/sum/acpica-unix2-20221020.tar.gz.cksum rename to util/crossgcc/sum/acpica-unix2-20221020.tar_0.gz.cksum -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

2 1

[coreboot - Bug #441] (New) [CRIT ] intel_me_path: mbp is not ready! & mei_me 0000:00:16.0: initialization failed.
by U dent 15 Jan '23

15 Jan '23

Issue #441 has been reported by U dent. ---------------------------------------- Bug #441: [CRIT ] intel_me_path: mbp is not ready! & mei_me 0000:00:16.0: initialization failed. https://ticket.coreboot.org/issues/441 * Author: U dent * Status: New * Priority: Normal * Category: board support * Target version: master * Start date: 2022-11-27 * Affected versions: master * Affected hardware: ASROCK H81M-HDS * Affected OS: debian 11.5 ---------------------------------------- **short journalctl -b** > Nov 27 21:19:37 debian kernel: mei_me 0000:00:16.0: H_RST is set = 0x80000015 > Nov 27 21:19:39 debian kernel: mei_me 0000:00:16.0: wait hw ready failed > Nov 27 21:19:39 debian kernel: mei_me 0000:00:16.0: hw_start failed ret = -62 > Nov 27 21:19:39 debian kernel: mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device > Nov 27 21:19:39 debian kernel: mei_me 0000:00:16.0: reset failed ret = -19 > Nov 27 21:19:39 debian kernel: mei_me 0000:00:16.0: link layer initialization failed. > Nov 27 21:19:39 debian kernel: mei_me 0000:00:16.0: init hw failure. > Nov 27 21:19:39 debian kernel: mei_me 0000:00:16.0: initialization failed.` **short cbmem -1** > [CRIT ] intel_me_path: mbp is not ready! > [NOTE ] ME: BIOS path: Error > [ERROR] ME: MBP not ready **also notice** > Nov 27 21:26:57 debian kernel: usb usb1-port9: over-current condition > Nov 27 21:26:57 debian kernel: usb usb1-port10: over-current condition ---Files-------------------------------- CBMEM-LOG (45.8 KB) defconfig (768 Bytes) journalctl_b.txt (83.9 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

2 9

[coreboot - Bug #432] (New) t440p reboots on suspend
by Josh R 15 Jan '23

15 Jan '23

Issue #432 has been reported by Josh R. ---------------------------------------- Bug #432: t440p reboots on suspend https://ticket.coreboot.org/issues/432 * Author: Josh R * Status: New * Priority: Normal * Target version: none * Start date: 2022-10-21 * Affected versions: 4.15 * Related links: https://ticket.coreboot.org/issues/412 * Affected hardware: Lenovo t440p * Affected OS: Ubuntu 22.04 (Pop OS) ---------------------------------------- Per request, adding new ticket for an issue with my t440p where attempting to resume on suspend results in a reboot (or at least, not resuming from DRAM). My t440p already has coreboot installed (via osbmk). Following instructions from issue #412, I have attempted the following: `sudo flashrom -p internal --ifd -i bios -w the_full_12MiB_osbmk.rom --noverify-all` ...but that did not seem to do the trick (still "restarts" without resuming from RAM). Note that I am using the "full" 12MB osbmk rom (not split by 4MiB and 8MiB, as that seemed intended for the hardware flashing instructions). coreboot version looks like 4.15.204, and flashrom version 1.2-640. If it helps, attached cbmem -1 output with a "normal boot" followed by a later resume from suspend (that resulted in a restart). Thanks in advance. I guess you don't realize how much you use suspend until it doesn't work anymore :) ---Files-------------------------------- cbmem.20221019195923.normal_boot.log (36.2 KB) cbmem.20221019200724.from_suspend.log (36.3 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

3 6

[coreboot - Bug #19] Violations of Coding guidelines: All objects should have fully qualified types (unsigned int instead of unsigned)
by Martin Roth 15 Jan '23

15 Jan '23

Issue #19 has been updated by Martin Roth. Some utilities and payload code still uses bare unsigned, but this is completely fixed in the coreboot src/ directory. There are unfortunately some false positives within names and comments, so the lint test should be updated in addition to fixing the above issues. ---------------------------------------- Bug #19: Violations of Coding guidelines: All objects should have fully qualified types (unsigned int instead of unsigned) https://ticket.coreboot.org/issues/19#change-1355 * Author: Martin Roth * Status: New * Priority: Normal * Start date: 2015-12-30 ---------------------------------------- Some (most?) of these can be seen using the following command: grep -Grin 'unsigned' | grep -v 'unsigned[[:space:]]*int\|unsigned[[:space:]]*long\|unsigned[[:space:]]*char\|unsigned[[:space:]]*short' -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

[coreboot - Bug #36] (Closed) x201: stuck ec event
by Martin Roth 15 Jan '23

15 Jan '23

Issue #36 has been updated by Martin Roth. Status changed from New to Closed No updates in 7 years. Closing. Please reopen if this is still an issue. ---------------------------------------- Bug #36: x201: stuck ec event https://ticket.coreboot.org/issues/36#change-1354 * Author: Alexander Couzens * Status: Closed * Priority: Normal * Start date: 2016-03-10 ---------------------------------------- sometime the ec on x201 is stuck in a queue which results in all fn buttons and lid isn't working. so most of the acpi events aren't generated. ec 0x34 bit 3 - attention is disabled temporary might interesting. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

[coreboot - Bug #33] (Closed) cbmem utility fails on newer linux kernels "Failed to mmap /dev/mem: Resource temporarily unavailable"
by Martin Roth 15 Jan '23

15 Jan '23

Issue #33 has been updated by Martin Roth. Status changed from New to Closed Closing as fixed. ---------------------------------------- Bug #33: cbmem utility fails on newer linux kernels "Failed to mmap /dev/mem: Resource temporarily unavailable" https://ticket.coreboot.org/issues/33#change-1353 * Author: Martin Roth * Status: Closed * Priority: Normal * Start date: 2016-02-05 ---------------------------------------- This has been going on for a while. Paul mentioned it here: https://www.coreboot.org/pipermail/coreboot/2015-September/080383.html -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

[coreboot - Bug #27] (Closed) Windows doesn't like references in ACPI to objects that are only defined later
by Martin Roth 15 Jan '23

15 Jan '23

Issue #27 has been updated by Martin Roth. Status changed from New to Closed Marking as closed due to the last update being 7 years old. Please reopen if we have a new update. ---------------------------------------- Bug #27: Windows doesn't like references in ACPI to objects that are only defined later https://ticket.coreboot.org/issues/27#change-1352 * Author: Patrick Georgi * Status: Closed * Priority: Normal * Start date: 2016-01-29 ---------------------------------------- There is some concern about Windows not liking ASL structured like in https://review.coreboot.org/#/c/13506/ because NVSA is defined "after" the OpRegion that uses it. Needs testing and potentially a tree-wide solution -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

[coreboot - Feature #20] Add make target to check if toolchain is up to date
by Martin Roth 15 Jan '23

15 Jan '23

Issue #20 has been updated by Martin Roth. Affected versions 4.18 added This was completed, but seems like it may now be broken again. The command 'make test-toolchain' should tell you if the toolchain version you are using is current, but currently reports that the toolchain is up-to-date even when that's not the case. ---------------------------------------- Feature #20: Add make target to check if toolchain is up to date https://ticket.coreboot.org/issues/20#change-1351 * Author: Timothy Pearson * Status: In Progress * Priority: Normal * Assignee: Martin Roth * Category: build system * Start date: 2015-12-30 * Affected versions: 4.18 ---------------------------------------- Various automated build/test services use a specific toolchain build for all tests, and have no way to know if the toolchain has been updated and requires a rebuild. This, in turn, means manual intervention is needed for these services every time the toolchain version changes. (unless various hacks involving searching the output text are used, but these are highly suboptimal). A new make target to check if the built toolchain is completely up to date with the current coreboot versions would be very useful. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot