From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 2 12:38:43 2012 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C0B3694; Fri, 2 Nov 2012 12:38:43 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 26EE18FC17; Fri, 2 Nov 2012 12:38:41 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA02684; Fri, 02 Nov 2012 14:38:36 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <5093BECC.1030709@FreeBSD.org> Date: Fri, 02 Nov 2012 14:38:36 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Tom Lislegaard Subject: Re: 9-Stable panic: resource_list_unreserve: can't find resource References: <509172F6.2040400@FreeBSD.org> <5092F209.7090803@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2012 12:38:43 -0000 on 02/11/2012 11:56 Tom Lislegaard said the following: > The machine is usually connected to a docking station and I believe the power is very stable. I sometimes take it home and connect it to a different powersupply and sees the same behavior with panics there. Panics can occur while I'm at the machine working, or if I leave the machine idle for some time I find it has paniced/rebooted when I come back. > The time of panic seems totally random and I can't correlate this to any particular activity like cronjobs, etc. I see. Could you please try setting debug.acpi.max_threads=1 in /boot/loader.conf, reboot and see if that makes any difference? -- Andriy Gapon