[Bug 211852] Unsafe shutdowns on Intel 750 SSD

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211852 --- Comment #8 from Nathan Whitehorn --- (In reply to Rajil Saraswat from comment #7) Assuming the patch applies, yes. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 211852] Unsafe shutdowns on Intel 750 SSD

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211852 --- Comment #7 from Rajil Saraswat --- (In reply to Nathan Whitehorn from comment #5) Can i patch this against 11.1-release? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 221458] as

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221458 Bug ID: 221458 Summary: as Product: Base System Version: 9.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority:

[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 --- Comment #9 from Mark Millard --- (In reply to Mark Millard from comment #8) I should also have said: The Windows 10 Task Manager Performance tab display of CPU usage on threads/cores suggested a possible

[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 --- Comment #8 from Mark Millard --- (In reply to execve from comment #7) I tried a couple of variations of the experiment that I suggested. Unfortunately the results are a little complicated to interpret. Context:

[Bug 211852] Unsafe shutdowns on Intel 750 SSD

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211852 --- Comment #6 from commit-h...@freebsd.org --- A commit references this bug: Author: nwhitehorn Date: Sat Aug 12 22:13:06 UTC 2017 New revision: 322443 URL: https://svnweb.freebsd.org/changeset/base/322443 Log: Move NVME controller

[Bug 221356] [patch] Improve swapon_check_swzone() function in swap_pager.c

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221356 --- Comment #1 from Konstantin Belousov --- There is WIP https://reviews.freebsd.org/D11435 which affects significant part of the patch. In particular, the zone limiting bits might go out altogether. I suggest to wait

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903 Mark Millard changed: What|Removed |Added CC|

[Bug 221445] The absence of the accept_rtadv option causes an error "ping6: sendmsg: No buffer space available"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221445 --- Comment #4 from Vladislav V. Prodan --- (In reply to Andrey V. Elsukov from comment #3) >> Read the description of the bug again. >> I described how I managed to get the ipv6 to work. >It is wrong, and this is

[Bug 221445] The absence of the accept_rtadv option causes an error "ping6: sendmsg: No buffer space available"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221445 --- Comment #3 from Andrey V. Elsukov --- (In reply to Vladislav V. Prodan from comment #2) > Read the description of the bug again. > I described how I managed to get the ipv6 to work. It is wrong, and this is why it

[Bug 221445] The absence of the accept_rtadv option causes an error "ping6: sendmsg: No buffer space available"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221445 --- Comment #2 from Vladislav V. Prodan --- (In reply to Andrey V. Elsukov from comment #1) Read the description of the bug again. I described how I managed to get the ipv6 to work. -- You are receiving this mail

[Bug 221446] add net default: gateway [IPv6 gateway] fib 0: route already in table

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221446 --- Comment #3 from Vladislav V. Prodan --- (In reply to Andrey V. Elsukov from comment #2) Then look Bug ID 221445. Without the accept_rtadv option, ipv6 stops working. -- You are receiving this mail because: You

[Bug 221446] add net default: gateway [IPv6 gateway] fib 0: route already in table

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221446 Andrey V. Elsukov changed: What|Removed |Added CC|

[Bug 221445] The absence of the accept_rtadv option causes an error "ping6: sendmsg: No buffer space available"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221445 Andrey V. Elsukov changed: What|Removed |Added CC|

[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 --- Comment #7 from exe...@gmail.com --- I do not think there is any need to increase the memory usage. Like I mentioned in the original PR description, even without X running on the same system with 8GB RAM, I could reproduce this using a

[Bug 221446] add net default: gateway [IPv6 gateway] fib 0: route already in table

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221446 --- Comment #1 from Vladislav V. Prodan --- Created attachment 185324 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185324=edit /etc/sysctl.conf -- You are receiving this mail because: You are the

[Bug 221446] add net default: gateway [IPv6 gateway] fib 0: route already in table

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221446 Bug ID: 221446 Summary: add net default: gateway [IPv6 gateway] fib 0: route already in table Product: Base System Version: 11.1-STABLE Hardware: Any

[Bug 221441] Hacked By KingSkrupellos Cyberizm.Org Digital Security Technological Turkish Moslem Army

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221441 Bartek Rutkowski changed: What|Removed |Added CC|

[Bug 221445] The absence of the accept_rtadv option causes an error "ping6: sendmsg: No buffer space available"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221445 Bug ID: 221445 Summary: The absence of the accept_rtadv option causes an error "ping6: sendmsg: No buffer space available" Product: Base System Version: 11.1-STABLE

[Bug 221441] Hacked By KingSkrupellos Cyberizm.Org Digital Security Technological Turkish Moslem Army

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221441 Andreas Andersson changed: What|Removed |Added Flags|

[Bug 221441] Hacked By KingSkrupellos Cyberizm.Org Digital Security Technological Turkish Moslem Army

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221441 Bug ID: 221441 Summary: Hacked By KingSkrupellos Cyberizm.Org Digital Security Technological Turkish Moslem Army Product: Base System Version: 9.1-RELEASE Hardware:

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903 muxx@gmail.com changed: What|Removed |Added CC||muxx@gmail.com ---

[Bug 221439] ix ethernet doesn't link to switch if vlans are enabled.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221439 Bug ID: 221439 Summary: ix ethernet doesn't link to switch if vlans are enabled. Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any

[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 --- Comment #6 from Mark Millard --- (In reply to execve from comment #4) FYI since you have more RAM than the original context for that stress command I'll quote from the man page: -m, --vm N

Re: [Bug 221418] FreeBSD 10.4-PRERELEASE fails to build on systems using 32 bit time_t since r322315.

On Fri, 11 Aug 2017 a bug that doesn't want repl...@freebsd.org wrote: --- Comment #1 from Conrad Meyer --- Truncated INT64_MIN should be INT32_MIN on 2's complement, not 0. Seems like we just lack a (time_t) cast on the value. Truncated INT64_MIN should be and is, 0 in

[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 --- Comment #5 from Mark Millard --- (In reply to execve from comment #4) Cool. (I suppose top or some such could be used to confirm the expected activity, given the amount of RAM and other such context.) I wonder

[Bug 221432] asdasd

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221432 Bug ID: 221432 Summary: asdasd Product: Base System Version: 8.4-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me

[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 --- Comment #4 from exe...@gmail.com --- Yes, it seems to hold itself together fine for more than 10 minutes :). root@mellon:~ # swapinfo Device 1K-blocks UsedAvail Capacity /dev/md99 83886080 8388608

[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 --- Comment #3 from Mark Millard --- (In reply to execve from comment #2) I suggest the test of using the port sysutils/stress and trying: stress -d 2 -m 3 --vm-keep I'd be interested to know if a swap file context