Your message dated Wed, 22 Oct 2014 19:12:41 +0100
with message-id <5447f399.9070...@pyro.eu.org>
and subject line Re: Bug#752571: kfreebsd-10: PCID disabled upstream
has caused the Debian Bug report #752571,
regarding kfreebsd-10: PCID disabled upstream
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
752571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kfreebsd-10
Version: 10.0-6
Severity: important
Tags: upstream
Hi,
Upstream have disabled PCID by default in the 10.0-RELEASE branch.
Errata Note EN-14:07 explains why:
http://security.freebsd.org/advisories/FreeBSD-EN-14:07.pmap.asc
The bug could cause instability in openjdk-7:
http://www.freebsd.org/cgi/query-pr.cgi?pr=187238
So, we may want to do this same. Although I haven't noticed any
problems that appear to be related to it. Probably I don't have any
CPUs with PCID support.
Later 10.x releases may re-enable it, as 10-STABLE already has some
further PCID fixes.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: kfreebsd-amd64 (x86_64)
Kernel: kFreeBSD 9.0-2-amd64-xenhvm-ipsec
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source-Version: 10.1~svn270273-1
--- End Message ---
