https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217138
--- Comment #20 from Mark Millard ---
Created attachment 180836
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180836&action=edit
Updated source that shows a tie to a 4KByte sized unit of failure
See the comments tied to partial
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #21 from Terry Kennedy ---
(In reply to Warner Losh from comment #19)
It is a MZVPW128HEGM-0 which is a SM961. This has happened in multiple
systems (identical hardware configs - see below) which otherwise are operating
flaw
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217782
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Summary|PVS-Studio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217783
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217784
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|freebsd-bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217785
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217796
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|b...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #20 from Warner Losh ---
In addition, you can control the timeout period with the sysctl
dev.nvme.X.timeout=S where S is the number of seconds. The min is 5, max is
120. The default is 30. It might be helpful to see if setting i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217796
Bug ID: 217796
Summary: BSD diff(1) long options aren't documented in manpage,
e.g., --ignore-case
Product: Base System
Version: CURRENT
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #19 from Warner Losh ---
My samsung 960 PRO works great. We have other (hundreds) drives at work that
are doing close to 3.8GB/s steady for hours So it can work... Let's dig
down a level...
So the 'reset' messages that Terr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217795
Ngie Cooper changed:
What|Removed |Added
Severity|Affects Only Me |Affects Many People
Assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217795
Bug ID: 217795
Summary: etcupdate broken after ^/head@r315051:
--changed-group-format not implemented
Product: Base System
Version: CURRENT
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217794
Bug ID: 217794
Summary: pcap-int.h of contrib/libpcap missing in /usr/include
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #18 from Terry Kennedy ---
(In reply to MacLemon from comment #17)
I'd suggest testing with a single card first, to rule out some potential PCIe
bifurcation* problems. My single SM961 works as expected under Linux (some
random L
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #17 from MacLemon ---
I've done some testing now on FreeBSD 11.0p3-RELEASE and 12.0-CURRENT.
I've tested two of these Samsung SM961/256GB in a SuperServer 5018D-FN4T with
SuperMicro AOC-SLG3-2M2.
I've done all possible combinati
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217787
Tobias Kortkamp changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Prog
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #16 from Terry Kennedy ---
Looks like my text got lost when I added the images. This is a boot with
12-CURRENT 20170309 (the latest snapshot available). It looks like the driver
is making a bit more progress with the nvd0: devic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #15 from Terry Kennedy ---
Created attachment 180828
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180828&action=edit
newfs output - also makes some progress
--
You are receiving this mail because:
You are the assi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #14 from Terry Kennedy ---
Created attachment 180827
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180827&action=edit
dd fails with error, but made some progress
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #13 from Terry Kennedy ---
Created attachment 180826
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180826&action=edit
Boot capture with uname and "resetting controller"
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217787
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: tobik
Date: Tue Mar 14 20:31:10 UTC 2017
New revision: 315283
URL: https://svnweb.freebsd.org/changeset/base/315283
Log:
Fix sysdecode_cap_rights which
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217787
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #2 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217789
Gleb Smirnoff changed:
What|Removed |Added
Status|New |Open
Assignee|freebsd-bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217787
John Baldwin changed:
What|Removed |Added
Status|New |In Progress
--- Comment #1 from Joh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217138
--- Comment #19 from Mark Millard ---
(In reply to Mark Millard from comment #18)
https://lists.freebsd.org/pipermail/freebsd-arm/2017-March/015869.html
Should have had a subject/title saying arm64, not amd64.
https://lists.freebsd.org/p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217789
--- Comment #1 from free...@ihead.ru ---
Created attachment 180824
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180824&action=edit
Second time
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217789
Bug ID: 217789
Summary: FreeBSD 11 panic nginx, probably sendfile problem
Product: Base System
Version: 11.0-RELEASE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217787
Bug ID: 217787
Summary: libsysdecode: Bogus rights when decoding cap_rights_t
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
--- Comment #12 from Warner Losh ---
(In reply to tkurmann from comment #11)
I just pushed a few changes into -head that may help. Any chance you can try
booting a snapshot?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217785
Bug ID: 217785
Summary: sys/dev/mpr/mpr.c: PVS-Studio: Dead Code (CWE-561)
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217784
Bug ID: 217784
Summary: sys/dev/wi/if_wi_pci.c: PVS-Studio: Dead Code
(CWE-561)
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217783
Bug ID: 217783
Summary: sys/dev/cyapa/cyapa.c: PVS-Studio: V778 Two similar
code fragments were found. Perhaps, this is a typo and
'cap_resy' variable should be used instead of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217782
Bug ID: 217782
Summary: PVS-Studio: Assignment to Variable without Use
(CWE-563) (3)
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #17 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #16)
Hi Mateusz,
Sorry but i can't try this patch, i had to rollback the old kernel to avoid
crashes. It's a production server and i can't let it down. :(
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713
tkurm...@gmail.com changed:
What|Removed |Added
CC||tkurm...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217138
Mark Millard changed:
What|Removed |Added
Summary|head (e.g.) -r313999 for|head (e.g.) -r314638 for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217138
--- Comment #18 from Mark Millard ---
Created attachment 180808
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=180808&action=edit
C source for showing fork/swap memory corruption failure
I'm still at a loss about how to figure o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217138
--- Comment #17 from Mark Millard ---
https://lists.freebsd.org/pipermail/freebsd-arm/2017-March/015869.html
shows an about 110 line C program that shows data
corruption for fork-then-swap-out-then-swap-in.
The known-corrupted data is a m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203431
--- Comment #3 from holin...@saunalahti.fi ---
(In reply to holindho from comment #1)
Typoed: %s/macpro1,2/macpro2,1/gc
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203431
--- Comment #2 from holin...@saunalahti.fi ---
I've tested my patch on 10.3 and stable/11 and it probably applies to 12, too.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203431
holin...@saunalahti.fi changed:
What|Removed |Added
CC||holin...@saunalahti.fi
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215143
--- Comment #4 from holin...@saunalahti.fi ---
No, option booting doesn't help on this machine. It will only show a Windows CD
Icon and then comes the numeric choice where you cannot choose.
The further booting problem of RELEASE-11.0.0 whe
42 matches
Mail list logo