Hello,
I've found another (easy) way to reproduce the problem with two scripts:
routes-add.sh and routes-remove.sh.
First run routes-add.sh for a while; then execute routes-remove.sh.
Cancel with CTRL+C and execute routes-remove.sh again.
Scripts:
# cat routes-add.sh
#!/usr/local/bin/b
The following reply was made to PR kern/155177; it has been noted by GNATS.
From: "Eduardo Schoedler"
To:
Cc: ,
Subject: Re: kern/155177: [route] [panic] Panic when inject routes in kernel
Date: Fri, 4 Mar 2011 09:10:00 -0300
Hello,
I've found another (easy) way to reproduce the pr
Silly question but have you checked your ram for issues, we had a machine
with seemingly unexplained problems and hangs and it turned out to be
a duff stick of ram which wasn't being chip killed.
- Original Message -
From: "Lev Serebryakov"
To: "Brandon Gooch"
Cc: "Arnaud Lacombe" ; ;
On Sun, 27 Feb 2011, Doug Barton wrote:
On 02/27/2011 12:23, Fernando Gont wrote:
On 08/02/2011 03:47 p.m., Doug Barton wrote:
[catching up with e-mail]
I've been up and running on this patch vs. r218391 for over 24 hours
now, using algorithm 4 (as someone said is now the default in Linux)
w
On 03/04/2011 16:21, Bjoern A. Zeeb wrote:
On Sun, 27 Feb 2011, Doug Barton wrote:
As for default algorithm, is there any reason not to make it 4?
Yes, it's expensive both computation time and stack wise. Last I put
MD5ctxs on the stack I was told that it was previously avoided do to
stack l
