aboutsummaryrefslogtreecommitdiff
path: root/ObsoleteFiles.inc
diff options
context:
space:
mode:
authorAndriy Gapon <avg@FreeBSD.org>2018-05-05 05:22:11 +0000
committerAndriy Gapon <avg@FreeBSD.org>2018-05-05 05:22:11 +0000
commit34577ddb157019f42a12193090c880440a62bf4d (patch)
tree433325841d5dc2aeb64eb37fd3d3065ff3c16579 /ObsoleteFiles.inc
parentbd3afae0cab4e5d8de28ef0045115fae00097669 (diff)
downloadsrc-34577ddb157019f42a12193090c880440a62bf4d.tar.gz
src-34577ddb157019f42a12193090c880440a62bf4d.zip
amdsbwd: fix reboot status reporting
Originally, I overlooked that PMIO register 0xc0 has a dual personality. It can either be S5/Reset Status register or Misc. Fix register (aka debug status register). The mode is controlled by bit 2 in PMIO register 0xc4. Apparently there are register programming requirements for the second personality, so many BIOSes leave the register, after programming it, in that mode. So, we need to switch the register to the correct mode. Additionally, AMDSB8_WD_RST_STS was defined incorrectly as bit 13 while it is actually bit 25 (and the register's width is 32 bits, not 16). With this change I see the following in dmesg after a reset by the watchdog: amdsbwd0: ResetStatus = 0x42000000 amdsbwd0: Previous Reset was caused by Watchdog MFC after: 2 weeks
Notes
Notes: svn path=/head/; revision=333269
Diffstat (limited to 'ObsoleteFiles.inc')
0 files changed, 0 insertions, 0 deletions