[coreboot] [coreboot - Bug #449] ThinkPad T440p fail to start, continous beeping & LED blinking

Issue #449 has been updated by Angel Pons. https://review.coreboot.org/72806 fixes the UBSAN errors, please review. Note that UBSAN-enabled coreboot still dies later on: ``` Loading module at 0x0003 with entry 0x0003. filesize: 0x178 memsize: 0x178 Processing 16 relocs. Offset value of

[coreboot] New Defects reported by Coverity Scan for coreboot

Hi, Please find the latest report on new defect(s) introduced to coreboot found with Coverity Scan. 6 new defect(s) introduced to coreboot found with Coverity Scan. 2 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New defect(s) Re

[coreboot] [coreboot - Bug #455] (New) superiotool recognizes the wrong chip and doesn't work.

Issue #455 has been reported by shen Liu. Bug #455: superiotool recognizes the wrong chip and doesn't work. https://ticket.coreboot.org/issues/455 * Author: shen Liu * Status: New * Priority: Normal * Category: userspace utilities * Target versio

[coreboot] [coreboot - Bug #455] superiotool recognizes the wrong chip and doesn't work.

Issue #455 has been updated by shen Liu. ```shell sudo ./superiotool superiotool r4.19-306-g12ec7901b7 Found Aspeed AST2400 (id=0x00) at 0x4e sudo ./superiotool superiotool r4.19-306-g12ec7901b7 No Super I/O found ``` Does superiotool provide debug symbols? Without debug symbols I

[coreboot] [coreboot - Bug #455] superiotool recognizes the wrong chip and doesn't work.

Issue #455 has been updated by Nicholas Chin. shen Liu wrote: > ``` shell > sudo ./superiotool > Found Aspeed AST2400 (id=0x00) at 0x4e > sudo ./superiotool > superiotool r4.19-306-g12ec7901b7 > No Super I/O found > ``` > Does superiotool provide debug symbols? > Without debug symbol

[coreboot] [coreboot - Bug #455] superiotool recognizes the wrong chip and doesn't work.

Issue #455 has been updated by shen Liu. Nicholas Chin wrote in #note-2: > shen Liu wrote: > > ``` shell > > sudo ./superiotool > > Found Aspeed AST2400 (id=0x00) at 0x4e > > sudo ./superiotool > > superiotool r4.19-306-g12ec7901b7 > > No Super I/O found > > ``` > > Does superiotool

[coreboot] [coreboot - Bug #455] superiotool recognizes the wrong chip and doesn't work.

Issue #455 has been updated by Nicholas Chin. shen Liu wrote in #note-3: > > `Starting program: /home/test/coreboot/util/superiotool/superiotool > Debuginfod has been enabled. > To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit. > [Thread debugging using libthr

[coreboot] [coreboot - Bug #455] superiotool recognizes the wrong chip and doesn't work.

Issue #455 has been updated by Angel Pons. Have you tried running `sudo superiotool -d`? This should show the register dump for the Nuvoton Super I/O on your board. The AST2400 detection procedure is delusional (read random registers, if any returns non-zero then we have an AST2400), so it

[coreboot] [coreboot - Bug #455] superiotool recognizes the wrong chip and doesn't work.

Issue #455 has been updated by shen Liu. Nicholas Chin wrote in #note-4: > As a workaround for now, you could try ignoring aspeed chips by commenting > out line 233 in superiotool.h I did that, but no superio was detected. Angel Pons wrote in #note-5: > Have you tried running `sudo su