[Bug 177845] WITH_BMAKE does not work on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177845 --- Comment #2 from yaneurab...@gmail.com --- This hasn't been an issue for some time; please close this bug. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 177845] WITH_BMAKE does not work on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177845 yaneurab...@gmail.com changed: What|Removed |Added Status|In Discussion |Issue Resolved Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 177845] WITH_BMAKE does not work on CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177845 --- Comment #3 from yaneurab...@gmail.com --- Aha.. I didn't realize I could close it... Closed :D! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 191054] New: make clean/cleanobj does not clean as expected with bsd.progs.mk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191054
Bug ID: 191054
Summary: make clean/cleanobj does not clean as expected with
bsd.progs.mk
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: Needs Triage
Severity: Affects Only Me
Priority: ---
Component: misc
Assignee: freebsd-bugs@FreeBSD.org
Reporter: yaneurab...@gmail.com
When trying to isolate some issues with bsd.test.mk, I noticed that make
clean/cleanobj was not cleaning as expected, in particular make clean does not
clean any of the compiled programs, and make cleanobj only cleans out the last
compiled program. If I run make cleandir, it napalms the heck out of the
directory by deleting the bsd.dep.mk files 6 times (twice for cleandir, twice
for cleanobj, twice for cleandepend) and the generated objects 2 times each
(once each for cleanobj, once each for cleandir).
I've provided an example below:
% uname -a
FreeBSD isilon-fuji-current.local 11.0-CURRENT FreeBSD 11.0-CURRENT #5
0d2be6b(isilon-atf): Sun Jun 8 21:34:32 PDT 2014
root@fuji-current.local:/usr/obj/usr/src/sys/FUJI i386
% cat *
# Makefile
FILESDIR=/tmp/share
FILES=c
BINDIR=/tmp/bin
PROGS=a b
MAN=
.include bsd.progs.mk
/* a.c */
#include stdio.h
int
main(void)
{
printf(hello world!\n);
return (0);
}
/* b.c */
#include stdio.h
int
main(void)
{
printf(hello world!\n);
return (0);
}
/* c */
This directory contains a simple C app that says, hello world!
% make obj
/usr/obj/root/make_clean_broken_with_progs_dot_mk created for
/root/make_clean_broken_with_progs_dot_mk
% make depend
(cd /root/make_clean_broken_with_progs_dot_mk make -f
/root/make_clean_broken_with_progs_dot_mk/Makefile _RECURSING_PROGS= SUBDIR=
PROG=a depend)
rm -f .depend.a
mkdep -f .depend.a -a -std=gnu99
/root/make_clean_broken_with_progs_dot_mk/a.c
echo a: /usr/lib/libc.a .depend.a
(cd /root/make_clean_broken_with_progs_dot_mk make -f
/root/make_clean_broken_with_progs_dot_mk/Makefile _RECURSING_PROGS= SUBDIR=
PROG=b depend)
rm -f .depend.b
mkdep -f .depend.b -a -std=gnu99
/root/make_clean_broken_with_progs_dot_mk/b.c
echo b: /usr/lib/libc.a .depend.b
% make all
(cd /root/make_clean_broken_with_progs_dot_mk make -f
/root/make_clean_broken_with_progs_dot_mk/Makefile _RECURSING_PROGS= SUBDIR=
PROG=a )
cc -O2 -pipe -std=gnu99 -fstack-protector -Qunused-arguments -c
/root/make_clean_broken_with_progs_dot_mk/a.c
cc -O2 -pipe -std=gnu99 -fstack-protector -Qunused-arguments -o a a.o
(cd /root/make_clean_broken_with_progs_dot_mk make -f
/root/make_clean_broken_with_progs_dot_mk/Makefile _RECURSING_PROGS= SUBDIR=
PROG=b )
cc -O2 -pipe -std=gnu99 -fstack-protector -Qunused-arguments -c
/root/make_clean_broken_with_progs_dot_mk/b.c
cc -O2 -pipe -std=gnu99 -fstack-protector -Qunused-arguments -o b b.o
% make clean
% make cleanobj
(cd /root/make_clean_broken_with_progs_dot_mk make -f
/root/make_clean_broken_with_progs_dot_mk/Makefile _RECURSING_PROGS= SUBDIR=
PROG=a cleanobj)
(cd /root/make_clean_broken_with_progs_dot_mk make -f
/root/make_clean_broken_with_progs_dot_mk/Makefile _RECURSING_PROGS= SUBDIR=
PROG=b cleanobj)
rm -f b b.o
rm -f .depend.b GPATH GRTAGS GSYMS GTAGS
% make cleandir
(cd /root/make_clean_broken_with_progs_dot_mk make -f Makefile
_RECURSING_PROGS= SUBDIR= PROG=a cleandepend)
rm -f .depend.a GPATH GRTAGS GSYMS GTAGS
(cd /root/make_clean_broken_with_progs_dot_mk make -f Makefile
_RECURSING_PROGS= SUBDIR= PROG=b cleandepend)
rm -f .depend.b GPATH GRTAGS GSYMS GTAGS
(cd /root/make_clean_broken_with_progs_dot_mk make -f Makefile
_RECURSING_PROGS= SUBDIR= PROG=a cleanobj)
rm -f a a.o
rm -f .depend.a GPATH GRTAGS GSYMS GTAGS
(cd /root/make_clean_broken_with_progs_dot_mk make -f Makefile
_RECURSING_PROGS= SUBDIR= PROG=b cleanobj)
rm -f b b.o
rm -f .depend.b GPATH GRTAGS GSYMS GTAGS
(cd /root/make_clean_broken_with_progs_dot_mk make -f Makefile
_RECURSING_PROGS= SUBDIR= PROG=a cleandir)
rm -f a a.o
rm -f .depend.a GPATH GRTAGS GSYMS GTAGS
(cd /root/make_clean_broken_with_progs_dot_mk make -f Makefile
_RECURSING_PROGS= SUBDIR= PROG=b cleandir)
rm -f b b.o
rm -f .depend.b GPATH GRTAGS GSYMS GTAGS
%
Expected behavior:
- make clean should clean all apps and generated files.
- make cleanobj should just nuke ${.OBJDIR}; it shouldn't have to nuke the
files under ${.OBJDIR} (bsd.obj.mk ensures that requirement is met for
cleanobj).
- make cleandir should does the same thing as cleanobj (why they're separate
targets, I have no idea, but cleanobj isn't advertised in the docs though...).
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to
[Bug 191055] make install with bsd.progs.mk installs FILES/SCRIPTS multiple times if PROGS is specified
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191055 yaneurab...@gmail.com changed: What|Removed |Added CC||j...@freebsd.org, ||s...@freebsd.org Summary|make install with |make install with |bsd.progs.mk installs FILES |bsd.progs.mk installs |multiple times if PROGS is |FILES/SCRIPTS multiple |specified |times if PROGS is specified -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 191056] bsd.progs.mk: bsd.prog.mk incompatibilities with variables being set and not set
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191056 --- Comment #1 from yaneurab...@gmail.com --- Created attachment 143799 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=143799action=edit Proposed fix -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
FreeBSD 9 w/ MPD5 crashes as LNS with 300+ tunnels. Netgraph issue?
Hi List, I¹m wondering if anyone can help me with this problem or at least help point me in the direction of where to start looking? I have FreeBSD 9 based servers which are crashing every 4-10 days and producing crash dumps similar to this one: http://pastebin.com/F82Jc08C All crash dumps seem to involve the net graph code and the current process is always ng_queueX. In summary, we have 4 x FreeBSD server running as LNS(MPD5) for around 2000 subscribers with 3 of the servers running a modified version of BSDRP, the fourth running a FreeBSD 9 install with what I thought was the latest stable source for the kernel because I fetched it from stable/9 however it shows up as 9.3-BETA in uname(the linked crash dump is from that server). 3 x LNS running modified BSDRP: DELL PowerEdge 2950, 2 x Xeon E5320, 4GB RAM, igb Quad Port NIC in LAGG, Quagga, MPD5, IPFW for Host Access Control, NTPD, BSNMPD 1 x LNS running latest FreeBSD 9 code: HP ProLiant DL380, 2 x Xeon X5465, 36GB RAM, em Quad Port NIC in LAGG, BIRD, MPD5, IPFW for Host Access Control, NTPD, BSNMPD The reason I built the fresh server on FreeBSD 9 is because I cannot save crash dumps for BSDRP easily. In short the problem is this servers with 10-50 clients will run indefinitely(as long as we have had them, which is probably about 1.5 years) without errors and serve clients fine, however any with over 300 clients appear to only stay online for 4-10 days maximum before crashing and rebooting. I have attached the crash file from the latest crash on the LNS running the latest FreeBSD 9 code however unsure what to do with it and where to look? When these devices crash they are often doing in excess of 200Mbps(anywhere between 200Mbps and 450Mbps), very little load(3-4.5 on the first 3, less than 2 on the fourth). Things I¹ve done to attempt resolution: - Replaced bce network cards with em network cards. This produced far less errors on the interfaces(was many before, now none) and I think caused the machines to stay up longer between reboots as before it would happen up to once a day. - Replaced em network cards with igb network cards. All this did was lower load and give us a little more time between reboots. - Tried an implementation using FreeBSD 10(this lasted less than 4 hours before reboots when under load) - Replaced memory - Increased memory on LNS4 to 36GB. - Various kernel rebuilds - Tweaked various kernel settings. This appears to have helped a little and given us more time between reboots. - Disabled IPv6 - Disabled IPFW - Disabled BSNMPD - Disabled Netflow - Versions 5.6 and 5.7 of MPD5 Anyone able to help me work out what the crash dump means? It only happens on servers running MPD5 (eg. Exact same boxes, exact same code pushing 800Mbps+ of routing and no crashes) and I can see the crash relates to net graph, however unsure where to go from there Thanks, Mark Relevant Current Settings: net.inet.ip.fastforwarding=1 net.inet.ip.fw.default_to_accept=1 net.bpf.zerocopy_enable=1 net.inet.raw.maxdgram=16384 net.inet.raw.recvspace=16384 hw.intr_storm_threshold=64000 net.inet.ip.fastforwarding=1 net.inet.ip.fw.default_to_accept=1 net.inet.ip.intr_queue_maxlen=10240 net.inet.ip.redirect=0 net.inet.ip.sourceroute=0 net.inet.ip.rtexpire=2 net.inet.ip.rtminexpire=2 net.inet.ip.rtmaxcache=256 net.inet.ip.accept_sourceroute=0 net.inet.ip.process_options=0 net.inet.icmp.log_redirect=0 net.inet.icmp.drop_redirect=1 net.inet.tcp.drop_synfin=1 net.inet.tcp.blackhole=2 net.inet.tcp.sendbuf_max=16777216 net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.sendbuf_auto=1 net.inet.tcp.recvbuf_auto=1 net.inet.udp.recvspace=262144 net.inet.udp.blackhole=0 net.inet.udp.maxdgram=57344 net.route.netisr_maxqlen=4096 net.local.stream.recvspace=65536 net.local.stream.sendspace=65536 net.graph.maxdata=65536 net.graph.maxalloc=65536 net.graph.maxdgram=2096000 net.graph.recvspace=2096000 kern.ipc.somaxconn=32768 kern.ipc.nmbclusters=524288 kern.ipc.maxsockbuf=26214400 kern.ipc.shmmax=³2147483648 kern.ipc.nmbjumbop=³53200 kern.ipc.maxpipekva=³536870912 kern.random.sys.harvest.ethernet=0 kern.random.sys.harvest.interrupt=0 vm.kmem_size=³4096M² # Only on box with over 12G RAM. Otherwise 2G. vm.kmem_size_max=³8192M # Only on box with over 12G RAM. hw.igb.rxd=4096 hw.igb.txd=4096 hw.em.rxd=4096 hw.em.txd=4096 hw.igb.max_interrupt_rate=³32000 hw.igb.rx_process_limit=4096 hw.em.rx_process_limit=500 net.link.ifqmaxlen=20480 net.isr.dispatch=direct net.isr.direct_force=1 net.isr.direct=1 net.isr.maxthreads=8 net.isr.numthreads=4 net.isr.bindthreads=1 net.isr.maxqlimit=20480 net.isr.defaultqlimit=8192 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: FreeBSD 9 w/ MPD5 crashes as LNS with 300+ tunnels. Netgraph issue?
Hello Mark, Sunday, June 15, 2014, 1:09:56 PM, you wrote: I¹m wondering if anyone can help me with this problem or at least help point me in the direction of where to start looking? I have FreeBSD 9 based servers which are crashing every 4-10 days and producing crash dumps similar to this one: http://pastebin.com/F82Jc08C Just for the fun of it, add this to the template definition: set iface down-script mpd-down.sh mpd-down.sh contents being: #!/bin/sh /bin/sleep 1 I've seen panics related to queuing with dummynet (not dummynet's fault :P), and this awful hack worked around the real problem. Not sure if you're suffering from the same race condition tough :) ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: FreeBSD 9 w/ MPD5 crashes as LNS with 300+ tunnels. Netgraph issue?
On 6/15/2014 3:39 PM, Mark van der Meulen wrote: Hi List, I¹m wondering if anyone can help me with this problem or at least help point me in the direction of where to start looking? I have FreeBSD 9 based servers which are crashing every 4-10 days and producing crash dumps similar to this one: http://pastebin.com/F82Jc08C All crash dumps seem to involve the net graph code and the current process is always ng_queueX. In summary, we have 4 x FreeBSD server running as LNS(MPD5) for around 2000 subscribers with 3 of the servers running a modified version of BSDRP, the fourth running a FreeBSD 9 install with what I thought was the latest stable source for the kernel because I fetched it from stable/9 however it shows up as 9.3-BETA in uname(the linked crash dump is from that server). 3 x LNS running modified BSDRP: DELL PowerEdge 2950, 2 x Xeon E5320, 4GB RAM, igb Quad Port NIC in LAGG, Quagga, MPD5, IPFW for Host Access Control, NTPD, BSNMPD 1 x LNS running latest FreeBSD 9 code: HP ProLiant DL380, 2 x Xeon X5465, 36GB RAM, em Quad Port NIC in LAGG, BIRD, MPD5, IPFW for Host Access Control, NTPD, BSNMPD The reason I built the fresh server on FreeBSD 9 is because I cannot save crash dumps for BSDRP easily. In short the problem is this servers with 10-50 clients will run indefinitely(as long as we have had them, which is probably about 1.5 years) without errors and serve clients fine, however any with over 300 clients appear to only stay online for 4-10 days maximum before crashing and rebooting. I have attached the crash file from the latest crash on the LNS running the latest FreeBSD 9 code however unsure what to do with it and where to look? When these devices crash they are often doing in excess of 200Mbps(anywhere between 200Mbps and 450Mbps), very little load(3-4.5 on the first 3, less than 2 on the fourth). Things I¹ve done to attempt resolution: - Replaced bce network cards with em network cards. This produced far less errors on the interfaces(was many before, now none) and I think caused the machines to stay up longer between reboots as before it would happen up to once a day. - Replaced em network cards with igb network cards. All this did was lower load and give us a little more time between reboots. - Tried an implementation using FreeBSD 10(this lasted less than 4 hours before reboots when under load) - Replaced memory - Increased memory on LNS4 to 36GB. - Various kernel rebuilds - Tweaked various kernel settings. This appears to have helped a little and given us more time between reboots. - Disabled IPv6 - Disabled IPFW - Disabled BSNMPD - Disabled Netflow - Versions 5.6 and 5.7 of MPD5 Anyone able to help me work out what the crash dump means? It only happens on servers running MPD5 (eg. Exact same boxes, exact same code pushing 800Mbps+ of routing and no crashes) and I can see the crash relates to net graph, however unsure where to go from thereŠ Thanks, Mark Relevant Current Settings: net.inet.ip.fastforwarding=1 net.inet.ip.fw.default_to_accept=1 net.bpf.zerocopy_enable=1 net.inet.raw.maxdgram=16384 net.inet.raw.recvspace=16384 hw.intr_storm_threshold=64000 net.inet.ip.fastforwarding=1 net.inet.ip.fw.default_to_accept=1 net.inet.ip.intr_queue_maxlen=10240 net.inet.ip.redirect=0 net.inet.ip.sourceroute=0 net.inet.ip.rtexpire=2 net.inet.ip.rtminexpire=2 net.inet.ip.rtmaxcache=256 net.inet.ip.accept_sourceroute=0 net.inet.ip.process_options=0 net.inet.icmp.log_redirect=0 net.inet.icmp.drop_redirect=1 net.inet.tcp.drop_synfin=1 net.inet.tcp.blackhole=2 net.inet.tcp.sendbuf_max=16777216 net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.sendbuf_auto=1 net.inet.tcp.recvbuf_auto=1 net.inet.udp.recvspace=262144 net.inet.udp.blackhole=0 net.inet.udp.maxdgram=57344 net.route.netisr_maxqlen=4096 net.local.stream.recvspace=65536 net.local.stream.sendspace=65536 net.graph.maxdata=65536 net.graph.maxalloc=65536 net.graph.maxdgram=2096000 net.graph.recvspace=2096000 kern.ipc.somaxconn=32768 kern.ipc.nmbclusters=524288 kern.ipc.maxsockbuf=26214400 kern.ipc.shmmax=³2147483648 kern.ipc.nmbjumbop=³53200 kern.ipc.maxpipekva=³536870912 kern.random.sys.harvest.ethernet=0 kern.random.sys.harvest.interrupt=0 vm.kmem_size=³4096M² # Only on box with over 12G RAM. Otherwise 2G. vm.kmem_size_max=³8192M # Only on box with over 12G RAM. hw.igb.rxd=4096 hw.igb.txd=4096 hw.em.rxd=4096 hw.em.txd=4096 hw.igb.max_interrupt_rate=³32000 hw.igb.rx_process_limit=4096 hw.em.rx_process_limit=500 net.link.ifqmaxlen=20480 net.isr.dispatch=direct net.isr.direct_force=1 net.isr.direct=1 net.isr.maxthreads=8 net.isr.numthreads=4 net.isr.bindthreads=1 net.isr.maxqlimit=20480 net.isr.defaultqlimit=8192 The following workarounds have worked for some people. They may not solve your problem, but are worth giving a try: 1. Increases netgraph limits: net.graph.maxdata=262140 # /boot/loader.conf net.graph.maxalloc=262140 # /boot.loader.conf 2. Remove FLOWTABLE kernel option. It would also help if you put your kernel and
[Bug 191067] New: NOT possible to run sshd in live-CD mode disk with FreeBSD-9.3-BETA3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191067 Bug ID: 191067 Summary: NOT possible to run sshd in live-CD mode disk with FreeBSD-9.3-BETA3 Product: Base System Version: 9.3-BETA2 Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: conf Assignee: freebsd-bugs@FreeBSD.org Reporter: ad...@support.od.ua Created attachment 143814 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=143814action=edit Service sshd onestart failed NOT possible to run sshd in live-CD mode I run Live-CD FreeBSD-9.3-BETA3-amd64-bootonly.iso I chose the live-CD mode Run the command: #dhclient em0 #service sshd onestart ... Could not load host key: /etc/ssh/ssh_host_ecdsa_key ... I propose to mount the /etc/ssh in write mode, so you can run sshd with the necessary parameters -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 191070] New: Boot hangs on Levono Thinkpad Edge E545 at atkdbc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191070 Bug ID: 191070 Summary: Boot hangs on Levono Thinkpad Edge E545 at atkdbc Product: Base System Version: unspecified Hardware: Any OS: Any Status: Needs Triage Severity: Affects Only Me Priority: Normal Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: jens.l...@gmx.de Booting FreeBSD current on my new Lenova Thinkpad Edge E545 hangs with atkbdc0 Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi atkbd0: AT Keyboard irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa Setting hint.atkdb.0.flags=0x10 or save boot have the same result. Same error with 10 stable r267232. The above port seems right for Linux, which boot without problems. I don't know, but maybe this notebook need other magic numbers than mention in http://lists.freebsd.org/pipermail/svn-src-head/2011-June/028224.html Environment: snapshot r266655 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 190669] 'emmintrin.h' file not found - in /usr/src/lib/clang/libclangbasic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190669
--- Comment #5 from roberth...@rcn.com ---
And it's not just about base. As of r375825 of ports, I am unable to build:
devel/boost-libs
graphics/opencv-core
mail/thunderbird
www/firefox
/seamonkey
/libxul
due to missing {emmintrin.h , xmmintrin.h}.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
[Bug 186971] [devd] [patch] install /etc/devd/zfs.conf if WITH_ZFS is set
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186971 yaneurab...@gmail.com changed: What|Removed |Added Severity|Affects Only Me |Affects Some People -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
