From owner-freebsd-stable@FreeBSD.ORG Sat Apr 30 13:14:45 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF6FD106564A; Sat, 30 Apr 2011 13:14:45 +0000 (UTC) (envelope-from sklauder@trimind.de) Received: from mikako.shopkeeper.de (mikako.shopkeeper.de [82.119.175.20]) by mx1.freebsd.org (Postfix) with ESMTP id 3BA268FC0A; Sat, 30 Apr 2011 13:14:44 +0000 (UTC) Received: from avalon.dobu.local (pD951D203.dip.t-dialin.net [217.81.210.3]) (authenticated bits=0) by mikako.shopkeeper.de (8.14.3/8.14.3) with ESMTP id p3UCxeCn006034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Apr 2011 14:59:42 +0200 (CEST) (envelope-from sklauder@trimind.de) Received: from avalon.dobu.local (localhost [127.0.0.1]) by avalon.dobu.local (8.14.4/8.14.2) with ESMTP id p3UCxef8001887; Sat, 30 Apr 2011 14:59:40 +0200 (CEST) (envelope-from sklauder@avalon.dobu.local) Received: (from sklauder@localhost) by avalon.dobu.local (8.14.4/8.14.4/Submit) id p3UCxej2001886; Sat, 30 Apr 2011 14:59:40 +0200 (CEST) (envelope-from sklauder) Date: Sat, 30 Apr 2011 14:59:40 +0200 From: Sascha Klauder To: freebsd-stable@freebsd.org Message-ID: <20110430125940.GA1872@trimind.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.96.5 at mikako.shopkeeper.de X-Virus-Status: Clean Cc: freebsd-acpi@freebsd.org Subject: ale(4) not attaching after suspend/resume cycle X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sklauder@trimind.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 13:14:45 -0000 Hi all, I'm trying to get suspend/resume functionality to work on my Acer Aspire One D250 netbook. I'm running 8.2-STABLE i386 as of 2011-02-25. Suspend was doing fine, but it would freeze on resume. By trial and error I've been able to pinpoint the problematic driver as ale(4). The machine will correctly resume once I un- load if_ale before suspending. I wouldn't mind that as a workaround, however, it fails to reattach after a suspend/resume cycle: pci0: driver added pci1: driver added found-> vendor=0x1969, dev=0x1026, revid=0xb0 domain=0, bus=1, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0407, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D3 MSI supports 1 message, 64 bit pci0:1:0:0: reprobing on driver added pci0:1:0:0: Transition from D3 to D0 ale0: port 0x3000-0x307f mem 0x95200000-0x9523ffff irq 16 at device 0.0 on pci1 pcib1: ale0 requested memory range 0x95200000-0x9523ffff: good ale0: phy write timeout : 29 ale0: phy write timeout : 30 ale0: phy write timeout : 29 ale0: phy write timeout : 30 ale0: phy write timeout : 29 ale0: phy write timeout : 30 ale0: phy write timeout : 29 ale0: phy write timeout : 29 ale0: phy write timeout : 29 ale0: phy write timeout : 29 ale0: master reset timeout! ale0: reset timeout(0xffffffff)! ale0: PCI device revision : 0x00b0 ale0: Chip id/revision : 0xffff ale0: chip revision : 0xffff, 4294967295 Tx FIFO 4294967295 Rx FIFO -- not initialized? device_attach: ale0 attach returned 6 It does attach and work correctly even if loaded after booting. Repeated loading and unloading works as well. Anything obvious that I could try? Complete dmesg is available here: http://arwen.shopkeeper.de/~sascha/acer/dmesg.verbose Cheers, -sascha