From owner-freebsd-mobile@FreeBSD.ORG Thu Jan 27 13:58:15 2005 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79AC616A4CE for ; Thu, 27 Jan 2005 13:58:15 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id C1A6F43D53 for ; Thu, 27 Jan 2005 13:58:14 +0000 (GMT) (envelope-from dwalton@acm.org) Received: (qmail 57589 invoked from network); 27 Jan 2005 10:44:52 -0000 Received: from unknown (HELO ?172.16.1.34?) (unknown) by unknown with SMTP; 27 Jan 2005 10:44:52 -0000 X-pair-Authenticated: 68.124.184.89 Message-ID: <41F8C5EA.3040007@acm.org> Date: Thu, 27 Jan 2005 02:43:54 -0800 From: Dave Walton User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Belashov References: <41EF6101.7010008@acm.org> <20050120092812.GB16150@cell.sick.ru> <41F02F9A.40201@acm.org> <41F0A398.7080800@orel.ru> <41F4C6BD.4060406@acm.org> <41F4D7EE.9030108@orel.ru> In-Reply-To: <41F4D7EE.9030108@orel.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: glebius@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Trouble with APM suspend in 5.3-R X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dwalton@acm.org List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2005 13:58:15 -0000 Andrew Belashov wrote: > Dave Walton wrote: > >> Since I now have a core file, I expect you'd like to see a backtrace... >> (Which is about the extent of my knowledge of gdb.) >> >> [...] >> > > Look like bug in pcm(4). Try to disable a sound support. Ok, I've tried that. I removed sound.ko and snd_mss.ko from /boot/loader.conf, rebooted without sound support, and did suspend/resume. Upon resume, FreeBSD locked up, requiring me to turn off the system to recover. Now what? How do we continue troubleshooting with no error message and no core dump? Thanks, Dave