From owner-freebsd-current@FreeBSD.ORG Mon Jan 26 17:55:09 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 0A2D916A4CE
for <freebsd-current@freebsd.org>;
Mon, 26 Jan 2004 17:55:09 -0800 (PST)
Received: from Espresso.NEEBU.Net (espresso.neebu.net [66.166.158.130])
by mx1.FreeBSD.org (Postfix) with SMTP id 69A7943D64
for <freebsd-current@freebsd.org>;
Mon, 26 Jan 2004 17:54:56 -0800 (PST)
(envelope-from khuon@Espresso.NEEBU.Net)
Received: from Espresso.NEEBU.Net (khuon@localhost [127.0.0.1])
by Espresso.NEEBU.Net (8.12.10/8.12.10) with ESMTP id i0R1sn7v025168
for <freebsd-current@freebsd.org>;
Mon, 26 Jan 2004 17:54:55 -0800 (PST)
Received: from Espresso.NEEBU.Net (khuon@localhost)i0R1smCL025167
for <freebsd-current@freebsd.org>;
Mon, 26 Jan 2004 17:54:49 -0800 (PST)
Message-Id: <200401270154.i0R1smCL025167@Espresso.NEEBU.Net>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4
From: "Jake Khuon" <khuon@NEEBU.Net>
To: freebsd-current@freebsd.org
Dcc:
Action:
Expires:
Precedence:
Priority: Normal
X-Face: "(e&e|OIYrcV1x8y?txN%k1E2f[qWLjRjOn+a30)3>x`Wx%_9Xi<co=3m#T]qdY{dLp5uKN
G&[(OVQ`SN::Jmar^rFK\zl]CDu!1;-s&@K.VwY|Fb)N)jT[yk'[P$oSTJnWUOK0;
+b.Ud:r%8(+Ji
knsoG~*Mmnx?ZF=>Xs<K2Z8)$)n%,C:B*qK2KP-WDIs)AZN8nlJb#R2h<|W-|9YS5;
5KBYwp|H99.? i9>\IO2#G5L1m=c/|^h|z29wJ#]D/.?Ks,Mw1
X-URI: http://Espresso.NEEBU.Net/~khuon/
X-Organisation: Network Engineers for Effective Bandwidth Utilisation
X-Header: /usr/include gives great headers
X-System: Sun UltraSPARCstation2/2300MP running SunOS Release 5.8
X-Shell: tcsh 6.07.02 (Astron) 1996-10-27 (sparc-sun-solaris) options
8b,nls,dl,al,ng,rh
X-Chtorr: History is full of revisionists. Where it used to say "THOU SHALT
NOT KILL" it now says, "except as specified in section III-B,
Paragraph 12, Sub-section D, Schedule 3." If that still doesn't
suit you, wait till next year's commandments come out and trade it
in for something that does.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 26 Jan 2004 17:54:48 -0800
Sender: khuon@Espresso.NEEBU.Net
Subject: an driver lockup with linux-mozilla
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2004 01:55:09 -0000
This is hard to debug but it seems to be reproducable. I get a hard lockup
of the machine when I'm running the latest nightly build of linux-mozilla
(1.7a) and accessing a webpage with a large amount of images. This doesn't
seem to happen with the native mozilla. Whatever it is, it happens so
quickly that I get no kernel debug or warning messages at all. Any ideas on
how I might go about further debugging?
--
/*===================[ Jake Khuon <khuon@NEEBU.Net> ]======================+
| Packet Plumber, Network Engineers /| / [~ [~ |) | | --------------- |
| for Effective Bandwidth Utilisation / |/ [_ [_ |) |_| N E T W O R K S |
+=========================================================================*/