Thus spake Doug Barton ([EMAIL PROTECTED]) [03.03.13 13:27]:
> Update your sources, and make sure that you have 1.202 of
> sys/netinet/tcp_input.c. I had a 100% reproducable panic very similar to
> yours, and hsu fixed it.
I'd like to verify, but using updated sources as of about four hours ago, I
Update your sources, and make sure that you have 1.202 of
sys/netinet/tcp_input.c. I had a 100% reproducable panic very similar to
yours, and hsu fixed it.
On Wed, 12 Mar 2003, Damian Gerow wrote:
> I've managed to write down the actual panic twice (no panic to screen if
> you're in X),
You pro
On Wed, 12 Mar 2003, Brent Jones wrote:
> Wow. That's quite a trick. I've CVSup'ed, buildworld/kernel and
> freshly installed gpg, within the last two hours.
>
> [EMAIL PROTECTED]:/home/brent $ gpg --keyserver pgp.mit.edu --recv-key
> BB6BC940
> and then it dies...
>
> Brent
>
> On Wednesday, Ma
Wow. That's quite a trick. I've CVSup'ed, buildworld/kernel and
freshly installed gpg, within the last two hours.
[EMAIL PROTECTED]:/home/brent $ gpg --keyserver pgp.mit.edu --recv-key
BB6BC940
and then it dies...
Brent
On Wednesday, Mar 12, 2003, at 14:45 America/Denver, Damian Gerow wrote:
I've been running -CURRENT on my workstation for a couple of months, and
have been quite impressed. But I've started seeing pretty consistant panics
when verifying PGP-signed messages.
Everything was fine until I cvsup'ed about two weeks ago, and is still
apparent in another cvsup as of March 10.
