Date: Tue, 15 Jul 2014 20:47:44 +0200 From: Daniele Mazzotti <kappei84@gmail.com> To: Ian Smith <smithi@nimnet.asn.au> Cc: Anthony Jenkins <Anthony.B.Jenkins@att.net>, freebsd-acpi@freebsd.org Subject: Re: ACPI support - Freebsd 10 on Sony Vaio VPCCA3C5E Message-ID: <CAC=ypSXYxpuqw9KA-OZRNJ=R50Cw9RoJtzp_bsqfG7pKvXYvmQ@mail.gmail.com> In-Reply-To: <20140716040719.Y50382@sola.nimnet.asn.au> References: <CAC=ypSVopgcL82FpqJosmgFeRkeeevP0RG-GrAEZD2YQyi%2BPrg@mail.gmail.com> <53BF0546.70505@att.net> <CAC=ypSUe0_09pTMFsMKw4u3J=Kb8Q_uV0g6%2Bk_f2p1so3mnTgA@mail.gmail.com> <53BFCBF4.2090104@att.net> <CAC=ypSULmXU2HBpG2gf2J=9_o-sLccECud%2Be9KUg6-ppz7phww@mail.gmail.com> <CAC=ypSV36Dk_3a30OeCxmowqnM5iqcJkM%2B4qKgsOTNTEzmztSQ@mail.gmail.com> <53C020CE.8010205@att.net> <CAC=ypSV_qQ-EsfwJAa6NRiZhTvOi-xh9A=oFKXzNMj9GTpHbOA@mail.gmail.com> <53C02604.9070207@att.net> <CAC=ypSV=yXjnNYJTMSU3tDTjez9NAe3PqsDPRiF5sf2D6FBxRA@mail.gmail.com> <CAC=ypSVbiOpTxUZeJnQUTMdjtbicu2JdG5p5g9%2BgR%2BS72-6RVg@mail.gmail.com> <CAC=ypSU3J3cPuEqDhrwAGm3MyNNGCc39W_4kTLJFbsYWjV5HoQ@mail.gmail.com> <53C3D322.3080302@att.net> <CAC=ypSXA8MZzT0V1RxhxyXd88Xk8od_6zmjn%2B9rd4W%2BtVgyvXQ@mail.gmail.com> <CAC=ypSUqHF%2B2_ajsjU5x3=if01twAtmsPcmQGBgNC=VEAdOKnQ@mail.gmail.com> <20140716040719.Y50382@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Ian, I have just rebooted the PC after turning the deep debug on. Here is the output: http://pastebin.com/H61zJhqc. It is very likely that the dmesg has been cut due to the large amount of output. Is there any way to have it all? Cheers, Daniele. 2014-07-15 20:22 GMT+02:00 Ian Smith <smithi@nimnet.asn.au>: > On Tue, 15 Jul 2014 19:49:46 +0200, Daniele Mazzotti wrote: > > > I made a few step ahead (at least on my side) and tried to follow the > > recommendation from the handbook ( > > http://www.pl.freebsd.org/doc/handbook/acpi-debug.html). > > > > I was able to turn on the verbose boot and here you can find the output: > > http://pastebin.com/kkDAZEVb. At boot time I can see an error stating > > "battery0: battery initialization failed, giving up" which is thrown by > the > > acpi_cmbat_init_battery within acpi_cmbat.c module. After six retries > the > > error is printed out. Actually I am not able to figure out who is > calling > > the method, but that is another story. > > Actually you'll see those messages on a 'normal' verbose boot, ie > there's nothing extra logged of note regarding battery issues. If you > are up for lots more output on one boot at least, perhaps try what > acpi(4) suggests: > > debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS" > debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" > > which is less deep, but wider :) Communications with batteries often, > likely usually, is moderated by the embedded controler (ACPI_EC) and it > wouldn't hurt to report any exceptions from other subsystems also. If > that yields nothing useful you could increase the level .. > > Sorry, I can't read messages backwards very well, so I'll drop the tail. > > cheers, Ian >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC=ypSXYxpuqw9KA-OZRNJ=R50Cw9RoJtzp_bsqfG7pKvXYvmQ>