Date: Thu, 08 Sep 2005 16:07:26 -0700 From: Nate Lawson <nate@root.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: cvs-src@freebsd.org, glebius@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/pccbb pccbb.c Message-ID: <4320C42E.8020900@root.org> In-Reply-To: <20050908.160715.127179498.imp@bsdimp.com> References: <20050908194607.GL53891@cell.sick.ru> <20050908.140057.84363209.imp@bsdimp.com> <4320ABA9.9010802@root.org> <20050908.160715.127179498.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh wrote: > In message: <4320ABA9.9010802@root.org> > Nate Lawson <nate@root.org> writes: > : BTW, there have been very few suspend/resume problems attributable to > : our ACPI or APM code. Almost all are in individual device drivers > : (especially video) or bus (PCI until it got config register save support > : although type 2 device support is still incomplete I think). > > Type 2 device support is handled by cbb, and is complete as far as I > can tell. I think I meant type 1, bridges. > : Currently, > : many systems hang if APIC support is included in the kernel but work > : without it. The rest of the bugs are usually individual BIOS problems > : that are difficult to track without a bus analyzer. > > Yes. I believe that I suspend correctly, but when I resume, the power > light comes back on and nothing else happens. Placing a beep in the > first line of the resume path results in no beep happening, which > suggests suspend didn't suspend quite correctly. This happens even > when all I have in my configured device list is ata. :-( I'm somewhat > frustrated by this turn of events, as you can well imagine :-). Try removing device apic. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4320C42E.8020900>