[Bug 275099] cat(1) can't read directories

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275099 WHR changed: What|Removed |Added Attachment #246324|text/x-c|text/x-csrc mime type|

[Bug 270798] sysctl(3) missing KERN_PROC_FILEDESC MIB

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270798 WHR changed: What|Removed |Added CC||msl023...@gmail.com --- Comment #2 from

[Bug 275099] cat(1) can't read directories

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275099 WHR changed: What|Removed |Added Attachment #246324|text/plain |text/x-c mime type|

[Bug 275099] cat(1) can't read directories

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275099 --- Comment #1 from WHR --- Created attachment 246325 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=246325&action=edit Proposed fix cat(1) should fallback to the read(2) system call if copy_file_range(2) failed with EISDIR. --

[Bug 275099] cat(1) can't read directories

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275099 Bug ID: 275099 Summary: cat(1) can't read directories Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only

[Bug 275086] Old i386 boot: CPU0: local APIC error 0x4 – Cannot boot any longer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275086 Mark Linimon changed: What|Removed |Added Keywords||regression -- You are receiving th

[Bug 275093] contrib/libevent is woefully out of date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275093 --- Comment #7 from Enji Cooper --- Also, yeah... deleting the invalid tag seems prudent. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 275093] contrib/libevent is woefully out of date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275093 --- Comment #6 from Enji Cooper --- I think it's ok to use the NTP embedded copy now since we only have a single libevent consumer in-tree.. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 275093] contrib/libevent is woefully out of date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275093 --- Comment #5 from Cy Schubert --- Do you see any problem with git tag -d vendor/libevent/2.1.18 ? Is that acceptable in the FreeBSD sense? That is after git tag -a vendor/libevent/2.1.8 before the import of 2.1.12. Does this make sense to

[Bug 275093] contrib/libevent is woefully out of date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275093 --- Comment #4 from Ed Maste --- (In reply to Cy Schubert from comment #3) Yes it should be 2.1.8. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 275093] contrib/libevent is woefully out of date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275093 --- Comment #3 from Cy Schubert --- That's what I think. The merge was clean. Build already in progress. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 275093] contrib/libevent is woefully out of date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275093 Herbert J. Skuhra changed: What|Removed |Added CC||herb...@gojira.at --- Comment

[Bug 275093] contrib/libevent is woefully out of date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275093 --- Comment #1 from Cy Schubert --- Looking at our vendor branch tags, our libevent is at 2.1.18 while upstream libevent.org is at 2.1.12. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 275086] Old i386 boot: CPU0: local APIC error 0x4 – Cannot boot any longer

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

[Bug 275093] contrib/libevent is woefully out of date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275093 Bug ID: 275093 Summary: contrib/libevent is woefully out of date Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: A

[Bug 275092] iostat columns run together

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275092 Bug ID: 275092 Summary: iostat columns run together Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects O

[Bug 275086] Old i386 boot: CPU0: local APIC error 0x4 – Cannot boot any longer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275086 Bug ID: 275086 Summary: Old i386 boot: CPU0: local APIC error 0x4 – Cannot boot any longer Product: Base System Version: 14.0-RELEASE Hardware: i386 O

[Bug 275081] freebsd-update erroneously reports that 14.0-RELEASE is approaching its EOL date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275081 --- Comment #2 from Dave Cottlehuber --- I don't think this has any of the expected info sadly. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 275081] freebsd-update erroneously reports that 14.0-RELEASE is approaching its EOL date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275081 --- Comment #1 from Dave Cottlehuber --- Created attachment 246311 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=246311&action=edit sh -x /usr/local/bin/poudriere jail -c -j 14_0_x64 -v 14.0-RELEASE -K GENERIC 2>&1 | tee /tmp/w

[Bug 275063] kernel using 100% CPU in arc_prune

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275063 martin.dierin...@gmx.de changed: What|Removed |Added Flags||mfc-stable13? -- You are

[Bug 275081] freebsd-update erroneously reports that 14.0-RELEASE is approaching its EOL date

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275081 Bug ID: 275081 Summary: freebsd-update erroneously reports that 14.0-RELEASE is approaching its EOL date Product: Base System Version: 14.0-RELEASE Hardware: Any

[Bug 266990] FreeBSD can not drive 16950 chip correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266990 --- Comment #4 from Andrey Korobkov --- In 14.0-RELEASE it still works well, but new message appeared: "ns8250: UART FCR is broken". What does it mean? # dmesg.boot puc0: port 0x1000-0x103f,0x1040-0x104f mem 0xba00-0xba000fff irq 27 a