-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'm wondering whether coreboot will work in my machine. Here is requested information according to http://www.coreboot.org/FAQ#Will_coreboot_work_on_my_machine.3F
1) System: SAPPHIRE PI-AM2RS780G, AMDx86-64 QuadCore, The cpuinfo is attached in cpuinfo.dump
2) lspci -tvnn see attached lspci.dump
3) see attached supiotools.dump
4) see attached flashrom.dump
5) http://www1.sapphiretech.com/dk/products/products_overview.php?gpid=213
6) -
Cheers,
Alois
Calibrating delay loop... 610M loops per second, 100 myus = 203 us. OK. No coreboot table found. Found chipset "ATI(AMD) SB700", enabling flash write... SPI base address is at 0xfec10000 OK. Probing for AMD Am29F002(N)BB, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29F002(N)BT, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMD Am29F016D, 2048 KB: probe_29f040b: id1 0x4d, id2 0x49 Probing for AMD Am29F040B, 512 KB: probe_29f040b: id1 0x0, id2 0x80 Probing for AMD Am29LV040B, 512 KB: probe_29f040b: id1 0x0, id2 0x80 Probing for ASD AE49F2008, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT25DF021, 256 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF041A, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF081, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF161, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF321, 4096 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF321A, 4096 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25DF641, 8192 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25F512B, 64 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25FS010, 128 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT25FS040, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF041, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF081A, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF161, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26DF161A, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT26F004, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT29C020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT29C040A, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for Atmel AT45CS1282, 16896 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB011D, 128 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB021D, 256 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB041D, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB081D, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB161D, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB321C, 4224 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB321D, 4096 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT45DB642D, 8192 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Atmel AT49F002(N), 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Atmel AT49F002(N)T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for AMIC A25L40P, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=4
The FIFO pointer 6 is 0. [ef][30][14][42] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for AMIC A29002B, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for AMIC A29002T, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for AMIC A29040B, 512 KB: probe_29f040b: id1 0x0, id2 0x80 Probing for AMIC A49LF040A, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for EMST F49B002UA, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EON EN29F002(A)(N)B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for EON EN29F002(A)(N)T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for Fujitsu MBM29F004BC, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for Fujitsu MBM29F004TC, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for Fujitsu MBM29F400BC, 512 KB: probe_m29f400bt: id1 0x0, id2 0x74 Probing for Fujitsu MBM29F400TC, 512 KB: probe_m29f400bt: id1 0x0, id2 0x74 Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x0, id2 0x80 Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x4d, id2 0x49 Probing for Macronix MX25L512, 64 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1005, 128 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L2005, 256 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L4005, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L8005, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L1605, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L3205, 4096 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX25L6405, 8192 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix MX29F002B, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for Macronix MX29F002T, 256 KB: probe_29f002: id1 0xff, id2 0xff Probing for Macronix MX29LV040C, 512 KB: probe_29f002: id1 0x0, id2 0x80 Probing for Numonyx M25PE10, 128 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Numonyx M25PE20, 256 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Numonyx M25PE40, 256 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Numonyx M25PE80, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Numonyx M25PE16, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV010, 128 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV016B, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV020, 256 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV040, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV080B, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm25LV512, 64 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC Pm49FL002, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for PMC Pm49FL004, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for Sharp LHF00L04, 1024 KB: probe_lhf00l04: id1 0x4d, id2 0x49 Probing for Spansion S25FL016A, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF016B, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF032B, 4096 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF040B, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST25VF080B, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST SST28SF040A, 512 KB: probe_28sf040: id1 0x0, id2 0x80 Probing for SST SST29EE010, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST29LE010, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST29EE020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST29LE020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39SF010A, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39SF020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39SF040, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for SST SST39VF512, 64 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF010, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF020, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST39VF040, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for SST SST49LF002A/B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF003A/B, 384 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF004A/B, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for SST SST49LF004C, 512 KB: probe_49lfxxxc: id1 0x0, id2 0x80 Probing for SST SST49LF008A, 1024 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for SST SST49LF008C, 1024 KB: probe_49lfxxxc: id1 0x4d, id2 0x49 Probing for SST SST49LF016C, 2048 KB: probe_49lfxxxc: id1 0x4d, id2 0x49 Probing for SST SST49LF020A, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SST SST49LF040, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for SST SST49LF040B, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for SST SST49LF080A, 1024 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for SST SST49LF160C, 2048 KB: probe_49lfxxxc: id1 0x4d, id2 0x49 Probing for ST M25P05-A, 64 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P10-A, 128 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P20, 256 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P40, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P40-old, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. Probing for ST M25P80, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P16, 2048 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P32, 4096 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P64, 8192 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M25P128, 16384 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST M29F002B, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M29F002T/NT, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M29F040B, 512 KB: probe_29f040b: id1 0x0, id2 0x80 Probing for ST M29F400BT, 512 KB: probe_m29f400bt: id1 0x0, id2 0x74 Probing for ST M29W010B, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for ST M29W040B, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for ST M50FLW040A, 512 KB: probe_stm50flw0x0x: id1 0x0, id2 0x80 Probing for ST M50FLW040B, 512 KB: probe_stm50flw0x0x: id1 0x0, id2 0x80 Probing for ST M50FLW080A, 1024 KB: probe_stm50flw0x0x: id1 0x4d, id2 0x49 Probing for ST M50FLW080B, 1024 KB: probe_stm50flw0x0x: id1 0x4d, id2 0x49 Probing for ST M50FW002, 256 KB: probe_49lfxxxc: id1 0xff, id2 0xff Probing for ST M50FW016, 2048 KB: probe_82802ab: id1 0x4d, id2 0x49 Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x0, id2 0x80 Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x4d, id2 0x49 Probing for ST M50LPW116, 2048 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for SyncMOS S29C31004T, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for SyncMOS S29C51001T, 128 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C51002T, 256 KB: probe_jedec: id1 0xff, id2 0xff, id1 parity violation Probing for SyncMOS S29C51004T, 512 KB: probe_jedec: id1 0x0, id2 0x80, id1 parity violation Probing for Winbond W25x10, 128 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25x20, 256 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25x40, 512 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Winbond W25x80, 1024 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 sb600_spi_command, cmd=5, writecnt=1, readcnt=1 [0] [ 0]The FIFO pointer 6 is 1. [00] Chip status register is 00 Found chip "Winbond W25x80" (1024 KB) at physical address 0xfff00000. Probing for Winbond W29C011, 128 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W29C020C, 256 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W29C040P, 512 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W29EE011, 128 KB: === Probing disabled for Winbond W29EE011 because the probing sequence puts the AMIC A49LF040A in a funky state. Use 'flashrom -c W29EE011' if you have a board with this chip. === Probing for Winbond W39V040A, 512 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W39V040B, 512 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W39V040C, 512 KB: probe_w39v040c: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W39V040FA, 512 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W39V080A, 1024 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W49F002U, 256 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W49V002A, 256 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W49V002FA, 256 KB: probe_jedec: id1 0x4d, id2 0x49, id1 parity violation Probing for Winbond W39V080FA, 1024 KB: probe_winbond_fwhub: vid 0x4d, did 0x49 Probing for Winbond W39V080FA (dual mode), 512 KB: probe_winbond_fwhub: vid 0x4d, did 0x49 Probing for Atmel unknown Atmel SPI chip, 0 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for EON unknown EON SPI chip, 0 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for Macronix unknown Macronix SPI chip, 0 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for PMC unknown PMC SPI chip, 0 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for SST unknown SST SPI chip, 0 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 Probing for ST unknown ST SPI chip, 0 KB: sb600_spi_command, cmd=9f, writecnt=0, readcnt=3
The FIFO pointer 6 is 0. [ef][30][14] RDID returned ef 30 14. probe_spi_rdid_generic: id1 0xef, id2 0x3014 No operations were specified.
-[0000:00]-+-00.0 Advanced Micro Devices [AMD] RS780 Host Bridge [1022:9600] +-02.0-[0000:01]--+-00.0 ATI Technologies Inc RV770 [Radeon HD 4850] [1002:9442] | -00.1 ATI Technologies Inc HD48x0 audio [1002:aa30] +-04.0-[0000:02]----00.0 Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller [11ab:4364] +-11.0 ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode] [1002:4390] +-12.0 ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] +-12.1 ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] +-12.2 ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] +-13.0 ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] +-13.1 ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398] +-13.2 ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] +-14.0 ATI Technologies Inc SBx00 SMBus Controller [1002:4385] +-14.1 ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] +-14.2 ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] +-14.3 ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] +-14.4-[0000:03]-- +-14.5 ATI Technologies Inc SB700/SB800 USB OHCI2 Controller [1002:4399] +-18.0 Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration [1022:1200] +-18.1 Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map [1022:1201] +-18.2 Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller [1022:1202] +-18.3 Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control [1022:1203] -18.4 Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control [1022:1204]
superiotool r3695 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0xffff, rev=0xff Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x4e... Found Fintek F71882FG/F71883FG (vid=0x3419, id=0x4105) at 0x4e Register dump: idx 20 21 23 24 25 26 27 28 29 2a 2b 2c 2d val 05 41 19 34 00 00 30 72 00 00 00 08 0e def 05 41 19 34 00 00 00 00 00 00 00 08 08 LDN 0x00 (Floppy) idx 30 60 61 70 74 f0 f2 f4 val 00 00 00 00 04 0e ff 00 def 01 03 f0 06 02 0e 03 00 LDN 0x01 (COM1) idx 30 60 61 70 f0 val 00 00 00 00 00 def 01 03 f8 04 00 LDN 0x02 (COM2) idx 30 60 61 70 f0 f1 val 01 02 f8 03 10 54 def 01 02 f8 03 00 04 LDN 0x03 (Parallel port) idx 30 60 61 70 74 f0 val 00 00 00 00 04 08 def 01 03 78 07 03 42 LDN 0x04 (Hardware monitor) idx 30 60 61 70 val 01 02 25 00 def 01 02 95 00 LDN 0x05 (Keyboard) idx 30 60 61 70 72 f0 val 01 00 60 01 0c 83 def 01 00 60 00 00 83 LDN 0x06 (GPIO) idx 70 e0 e1 e2 e3 d0 d1 d2 d3 c0 c1 c2 c3 b0 b1 b2 b3 f0 f1 f2 f3 val ff 00 9f 04 00 00 ff ff 00 00 0f 0d 00 00 0f 09 00 00 7f 40 00 def 00 00 ff NA 00 00 ff NA 00 00 0f NA 00 00 0f NA 00 00 ff NA 00 LDN 0x07 (VID) idx 30 60 61 val 00 00 00 def 00 00 00 LDN 0x07 (SPI) idx f0 f1 f2 f3 f4 f5 f6 f7 f8 fa fb fc fd fe ff val 00 00 00 00 83 00 00 c7 77 3f 00 00 00 0f ff def 10 04 01 00 00 00 00 00 00 00 00 00 00 00 00 LDN 0x0a (PME, ACPI) idx 30 f0 f1 f4 f5 val 01 00 6c 06 1c def 00 00 01 06 1c Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x01,0x55,0x55/0xaa) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0x0541, rev=0x0 Probing for ITE Super I/O (init=legacy/it8661f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=legacy/it8671f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for NSC Super I/O at 0x2e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x15c... Failed. Returned data: port=0xff, port+1=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0x05/0x0f, rev=0x41 Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff
processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 9750 Quad-Core Processor stepping : 3 cpu MHz : 2399.227 cache size : 512 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good pni monitor cx16 lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs bogomips : 4798.44 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate
processor : 1 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 9750 Quad-Core Processor stepping : 3 cpu MHz : 2399.227 cache size : 512 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 4 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good pni monitor cx16 lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs bogomips : 4800.35 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate
processor : 2 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 9750 Quad-Core Processor stepping : 3 cpu MHz : 2399.227 cache size : 512 KB physical id : 0 siblings : 4 core id : 2 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good pni monitor cx16 lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs bogomips : 4800.21 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate
processor : 3 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 9750 Quad-Core Processor stepping : 3 cpu MHz : 2399.227 cache size : 512 KB physical id : 0 siblings : 4 core id : 3 cpu cores : 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good pni monitor cx16 lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs bogomips : 4800.22 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate
Hi Alois,
On 23.06.2009 10:15, Alois Schlögl wrote:
I'm wondering whether coreboot will work in my machine. Here is requested information [...]
- System:
SAPPHIRE PI-AM2RS780G, AMDx86-64 QuadCore,
I have good and bad news for you. The good news is that your processor is supported pretty well (I think we're hunting down one strange interaction) and the 780G/SB700 combination is being worked on. The bad news is that we don't yet have a time estimate for when the 780G/SB700 code will be ready (it's blocked on some legal review inside AMD). Porting to any given board should be doable in a few weeks (or days, if we're really lucky) after the availability of 780G/SB700 code.
We'll make sure to send out an announcement once the 780G/SB700 code (or parts of it) has been released.
Judging from experience, the legal review happens faster if we can show more (or more interesting) reference customers, so if you plan to use coreboot on 780G/SB700 as part of university research, we'd tell AMD about this immediately.
Regards, Carl-Daniel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Carl-Daniel Hailfinger wrote:
Hi Alois,
On 23.06.2009 10:15, Alois Schlögl wrote:
I'm wondering whether coreboot will work in my machine. Here is requested information [...]
- System:
SAPPHIRE PI-AM2RS780G, AMDx86-64 QuadCore,
I have good and bad news for you. The good news is that your processor is supported pretty well (I think we're hunting down one strange interaction) and the 780G/SB700 combination is being worked on. The bad news is that we don't yet have a time estimate for when the 780G/SB700 code will be ready (it's blocked on some legal review inside AMD). Porting to any given board should be doable in a few weeks (or days, if we're really lucky) after the availability of 780G/SB700 code.
We'll make sure to send out an announcement once the 780G/SB700 code (or parts of it) has been released.
Judging from experience, the legal review happens faster if we can show more (or more interesting) reference customers, so if you plan to use coreboot on 780G/SB700 as part of university research, we'd tell AMD about this immediately.
Regards, Carl-Daniel
The reason for asking is the bug as described here: http://bugzilla.kernel.org/show_bug.cgi?id=13573
The bug is affecting my research at the university. It was suggested that a Bios-update could solve the problem.
Cheers, Alois
On Tue, Jun 23, 2009 at 2:28 AM, Alois Schlögl alois.schloegl@tugraz.atwrote:
The reason for asking is the bug as described here: http://bugzilla.kernel.org/show_bug.cgi?id=13573
The bug is affecting my research at the university. It was suggested that a Bios-update could solve the problem.
IIRC you can disable thermal throttling, but it's usually not a good idea if you expect to keep your machine running with reasonable performance under load. If the vendor BIOS had the proper tables (See section 2.4.2 on P-States in the AMD BIOS and Kernel Developer's Guide for Fam10 processors), your CPU would slow itself down to avoid generating too much heat. If you disable thermal throttling and continue to run your workload, your CPU will hit "Tjunction" at around 116 degrees C and shut itself off abruptly, possibly after physical damage has been done to the CPU or the socket.
I would suggest starting with something much simpler, like making sure you have quality thermal transfer compound applied in the proper quantity for your CPUs. I know it sounds stupid, but I have seen many machines from many datacenters with very powerful rack cooling overheat under heavy loads due to improperly applied thermal grease. There are many tutorials and videos on how to do this. Make sure you clean off the old thermal grease first with a high-concentration isopropyl alcohol (>90%) first.
On Wed, Jun 24, 2009 at 12:30 AM, David Hendricks dhendrix@google.comwrote:
On Tue, Jun 23, 2009 at 2:28 AM, Alois Schlögl alois.schloegl@tugraz.atwrote:
The reason for asking is the bug as described here: http://bugzilla.kernel.org/show_bug.cgi?id=13573
The bug is affecting my research at the university. It was suggested that a Bios-update could solve the problem.
IIRC you can disable thermal throttling, but it's usually not a good idea if you expect to keep your machine running with reasonable performance under load. If the vendor BIOS had the proper tables (See section 2.4.2 on P-States in the AMD BIOS and Kernel Developer's Guide for Fam10 processors), your CPU would slow itself down to avoid generating too much heat. If you disable thermal throttling and continue to run your workload, your CPU will hit "Tjunction" at around 116 degrees C and shut itself off abruptly, possibly after physical damage has been done to the CPU or the socket.
I would suggest starting with something much simpler, like making sure you have quality thermal transfer compound applied in the proper quantity for your CPUs. I know it sounds stupid, but I have seen many machines from many datacenters with very powerful rack cooling overheat under heavy loads due to improperly applied thermal grease. There are many tutorials and videos on how to do this. Make sure you clean off the old thermal grease first with a high-concentration isopropyl alcohol (>90%) first.
Oh, and while you're at it make sure the heatsinks are securely fastened. After you re-apply thermal grease, tighten the screws such that they will not turn any more. The mounting points on the motherboard will ensure the maximum threshold is not exceeded, though I suggest tightening one about 80-90%, then the second one 100%, then finish the first one to apply the pressure more evenly.
Just another very silly thing that can cause unexpected behavior under heavy workloads...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
David Hendricks wrote:
On Wed, Jun 24, 2009 at 12:30 AM, David Hendricks dhendrix@google.comwrote:
On Tue, Jun 23, 2009 at 2:28 AM, Alois Schlögl alois.schloegl@tugraz.atwrote:
The reason for asking is the bug as described here: http://bugzilla.kernel.org/show_bug.cgi?id=13573
The bug is affecting my research at the university. It was suggested that a Bios-update could solve the problem.
IIRC you can disable thermal throttling, but it's usually not a good idea if you expect to keep your machine running with reasonable performance under load. If the vendor BIOS had the proper tables (See section 2.4.2 on P-States in the AMD BIOS and Kernel Developer's Guide for Fam10 processors), your CPU would slow itself down to avoid generating too much heat. If you disable thermal throttling and continue to run your workload, your CPU will hit "Tjunction" at around 116 degrees C and shut itself off abruptly, possibly after physical damage has been done to the CPU or the socket.
I would suggest starting with something much simpler, like making sure you have quality thermal transfer compound applied in the proper quantity for your CPUs. I know it sounds stupid, but I have seen many machines from many datacenters with very powerful rack cooling overheat under heavy loads due to improperly applied thermal grease. There are many tutorials and videos on how to do this. Make sure you clean off the old thermal grease first with a high-concentration isopropyl alcohol (>90%) first.
Oh, and while you're at it make sure the heatsinks are securely fastened. After you re-apply thermal grease, tighten the screws such that they will not turn any more. The mounting points on the motherboard will ensure the maximum threshold is not exceeded, though I suggest tightening one about 80-90%, then the second one 100%, then finish the first one to apply the pressure more evenly.
Just another very silly thing that can cause unexpected behavior under heavy workloads...
Thanks for these hints. That sound very reasonable to me. If understood you correctly, the shutdown occurs because the current bios is missing the _PSS table. Update the bios would resolve this, and re-apply thermal grease, would throttle the CPU later or not at all.
In order to update the bios, I tried followed also this approach http://ubuntuforums.org/showthread.php?p=2195208 as well as this http://manual.sidux.com/en/bios-freedos-en.htm
The final test showed that my USB-stick is bootable. Unfortunately, the system never boots from USB. I changed 1st, 2nd and 3rd boot device to USB-floppy, USB-ZIP, USB-CDROM and turned off HDD, no boot device was found. I guess this is another problem of the current bios. Therefore, coreboot would be really appreciated.
Carl-Daniel Hailfinger wrote:
Judging from experience, the legal review happens faster if we can show more (or more interesting) reference customers, so if you plan to use coreboot on 780G/SB700 as part of university research, we'd tell AMD about this immediately.
Carl,
you can tell AMD, that I'm working on some numerical methods that can efficiently handle missing values (encoded as NaN)
http://hci.tugraz.at/schloegl/matlab/NaN/ http://hci.tugraz.at/schloegl/matlab/tsa/
These methods are quite useful in various applications of biomedical signal processing (like electroencephalography) http://biosig.sourceforge.net/ http://hci.tugraz.at/schloegl/
These methods could be useful for Brain-Computer interface research, and for a better understanding of the human brain. Perhaps, the methods will be also useful in other application areas.
Best regards, Alois
Hi Alois,
On 24.06.2009 14:24, Alois Schlögl wrote:
you can tell AMD, that I'm working on some numerical methods that can efficiently handle missing values (encoded as NaN) [...] These methods could be useful for Brain-Computer interface research, and for a better understanding of the human brain. Perhaps, the methods will be also useful in other application areas.
Thank you for the detailed description. I've forwarded the info to AMD and hope it will give us additional leverage.
Regards, Carl-Daniel
Hi Alois,
I first want to say that I agree with kernel people that this is a BIOS issue.
Alois Schlögl wrote:
I'm wondering whether coreboot will work in my machine.
Not coreboot, but flashrom looks good.
Found chip "Winbond W25x80" (1024 KB) at physical address 0xfff00000.
The BIOS update you linked to in kernel bugzilla, http://us.sapphiretech.com/drivers/78SAPV09_20090522_4854.zip, contains a BIOS from May, with upgrades from AGESA (this is a BIOS library from AMD) 3.3.2.0 to 3.3.2.3. I don't know if this will fix the problem you are seeing.
You could update your BIOS using flashrom and the 78SAPV09.BIN file in that zip. Run flashrom -E to erase your flash chip and then flashrom -wv 78SAPV09.BIN to program and verify the new BIOS.
Ideally you should have a restore method before trying this. flashrom -E if it works will erase the flash chip completely. If you have a power outage at that point the system will not start again and the flash chip must be reprogrammed somewhere/somehow else, or the mainboard replaced.
//Peter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Stuge wrote:
Hi Alois,
I first want to say that I agree with kernel people that this is a BIOS issue.
Alois Schlögl wrote:
I'm wondering whether coreboot will work in my machine.
Not coreboot, but flashrom looks good.
Found chip "Winbond W25x80" (1024 KB) at physical address 0xfff00000.
The BIOS update you linked to in kernel bugzilla, http://us.sapphiretech.com/drivers/78SAPV09_20090522_4854.zip, contains a BIOS from May, with upgrades from AGESA (this is a BIOS library from AMD) 3.3.2.0 to 3.3.2.3. I don't know if this will fix the problem you are seeing.
You could update your BIOS using flashrom and the 78SAPV09.BIN file in that zip. Run flashrom -E to erase your flash chip and then flashrom -wv 78SAPV09.BIN to program and verify the new BIOS.
Ideally you should have a restore method before trying this. flashrom -E if it works will erase the flash chip completely. If you have a power outage at that point the system will not start again and the flash chip must be reprogrammed somewhere/somehow else, or the mainboard replaced.
//Peter
Hi Peter,
thanks for this hint. I tried it,
flashrom -E says:
$ sudo flashrom -E Calibrating delay loop... OK. No coreboot table found. Found chipset "ATI(AMD) SB700", enabling flash write... OK. Found chip "Winbond W25x80" (1024 KB) at physical address 0xfff00000. Erasing flash chip... FAILED! ERROR at 0x00100000: Expected=0xff, Read=0x00
My first thought was to reboot the machine, and see whether there is a bios setting the protected the flash from writing. Thankfully, I checked first the content of the bios with flashrom -r bios.1 and the bios was empty.
I think the error message "Erasing flash chip... FAILED!" is misleading, because the bios was already erased.
Flashing the bios was no problem.
$ sudo flashrom -wv 78SAPV09.BIN Calibrating delay loop... OK. No coreboot table found. Found chipset "ATI(AMD) SB700", enabling flash write... OK. Found chip "Winbond W25x80" (1024 KB) at physical address 0xfff00000. Flash image seems to be a legacy BIOS. Disabling checks. Erasing flash before programming... done. Programming flash................................ done. Verifying flash... VERIFIED.
Thanks,
Alois
Alois Schlögl wrote:
Found chip "Winbond W25x80" (1024 KB) at physical address 0xfff00000. Erasing flash chip... FAILED! ERROR at 0x00100000: Expected=0xff, Read=0x00
..
I think the error message "Erasing flash chip... FAILED!" is misleading, because the bios was already erased.
I agree. This is a bug in flashrom. It seems that you are using somewhat old code and I think the bug may have been fixed already.
It would be good if you could test erasing and writing again, using the very latest source code from svn.
Flashing the bios was no problem.
Good.
//Peter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Stuge wrote:
Hi Alois,
I first want to say that I agree with kernel people that this is a BIOS issue.
Alois Schlögl wrote:
I'm wondering whether coreboot will work in my machine.
Not coreboot, but flashrom looks good.
Found chip "Winbond W25x80" (1024 KB) at physical address 0xfff00000.
The BIOS update you linked to in kernel bugzilla, http://us.sapphiretech.com/drivers/78SAPV09_20090522_4854.zip, contains a BIOS from May, with upgrades from AGESA (this is a BIOS library from AMD) 3.3.2.0 to 3.3.2.3. I don't know if this will fix the problem you are seeing.
You could update your BIOS using flashrom and the 78SAPV09.BIN file in that zip. Run flashrom -E to erase your flash chip and then flashrom -wv 78SAPV09.BIN to program and verify the new BIOS.
Ideally you should have a restore method before trying this. flashrom -E if it works will erase the flash chip completely. If you have a power outage at that point the system will not start again and the flash chip must be reprogrammed somewhere/somehow else, or the mainboard replaced.
//Peter
As pointed out in my previous mail, http://www.coreboot.org/pipermail/coreboot/2009-June/050342.html I flashed the bios. Unfortunately, the thermal problem did not go away:
/var/log/kern.log still contains this message:
Jun 30 08:37:56 bcipc038 kernel: [ 4.123091] powernow-k8: Found 1 AMD Phenom(tm) 9750 Quad-Core Processor processors (4 cpu cores) (version 2.20.00) Jun 30 08:37:56 bcipc038 kernel: [ 4.123109] [Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands. Please report this to the Linux ACPI maintainers and complain to your BIOS vendor. Jun 30 08:37:56 bcipc038 kernel: [ 4.123173] [Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands. Please report this to the Linux ACPI maintainers and complain to your BIOS vendor. Jun 30 08:37:56 bcipc038 kernel: [ 4.123232] [Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands. Please report this to the Linux ACPI maintainers and complain to your BIOS vendor. Jun 30 08:37:56 bcipc038 kernel: [ 4.123292] [Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands. Please report this to the Linux ACPI maintainers and complain to your BIOS vendor.
And when running the test program, the computer shuts down after about 5 minutes. kern.log contains this message.
Jun 30 08:36:37 bcipc038 kernel: [ 489.955510] ACPI Exception (thermal-0479): AE_ERROR, ACPI thermal trip point state changed Jun 30 08:36:37 bcipc038 kernel: [ 489.955513] Please send acpidump to linux-acpi@vger.kernel.org Jun 30 08:36:37 bcipc038 kernel: [ 489.955515] [20080926] Jun 30 08:36:37 bcipc038 kernel: [ 489.955859] ACPI: Critical trip point Jun 30 08:36:37 bcipc038 kernel: [ 489.955869] Critical temperature reached (71 C), shutting down. Jun 30 08:36:37 bcipc038 kernel: [ 489.955895] ACPI: Unable to turn cooling device [ffff88012f815ba0] 'on' Jun 30 08:36:39 bcipc038 kernel: [ 491.278881] [drm] Resetting GPU Jun 30 08:36:39 bcipc038 kernel: [ 491.462578] mtrr: MTRR 5 not used Jun 30 08:36:43 bcipc038 kernel: [ 495.952253] Critical temperature reached (58 C), shutting down.
The reduction of the shutdown time from 50 min to 5 min makes the situation even worse.
Alois
Alois Schlögl wrote:
/var/log/kern.log still contains this message:
Jun 30 08:37:56 bcipc038 kernel: [ 4.123091] powernow-k8: Found 1 AMD Phenom(tm) 9750 Quad-Core Processor processors (4 cpu cores) (version 2.20.00) Jun 30 08:37:56 bcipc038 kernel: [ 4.123109] [Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands. Please report this to the Linux ACPI maintainers and complain to your BIOS vendor.
I think the BIOS basically does not properly support either your CPU or Linux or the combination of the two. :\
The reduction of the shutdown time from 50 min to 5 min makes the situation even worse.
I understand. It should be equally easy to flash an older version of the BIOS using flashrom to get the old behavior back.
//Peter
-
Alois Schlögl -
Carl-Daniel Hailfinger -
David Hendricks -
Peter Stuge