From owner-freebsd-stable@FreeBSD.ORG Thu Jan 8 01:19:26 2009 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 465B510656EB for ; Thu, 8 Jan 2009 01:19:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by mx1.freebsd.org (Postfix) with ESMTP id 0589F8FC14 for ; Thu, 8 Jan 2009 01:19:25 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so9989067rvf.43 for ; Wed, 07 Jan 2009 17:19:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=FeBXuyEsjSjriS/fWQLa8O3h7sVYk171v5Qwl9mlTR8=; b=n2tUDulrdeeZg9DIsztUPBAjMJCyaYGb3CdAmPAmXKjDUHlEGc0hNX+Q8+D071hhmG hOgbBlYSyXzPjxntmQM+MtYEQnSn8Jwcfe0QYSdx3ocfaGhFuavq53qoBPW6uXC84SI9 t2ZY8uTWDPCqcG+RZu3ENC2V/DCDAQN9zCRhk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=iIeyimiR0CScEpGtbTwjOMp3QqveCD0aQGiPehkYzTXpRW3YVu4/3lf8rBFu5NBbib Cop1E+uqjeWy8UflVtnYaDqswO0L98hWe1ku0vum28rbBEVe3msg5nWGcSir1hQ4el93 mXZqfhj/vzyqYXESOWLYujhI4F6nwucMP3OU4= Received: by 10.115.19.16 with SMTP id w16mr15680730wai.51.1231377565566; Wed, 07 Jan 2009 17:19:25 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id z15sm37822694pod.14.2009.01.07.17.19.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 07 Jan 2009 17:19:23 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.14.3/8.14.3) with ESMTP id n081JG4o050984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Jan 2009 10:19:16 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.14.3/8.14.3/Submit) id n081JFDh050983; Thu, 8 Jan 2009 10:19:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 8 Jan 2009 10:19:14 +0900 From: Pyun YongHyeon To: Brandon Weisz Message-ID: <20090108011914.GB1256@cdnetworks.co.kr> References: <49600E2E.7070601@avioc.org> <3163F769-48B0-4CFC-8842-BBBDDAE78B51@gmail.com> <20090105032657.GA1842@cdnetworks.co.kr> <4961FACE.4060203@avioc.org> <20090106080333.GA6168@cdnetworks.co.kr> <49637755.1070708@avioc.org> <20090107103924.GA126@cdnetworks.co.kr> <4964D384.1060301@avioc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4964D384.1060301@avioc.org> User-Agent: Mutt/1.4.2.3i Cc: Garrett Cooper , stable@freebsd.org, marcel@freebsd.org Subject: Re: Panic in RELENG_7_1 with fxp(4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2009 01:19:26 -0000 On Wed, Jan 07, 2009 at 10:08:36AM -0600, Brandon Weisz wrote: > Pyun YongHyeon wrote: > > .... > > >I think the panic message you posted below is not related with > >fxp(4). Show me panic message for fxp(4), that would be more > >helpful to narrow down possible cause of issue. > >BTW, are you using non-standard compilation flag or customized > >kernel? Since there are lot of systems that still rely on fxp(4) > >I wonder how this issue is not reported yet. > >Did GENERIC kernel also show exact the same behaviour? > > > > Hi Pyun, > > As suggested, the GENERIC kernel did not panic. After a few more tests, > the culprit appears to be: > > device puc > > With puc(4) removed, the system is running on 7.1-RELEASE kernel with > the fxp(4) card operating as expected. For now I'll be shelving the > cheap pci serial card. > > If anyone wishes to investigate this further I'm happy to continue testing. > Hmm, I still have no idea how puc(4) can trigger the issue. Marcel may have more idea how to debug this(CCed). > Thank you very much for your help. > > Brandon > > > > > After the system panic with this patch, I went into the bios and > > > disabled all unnecessary hardware such as parallel port, usb controller > > > and on-board audio. The resulting panic below appears different. > > > > > > Fatal trap 12: page fault while in kernel mode > > > cpuid = 0; apic id = 00 > > > fault virtual address = 0x400 > > > fault code = supervisor read, page not present > > > instruction pointer = 0x20:0xc07eefec > > > stack pointer = 0x28:0xe4339ac0 > > > frame pointer = 0x28:0xe4339ae4 > > > code segment = base 0x0, limit 0xfffff, type 0x1b > > > = DPL 0, pres 1, def32 1, gran 1 > > > processor eflags = interrupt enabled, resume, IOPL = 0 > > > current process = 28 (irq23: vr0) > > > trap number = 12 > > > panic: page fault > > > cpuid = 0 > > > Uptime: 50s > > > Physical memory: 995 MB > > > Dumping 162 MB: 147 131 115 99 83 67 51 35 19 3 > > > > > > >[...] > > > -- Regards, Pyun YongHyeon