[Bug 244640] [Patch][Lua loader] Implement missing "read-conf" 4th command
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244640 Olivier Certner changed: What|Removed |Added Status|New |Closed Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246309] r360637 kern.evdev.rcpt_mask=12 by default breaks doubletap on Thinkpad T400 synaptic touchpad
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246309 --- Comment #5 from Andriy Gapon --- I am using an additional conf file to customize my touchpad's behavior. I named the file /usr/local/etc/X11/xorg.conf.d/90-touchpad.conf Here is what it has: Section "InputClass" Identifier "The touchpad" MatchDriver "libinput" MatchIsTouchpad "on" Option "Tapping" "on" Option "TappingDrag" "on" Option "TappingDragLock" "on" Option "ClickMethod" "clickfinger" Option "ScrollMethod" "twofinger" Option "NaturalScrolling" "off" Option "DisableWhileTyping" "on" EndSection Maybe you can use a similar method to configure features that you want. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246323] [bsnmpd] crashes after upgrade to 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246323 Bug ID: 246323 Summary: [bsnmpd] crashes after upgrade to 12-STABLE Product: Base System Version: 12.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: zarych...@plan-b.pwste.edu.pl The daemon starts fine, but after some time it exits on signal 11, probably when remotely polled. Here is the backtrace (lldb) target create --core "bsnmpd.76367.core" Core file '/tmp/bsnmpd.76367.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'bsnmpd', stop reason = signal SIGSEGV * frame #0: 0x00220f22 frame #1: 0x7ffe28a0 (lldb) up frame #1: 0x7ffe28a0 -> 0x7ffe28a0: jo 0x7ffe2865 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246323] [bsnmpd] crashes after upgrade to 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246323 Marek Zarychta changed: What|Removed |Added Hardware|Any |amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246327] Invalid partition table after all-default installation of 13.0-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246327 Bug ID: 246327 Summary: Invalid partition table after all-default installation of 13.0-CURRENT Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: andrewponomare...@yandex.ru Default installation of 13.0-CURRENT (with Zfs) to Dell E6530 fails to boot with the error: Invalid partition table All is OK if select non-default Ufs in the installer. SATA controller: 8086:1e03 Drive: WD5000BPVT-24HXZT3 Motherboard: 024YM1 Tested on: FreeBSD-13.0-CURRENT-amd64-20200430-r360479-memstick.img FreeBSD-13.0-CURRENT-amd64-20200507-r360723-memstick.img -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246323] [bsnmpd] crashes after upgrade to 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246323 --- Comment #1 from Marek Zarychta --- Created attachment 214307 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214307&action=edit backtrace Thanks to guidance from kaktus@ I am able to submit a better report. The issue occurred just after the transition from 11.4-STABLE to 12.1-STABLE. So far all upgraded systems are affected. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246323] [bsnmpd] crashes after upgrade to 12-STABLE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246323 Pawel Biernacki changed: What|Removed |Added CC||kak...@freebsd.org Assignee|b...@freebsd.org|ha...@freebsd.org --- Comment #2 from Pawel Biernacki --- Assign to maintainer. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246215] [rtld] fails for i386 on amd64 if auxv does not contain PAGESIZES
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246215 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Sat May 9 13:00:39 UTC 2020 New revision: 360845 URL: https://svnweb.freebsd.org/changeset/base/360845 Log: Avoid spurious ENOMEMs from sysctl hw.pagesizes. Reported by: Paul Floyd PR: 246215 Reviewed by: emaste Sponsored by: The FreeBSD Foundation MFC after:1 week Differential revision:https://reviews.freebsd.org/D24737 Changes: head/sys/kern/kern_mib.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246119] ahci: MFC of r359499 in 12.1-STABLE r359972 breaks cd device detection on JMicron JMB362
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246119 --- Comment #2 from rk --- Created attachment 214310 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214310&action=edit Patch adds AHCI_Q_NOFORCE quirk to JMB362 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246119] ahci: MFC of r359499 in 12.1-STABLE r359972 breaks cd device detection on JMicron JMB362
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246119
--- Comment #3 from rk ---
The following change from r359970 appears to be the culprit:
--- stable/12/sys/dev/ahci/ahci_pci.c (revision 359969)
+++ stable/12/sys/dev/ahci/ahci_pci.c (revision 359970)
@@ -247,6 +247,7 @@
{0x2365197b, 0x00, "JMicron JMB365",AHCI_Q_NOFORCE},
{0x2366197b, 0x00, "JMicron JMB366",AHCI_Q_NOFORCE},
{0x2368197b, 0x00, "JMicron JMB368",AHCI_Q_NOFORCE},
+ {0x0585197b, 0x00, "JMicron JMB58x",0},
{0x61ab, 0x00, "Marvell 88SE6111", AHCI_Q_NOFORCE | AHCI_Q_NOPMP |
AHCI_Q_1CH | AHCI_Q_EDGEIS},
{0x612111ab, 0x00, "Marvell 88SE6121", AHCI_Q_NOFORCE | AHCI_Q_NOPMP |
@@ -399,6 +400,7 @@
!(ahci_ids[i].quirks & AHCI_Q_NOFORCE {
/* Do not attach JMicrons with single PCI function. */
if (pci_get_vendor(dev) == 0x197b &&
+ (ahci_ids[i].quirks & AHCI_Q_NOFORCE) &&
(pci_read_config(dev, 0xdf, 1) & 0x40) == 0)
return (ENXIO);
snprintf(buf, sizeof(buf), "%s AHCI SATA controller",
This breaks JMB362. I've added the AHCI_Q_NOFORCE quirk to JMB362 and with
that change it works again. Tested on r360840 with the following patch:
Index: sys/dev/ahci/ahci_pci.c
===
--- sys/dev/ahci/ahci_pci.c (revision 360840)
+++ sys/dev/ahci/ahci_pci.c (working copy)
@@ -242,7 +242,7 @@
{0x23238086, 0x00, "Intel DH89xxCC",0},
{0x2360197b, 0x00, "JMicron JMB360",0},
{0x2361197b, 0x00, "JMicron JMB361",AHCI_Q_NOFORCE | AHCI_Q_1CH},
- {0x2362197b, 0x00, "JMicron JMB362",0},
+ {0x2362197b, 0x00, "JMicron JMB362",AHCI_Q_NOFORCE},
{0x2363197b, 0x00, "JMicron JMB363",AHCI_Q_NOFORCE},
{0x2365197b, 0x00, "JMicron JMB365",AHCI_Q_NOFORCE},
{0x2366197b, 0x00, "JMicron JMB366",AHCI_Q_NOFORCE},
Now JMB362 works again (and cd0 is detected). I don't know if this is by
accident due to the code from r359970 or if JMB362 really needs AHCI_Q_NOFORCE.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246119] ahci: MFC of r359499 in 12.1-STABLE r359970 breaks JMicron JMB362
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246119 rk changed: What|Removed |Added Summary|ahci: MFC of r359499 in |ahci: MFC of r359499 in |12.1-STABLE r359972 breaks |12.1-STABLE r359970 breaks |cd device detection on |JMicron JMB362 |JMicron JMB362 | -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] cam / ciss driver unable to see more than 48(?) physical drives per controller
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Peter Eriksson changed: What|Removed |Added Attachment #214289|0 |1 is obsolete|| --- Comment #4 from Peter Eriksson --- Created attachment 214315 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214315&action=edit Output from "cciss_vol_status" -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] cam / ciss driver unable to see more than 48(?) physical drives per controller
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #5 from Peter Eriksson --- Ok, with some bits of printf-debugging I found some suspect code in sys/dev/ciss/ciss.c:ciss_cam_action() at the "case XPT_PATH_INQ" section: cpi->max_target = sc->ciss_cfg->max_logical_supported; Notice the "max logical logical volumes: 64" below? ciss0: PERFORMANT Transport ciss0: 0 logical drives configured ciss0: firmware 5.04 ciss0: 1 SCSI channels ciss0: signature 'CISS' ciss0: valence 3 ciss0: supported I/O methods 0x7e000147 ciss0: active I/O method 0x5 ciss0: 4G page base 0x ciss0: interrupt coalesce delay 0us ciss0: interrupt coalesce count 16 ciss0: max outstanding commands 1024 ciss0: bus types 0x20 ciss0: server name 'CZ3729EX3D' ciss0: heartbeat 0xc0 ciss0: max logical logical volumes: 64 ciss0: max physical disks supported: 384 ciss0: max physical disks per logical volume: 128 ciss0: JBOD Support is Available ciss0: JBOD Mode is Enabled ciss0: 72 physical devices (72 is 2 too many, but I guess the two extra are the storage drawers) If I change that line to: cpi->max_target = sc->ciss_cfg->max_physical_supported; then "camcontrol devlist" now show 69 of 70 drives... Better but not 100% there. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246311] [patch] procstat can't view current working directory (affects xfce4-terminal, linprocfs, ...)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246311 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org Version|12.1-STABLE |CURRENT --- Comment #1 from Conrad Meyer --- Why is PGET_CANDEBUG a problem? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] cam / ciss driver unable to see more than 48(?) physical drives per controller
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #6 from Peter Eriksson --- It now probes targets up to around 373 (but it takes a looong time) or so, and also detects the SES devices that have been hidden before since it only probed up to target 63... ses0 at ciss0 bus 33 scbus2 target 119 lun 0 ses0: Fixed Enclosure Services SPC-4 SCSI device ses0: Serial Number 7CE952P06X ses0: 135.168MB/s transfers ses0: SES Device ses1 at ciss0 bus 33 scbus2 target 121 lun 0 ses1: Fixed Enclosure Services SPC-4 SCSI device ses1: Serial Number 7CE952P06X ses1: 135.168MB/s transfers ses1: SES Device Due to the probing taking a loong time I also see timeouts: > run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config > and SCSI errors: (probe0:ciss1:33:351:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 (probe0:ciss1:33:351:0): CAM status: CCB request completed with an error (probe0:ciss1:33:351:0): Retrying command, 4 more tries remain (probe0:ciss1:33:351:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 (probe0:ciss1:33:351:0): CAM status: CCB request completed with an error (probe0:ciss1:33:351:0): Retrying command, 3 more tries remain This code feels... broken :-) Ah well, I'll see if I can modify the driver code to be a bit smarter on how many targets to probe. It really doesn't have to check all since it knows how many target there are (72 in my case) - it could stop after having detected that many... (No wonder the Linux folks have replaced their cciss driver with a rewritten one called hpsa). - Peter -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246339] [Patch] SIGSEGV of linux java packaged with ADVA NMS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246339
Bug ID: 246339
Summary: [Patch] SIGSEGV of linux java packaged with ADVA NMS
Product: Base System
Version: 12.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: j...@sanren.ac.za
Created attachment 214321
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214321&action=edit
patch to add LINUX_SYS_linux_getcpu to linux_vsyscall
The linux java packaged with the ADVA NMS SIGSEGV:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xff600800, pid=12763, tid=101256
#
# JRE version: (11.0.4+11) (build )
# Java VM: OpenJDK 64-Bit Server VM (11.0.4+11, mixed mode, aot, sharing,
tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C 0xff600800
That is when it is trying to execute the vsyscall linux_getcpu.
Just by adding it, even though it is not implemented, allow their java to
continue and the NMS is working.
The patch is simple:
--- sys/amd64/linux/linux_sysvec.c.orig 2019-11-01 02:01:48.0 +0200
+++ sys/amd64/linux/linux_sysvec.c 2020-05-09 20:43:42.01051 +0200
@@ -667,7 +667,7 @@
const unsigned long linux_vsyscall_vector[] = {
LINUX_SYS_gettimeofday,
LINUX_SYS_linux_time,
- /* getcpu not implemented */
+ LINUX_SYS_linux_getcpu, /* getcpu not implemented */
};
static int
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] cam / ciss driver unable to see more than 48(?) physical drives per controller
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #7 from Peter Eriksson --- The current code probably works reasonable well for cases where the controller is being used in RAID mode (where it works with logical LUNs). Well, except that it probably fails to detect the SES devices on the D6020 cabinets. But when used as "dumb" HBA with more physical drives than a certain controller handles logical devices (64 in my case for the H241 controller) it will always do the wrong thing. And since it starts numbering physical targets 16 (probably since the controller signals "0" as supported logical luns - since it's a HBA!) and then the driver code uses a compile-time-default of 16 (intended for really old controllers) things become strange... So 64-16 = 48. Okidoki. Time for some code hacking :-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] ciss driver unable to present more than 48(?) physical drives per controller to the CAM layer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Peter Eriksson changed: What|Removed |Added Summary|cam / ciss driver unable to |ciss driver unable to |see more than 48(?) |present more than 48(?) |physical drives per |physical drives per |controller |controller to the CAM layer -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] ciss driver unable to present more than 48(?) physical drives per controller to the CAM layer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #8 from Peter Eriksson --- Created attachment 214328 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214328&action=edit Patch to fix support for more than 48 drives in HBA mode The attached patch will fix a couple of bugs in the current ciss driver code where it incorrectly enumerates physical drives if the controller is in JBOD mode. There are two bugs/problems: 1. If you attach more physical drives to a controller than how many logical volumes the controller supports (yes, really - totally wrong logic here) the additional drives will not be available because the driver sets the max_target limit to the number of logical volumes, but the enumeration of hardware drives starts at 16. So for a controller that support say 64 logical volumes, only the first (64-16) drives will be detected. 2. The code also sets the initiator_id to same max logical volume number so any physical drive that happens to have the same target number will silently be skipped... The patch also enables a little more verbosity. This patch has been tested with HP H241 controllers in JBOD mode with 70 drives connected to a HP D6020 external SAS enclosure on FreeBSD 12.1-RELEASE-p3. This patch has not been tested with controllers in "RAID" mode but the patch should be compatible... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] [patch] ciss driver unable to present more than 48(?) physical drives per controller to the CAM layer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Peter Eriksson changed: What|Removed |Added Summary|ciss driver unable to |[patch] ciss driver unable |present more than 48(?) |to present more than 48(?) |physical drives per |physical drives per |controller to the CAM layer |controller to the CAM layer -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] [patch] ciss driver unable to present more than 48(?) physical drives per controller to the CAM layer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #9 from Peter Eriksson --- This part: "but the enumeration of hardware drives starts at 16. So for a controller that support say 64 logical volumes, only the first (64-16) drives will be detected." should probably read: Depending on how disk enclosures enumerate drive the exact number of drives allowed might differ. For HP D6020 enclosures they seem to start enumeration at 16, and with a HP H241 controller that supports 64 logical volumes only the first (64-16) drives will be detected. And none of the SES "targets" (one per drawer in the D6020 enclosure) either since they are listed last... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246279] ciss driver unable to present more than 48(?) physical drives per controller to the CAM layer
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Mark Linimon changed: What|Removed |Added Keywords||patch Summary|[patch] ciss driver unable |ciss driver unable to |to present more than 48(?) |present more than 48(?) |physical drives per |physical drives per |controller to the CAM layer |controller to the CAM layer --- Comment #10 from Mark Linimon --- Convert to modern way to indicate "patch". -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 246339] fix SIGSEGV of linux java packaged with ADVA NMS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246339 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|emulat...@freebsd.org Summary|[Patch] SIGSEGV of linux|fix SIGSEGV of linux java |java packaged with ADVA NMS |packaged with ADVA NMS Keywords||patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
