Date: Tue, 14 Jun 2005 16:21:30 -0400 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-acpi@freebsd.org Subject: Re: cvs commit: src/sys/dev/acpica acpi.c Message-ID: <200506141621.32011.jhb@FreeBSD.org> In-Reply-To: <42AD849E.8030908@centtech.com> References: <200506032012.j53KCC5k077879@repoman.freebsd.org> <42AD83ED.8070703@centtech.com> <42AD849E.8030908@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 13 June 2005 09:05 am, Eric Anderson wrote: > Eric Anderson wrote: > > Eric Anderson wrote: > >> Eric Anderson wrote: > > > > [..snip..] > > > >>> Awesome!! Now does anyone have any hints on how I can start looking > >>> at why it powers off instead of resumes? Screen is blank the whole > >>> time so it's hard to tell whats happening. > >> > >> Of course, as soon as I send this email, it *STOPS* working. I cannot > >> figure this out - it successfully went into suspend, and now I can't > >> get it to go into it. I haven't recompiled anything, haven't changed > >> any settings, nothing. > >> > >> I'm so lost.. Does anyone have any hints, clues, etc? I have a spare > >> D610 now to experiment on - I'm open to suggestions.. > > > > Ok - I've narrowed it down. A GENERIC kernel will go into S3 just fine > > on this laptop. Removing apic from the kernel will break that. > > > > I've also run into some bugs with having smp in the kernel and certain > > modules, so beware. > > > > Now, I can successfully go into S3, but coming back out (using the lid > > switch button or the power button are the only ways I know of) seems to > > reboot the machine. Maybe I should say that I can't tell if it's > > rebooting the machine, or if the machine just 'powers up' as if it was > > off. > > > > How do I go about debugging from here? > > Oh - and here's what it looks like when it goes to sleep: > > acpi_lid0: Lid closed > acpi_lid0: wake_prep enabled for \_SB_.LID_ (S3) > acpi_button0: wake_prep enabled for \_SB_.PBTN (S3) > uhci0: wake_prep disabled wake for \_SB_.PCI0.USB0 (S3) > uhci1: wake_prep disabled wake for \_SB_.PCI0.USB1 (S3) > uhci2: wake_prep disabled wake for \_SB_.PCI0.USB2 (S3) > uhci3: wake_prep disabled wake for \_SB_.PCI0.USB4 (S3) > ehci0: wake_prep disabled wake for \_SB_.PCI0.USB3 (S3) > pci2:0:0: Transition from D0 to D3 > vga0: saving 68 bytes of video state > pci0:31:2: Transition from D0 to D3 > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ioapic_suspend: not implemented! > ======== acpi_printcpu() debug dump ======== > gdt[0097:c09c7380] idt[07ff:c09c7ea0] ldt[0050] tr[0048] efl[00080086] > eax[00000001] ebx[c23ccc80] ecx[00000001] edx[00000004] > esi[00000003] edi[00000000] ebp[e3618c5c] esp[e3618c40] > cr0[8005003b] cr2[2813d704] cr3[00c1e000] cr4[00000691] > cs[0020] ds[0028] es[0028] fs[0008] gs[003b] ss[0028] Does it actually resume ok? If so, I can probably shut up the ioapic_suspend printfs. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506141621.32011.jhb>