From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 23:54:53 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 70F9816A403 for ; Thu, 4 Jan 2007 23:54:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232]) by mx1.freebsd.org (Postfix) with ESMTP id 17C4713C45E for ; Thu, 4 Jan 2007 23:54:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so6421061wxc for ; Thu, 04 Jan 2007 15:54:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=XdtYbSEZ8DLUojlmCuSHKqJbEPXCv1fLyJon2S+J0CxnhjopseLTThHZ73QpUVDZBB1XYLnrne05MgzzMMpYiJD7j58wuru6m3DcWacm3l4xZnkNwFBuKAHXdPmcNHdftvz1siT2ZLBD0t8bax0nxliKl97e7ttecJ/9nQmO+5E= Received: by 10.70.117.1 with SMTP id p1mr42034946wxc.1167954892053; Thu, 04 Jan 2007 15:54:52 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 10sm41461312wrl.2007.01.04.15.54.49; Thu, 04 Jan 2007 15:54:51 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l04NsvZd013207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jan 2007 08:54:57 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l04Nsrsj013206; Fri, 5 Jan 2007 08:54:53 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 5 Jan 2007 08:54:53 +0900 From: Pyun YongHyeon To: Randall Stewart Message-ID: <20070104235453.GA13114@cdnetworks.co.kr> References: <45891FE9.4020700@cisco.com> <58281AA0-3738-490C-9EA8-7766033713A2@siliconlandmark.com> <458960F2.9090703@cisco.com> <200612281756.29949.jhb@freebsd.org> <4594F282.7080504@cisco.com> <20070103100555.3611b41c.rnsanchez@wait4.org> <459CE5F9.3020504@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <459CE5F9.3020504@cisco.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, Ricardo Nabinger Sanchez Subject: Re: A stuck system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2007 23:54:53 -0000 On Thu, Jan 04, 2007 at 06:33:13AM -0500, Randall Stewart wrote: > Ricardo Nabinger Sanchez wrote: > >On Fri, 29 Dec 2006 05:48:34 -0500 > >Randall Stewart wrote: > > > >>Nope... its just a single port, on-motherboard msk0. > >> > >>It does wake up though if I ping any interface... > >> > >>I suspect it might be a hardware problem.. not sure > >>yet :-0 > > > >How about installing a ping trap in the device driver to generate a dump? > >What I mean is to, whenever the device driver receives a packet, it checks > >if > >the packet is a special ping packet (with some specific data, like > >"dumpdump..." in the data field), and if so, forces a dump so you can check > >(luckily) where the system came from. > > > >It's a long shot, but perhaps it gives a hint. > > > >Does this behavior happens on IA-64 boxes? If so, the kernel could set up > >the processor to save performance data (specifically the branch history), > >and > >the special ping (or something else) could be used to print the branch > >buffer > >history, instead of dumping a core. Debugging symbols would be a must, I > >believe. > > > Well... the machine is only a p4d gigabit motherboard... > > I am more and more suspecting a hardware problem. > > There is a em card in the machine and the motherboard msk card. > The most recent update of the msk card seems to crash the system > at startup.. so I took it out of my load config.. have not > played with it yet.. > Would you post backtrace information for msk(4)? Btw, how about disabling MSI for msk(4)? (loader tunable: hw.msk.msi_disable) > Previously I could ping the msk net.. and the machine would > wakeup.. now that I don't have the msk card.. guess what.. pinging > the em0 card DOES NOT wake the machine up.. > > I bet there is some foul-up on the motherboard causing it to > not deliver interrupts until another one (on the mother board) > comes in... oh well.. > > R > > -- > Randall Stewart > NSSTG - Cisco Systems Inc. > 803-345-0369 803-317-4952 (cell) > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Regards, Pyun YongHyeon