From owner-freebsd-current@FreeBSD.ORG Wed Oct 22 10:41:42 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A917F1065671; Wed, 22 Oct 2008 10:41:42 +0000 (UTC) (envelope-from wjw@withagen.nl) Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.freebsd.org (Postfix) with ESMTP id 5B3148FC22; Wed, 22 Oct 2008 10:41:42 +0000 (UTC) (envelope-from wjw@withagen.nl) Received: from localhost (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id AC145174FD; Wed, 22 Oct 2008 12:41:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dqvhcwkl8PHF; Wed, 22 Oct 2008 12:41:39 +0200 (CEST) Received: from [212.61.27.67] (opteron [212.61.27.67]) by mail.digiware.nl (Postfix) with ESMTP id 6C74F173A1; Wed, 22 Oct 2008 12:41:39 +0200 (CEST) Message-ID: <48FF0347.3000804@withagen.nl> Date: Wed, 22 Oct 2008 12:41:11 +0200 From: Willem Jan Withagen Organization: Digiware User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Ivan Voras References: <48FCED88.1090502@withagen.nl> <48FDC047.8050101@withagen.nl> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Dumping kernel in SMP env X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Oct 2008 10:41:42 -0000 Ivan Voras wrote: > Willem Jan Withagen wrote: >> Ivan Voras wrote: >>> Willem Jan Withagen wrote: >>>> Hi, >>>> >>>> Once again trying to get a little further with the freezes and lockups. >>>> But panic-ing the kernel from the debugger only works with one >>>> processor. Doing it with both processors active just generates 2 >>>> backtraces, but no dump. >>> If you're asking if kernel dumps work on 8-CURRENT on SMP then the >>> answer is yes - I made a couple of them the day before yesterday. >>> >>>> Is this a known fact? There was a similar question beginning of the >>>> month asking about 'call doadump' not working, without an answer. >>>> If it should work, I'll try and recreate the traceback. >>> Both automatic and doadump work for me. >> Right, that was the question. >> >> So then I have a problem there that needs to be fixed first. >> I'll try to get a serial console working and capture the trace and or >> any other stuff that can help. >> >> Suggestions for things to look at are welcome > > Your problem might be caused by bad hardware. I don't have anything > specific to suggest, except looking at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html That's why I'm going to get 5.x, 6.x or 7.x running first. I'm pretty confident that one of those did work quite wel. The board did have some bad temperament when amd64 first got started, it was one of the first dual opteron MSI boards at that time. Then it took a while to get going as well. --WjW