https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #46 from Warner Losh ---
I've re-read things, and I think everybody is hanging the 'timeout' issue on
this bug report when really it looks like there's several different
pathologies... Those that clear up after a power cycle, f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245189
--- Comment #7 from commit-h...@freebsd.org ---
A commit references this bug:
Author: sjg
Date: Tue Apr 14 01:07:59 UTC 2020
New revision: 359913
URL: https://svnweb.freebsd.org/changeset/base/359913
Log:
Do not claim libbearssl et al ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #45 from Wayne Willcox ---
(In reply to Warner Losh from comment #44)
one of the power supplies is a 600 corsair (not going to take the other system
apart that also had this issue). I will try a third one power supply when I
ta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #44 from Warner Losh ---
(In reply to Wayne Willcox from comment #42)
I ask because we have many thousands of machines deployed, and a thousand or so
of those have intermittent power supply issues which means at any time we hav
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #43 from Daniel Bell ---
(In reply to sec from comment #38)
I'm sorry I didn't respond sooner, but for my issue, sec was 100% right: a cold
power cycle, as bizarre as that sounded to me, along with the loader.conf
tweaks mentio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #42 from Wayne Willcox ---
Absolutely sure? No having said that I have seen the problem on 2 different
systems with 2 different power supplies. Additionally the power supplies have
been fine and not had any other problems AND
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #41 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #40 from Wayne Willcox ---
Ok so even with the write_cache disabled it started getting the errors and
hung. So this is a pretty serious issue at this point the WD Blue drives (and
maybe others) are not at all reliable with zfs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245597
Rafal Lukawiecki changed:
What|Removed |Added
Summary|TSC |TSC Running Slow on Xeon
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240762
--- Comment #7 from Dan Langille ---
I updated a host to FreeBSD 12 -stable on 2020-04-08:
$ uname -a
FreeBSD fmd-12stbl-01tst.vrt.sourcefire.com 12.1-STABLE FreeBSD 12.1-STABLE
r359329 GENERIC amd64
We're still see this on that host:
A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
Wayne Willcox changed:
What|Removed |Added
CC||wwillc...@gmail.com
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233098
John Murphy changed:
What|Removed |Added
CC||johnjomur...@gmail.com
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245597
Bug ID: 245597
Summary: TSC
Product: Base System
Version: 11.3-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
P
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245541
--- Comment #1 from Sebastian S ---
I found some memory related issues on the server. I will replace the modules
and will update or close the bug ticket.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216897
Sofian Brabez changed:
What|Removed |Added
URL||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216897
Sofian Brabez changed:
What|Removed |Added
Status|New |In Progress
CC|
16 matches
Mail list logo
