Hi, I'd like to invite you to back our Kickstarter project - The World's
First Personal Robot
https://www.kickstarter.com/projects/403524037/personal-robot.
We're already 210% funded and the #1 Robot Project on Kickstarter now.
PERSONAL ROBOT IS THE WHOLE PACKAGE:
- The world's first
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194515
--- Comment #18 from dar...@dons.net.au ---
Is this going to be MFCd?
The 3 commits apply cleanly to stable/10 and seem to work (but I have only
tested it lightly so far)
--
You are receiving this mail because:
You are the assignee for
Hi,
I get below from another email this morning, the ipfw can add dynamic rules
according to below email.
*You can manually insert a state as below and the state will be maintain by
ipfw itself.*
*ipfw state add rulenum 100 udp 192.168.1.1:0
http://192.168.1.1:0/ 8.8.8.8:53 http://8.8.8.8:53/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
Craig Rodrigues rodr...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #6 from Craig Rodrigues rodr...@freebsd.org ---
Herbert found by creating VNET jails and then stopping them, he could reproduce
the problem. Here are the steps he used to reproduce the problem:
/etc/rc.conf:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #7 from Craig Rodrigues rodr...@freebsd.org ---
Created attachment 151803
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151803action=edit
dump2.txt
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859
--- Comment #8 from Craig Rodrigues rodr...@freebsd.org ---
Herbert provided a traceback from his kernel panic. This looks like the source
of the problem:
panic: mtx_lock() of destroyed mutex @
