From owner-freebsd-current Mon Feb 8 16:42:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03560 for freebsd-current-outgoing; Mon, 8 Feb 1999 16:42:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03549 for ; Mon, 8 Feb 1999 16:42:41 -0800 (PST) (envelope-from tcobb@staff.circle.net) From: tcobb@staff.circle.net Received: by freya.circle.net with Internet Mail Service (5.5.2232.9) id <1PTHK00W>; Mon, 8 Feb 1999 19:41:54 -0500 Message-ID: To: mike@smith.net.au Cc: current@FreeBSD.ORG Subject: RE: Tracking a Fatal Double Fault Date: Mon, 8 Feb 1999 19:41:52 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So a double-fault is always a kernel stack problem? I find it suspicious that this same machine also had trouble with the 3c905B flaking out -- dropping packets during an ifconfig alias, and sometimes never reactivating the interface according to what tcpdump shows. The 3c905B problem repeates itself on EVERY machine that I've them installed into (7 or so), the double-faults are infrequent on some of the busier machines, and almost always during the initial boot process. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > There's nothing immediately obvious in the xl driver that > would suggest > that it uses excessive kernel stack either. 8( Maybe > someone has some > clues on measuring stack usage (or simply on how to > increase the kernel > stack allocation...). > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message