From owner-freebsd-stable@FreeBSD.ORG Wed Nov 17 12:39:36 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED1FF16A4CE for ; Wed, 17 Nov 2004 12:39:36 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E32C43D4C for ; Wed, 17 Nov 2004 12:39:36 +0000 (GMT) (envelope-from lukas.ertl@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so876868rnf for ; Wed, 17 Nov 2004 04:39:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=HPi33Eqy0VnzgkwoOe/VL21AXd5SB58rVhRmsPx7SeqG5k24mx+E58nkXreXO0/9bVF7+xVWtnQeN30B2AD10rmwRK4T0DqxJ514UVDnbL2e6h6HRpNfVVjA5My4z5ZslzGwcMEi6EW70yAyxr0qjtQj8hc1W6xEhiIO/NfWjW8= Received: by 10.38.82.27 with SMTP id f27mr399626rnb; Wed, 17 Nov 2004 04:39:35 -0800 (PST) Received: by 10.38.70.62 with HTTP; Wed, 17 Nov 2004 04:39:35 -0800 (PST) Message-ID: <4379f9100411170439643dcbab@mail.gmail.com> Date: Wed, 17 Nov 2004 13:39:35 +0100 From: Lukas Ertl To: Robert Watson In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4379f9100411170140118fcb3f@mail.gmail.com> cc: freebsd-stable@freebsd.org Subject: Re: 5.3-STABLE frozen on heavy network load X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Lukas Ertl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 12:39:37 -0000 On Wed, 17 Nov 2004 10:22:14 +0000 (GMT), Robert Watson wrote: > > On Wed, 17 Nov 2004, Lukas Ertl wrote: > > > I'm seeing complete freezes on a 5.3-STABLE SMP (with HTT) kernel from > > Fri Nov 12. The machine is acting as a newsserver, thus it has heavy > > network and disk load. > > Do you know if the freeze happens with 5.3-RELEASE "as released"? No, as I went directly from some 5-CURRENT to RELENG_5. > If you set 'debug.mpsafenet=0', do the freezes keep happening? > > What happens if you run with INVARIANTS on? I'll check that. > Is the system too slow with WITNESS to run your workload? Unfortunately, yes. > Could you send dmesg output? Can be found at . > Do you have an estimate of how long it takes to go from boot to hang? Somewhere between one, two days and one, two weeks. > If/when this recurs, could I get you to run the following commands in DDB, > and send output: > > - ps > - show lockedvnods > - show pcpu > - show pcpu X, for each valid value of X (0 ... maxcpus-1) > - do trace on each thread active on a CPU > - do trace on any network device driver ithread, on the netisr, and any > other thread that appears to be involved in network activity OK, will do. > Using the current core, could you go to frame #29, and print *td, > *td->td_proc, *uio, *active_cred, and *fp. Go to frame #28 and print *so. > If possible, please keep this dump around, I may also ask you to inspect > *so_pcb once we know what to cast it to (given that it's a news server, > could well be TCP, in which cast *(struct inpcb *)so->so_pcb, as well as > the tcpcb reached through that). Can be found at . > Oh, one more thing that would be useful: if you compile with > BREAK_TO_DEBUGGER, are you able to get into the debugger using a console > break or a serial break? If so, which? I assume that because you're > using MP_WATCHDOG, you can't, but it's worth asking. Right now, syscons > requires Giant, so if you can get into the debugger via the serial link > but not syscons, it will suggest something is spinning with Giant. Unfortunately, I don't have a serial link available. MP_WATCHDOG was my last resort to get at some info. Hope that helps, thanks, le