[Bug 241905] SSP setup is not thread-safe ?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241905 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org --- Comment #2 fro

[Bug 241906] `locale -k` with an invalid keyword exits with 0

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241906 Bug ID: 241906 Summary: `locale -k` with an invalid keyword exits with 0 Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New

[Bug 241905] SSP setup is not thread-safe ?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241905 Kyle Evans changed: What|Removed |Added CC||jil...@freebsd.org,

[Bug 241905] SSP setup is not thread-safe ?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241905 Bug ID: 241905 Summary: SSP setup is not thread-safe ? Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Onl

[Bug 232921] freebsd-update upgrade does not execute pwd_mkdb for ntpd

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232921 --- Comment #8 from John W. O'Brien --- I'm don't think I understand why it was still necessary, but I had to recover from this after a freebsd-update from 11.3-RELEASE-p3 to 12.1-RELEASE-p0. I had to A) manually run pwd_mkdb, and B) forcib

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #21 from Ronald F. Guilmette --- (In reply to Mark Johnston from comment #13) I am willing to share one or more of the vmcore files, as may be useful, however this may be somewhat ardouous to achieve. I am not on the end of a

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #20 from Ronald F. Guilmette --- Created attachment 209078 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209078&action=edit /v/crash/core.txt.5 -- You are receiving this mail because: You are the assignee for the b

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #19 from Ronald F. Guilmette --- Created attachment 209077 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209077&action=edit /v/crash/core.txt.4 -- You are receiving this mail because: You are the assignee for the b

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #18 from Ronald F. Guilmette --- Created attachment 209076 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209076&action=edit /v/crash/core.txt.3 -- You are receiving this mail because: You are the assignee for the b

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #17 from Ronald F. Guilmette --- Created attachment 209075 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209075&action=edit /v/crash/core.txt.2 -- You are receiving this mail because: You are the assignee for the b

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #16 from Ronald F. Guilmette --- Regarding the several other kernal panics that I have gottns ince "upgrading" to 12.0-RELEASE I have my crash directory set to /v/crash (where I have a lot of space available) and here is a recor

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #15 from Ronald F. Guilmette --- In answer to the question regarding which driver I am using, I do not know how to unambiguously determine the correct answer to this question, however I do have a recollection, from back when I i

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #14 from Ronald F. Guilmette --- Output from: "pkg info | grep drm" drm-fbsd12.0-kmod-4.16.g20190624 DRM modules for the linuxkpi-based KMS components drm-kmod-g20181126 Metaport of DRM modules for the linuxkpi-base

[Bug 236686] BSD grep causes openjdk11 configuration failures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236686 Kyle Evans changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress

[Bug 236686] BSD grep causes openjdk11 configuration failures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236686 Kyle Evans changed: What|Removed |Added Assignee|b...@freebsd.org|kev...@freebsd.org CC

[Bug 233405] sparc64: DWARF unwinder required for GCC 4.2.1 retirement

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405 --- Comment #13 from Conrad Meyer --- (In reply to Mark Linimon from comment #12) Right. libunwind comes from LLVM upstream. All I meant by my comments about retaining 32-bit Sparc were directed at not breaking support for it in LLVM upst

[Bug 241884] elf_aux_info(3) return types are not documented

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241884 Bug ID: 241884 Summary: elf_aux_info(3) return types are not documented Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keyw

[Bug 233405] sparc64: DWARF unwinder required for GCC 4.2.1 retirement

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405 --- Comment #12 from Mark Linimon --- (In reply to Conrad Meyer from comment #11) FreeBSD never supported 32 bit sparc. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 228251] Touchpad non-functional on Dell Latitude 5580

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228251 --- Comment #8 from Trenton Schulz --- Having a Dell 5580, I took a deeper look at this. It seems the problem is more that the touchpad on the 5580 is now using i2c. One can get it to work on 12.1-RELEASE if one isn't scared of getting one

[Bug 233405] sparc64: DWARF unwinder required for GCC 4.2.1 retirement

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405 --- Comment #11 from Conrad Meyer --- (In reply to Ed Maste from comment #10) For us, they’re both defined, and we only support sparc64. The un-numbered variant was already used in that file, so I just followed existing convention. The up

[Bug 237768] 12.0-RELEASE: Calling fortune(6) with no parameters yields "No fortunes found" error.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237768 Andy Farkas changed: What|Removed |Added CC||an...@andyit.com.au --- Comment #1 f

[Bug 233405] sparc64: DWARF unwinder required for GCC 4.2.1 retirement

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405 --- Comment #10 from Ed Maste --- (In reply to Conrad Meyer from comment #7) > +defined(__sparc__) __sparc__ or __sparc64__? -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #13 from Mark Johnston --- Also, would you be willing to share one or more of the kernel dumps with me? I would basically need a copy of a vmcore from /var/crash and the contents of /boot/modules. -- You are receiving this ma

[Bug 239352] kernel panic - cause as yet undetermined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239352 --- Comment #12 from Mark Johnston --- (In reply to Ronald F. Guilmette from comment #11) The second panic report you posted is different, and is occurring in the graphics driver. It would indeed help to see any other crash reports that we

[Bug 183024] textdump(4) mentions call doadump, should be textdump dump

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183024 --- Comment #4 from sig...@gmail.com --- (In reply to Andriy Gapon from comment #3) Sure seems like you did! Thanks. I forgot to check if it had already been fixed after finding this PR. For reference, I just checked if making sure that d

[Bug 183024] textdump(4) mentions call doadump, should be textdump dump

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183024 --- Comment #3 from Andriy Gapon --- I think that I recently fixed the issue without being aware of this bug report. See base r353726 and base r354353. -- You are receiving this mail because: You are the assignee for the bug.