From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 30 17:37:10 2015 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF54D7A4; Fri, 30 Jan 2015 17:37:10 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A54CDDA; Fri, 30 Jan 2015 17:37:10 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id kx10so54756162pab.12; Fri, 30 Jan 2015 09:37:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=TgBjHcaGOVh8z9pYOGCbM1/Nh8DMTTv51e1AIC0llZE=; b=vO6rAJWVhv8qRDjJI81O3ix+oJ9tgT6hDSnmfYbxiQWkai9QiRSIJtn6IMd2VR5Jw8 Oma8H1RpfUQbeDdQuj9/oehooWpZ3DY8CM5mJiuyjo3sKJjR5GqWgKAihvNBw43XPmk/ nVjKKYcWYv32uJu3y9N5qkhxNVELAL9GJsmm/FD+yWk/zmWPLE5jXTwyn5KTLsAfoN4f a7gNWimzlyTu8os2l/a1n4ZiPqziDUfKVdEevbnBESRplCEyP4HKEKE9z+P4Df3hqKU1 lvaMOh93ISIeM2KUng7xmxan0stekMxwSmlz/NPP5wF2vuR7CXfEzBSlt5KUqT8zfB+Q go7Q== MIME-Version: 1.0 X-Received: by 10.70.89.225 with SMTP id br1mr10636194pdb.8.1422639430148; Fri, 30 Jan 2015 09:37:10 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.22.231 with HTTP; Fri, 30 Jan 2015 09:37:10 -0800 (PST) In-Reply-To: <54CA9529.1060903@att.net> References: <54CA4C9D.4020500@att.net> <54CA9529.1060903@att.net> Date: Fri, 30 Jan 2015 09:37:10 -0800 X-Google-Sender-Auth: DwlUPLxmpLBJzZFjSuRU_BqLGpk Message-ID: Subject: Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1 From: Kevin Oberman To: Anthony Jenkins Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Mohammad Najafi , "freebsd-acpi@freebsd.org" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2015 17:37:10 -0000 On Thu, Jan 29, 2015 at 12:16 PM, Anthony Jenkins wrote: > Ahhh... good ol' VESA driver: > > Jan 29 23:06:57 MyBSD kernel: Fatal trap 12: page fault while in > kernel mode > Jan 29 23:06:57 MyBSD kernel: cpuid = 0; apic id = 00 > Jan 29 23:06:57 MyBSD kernel: fault virtual address = 0x378 > Jan 29 23:06:57 MyBSD kernel: fault code = supervisor read > data, page not present > Jan 29 23:06:57 MyBSD kernel: instruction pointer = > 0x20:0xffffffff809149e1 > Jan 29 23:06:57 MyBSD kernel: stack pointer = > 0x28:0xfffffe011b3b9480 > Jan 29 23:06:57 MyBSD kernel: frame pointer = > 0x28:0xfffffe011b3b9500 > Jan 29 23:06:57 MyBSD kernel: code segment = base 0x0, limit > 0xfffff, type 0x1b > Jan 29 23:06:57 MyBSD kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 > Jan 29 23:06:57 MyBSD kernel: processor eflags = interrupt > enabled, resume, IOPL = 0 > Jan 29 23:06:57 MyBSD kernel: current process = 996 (acpiconf) > Jan 29 23:06:57 MyBSD kernel: trap number = 12 > Jan 29 23:06:57 MyBSD kernel: panic: page fault > Jan 29 23:06:57 MyBSD kernel: cpuid = 0 > Jan 29 23:06:57 MyBSD kernel: KDB: stack backtrace: > Jan 29 23:06:57 MyBSD kernel: #0 0xffffffff80963000 at > kdb_backtrace+0x60 > Jan 29 23:06:57 MyBSD kernel: #1 0xffffffff80928125 at panic+0x155 > Jan 29 23:06:57 MyBSD kernel: #2 0xffffffff80d24f1f at trap_fatal+0x38f > Jan 29 23:06:57 MyBSD kernel: #3 0xffffffff80d25238 at > trap_pfault+0x308 > Jan 29 23:06:57 MyBSD kernel: #4 0xffffffff80d2489a at trap+0x47a > Jan 29 23:06:57 MyBSD kernel: #5 0xffffffff80d0a782 at calltrap+0x8 > Jan 29 23:06:57 MyBSD kernel: #6 0xffffffff80d96ed5 at > vesa_bios_save_restore+0x95 > Jan 29 23:06:57 MyBSD kernel: #7 0xffffffff80e02296 at vga_suspend+0xa6 > Jan 29 23:06:57 MyBSD kernel: #8 0xffffffff80e0258d at > isavga_suspend+0x1d > Jan 29 23:06:57 MyBSD kernel: #9 0xffffffff8095b204 at > bus_generic_suspend+0x64 > Jan 29 23:06:57 MyBSD kernel: #10 0xffffffff8095b204 at > bus_generic_suspend+0x64 > Jan 29 23:06:57 MyBSD kernel: #11 0xffffffff8095b204 at > bus_generic_suspend+0x64 > Jan 29 23:06:57 MyBSD kernel: #12 0xffffffff8067e97d at > pci_suspend+0x5d > Jan 29 23:06:57 MyBSD kernel: #13 0xffffffff8095b204 at > bus_generic_suspend+0x64 > Jan 29 23:06:57 MyBSD kernel: #14 0xffffffff8095b204 at > bus_generic_suspend+0x64 > Jan 29 23:06:57 MyBSD kernel: #15 0xffffffff8035bc7f at > acpi_suspend+0xf > Jan 29 23:06:57 MyBSD kernel: #16 0xffffffff8095b204 at > bus_generic_suspend+0x64 > Jan 29 23:06:57 MyBSD kernel: #17 0xffffffff8095b204 at > bus_generic_suspend+0x64 > Jan 29 23:06:57 MyBSD kernel: Uptime: 1m7s > > > A frequent recommendation I see is to remove VESA support from your > kernel, apparently it has suspend/resume issues. I don't think > FreeBSD-10.1 uses the KMS graphics drivers by default, and I /thought/ > the recommendation was for KMS systems. Shouldn't hurt to build a > kernel without 'options VESA' and see what happens... > > Anthony My experience is the opposite. With KMS I could run with VESA and without it I needed to pull VESA from my kernel. As of today I am running fine with KMS, i915, and vt(4) with a standard GENERIC 10-STABLE kernel. I was running KMS and vt(4) well before they were MFCed, so I don't remember when I stopped adding "nooptions VESA", but I definitely used to need it to make suspect/resume work and don't any longer. In any case, trying kernel without VESA is a good idea. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com