login
Search
Hope double post is ok, have issue with -CURRENT and ACPI. Kernel is ~week old cvsup -CURRENT amd64, issue has occurred with all versions of freebsd amd64 tried, however. Upon entering S3 sleep (or S4), the laptop emits 3 loud beeps and the sleep indicator begins flashing faster than normal. Older -CURRENT kernels also result in spinning fans at this point, which no longer occurs. Device will remain in this state indefinitely. Device must be powered off using the ten second rule. Occurs with custom kernel as well as GENERIC. Last entry is /var/log/messages is: Aug 23 17:59:09 ono-sendai acpi: suspend at 20100823 17:59:09 Please note atrtc0 error in dmesg? Can provide KERNCONF or other files as needed. Thank you all! I have been using various *bsd since I was 15 (~decade), can't tell you how grateful I am for your work, I hope to be able to help more soon! ACPI dump: http://pastebin.com/buQktjnq Dmesg: Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #2: Sun Aug 15 23:33:22 PDT 2010 root@ono-sendai.local:/usr/obj/usr/src/sys/ONOSENDAI amd64 CPU: Intel(R) Core(TM)2 Duo CPU T6570 @ 2.10GHz (2094.80-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x408e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE> AMD Features=0x20100800<SYSCALL,NX,LM> AMD Features2=0x1<LAHF> TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 3927597056 (3745 MB) Event timer "LAPIC" frequency 0 Hz quality 500 ACPI APIC Table: <LENOVO TP-6J > FreeBSD/SMP: Multiprocessor System Detected: 2 ...
I get this on a Toshiba A105 but it doesn't seem to hurt anything, imb _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Success! After setting every possible suspend/resume sysctl, "sysctl hw.pci.do_power_resume=0" allowed suspend and resume. Still beeps 1-3 times before suspend, with rapid sleep light flashing until suspend complete. Kernel conf is attached. World built from last Friday's CVS, -CURRENT acpiconf -s3 works perfectly from console previously opened windows are garbled until refresh in X acpiconf -s4 causes shutdown, does not resume on power on. Swap is 2x RAM. VMstat -i rate is 540. Thank you FreeBSD! Matt
On Thu, 30 Sep 2010, Matt wrote: > Success! > > After setting every possible suspend/resume sysctl, > "sysctl hw.pci.do_power_resume=0" > allowed suspend and resume. Still beeps 1-3 times before suspend, with rapid > sleep light flashing until suspend complete. Interesting; $someone may document do_power_resume a bit more $someday? > Kernel conf is attached. > World built from last Friday's CVS, -CURRENT > > acpiconf -s3 works perfectly from console > previously opened windows are garbled until refresh in X Some thinkpads have responded positively in this regard to setting hw.syscons.sc_no_suspend_vtswitch=1 > acpiconf -s4 causes shutdown, does not resume on power on. Suspend To Disk is not expected to work; your laptop (like most) has no BIOS support for S4, as per your hw.acpi.s4bios: 0 cheers, Ian > Swap is 2x RAM. > > VMstat -i rate is 540. > > Thank you FreeBSD! > > Matt _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Suspend to disk does not work because FreeBSD does not support it. (s4bios is irrelevant here) _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
My experience with a sleeping freebsd laptop has been shortlived! Today I rebuilt world using clang & this morning's csup current. Clang build went just swimmingly. Unthinkingly, I closed my laptop lid and put it in my case. When I got to my house, it was roasting with fans spinning and sleep light flashing. No damage, thankfully. Low and behold, hw.pci.do_power_resume=0 no longer lets my laptop sleep! I had recently fiddled with powerd, but problem persisted after reverting to previous configuration of associated sysctls etc. Interestingly, sleep bounce now fails with a hard freeze, which it never has in the past. Verbose output shows the wifi then re0 network interfaces going from D0->D3 as last living output. Please note problem persists regardless of user, X running, sleep_delay sysctl, do_power_resume, do_power_nodriver, powerd running/not running. Without sleep bounce, problem is characterized by flashing sleep light and spinning fans (CPU temperature is high). No devices added or removed, was sleeping this morning before buildworld. Is it worth rebuilding with gcc? Or a content change and not a compiler issue? Any major pci changes lately maybe? Matt sendtomatt@gmail.com Not sure where to go from here... If it is helpful, I can provide any required logs, verbose dmesg etc. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
On Tue, 19 Oct 2010 18:15:54 -0700 Did you _not_ have this problem when compiling with the base C compiler (gcc)? Not really clear from your description. -- Gary Jennejohn _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
It wasn't particularly clear to me at the time of posting. I subsequently compiled generic with both gcc and clang and issue persists, ruling out clang as source of issue. A diff of dmesg output from before csup buildworld and after did not reveal any startling differences. Booting from kernel.prev allowed it to sleep again, so it seems something changed in cvs. Matt _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Can you please update source and try again? If it does not work, please set a new tunable "hw.pci.do_power_suspend=0" and tell me whether it helps or not. FYI, hw.pci.do_power_resume does not apply to suspend any more. So, if you want to restore the previous behaviour, you need both "hw.pci.do_power_resume=0" and "hw.pci.do_power_suspend=0". However, my hunch tells me that you only need the latter. Also, if possible, I'd like to see 'devinfo -rv', 'pciconf -clv', 'acpidump -dt', and 'lspci -vvv' output. Note lspci is available via ports/sysutils/pciutils. Thanks, Jung-uk Kim _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Wow, i mounted my phone last nite and nothing that bad happened. Is there any other messages in /var/log/messages?? hbca# dmesg | grep da rum0: need multicast update callback da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 scbus0 target 0 lun 1 da1: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry (da1:umass-sim0:0:0:1): lost device (da1:umass-sim0:0:0:1): removing device entry da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 scbus0 target 0 lun 1 da1: <HTC Android Phone 0100> Removable Direct Access SCSI-2 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry (da1:umass-sim0:0:0:1): lost device (da1:umass-sim0:0:0:1): removing device entry hbca# _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
A >> dump file of the above commands in order: http://pastebin.com/KhFn9xaK I'm grabbing a new csup now, glad it wasn't clang at least. When I did Mac development, LLVM binaries were generally significantly faster for some things. Interesting, I got some phone related topic added into your post, and no direct mail, so hopefully you can get your hands on the pastebin link. Thank you, I will let you know if the new tunable does the trick. Matt _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Build fails. I will also try gcc, but it seems like it doesn't know
about do_power_suspend yet!
cd /usr/obj/usr/src/sys/ONOSENDAI; MAKEOBJDIRPREFIX=/usr/obj
MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE=nocona
GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin
GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font
GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac
_SHLIBDIRPREFIX=/usr/obj/usr/src/tmp VERSION="FreeBSD 9.0-CURRENT amd64
900023" INSTALL="sh /usr/src/tools/install.sh"
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
make KERNEL=kernel all -DNO_MODULES_OBJ
clang -c -O2 -fno-strict-aliasing -pipe -march=nocona -std=c99 -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
-Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS
-include opt_global.h -fno-omit-frame-pointer -mcmodel=kernel
-mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx
-mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
-fstack-protector /usr/src/sys/dev/pci/pci_pci.c
clang: warning: argument unused during compilation: '-mfpmath=387'
/usr/src/sys/dev/pci/pci_pci.c:450:20: error: use of undeclared identifier
'pci_do_power_suspend'; did you mean 'pci_do_power_resume'?
if (error == 0 && pci_do_power_suspend) {
^~~~~~~~~~~~~~~~~~~~
pci_do_power_resume
In file included from /usr/src/sys/dev/pci/pci_pci.c:51:
/usr/src/sys/dev/pci/pci_private.h:41:13: note: 'pci_do_power_resume'
declared
here
extern int pci_do_power_resume;
^
1 error generated.
*** Error code 1
Stop in ...It seems your sys/dev/pci/pci_private.h is out of sync somehow. It was updated with pci_pci.c in the same commit. Please try csup again. Jung-uk Kim _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
After current cvsup, SL410 sleeps again (with both hw.pci.do_power_suspend and hw.pci.do_power_resume set to 0). Initial toggling indicated that at least would work, I will experiment more. Thank you all for a quick resolution to the problem! Matt _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Commented out code at as though "pci_do_power_suspend" = false, still does not sleep. Tried setting do_power_resume to 1 and 0, same result. debug.acpi.suspend_bounce returns to VT and freezes, nothing logged (was not verbose booted at the time however). _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
I am quite surprised it didn't work for you. Can you please csup again and make sure you have the latest source? Have you ever set debug.acpi.do_powerstate tunable before? Jung-uk Kim _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
