[Bug 259024] ext2_search_dirblock() loops forever if e2d_reclen is zero

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259024 Fedor Uporov changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 259041] ext2fs can read beyond the end of fs->e2fs_gd[] if a directory contains an invalid i-number

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259041 Fedor Uporov changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 259105] ext2fs would be more robust if it checked the type of inode 2

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259105 Fedor Uporov changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #66 from tech-li...@zyxst.net --- writing to say the pf on the rpi4 is still working without error % uptime 10:50p.m. up 12 days, 7:04, 7 users, load averages: 5.11, 4.85, 4.65 -- You are receiving this mail because: You

[Bug 260958] pfctl: expand_rule: strlcpy

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260958 --- Comment #2 from Thomas Steen Rasmussen / Tykling --- Hello, Yes, I should have mentioned that, of course. It isn't a valid config, but normally we would get a message from pfctl with the line number and a "syntax error" message, so

[Bug 260958] pfctl: expand_rule: strlcpy

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260958 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org --- Comment #1

[Bug 260963] vt newcons: mouse paste incorrectly adds newlines

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260963 Bug ID: 260963 Summary: vt newcons: mouse paste incorrectly adds newlines Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New

[Bug 225341] System locks up due to atkbd_timeout kludge when using /dev/atkbd0 directly

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225341 Alexander Motin changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 225341] System locks up due to atkbd_timeout kludge when using /dev/atkbd0 directly

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225341 Alexander Motin changed: What|Removed |Added CC||m...@freebsd.org --- Comment #3

[Bug 260962] sysutils/openzfs fsck.zfs(8) does not detect OpenZFS pool degradation

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260962 Graham Perrin changed: What|Removed |Added Component|bin |Individual Port(s)

[Bug 260962] fsck.zfs(8) does not detect OpenZFS pool degradation

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260962 --- Comment #1 from Graham Perrin --- -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260962] fsck.zfs(8) does not detect OpenZFS pool degradation

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260962 Bug ID: 260962 Summary: fsck.zfs(8) does not detect OpenZFS pool degradation Product: Base System Version: CURRENT Hardware: Any URL:

[Bug 260793] 'swapon -a' can crash the system

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260793 Mark Johnston changed: What|Removed |Added Status|New |Open --- Comment #3 from Mark

[Bug 260257] CAM_IO_STATS does not track MEDIUM ERRORs

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260257 Robert Wing changed: What|Removed |Added CC||r...@freebsd.org --- Comment #7

[Bug 260793] 'swapon -a' can crash the system

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260793 --- Comment #2 from Peter Much --- @markj You're great. That explains it. So, indeed, one shouldn't re-run "swapon -a" when trimonce is set. Or, maybe, we could catch the issue? -- You are receiving this mail because: You are the

[Bug 260896] The 14-CURRENT system hangs if kern.vt.splash_cpu is set to 1 in loader.conf

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260896 --- Comment #2 from Oleg --- I just compiled the latest kernel from the main branch and the problem is still there. If I boot into the single-user mode, then I am able to login, but the system will become fully unresponsive a few seconds

[Bug 260793] 'swapon -a' can crash the system

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260793 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #1

[Bug 260958] pfctl: expand_rule: strlcpy

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260958 Bug ID: 260958 Summary: pfctl: expand_rule: strlcpy Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects

[Bug 260868] possible i386 regression after ce35a3bc852d25cb989bc1f3dc4ddb723d7d5117

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260868 Mark Johnston changed: What|Removed |Added Status|Open|In Progress

[Bug 260896] The 14-CURRENT system hangs if kern.vt.splash_cpu is set to 1 in loader.conf

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260896 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #1

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 Kajetan Staszkiewicz changed: What|Removed |Added CC||veg...@tuxpowered.net ---

[Bug 260955] pkg 1.17: keywords "preunexec" and "postexec" no longer recognized

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260955 Bug ID: 260955 Summary: pkg 1.17: keywords "preunexec" and "postexec" no longer recognized Product: Base System Version: Unspecified Hardware: Any

[Bug 260954] waiting for runnimg MySQL

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954 --- Comment #7 from Aleks --- In a naive attempt, I just added the hw.pagesize=... to my /etc/sysctl config file, without any success. Now, when I run pagesize I get my sad 4096 bytes value: -- You are receiving this mail because: You

[Bug 260954] waiting for runnimg MySQL

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954 --- Comment #6 from Aleks --- ./mysql-server status mysql is running as pid 2047. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954 --- Comment #5 from Aleks --- sysctl hw.pagesize=8192 sysctl: oid 'hw.pagesize' is read only -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954 --- Comment #4 from Aleks --- sysctl hw.pagesize hw.pagesize: 4096 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954 --- Comment #3 from Aleks --- error [ERROR] InnoDB: The Auto-extending innodb_system data file '/var/db/mysql/ibdata1' is of a different size 4864 pages (rounded down to MB) than specified in the .cnf file: initial 8192 pages, max 0 --

[Bug 260954] waiting for runnimg MySQL

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954 --- Comment #2 from Aleks --- https://forums.freebsd.org/threads/ibdata1-page-size-diffrent-after-upgrading-mysql-5-6-to-5-7.72289/ my.cnf=" # For advice on how to change settings please see #

[Bug 260954] waiting for runnimg MySQL

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954 --- Comment #1 from Aleks --- Update mysql56-server mysql56-client -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260954] waiting for runnimg MySQL

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260954 Bug ID: 260954 Summary: waiting for runnimg MySQL Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects

[Bug 260952] Add usbids for EDIMAX EW-7811UN V2

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260952 Tilman Keskinoz changed: What|Removed |Added Keywords||easy Component|kern

[Bug 260952] Add usbids for EDIMAX EW-7811UN V2

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260952 Bug ID: 260952 Summary: Add usbids for EDIMAX EW-7811UN V2 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity:

[Bug 260949] fsck(8): Fix typo

2022-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260949 Kubilay Kocak changed: What|Removed |Added Status|New |Open See Also|