From owner-freebsd-current Tue Jan 14 17:27:31 2003 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 DDA2E37B401 for ; Tue, 14 Jan 2003 17:27:29 -0800 (PST) Received: from mail2.dbitech.ca (radius.wavefire.com [64.141.13.252]) by mx1.FreeBSD.org (Postfix) with SMTP id 2D00E43F13 for ; Tue, 14 Jan 2003 17:27:29 -0800 (PST) (envelope-from wade@wavefire.com) Received: (qmail 4985 invoked from network); 15 Jan 2003 02:09:06 -0000 Received: from wade.wavefire.com (HELO wade) (64.141.15.223) by radius.wavefire.com with SMTP; 15 Jan 2003 02:09:06 -0000 Message-Id: <3.0.32.20030114171936.020f1790@mail.wavefire.com> X-Sender: wade@mail.wavefire.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 14 Jan 2003 17:19:36 -0800 To: freebsd-current@freebsd.org From: wade Subject: Re: 5.0 Freezes under high load with SMP. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oops... my original posts got sent to their posters in stead of the list... At 11:12 AM 1/14/03 -0800, you wrote: >On Tue, 14 Jan 2003, wade wrote: >> Although GENERIC functions perfectly, when I enable SMP in GENERIC, the box >> freezes during big build jobs ( i.e. buildworld. ). This box functioned >> well in SMP mode und 4.7-STABLE. The big problem is that freezing does not >> leave core files or any other debugging information. >> >> Hardware: >> ASUS CUV4X-D >> 2 X PIII 600 MHz Coppermine. >> 512 MB 133MHz RAM. > >Hit ctl-alt-esc on console to enter DDB (enable this kernel option if you >haven't already). Type "trace" to find out what is hung. If this doesn't >work, attach a serial console and do a break there and "trace". > >-Nate I tried this, but when the box froze, the keyboard was completely unresponsive, no numlock, nothing. The serial console is similarly unresponsive. I have all the debugging options that are on in the default GENERIC from -CURRENT which include DDB. I have also checked out the section in the handbook on serial consoles and enabled the option BREAK_TO_DEBUGGER as suggested there. Break does not get a response either. It may be worth noting that I can get a freeze condition on any large operation regardless of the -j setting for make. As an additional note, dmesg output for the problematic kernel can be seen at http://archeron.wavefire.com/~wade/dmesg.arch.txt . This is not localized to a keyboard. Screen save freezes, remote sessions lock and machine pings as if dead. Any other avenues I can follow to resolve this or find the problematic code/hardware? thanx. -Wade Klaver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message