> If this is how I got most of my panics, this little script running in
> two different xterms helped decrease the time to panic. It got my
> system to panic a lot with the older nvidia drivers.
[script trimmed out]
> This always helped get my system unstable on 4-STABLE rather quickly. I
> thi
In the last episode (Aug 23), Dan Nelson said:
> --- coregrind/vg_proxylwp.c~ Mon Aug 23 15:47:33 2004
> +++ coregrind/vg_proxylwp.c Mon Aug 23 15:48:42 2004
And of course I screwed up the patch. The first argument of each print
call should be printing &px->mutex, not px->mutex. Here's better
On Saturday 21 August 2004 07:07 am, Maxim Konovalov wrote:
> On Sat, 21 Aug 2004, 13:19+0400, Maxim Konovalov wrote:
> > On Sat, 21 Aug 2004, 05:00-0400, Skip Ford wrote:
> > > Maxim Konovalov wrote:
> > > > On Fri, 20 Aug 2004, 12:36-0700, Ted Unangst wrote:
> > > >> errors in freebsd 4.10 found
On Mon, 23 Aug 2004, Kevin Brunelle wrote:
Alright, this is driving me nuts. For a little while there I could
not get the system to panic -- it would spontaniously reboot when
running a GL program instead of panic. This afternoon it finally
panic'd (who would think that would be something I want
In the last episode (Aug 23), Simon Barner said:
> Miguel Mendez wrote:
> > Is anybody using valgrind on 5.3BETA1 or newer? I've been using it
> > for a while on 5.2.1 without any problems, until I upgraded my
> > system to RELENG_5. The program works but it never exits after
> > running your progr
On Mon, 23 Aug 2004 22:03:39 +0200
Simon Barner <[EMAIL PROTECTED]> wrote:
Hi,
> there is a closed problem report in the database:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=68992
>
> At the end of that PR, there is a patch that seems to work around
> the problem. Could you please test it?
I
Alright, this is driving me nuts. For a little while there I could not
get the system to panic -- it would spontaniously reboot when running a
GL program instead of panic. This afternoon it finally panic'd (who
would think that would be something I want to see but it was).
I am attaching the tra
Miguel Mendez wrote:
> Hi all,
>
> Is anybody using valgrind on 5.3BETA1 or newer? I've been using it for a
> while on 5.2.1 without any problems, until I upgraded my system to
> RELENG_5. The program works but it never exits after running your
> program, it gets stuck into `umtx' state indefinite
Hi all,
Is anybody using valgrind on 5.3BETA1 or newer? I've been using it for a
while on 5.2.1 without any problems, until I upgraded my system to
RELENG_5. The program works but it never exits after running your
program, it gets stuck into `umtx' state indefinitely. This is happening
with both p
In message: <[EMAIL PROTECTED]>
"Kyle Mott" <[EMAIL PROTECTED]> writes:
: I have tried several times now to compile a GENERIC kernel on
: 4.10-STABLE with dgm0 (Digi Ports/16em, PCI version!) enabled, and have
: had no luck. Can anyone give me pointers? Right now, it's not showing up
:
In message: <[EMAIL PROTECTED]>
Ted Unangst <[EMAIL PROTECTED]> writes:
: M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > Ted Unangst <[EMAIL PROTECTED]> writes:
: > : aha_isa.c: aha_isa_attach: aha_free free "aha", can't use it
: > : afterwards, lots of exam
I have tried several times now to compile a GENERIC kernel on
4.10-STABLE with dgm0 (Digi Ports/16em, PCI version!) enabled, and have
had no luck. Can anyone give me pointers? Right now, it's not showing up
in dmesg (no errors, no warnings, nothing). The config line I have been
using is below (but
12 matches
Mail list logo
