[Bug 193367] [panic] sleeping thread

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 Rene Ladan changed: What|Removed |Added Assignee|r...@freebsd.org |b...@freebsd.org -- You are

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 --- Comment #11 from Kalero --- (In reply to Lena from comment #10) Well, while I was waiting for an answer, I installed FreeBSD-11.2-RELEASE, installed nvidia-driver-340 from ports and, to check if the binary package also worked, removed

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 --- Comment #10 from Lena --- > Does this known bug also apply to nvidia-driver-340? Yes. Install from ports (make or portupgrade/portmaster). I have almost all others installed from packages. -- You are receiving this mail because: You

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 Kalero changed: What|Removed |Added CC||cronicasdebolsi...@gmail.co

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 Kubilay Kocak changed: What|Removed |Added Status|New |Closed

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 230620] "install -d" issue

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230620 --- Comment #2 from Eugene Grosbein --- (In reply to Ian Lepore from comment #1) Thank you for explanation. This is not obvious from the synopsis. Perhaps, it should be made more clear by replacing "directory ..." with "directory1 ...

[Bug 230620] "install -d" issue

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230620 Ian Lepore changed: What|Removed |Added CC||i...@freebsd.org --- Comment #1 from

[Bug 230620] "install -d" issue

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230620 Bug ID: 230620 Summary: "install -d" issue Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 --- Comment #8 from Paco Falcón --- Hola Dave!! Te envío un saludo muy grato y respetuoso. Muchas gracias por la atención y tú interés en aportarme tu experiencia. Fue inspiradora tu respuesta, pero no terminó de resolver mi angustia,

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 --- Comment #7 from Dave Cottlehuber --- Hi Paco! Welcome to FreeBSD. I used translate.google.com as I don't speak Spanish. I'll put some quick notes on how to build this package from source here but if you have any trouble please open a

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 Paco Falcón changed: What|Removed |Added CC||pacofalc...@gmail.com --- Comment

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694 --- Comment #3 from Eugene Grosbein --- Created attachment 195052 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=195052=edit procstat -kk -a output -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694 Eugene Grosbein changed: What|Removed |Added CC||sta...@freebsd.org --- Comment

[Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694 Mark Linimon changed: What|Removed |Added Assignee|sta...@freebsd.org |f...@freebsd.org

[Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694 --- Comment #1 from Andriy Gapon --- I am not too surprised. The pool configuration is not redundant and the whole top level vdev is corrupted. I suspect that the scrub command needs to write something to the pool to record the initial

[Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694 Bug ID: 229694 Summary: [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data Product: Base System Version: 11.2-STABLE Hardware: Any

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 --- Comment #5 from Ka Ho Ng --- (In reply to Jonathan M Davis from comment #3) kld built for FreeBSD 11.1 is supposed to work on FreeBSD 11.2 and so on. However due to a KBI bug exposed by r328469 the KBI of vm_map becomes incompatible

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: gjb Date: Thu Jun 28 15:30:52 UTC 2018 New revision: 335764 URL: https://svnweb.freebsd.org/changeset/base/335764 Log: Add an errata entry regarding

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 Jonathan M Davis changed: What|Removed |Added CC||freebsd.b...@jmdavisprog.co

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 m...@janh.de changed: What|Removed |Added CC||m...@janh.de --- Comment #9 from

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 227342] [dpv] dpv -x is broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227342 Eugene Grosbein changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 227342] [dpv] dpv -x is broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227342 --- Comment #2 from Devin Teske --- Tried with 11.2-RC3 and still unable to replicate -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org

[Bug 227342] [dpv] dpv -x is broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227342 --- Comment #1 from Devin Teske --- I will try with 11.2, but so far I was unable to replicate with either 11.0-RELEASE-p1 or 11.1-RELEASE (both amd64). -- You are receiving this mail because: You are on the CC list for the bug.

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

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

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 --- Comment #7 from Eric van Gyzen --- At the very least, this needs special mention in the release notes. Maybe the release notes could suggest that users change their configuration to avoid loading these modules until their packages

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 Rodney W. Grimes changed: What|Removed |Added CC||rgri...@freebsd.org ---

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 --- Comment #5 from Ka Ho Ng --- Below is one of the suspected change that causes KBI breakage, as vm_map_min/max/pmap are inline helpers before being made non-inline by https://svnweb.freebsd.org/base?view=revision=332091 :

[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 Ka Ho Ng changed: What|Removed |Added CC||khng...@gmail.com, |

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 Ka Ho Ng changed: What|Removed |Added CC||sta...@freebsd.org -- You are

[Bug 193367] [panic] sleeping thread

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org

[Bug 193367] [panic] sleeping thread

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367 Eitan Adler changed: What|Removed |Added Status|In Progress |Open --- Comment #19 from Eitan

[Bug 228174] [dump] dump(8) can read garbage and loop forever

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228174 Eugene Grosbein changed: What|Removed |Added Resolution|--- |Works As

[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 Eitan Adler changed: What|Removed |Added Status|In Progress |Open ---

[Bug 193388] [panic] bad pte

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193388 Eitan Adler changed: What|Removed |Added Status|In Progress |Open -- You

[Bug 193388] [panic] bad pte

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193388 Eitan Adler changed: What|Removed |Added Resolution|--- |Not Enough

[Bug 193388] [panic] bad pte

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193388 --- Comment #2 from Eitan Adler --- For bugs matching the following conditions: - Status == In Progress - Assignee == "b...@freebsd.org" - Last Modified Year <= 2017 Do - Set Status to "Open" -- You are receiving

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

[Bug 215471] Using bsnmpd with the snmp_hostres module on a vmware ESXi guest with a disconnected CD drive uses 100% CPU

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215471 Conrad Meyer changed: What|Removed |Added Resolution|--- |DUPLICATE

[Bug 221376] 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376 Eugene Grosbein changed: What|Removed |Added CC|

[Bug 215471] Using bsnmpd with the snmp_hostres module on a vmware ESXi guest with a disconnected CD drive uses 100% CPU

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215471 Eugene Grosbein changed: What|Removed |Added CC|

[Bug 215471] Using bsnmpd with the snmp_hostres module on a vmware ESXi guest with a disconnected CD drive uses 100% CPU

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215471 Eugene Grosbein changed: What|Removed |Added CC|

[Bug 228174] [dump] dump(8) can read garbage and loop forever

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228174 --- Comment #3 from Kirk McKusick --- Taking a snapshot is the same as if you unmounted the filesystem and dumped it. When you take a snapshot, the following steps are taken: 1) Any new system calls that want to write

[Bug 228174] [dump] dump(8) can read garbage and loop forever

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228174 --- Comment #2 from Eugene Grosbein --- (In reply to Kirk McKusick from comment #1) Yes, this is mounted and live file system and files are created here. Does UFS2+SU snapshot guarantee that dump won't get

[Bug 228174] [dump] dump(8) can read garbage and loop forever

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228174 --- Comment #1 from Kirk McKusick --- Are you are dumping on a live filesystem? If so, is it possible that the file causing the problem is being written at the time that dump is trying to dump it? If so, then dump may

[Bug 228174] [dump] dump(8) can read garbage and loop forever

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228174 Bug ID: 228174 Summary: [dump] dump(8) can read garbage and loop forever Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any Status: New

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 Kubilay Kocak changed: What|Removed |Added Keywords||crash, needs-qa

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 Eugene Grosbein changed: What|Removed |Added CC|

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #34 from Andriy Gapon --- (In reply to Eugene Grosbein from comment #32) Oh, yes, I have. I think that that stack trace indicates two issues. 1. That a sysctl handler to print dev.XXX.N.%pnpinfo performs an

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #33 from Eugene Grosbein --- Created attachment 193116 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193116=edit Giant lock(?) It seems, we have Giant lock here? See attachment. -- You are

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #32 from Eugene Grosbein --- (In reply to Andriy Gapon from comment #31) You probably overlooked the attachment https://bz-attachments.freebsd.org/attachment.cgi?id=193023 named "thread 257/100247", it has

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #31 from Andriy Gapon --- Have we seen a stack trace of what hald is doing in kernel yet? Konstantin requested that information in comment #19. -- You are receiving this mail because: You are the assignee

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #30 from Mark Knight --- Kernel and user land are now FreeBSD 10.4-RELEASE-p8 (SHREWD) #0 r333193: Thu May 3 22:30:26 BST 2018. Has been fine since I stopped running hald. As a test I just rebuilt

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #29 from Konstantin Belousov --- (In reply to Eugene Grosbein from comment #28) Did you rebuild hald itself when upgraded from 10.3 to 10.4 ? If not, do that. -- You are receiving this mail because: You are

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #28 from Eugene Grosbein --- (In reply to Bengt Ahlgren from comment #26) I think this is kernel or hardware problem despite of possible desync. In no event should simple sysctl system call hang "forever"

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #27 from Mark Knight --- The move to 10.4 was a buildworld buildkernel installkernel installworld and mergemaster so all modules and userland were rebuilt. Indeed, for a long time I've been running a 10.3

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 Bengt Ahlgren changed: What|Removed |Added CC||ben...@sics.se

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #25 from Eugene Grosbein --- (In reply to Mark Knight from comment #24) Have you rebuilt/reinstalled sysutils/hal after upgrade from 10.3 to 10.4? -- You are receiving this mail because: You are the

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #24 from Mark Knight --- Ah, thank you!! I don't recall why hald was installed (it was probably from a long time ago). I've removed it, and so far, I'm not seeing any symptoms, so long as I avoid sysctl -a.

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #23 from Eugene Grosbein --- The process holding sx lock is hald: 257 Thread 100247 (PID=1343: hald) sched_switch (td=0xf80079fd3000, newtd=, flags=) at /usr/src/sys/kern/sched_ule.c:1956 Hald

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #22 from Mark Knight --- Thanks. BIOS is 1006 (updated before I filed this bug) from https://www.asus.com/uk/Motherboards/PRIME-H270M-PLUS/HelpDesk_Download/. I see there's now a 1010 I could try. To reiterate

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #21 from Eugene Grosbein --- Mark, you should check if you have BIOS update for this box. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #20 from Eugene Grosbein --- Created attachment 193023 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193023=edit thread 257/100247 (In reply to Konstantin Belousov from comment #19) How does one

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 Konstantin Belousov changed: What|Removed |Added CC|

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #18 from Eugene Grosbein --- (In reply to Mark Knight from comment #16) I'm out of ideas. Could you please test 11.1-RELEASE or 11.2-PRERELEASE? I've seen similar reports that were 'fixed' by upgrading to

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 Kurt Jaeger changed: What|Removed |Added CC||p...@freebsd.org

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #16 from Mark Knight --- Any more thoughts on this please? Now Ports collection support for 10.3 has ended, this bug is now a hard blocker preventing me from upgrading to 10.4 and continuing to apply security

[Bug 227603] [panic] r323477: Sleeping thread owns a non-sleepable lock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227603 Eugene Grosbein changed: What|Removed |Added Resolution|--- |FIXED

[Bug 227603] [panic] r323477: Sleeping thread owns a non-sleepable lock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227603 --- Comment #4 from Stephen Hurd --- How's it looking? -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-stable@freebsd.org mailing list

[Bug 227654] [panic] repeatable crash with lagg+vlan+em

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654 Eugene Grosbein changed: What|Removed |Added Summary|[panic] repeatable crash|[panic]

[Bug 227654] [panic] repeatable crash with IPv6+lagg+vlan+em

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654 --- Comment #2 from Eugene Grosbein --- Created attachment 192690 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=192690=edit debugging patch for single user only Forgot to note that my kernel has VIMAGE too.

[Bug 227654] [panic] repeatable crash with IPv6+lagg+vlan+em

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654 --- Comment #1 from Eugene Grosbein --- $ addr2line -e kernel.debug -i -f -C 806fe6ac ether_output_frame /data2/src/sys/net/if_ethersubr.c:449 ether_output /data2/src/sys/net/if_ethersubr.c:435 (kgdb) l

[Bug 227654] [panic] repeatable crash with IPv6+lagg+vlan+em

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654 Bug ID: 227654 Summary: [panic] repeatable crash with IPv6+lagg+vlan+em Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any Status: New

[Bug 227603] [panic] r323477: Sleeping thread owns a non-sleepable lock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227603 Eugene Grosbein changed: What|Removed |Added Status|New |In Progress

[Bug 227603] [panic] r323477: Sleeping thread owns a non-sleepable lock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227603 Stephen Hurd changed: What|Removed |Added Assignee|mjo...@freebsd.org

[Bug 227603] [panic] r323477: Sleeping thread owns a non-sleepable lock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227603 Matthew Macy changed: What|Removed |Added CC|

[Bug 227603] [panic] r323477: Sleeping thread owns a non-sleepable lock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227603 Bug ID: 227603 Summary: [panic] r323477: Sleeping thread owns a non-sleepable lock Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any

[Bug 227342] [dpv] dpv -x is broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227342 Bug ID: 227342 Summary: [dpv] dpv -x is broken Product: Base System Version: 11.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some

[Bug 227322] [patch] [iicbus] sys/modules/i2c/iicbus cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227322 Ian Lepore changed: What|Removed |Added Resolution|--- |FIXED

[Bug 227323] [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227323 Ian Lepore changed: What|Removed |Added Resolution|--- |FIXED

[Bug 227322] [patch] [iicbus] sys/modules/i2c/iicbus cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227322 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: ian Date: Fri Apr 6 16:48:08 UTC 2018 New revision: 332113 URL: https://svnweb.freebsd.org/changeset/base/332113 Log: MFC r331868: Add

[Bug 227323] [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227323 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: ian Date: Fri Apr 6 16:48:08 UTC 2018 New revision: 332113 URL: https://svnweb.freebsd.org/changeset/base/332113 Log: MFC r331868: Add

[Bug 227323] [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227323 Bug ID: 227323 Summary: [patch] [spi] sys/modules/spi/mx25l cannot be built outside of kernel build environment Product: Base System Version: 11.1-STABLE Hardware:

[Bug 227322] [patch] [iicbus] sys/modules/i2c/iicbus cannot be built outside of kernel build environment

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227322 Bug ID: 227322 Summary: [patch] [iicbus] sys/modules/i2c/iicbus cannot be built outside of kernel build environment Product: Base System Version: 11.1-STABLE

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #15 from Mark Knight --- Created attachment 192199 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=192199=edit Kernel config file Attached kernel config. My kernel is close to generic, extras are:

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #14 from Eugene Grosbein --- (In reply to Mark Knight from comment #13) Do you use GENERIC kernel? If not, please attach your kernel config file. -- You are receiving this mail because: You are the

[Bug 227213] FreeBSD 10.4 kernel deadlocks on sysctlmemlock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213 --- Comment #13 from Mark Knight --- I just tried disabling logitechmediaserver and restarting. Didn't help. Then I disabled mrtg and restarted. Still didn't help. Here's a fresh dump with neither running. Same repo

<    1   2   3   4   >