My system don't started Tor daemon and dnscrypt-proxy
daemon and still I get this kernel panic.
I still use Unbound.
I still have pf rules for transparent
proxying. I only disabled Tor client.
I was thinking about simplify more before I answer, but
dhill () mindcry ! org posted similar bug to bug
>
> > The key is really being able to reproduce the problem, Lampshade do you
> > already know which service or config triggers this panic? Could you try
> > to figure out by simplifying your setup?
>
> I don't know.
> Problem is that even with most complicated config it happens a few times
>
Another crash.
I should note that this kernel is build by me with patches
to GENERIC (HZ from 100 to 300), pci and acpi files.
Both previous reports were from
official kernel builds (snapshots).
Source code is based on:
cvs -d$CVSROOT up -D "2016-08-26 12:45" -Pd
As always with this panic I
> Are you using the tor TRANS_PF stuff for transparent proxying?
Yes, I am.
# grep -v -e ^# -e Password /etc/tor/instancjaDlaFF.conf
user _tor_do_FF
RunAsDaemon 1
DataDirectory /home/_tor_do_FF/
Log notice file /home/_tor_do_FF/logs/log
SocksPort 0
TransListenAddress 172.10.0.2:9040
TransPort
Are you using the tor TRANS_PF stuff for transparent proxying?
On 9 August 2016 10:06:11 p.m. Lampshade wrote:
> Which daemons do you use on this machine?
# rcctl ls on
check_quotas
cron
dnscrypt_proxy_one
dnscrypt_proxy_second
messagebus
pf
pflogd
relayd
sndiod
>
> > Which daemons do you use on this machine?
>
> # rcctl ls on
> check_quotas
> cron
> dnscrypt_proxy_one
> dnscrypt_proxy_second
> messagebus
> pf
> pflogd
> relayd
> sndiod
> syslogd
> unbound
> # rcctl ls started
> cron
> dnscrypt_proxy_one
> dnscrypt_proxy_second
> messagebus
On 08/09/16 20:47, Lampshade wrote:
> It happened again. I have:
That's bad.
> Tail of dmesg under kernel debugger:
> $ dmesg
> Debugger() at Debugger+0x9
> panic() at panic+0xfe
> __assert() at assert+0x25
> pf_state_key_unref() at pf_state_key_unref+0xc6
> pf_pkt_unlink_state_key() at
> On 22/06/16(Wed) 00:53, Lampshade wrote:
> > I don't know if this is enough, but I haven't had access to web
> > using other device when kernel panicked.
>
> What's the output of ifconfig and route -n show for this system?
>
Sorry for silence.
Kernel panic happened only once in June and this
On 22/06/16(Wed) 00:53, Lampshade wrote:
> I don't know if this is enough, but I haven't had access to web
> using other device when kernel panicked.
What's the output of ifconfig and route -n show for this system?
> sysctl kern.version
>
I don't know if this is enough, but I haven't had access to web
using other device when kernel panicked.
sysctl kern.version
kern.version=OpenBSD 6.0-beta (GENERIC.MP) #2198: Sun Jun 19 11:58:45 MDT 2016
10 matches
Mail list logo