It's sent out weekly.
So only people which are on bugbusters@ receive it. If someone is
interested in this but is not interested in the other bugbusters@
mails, they will not see it.
Actually apart from this thread that weekly email is the only traffic
on bugbusters@
_
Hi Damon,
Am 12.06.2005 um 23:02 schrieb Damon Hopkins:
Tracing pid 27 tid 100021 td 0xc15a4180
mcopydata(c17fa400,0,38,c193abc0,0) at m_copydata+0x28
ipllog(0,d3d46bc8,d3d46b50,d3d46b48,d3d46b40) at ipllog+0x1f1
ipflog(105819,c17fa450,d3d46bc8,c17fa400,0) at ipflog+0x18f
fr_check(c17fa450,14,c1
Hi,
Same situation like the panic i reported last month
(http://lists.freebsd.org/pipermail/freebsd-stable/2005-March/013066.html )
but this time without ipl(4) in the kernel.
I closed my laptop lid without closing the ssh session and boom the
NAT gateway (running 5.4-PRERELEASE) crashed.
db> w
Hi,
I am frequently running into this problem, when connecting from a NAT'ed
network via SSH to a host behind my IPfilter/IPnat firewall running
RELENG_5. It usually happens if i close my laptop's lid without closing the
SSH session.
DDB backtrace looks like this:
Tracing pid 27 tid 100021 td 0