From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 11 17:40:10 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4393E971 for ; Fri, 11 Jul 2014 17:40:10 +0000 (UTC) Received: from nm4-vm2.access.bullet.mail.gq1.yahoo.com (nm4-vm2.access.bullet.mail.gq1.yahoo.com [216.39.63.32]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 024202334 for ; Fri, 11 Jul 2014 17:40:09 +0000 (UTC) Received: from [216.39.60.172] by nm4.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Jul 2014 17:37:18 -0000 Received: from [67.195.23.148] by tm8.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Jul 2014 17:37:18 -0000 Received: from [127.0.0.1] by smtp120.sbc.mail.gq1.yahoo.com with NNFMP; 11 Jul 2014 17:37:18 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1405100238; bh=kKiXr4LnXnMABzVyhq8KZnNlCMNwMGTJCBLQv0LEGgg=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=eleIsgaJnTOTDWcxb3akUl8Phy2IuqnqOjugiLa6CC25gOQEGsOHxlv7nurBaRe3ejlCsf8Esu26vcWcTdOCQWnpDXIvZ+9f1y9Z6A8pdjzpDM4T3nucBaHZ71e85fIn+Lg4JGe/wkLh10CzDS/Dqn0h4fj1Z7rJKO7okZU13Aw= X-Yahoo-Newman-Id: 692934.44482.bm@smtp120.sbc.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: nv30bqAVM1mmiK11UgqNO3yrTLWv3cUON1bkZL.VFtNwtQS q6d2Bal6XkbMYhb7djJrFAibuMCVktT_MSl2LSYoCNDutuqFo3hPCweJrS5h ASnTRDGlnUingLFIOC364kQqtJdM.zom0yot00Fp5.urNSEg5tbsI0PAaJQm OFMMDX97fcvFoeaJo2QwhEt3I0Zv2eVv7laTNKnQVOkE_VCqWoK0PUSgnM2L RkKXKgRqtIj67vlXkYIpPpZri2uQ_wR4hLgE0qJsH4ocuzNx4XcgAmzW9N_v iXLIbVtebXWuXrHBZmNvEC8XCo3kkty.gzBR.rN2e65K2AXgZtXenbAas6PB Bya_pc28tQPuy0z6LJTJLodw7NW7RHvM4vKiAGAz0zfYAYthdJGKBgn57uHo _kwbuEwqeYcQR0.9GmgbZq1I7t_Yv9Nu1MRKAoVSt7KBNL6UYlVWfJcQJDsz dU9h8kiYy6TJ4BcnyRw3cBg9PVvw7Nw5Fp1hDKaTtC9VeF8Vsq9GythbVETr zdxJiIBCV5xtahBzxKGDY1eB5obuGz6bM2X_5HuQAZVYqGbWCK8_v1Eq_2f9 nWNu8UlyJYpgyl7LjPP0iNoSJTPcHnPdacszAMBF0hAJ7fdcxJ_lOI8jT X-Yahoo-SMTP: OKD1keCswBBTAmAF1s00hLyKW3wE3YfSK0Eazl6b4VZG4LTqJxg- X-Rocket-Received: from [64.100.76.103] (Anthony.B.Jenkins@64.100.76.103 with plain [67.195.15.5]) by smtp120.sbc.mail.gq1.yahoo.com with SMTP; 11 Jul 2014 17:37:18 +0000 UTC Message-ID: <53C020CE.8010205@att.net> Date: Fri, 11 Jul 2014 13:37:18 -0400 From: Anthony Jenkins User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Daniele Mazzotti , takawata@init-main.com Subject: Re: ACPI support - Freebsd 10 on Sony Vaio VPCCA3C5E References: <53BF0546.70505@att.net> <53BFCBF4.2090104@att.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2014 17:40:10 -0000 I just tried a build of GENERIC + 'options ACPI_DEBUG' and it seems to get past the error you're seeing. What revision of the source code are you using... or where'd you get it from? Anthony On 07/11/2014 13:12, Daniele Mazzotti wrote: > Hi guys, > > everything as planned! I am getting a compiling error :-). > > This is the way i managed to update the GENERIC kernel > > # Bus support. > device acpi > options ACPI_DEBUG # Debug support for ACPI > device pci > > and this is the result of > > # *make buildkernel KERNCONF=MYKERNEL* > > > ===> crypto (depend) > @ -> /usr/src/sys > awk -f @/tools/makeobjops.awk @/opencrypto/cryptodev_if.m -c > > make[4]: stopped in /usr/src/sys/modules/crypto > *** Error code 2 > > Stop. > make[3]: stopped in /usr/src/sys/modules > *** Error code 1 > > Stop. > make[2]: stopped in /usr/obj/usr/src/sys/GENERIC > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > I googled a bit, but I could not find any valuable help and actually I do > not know what could be wrong as the custom kernel is essentially the > GENERIC with just one line added. > Have you ever experienced such a problem? > > Cheers, > Daniele. > > > > 2014-07-11 18:10 GMT+02:00 Daniele Mazzotti : > >> Hi guys, >> >> thanks again for the support. >> >> @Takanori: here you go http://pastebin.com/F0a2mZP4 >> @Anthony: I will try to include the options in a custom kernel and compile >> it. As this is the first time after years I am compiling a custom kernel it >> will take a few time I guess. >> >> Just let me know if the output of the acpidump is of any help to you. >> Cheers, >> Daniele. >> >> >> 2014-07-11 13:35 GMT+02:00 Anthony Jenkins : >> >> Hi Daniele, >>> I was just going from acpi(4) man page; you'll likely have to build a new >>> kernel with 'options ACPI_DEBUG' added to your kernel config file, as I >>> don't know if it's even possible to turn on the logging I want at runtime. >>> >>> [ajenkins@ajenkins-hplaptop /usr/home/ajenkins]$ grep -i acpi >>> /usr/src/sys/amd64/conf/MYKERNEL >>> device acpi >>> options ACPI_DEBUG >>> >>> I also have an 'options ACPI_DMAR' , but I don't recognize that and you >>> don't need that to debug your battery. >>> >>> Anthony >>> >>> On 07/11/2014 01:58, Daniele Mazzotti wrote: >>>> Hello Anthony, >>>> >>>> thanks for the quick reply! I tried what you suggested. >>>> >>>> loader.conf: >>>> >>>> # Module for Windows Partition & Linux Mount >>>> fuse_load="YES" >>>> autoboot_delay="5" >>>> #acpi_sony_load="YES" >>>> >>>> # Debugging Symbols for ACPI >>>> debug.acpi.layer="ACPI_BATTERY" >>>> debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" >>>> debug.acpi.enable_debug_objects="1" >>>> >>>> sysctl hw.acpi.battery: >>>> >>>> hw.acpi.battery.life: -1 >>>> hw.acpi.battery.time: -1 >>>> hw.acpi.battery.state: 7 >>>> hw.acpi.battery.units: 1 >>>> hw.acpi.battery.info_expire: 5 >>>> >>>> log/messages: >>>> >>>> cat /var/log/messages | grep acpi >>>> >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi0: on motherboard >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_ec0: >>> 0x17, ECDT> port 0x62,0x66 on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: cpu0: on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: cpu1: on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: cpu2: on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: cpu3: on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: hpet0: >>>> iomem 0xfed00000-0xfed003ff on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: atrtc0: port >>>> 0x70-0x77 irq 8 on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: attimer0: port >>>> 0x40-0x43,0x50-0x53 irq 0 on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_timer0: <24-bit timer at >>>> 3.579545MHz> port 0x408-0x40b on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: pcib0: port >>>> 0xcf8-0xcff on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: battery0: >> Battery> >>>> on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_acad0: on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_lid0: >> Switch> >>>> on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_button0: on >>> acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_tz0: on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_tz1: on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: atkbdc0: >> (i8042)> >>>> port 0x60,0x64 irq 1 on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_sony0: >> controller> >>>> on acpi0 >>>> Jul 11 07:30:47 Von-Neumann kernel: acpi_sony0: PID 0 >>>> Jul 11 07:37:54 Von-Neumann kernel: acpi0: on motherboard >>>> Jul 11 07:37:54 Von-Neumann kernel: acpi_ec0: >>> 0x17, ECDT> port 0x62,0x66 on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: cpu0: on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: cpu1: on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: cpu2: on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: cpu3: on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: hpet0: >>>> iomem 0xfed00000-0xfed003ff on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: atrtc0: port >>>> 0x70-0x77 irq 8 on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: attimer0: port >>>> 0x40-0x43,0x50-0x53 irq 0 on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: acpi_timer0: <24-bit timer at >>>> 3.579545MHz> port 0x408-0x40b on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: pcib0: port >>>> 0xcf8-0xcff on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: battery0: >> Battery> >>>> on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: acpi_acad0: on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: acpi_lid0: >> Switch> >>>> on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: acpi_button0: on >>> acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: acpi_tz0: on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: acpi_tz1: on acpi0 >>>> Jul 11 07:37:54 Von-Neumann kernel: atkbdc0: >> (i8042)> >>>> port 0x60,0x64 irq 1 on acpi0 >>>> >>>> It seems to me the verbose debugging is either not enabled (perhaps I >>> made >>>> some mistakes with the loader.conf) or the debug is really enabled but >>>> there is no special output on the wrong log file. Actually I am a bit >>>> puzzled as I am not a real expert "admin". I only enjoy getting my >>> hands on >>>> Unix on my desktop PC just for fun. >>>> >>>> However, do you think either I missed something or made anything wrong? >>>> I look forward to receiving from you. >>>> >>>> Cheers, >>>> Daniele. >>>> >>>> >>>> >>>> 2014-07-10 23:27 GMT+02:00 Anthony Jenkins : >>>> >>>>> On 07/10/2014 16:49, Daniele Mazzotti wrote: >>>>>> Hello there, >>>>>> >>>>>> it is been a while since I finished installing Freebsd 10 on my Sony >>> Vaio >>>>>> PC and resolving (or at least I am trying to) one by one, all the >>>>> problems >>>>>> this hardware is giving me. Actually I cannot find a solution to >>>>> correctly >>>>>> display the battery level on my laptop. If I unplug my PC from the >>> power >>>>>> and type 'sysctl hw.acpi.battery' this is the result I get: >>>>>> >>>>>> hw.acpi.battery.life: -1 >>>>>> hw.acpi.battery.time: -1 >>>>>> hw.acpi.battery.state: 7 >>>>>> hw.acpi.battery.units: 1 >>>>>> hw.acpi.battery.info_expire: 5 >>>>>> >>>>>> Moreover the suspend mode is giving me some problems as well, but this >>>>> has >>>>>> definitely a lower priority. >>>>>> >>>>>> I either tried to search for a solution on the FreeBSD Handook with no >>>>>> luck, and google the problem a little bit, but I could not find any >>>>>> valuable help. I would be really interested to investigate the problem >>>>>> further. Is there anyone who can help me out with this and tell me >>> what >>>>>> pieces of information are needed to better understand the problem? >>>>> Try enabling the ACPI_BATTERY layer and ACPI_LV_ALL_EXCEPTIONS level in >>>>> /boot/loader.conf: >>>>> >>>>> debug.acpi.layer="ACPI_BATTERY" >>>>> debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" >>>>> debug.acpi.enable_debug_objects="1" # I assume this is how >>> you >>>>> turn on ACPI debugging without recompiling the kernel with 'options >>>>> ACPI_DEBUG' >>>>> >>>>> and running 'sysctl hw.acpi.battery' again. Post /var/log/messages >>> ACPI >>>>> messages about battery here. >>>>> >>>>> Anthony >>>>> >>>>>> Cheers, >>>>>> Daniele. >>>>>> _______________________________________________ >>>>>> freebsd-acpi@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >>>>>> To unsubscribe, send any mail to " >>> freebsd-acpi-unsubscribe@freebsd.org" >>>> _______________________________________________ >>>> freebsd-acpi@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >>>> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" >>>> >>> > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" >