From owner-freebsd-current@FreeBSD.ORG Mon Aug 23 16:51:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3841D16A4CE for ; Mon, 23 Aug 2004 16:51:53 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D3A043D2D for ; Mon, 23 Aug 2004 16:51:53 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i7NGpl8U026169; Mon, 23 Aug 2004 09:51:48 -0700 Message-ID: <412A20A3.8060600@root.org> Date: Mon, 23 Aug 2004 09:51:47 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7 (X11/20040702) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <4123FC71.8060308@root.org> <41245804.7060008@DeepCore.dk> In-Reply-To: <41245804.7060008@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: current@freebsd.org Subject: Re: suspend/resume panic in ACPI.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 23 Aug 2004 16:51:53 -0000 Søren Schmidt wrote: > Nate Lawson wrote: > >> Try the attached patch. > > > OK, that makes the box suspend alright, but neither that nor any other > box or laptop I've got can get out of suspend without locking up. > > If I revert just /sys/dev/acpica and /sys/i386/acpica to aug-01 both > suspend and resume works (sortof, it does tend to panic later on). > It starts failing around aug-05 and then detoriates from that on to the > current state of locking up hard on resume. > It also fails in the exact same way on non-ATA systems, so I think I'm > out of the loop this time :) This may be fixed now in both current and releng_5. A logic inversion bug (= / !=) was causing pci irq link programming on resume to fail. It didn't impact many people since a lot of systems have chipsets that keep power to irq links while suspended. Please test again. -Nate