Date: Tue, 27 Feb 2007 00:05:18 -0500 From: drgerlists@gmail.com (Dr. Gary E. RAFE) To: freebsd-acpi@freebsd.org Subject: No ad0 following ACPI Resume on Toshiba Sat Pro 6100/6.2-R ? Message-ID: <45e3bc0e.ysCcBQJVFan8KBpdQmS3zu1U@lmrmac.uhw.utoledo.edu>
next in thread | raw e-mail | index | archive | help
Having yet another look at ACPI Suspend/Resume on my Toshiba Satellite Pro 6100 now running 6.2-R. The system goes into Suspend-to-Ram state OK, but the resume-on-power-switch-actuation fails with a kernel panic. I don't know where to look next at this; hints & suggestions from the experts are welcome. Note that I had the same behavior under 6.1-R, and that APM Suspend/Resume works reliably on this hardware. This looks alot like the problem reported by A. Scherbanov in a recent freebsd-current message <http://lists.freebsd.org/pipermail/freebsd-current/2007-February/069214.html>; dmesg(8) output of a verbose boot session follow: $ acpiconf -s 3 [System enters Suspend-to-RAM state correctly] [Actuate Power button] [Messages issued to console] wi0: detached pci2:8:0: Transition from D0 to D3 vga0: saving 68 bytes of video state ======== acpi_printcpu() debug dump ======== gdt[0097:c0701e60] idt[07ff:c0702340] ldt[0050] tr[0048] efl[00000096] eax[00000001] ebx[c2f24e00] ecx[c2ef67b0] edx[0009e227] esi[00000003] edi[00000000] ebp[d56cfc18] esp[d56cfbfc] cr0[8005003b] cr2[080937b4] cr3[1f433000] cr4[00000691] cs[0020] ds[0028] es[0028] fs[0008] gs[001b] ss[0028] ======== acpi_printcpu() debug dump ======== gdt[0097:c0701e60] idt[07ff:c0702340] ldt[0050] tr[0048] efl[00000002] eax[00000046] ebx[c2f24e00] ecx[000000a0] edx[00000001] esi[00000003] edi[00000000] ebp[d56cfc18] esp[d56cfbfc] cr0[8005003b] cr2[080937b4] cr3[1f433000] cr4[00000691] cs[0020] ds[0028] es[0028] fs[0008] gs[001b] ss[0028] acpi: suspend request ignored (not ready yet) cbb0: [MPSAFE] cbb1: [MPSAFE] cbb2: [MPSAFE] wakeup from sleeping state (slept 00:01:08) ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=80 ostat1=80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x50 err=0x00 lsb=0xfe msb=0x3f ata0: stat1=0x00 err=0x00 lsb=0xfe msb=0x3f ata0: reset tp2 stat0=50 stat1=00 devices=0x0 subdisk0: detached <== That can't be right ! ad0: detached <== That can't be right ! ata0: reinit done .. ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x04 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4<ATAPI_MASTER> g_vfs_done():ad0s2a[WRITE(offset=10314055680, length=10240)]error = 6 (... message repeated another 9 times here ...) acd0: setting PIO4 on ICH3 chip acd0: setting UDMA33 on ICH3 chip ata1: reinit done .. battery0: battery initialization start battery0: battery initialization done, tried 1 times battery1: battery initialization start atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa g_vfs_done():ad0s2a[READ(offset=10256183296, length=2048)]error = 6 panic: vinvalbuf: dirty bufs Uptime: 58s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. Rebooting... -- Dr Gary E RAFE: drgerlists at gmail dot com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45e3bc0e.ysCcBQJVFan8KBpdQmS3zu1U>