[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 fixes. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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 --- Comment #17 from Kurt Jaeger --- I once had a box where sysctl -a would hang, too. It's been a while, so no more details until I stumble open that box again. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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 11.1. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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||k...@freebsd.org --- Comment #19 from Konstantin Belousov --- (In reply to Eugene Grosbein from comment #8) Well, there is the sx owner which blocks snmpd. It does not make your note about the request length less valid, but still first thing to look at is the state of the lock owner. Print p *(struct thread *)0xf80079fd3000, then get the backtrace for that thread. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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&action=edit thread 257/100247 (In reply to Konstantin Belousov from comment #19) How does one recover original sysctl name? This one seems to be ACPI-related, see attachment. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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 this is fine under 10.3. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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 is installed with ports/sysutils/hal. Mark, why do you need hald? If it's possible, try running 10.4 with hald disabled. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[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. :) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
