The following reply was made to PR amd64/134978; it has been noted by GNATS.
From: Andriy Gapon
To: GD
Cc: bug-follo...@freebsd.org
Subject: Re: amd64/134978: [panic] g_up pmap amd64 panic
Date: Sun, 05 Dec 2010 16:22:34 +0200
on 05/12/2010 14:59 GD said the following:
> Sorry, but t
Synopsis: [panic] g_up pmap amd64 panic
State-Changed-From-To: open->closed
State-Changed-By: avg
State-Changed-When: Sun Dec 5 14:21:49 UTC 2010
State-Changed-Why:
The problem is not reproducible with the head code.
http://www.freebsd.org/cgi/query-pr.cgi?pr=134978
_
The following reply was made to PR amd64/134978; it has been noted by GNATS.
From: GD
To: Andriy Gapon
Cc: bug-follo...@freebsd.org
Subject: Re: amd64/134978: [panic] g_up pmap amd64 panic
Date: Sun, 5 Dec 2010 13:59:52 +0100
Sorry, but this problem in 9.0-CURRENT is not repeating.
On
The following reply was made to PR amd64/134978; it has been noted by GNATS.
From: Andriy Gapon
To: bug-follo...@freebsd.org, g...@wp.pl
Cc:
Subject: Re: amd64/134978: [panic] g_up pmap amd64 panic
Date: Sun, 05 Dec 2010 14:28:41 +0200
Are still able to reproduce the problem?
Some
The following reply was made to PR amd64/134978; it has been noted by GNATS.
From: Andriy Gapon
To: bug-follo...@freebsd.org, g...@wp.pl
Cc:
Subject: Re: amd64/134978: [panic] g_up pmap amd64 panic
Date: Thu, 01 Apr 2010 00:02:30 +0300
The panic seems to be caused by NULL pointer passed to
