summaryrefslogtreecommitdiffstats
path: root/sys/vm
diff options
context:
space:
mode:
authorattilio <attilio@FreeBSD.org>2009-11-04 01:32:59 +0000
committerattilio <attilio@FreeBSD.org>2009-11-04 01:32:59 +0000
commit68e40aae5fc21f7296db7a8328b1ebb5d8683c1b (patch)
tree237457e82c0af41da784995938264934515de402 /sys/vm
parentf9efe0335684909e08cb425bae838b98bdce4e6a (diff)
downloadFreeBSD-src-68e40aae5fc21f7296db7a8328b1ebb5d8683c1b.zip
FreeBSD-src-68e40aae5fc21f7296db7a8328b1ebb5d8683c1b.tar.gz
Opteron rev E family of processor expose a bug where, in very rare
ocassions, memory barriers semantic is not honoured by the hardware itself. As a result, some random breakage can happen in uninvestigable ways (for further explanation see at the content of the commit itself). As long as just a specific familly is bugged of an entire architecture is broken, a complete fix-up is impratical without harming to some extents the other correct cases. Considering that (and considering the frequency of the bug exposure) just print out a warning message if the affected machine is identified. Pointed out by: Samy Al Bahra <sbahra at repnop dot org> Help on wordings by: jeff MFC: 3 days
Diffstat (limited to 'sys/vm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud