From gaijin.k at gmail.com Thu Jan 1 16:26:29 2009 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Thu Jan 1 16:26:40 2009 Subject: ACPI issues on Averatec 3250 In-Reply-To: <20081230185743.12fd1c3a@avera> References: <20081230185743.12fd1c3a@avera> Message-ID: <1230825713.1182.10.camel@RabbitsDen> On Tue, 2008-12-30 at 18:57 -0500, J.R. Oldroyd wrote: > I have just put 7-stable on an Averatec 3250HX laptop. Three things > connected with ACPI do not work as they should. > [skip] > 2. Thermal Zone > The thermal zone reporting is not working. > From the boot info: > acpi_tz0: on acpi0 > But sysctl info: > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.user_override: 0 > hw.acpi.thermal.tz0.temperature: 0.0C > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.passive_cooling: 1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 90.0C > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 110.0C > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.thermal.tz0._TC1: 2 > hw.acpi.thermal.tz0._TC2: 4 > hw.acpi.thermal.tz0._TSP: 30 > About four years ago I have cobbled together thermal zones for Averatec 3150H. Quick look at you ASL shows that they still adjust fan speed using RTEP() function, which, in turn, gets called from (off all places) _PSV. The trick is to break RTEP() into pieces at different temperature levels, create fan devices and plug them into proper _ACx. I still have modified ASL laying around, but no longer have access to the laptop to make a diff with the original. If you are interested, I can send you ASL off list -- it should not be that hard to follow, especially if you keep thermal chapter of the ACPI spec close at hand (it is about 13 pages long). Let me know. -- Alexandre "Sunny" Kovalenko (????????? ?????????) From gaijin.k at gmail.com Thu Jan 1 17:09:56 2009 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Thu Jan 1 17:10:02 2009 Subject: Problem on AMD64 In-Reply-To: <20081228124345.D51566@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> <20081227160941.I29108@sola.nimnet.asn.au> <1230388519.1270.1.camel@RabbitsDen> <20081228124345.D51566@sola.nimnet.asn.au> Message-ID: <1230829779.1182.17.camel@RabbitsDen> On Sun, 2008-12-28 at 13:20 +1100, Ian Smith wrote: > On Sat, 27 Dec 2008, Alexandre "Sunny" Kovalenko wrote: > > On Sat, 2008-12-27 at 17:13 +1100, Ian Smith wrote: > > > On Fri, 26 Dec 2008, Garrett Cooper wrote: > > > > On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: > > > [..] > > > > >> Look into the following sysctls: > > > > >> > > > > >> hw.acpi.cpu.cx_lowest > > > > >> hw.acpi.cpu.cx_highest > > > > >> > > > > > > > > > > I tried to find out what I can do with those sysctls. > > > > > hw.acpi.cpu.cx_highest is not available on my system. > > > > > > I don't think it exists; C1 state is always available AFAIK. > > > > > > > > hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I > > > > > should set it to C2 or C3??? > > > > > > Give it a try. Setting it to C3 won't hurt, whether it's used or not. > > > Actually it just might (hurt that is). See below for the discussion. > > > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+2482 > > +/usr/local/www/db/text/2008/freebsd-acpi/20081109.freebsd-acpi > > Thanks. Yes that was indeed an interesting discussion. FWIW, I find > that interface awkward, without threading. For me it's easier from: > http://lists.freebsd.org/pipermail/freebsd-acpi/2008-November/005182.html > > Could I then safely say, setting it to C2 won't hurt? It is hard to generalize. I am using: RabbitsDen# sysctl dev.cpu.1.cx_lowest=C3 dev.cpu.1.cx_lowest: C2 -> C3 RabbitsDen# sysctl dev.cpu | grep cx dev.cpu.0.cx_supported: C1/1 C2/1 C3/57 dev.cpu.0.cx_lowest: C2 dev.cpu.0.cx_usage: 0.00% 100.00% 0.00% dev.cpu.1.cx_supported: C1/1 C2/1 C3/57 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 0.00% 30.43% 69.56% without any obvious ill effects. Whether having C3 on one of the cores is makes any difference in power consumption or heat dissipation, I do not know. I also do not know whether there are machines out there which would exhibit odd behavior with C2 set. As usual, YMMV. -- Alexandre "Sunny" Kovalenko (????????? ?????????) From cokane at FreeBSD.org Fri Jan 2 17:06:57 2009 From: cokane at FreeBSD.org (Coleman Kane) Date: Fri Jan 2 17:07:03 2009 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <495A7309.2060400@root.org> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> Message-ID: <1230915992.4841.4.camel@localhost> On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: > Coleman Kane wrote: > > On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: > >> Coleman Kane wrote: > >>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: > >>>> Coleman Kane wrote: > >>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on my HP > >>>>> notebook, and it seems to be very close to working well. > >>>>> > >>>>> The notebook goes into S3 state properly, but when it comes back out it > >>>>> seems that the hardware is left in a bad state. I cannot attach my > >>>>> if_bge and if_ndis network drivers after a resume. > >>>> Dump the pci config register states for those devices both before and > >>>> after the resume. Where the bits differ is probably where you'll find > >>>> the problem. > >>>> > >>>> Example to read 256 bytes: > >>>> pciconf -r pci0:4:0 0:256 > >>>> > >>> Tried that, and I also tried to use pciconf -w to set the registers to > >>> the initial state of the hardware before if_bge is loaded. I still get > >>> the following messages when I attempt to reload the kld after the > >>> resume, followed by a failed attach: > >>> > >>> bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 > >>> bge0: firmware handshake timed out, found 0x4b657654 > >>> bge0: firmware handshake timed out, found 0x4b657654 > >>> bge0: RX CPU self-diagnostics failed! > >>> bge0: chip initialization failed > >>> device_attach: bge0 attach returned 6 > >>> > >>> Anyone have success with S3 on amd64 or i386 with if_bge cards? > >> Did you post the register states before and after? > >> > > Attached are the before and after snapshots of the device's PCI register > > space. I need to track down a good table to mate these with. In this > > case, I didn't unload the driver, as the if_bge driver is supposed to be > > able to properly handle suspend/resume now. > > > > These are dumps of the whole 256-byte register space, using: > > pciconf -r -b pci0:16:0:0 0:0x100 > > Great. So far in FreeBSD, anything after the first 64 bytes is the > driver's responsibility. According to your dump, that is where all the > differences are. > So, my guess is that the bge_suspend and bge_resume methods in the bge driver need some tweaking to support my hardware (the BCM5754/5787) when it comes out of resume... Any pointers on who I might be able to work on this with? -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20090102/4294e9a0/attachment.pgp From yanefbsd at gmail.com Fri Jan 2 19:09:11 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Jan 2 19:09:17 2009 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <1230915992.4841.4.camel@localhost> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> <1230915992.4841.4.camel@localhost> Message-ID: <3533670F-754C-40C8-B76A-0C17333E7569@gmail.com> On Jan 2, 2009, at 9:06, Coleman Kane wrote: > On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: >> Coleman Kane wrote: >>> On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: >>>> Coleman Kane wrote: >>>>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: >>>>>> Coleman Kane wrote: >>>>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on >>>>>>> my HP >>>>>>> notebook, and it seems to be very close to working well. >>>>>>> >>>>>>> The notebook goes into S3 state properly, but when it comes >>>>>>> back out it >>>>>>> seems that the hardware is left in a bad state. I cannot >>>>>>> attach my >>>>>>> if_bge and if_ndis network drivers after a resume. >>>>>> Dump the pci config register states for those devices both >>>>>> before and >>>>>> after the resume. Where the bits differ is probably where >>>>>> you'll find >>>>>> the problem. >>>>>> >>>>>> Example to read 256 bytes: >>>>>> pciconf -r pci0:4:0 0:256 >>>>>> >>>>> Tried that, and I also tried to use pciconf -w to set the >>>>> registers to >>>>> the initial state of the hardware before if_bge is loaded. I >>>>> still get >>>>> the following messages when I attempt to reload the kld after the >>>>> resume, followed by a failed attach: >>>>> >>>>> bge0: mem >>>>> 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 >>>>> bge0: firmware handshake timed out, found 0x4b657654 >>>>> bge0: firmware handshake timed out, found 0x4b657654 >>>>> bge0: RX CPU self-diagnostics failed! >>>>> bge0: chip initialization failed >>>>> device_attach: bge0 attach returned 6 >>>>> >>>>> Anyone have success with S3 on amd64 or i386 with if_bge cards? >>>> Did you post the register states before and after? >>>> >>> Attached are the before and after snapshots of the device's PCI >>> register >>> space. I need to track down a good table to mate these with. In this >>> case, I didn't unload the driver, as the if_bge driver is supposed >>> to be >>> able to properly handle suspend/resume now. >>> >>> These are dumps of the whole 256-byte register space, using: >>> pciconf -r -b pci0:16:0:0 0:0x100 >> >> Great. So far in FreeBSD, anything after the first 64 bytes is the >> driver's responsibility. According to your dump, that is where all >> the >> differences are. >> > > So, my guess is that the bge_suspend and bge_resume methods in the bge > driver need some tweaking to support my hardware (the BCM5754/5787) > when > it comes out of resume... > > Any pointers on who I might be able to work on this with? Dumb observation: driver maintainer? -Garrett From cokane at FreeBSD.org Fri Jan 2 19:23:47 2009 From: cokane at FreeBSD.org (Coleman Kane) Date: Fri Jan 2 19:23:53 2009 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <3533670F-754C-40C8-B76A-0C17333E7569@gmail.com> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> <1230915992.4841.4.camel@localhost> <3533670F-754C-40C8-B76A-0C17333E7569@gmail.com> Message-ID: <1230924212.4841.7.camel@localhost> On Fri, 2009-01-02 at 11:08 -0800, Garrett Cooper wrote: > On Jan 2, 2009, at 9:06, Coleman Kane wrote: > > > On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: > >> Coleman Kane wrote: > >>> On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: > >>>> Coleman Kane wrote: > >>>>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: > >>>>>> Coleman Kane wrote: > >>>>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on > >>>>>>> my HP > >>>>>>> notebook, and it seems to be very close to working well. > >>>>>>> > >>>>>>> The notebook goes into S3 state properly, but when it comes > >>>>>>> back out it > >>>>>>> seems that the hardware is left in a bad state. I cannot > >>>>>>> attach my > >>>>>>> if_bge and if_ndis network drivers after a resume. > >>>>>> Dump the pci config register states for those devices both > >>>>>> before and > >>>>>> after the resume. Where the bits differ is probably where > >>>>>> you'll find > >>>>>> the problem. > >>>>>> > >>>>>> Example to read 256 bytes: > >>>>>> pciconf -r pci0:4:0 0:256 > >>>>>> > >>>>> Tried that, and I also tried to use pciconf -w to set the > >>>>> registers to > >>>>> the initial state of the hardware before if_bge is loaded. I > >>>>> still get > >>>>> the following messages when I attempt to reload the kld after the > >>>>> resume, followed by a failed attach: > >>>>> > >>>>> bge0: mem > >>>>> 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 > >>>>> bge0: firmware handshake timed out, found 0x4b657654 > >>>>> bge0: firmware handshake timed out, found 0x4b657654 > >>>>> bge0: RX CPU self-diagnostics failed! > >>>>> bge0: chip initialization failed > >>>>> device_attach: bge0 attach returned 6 > >>>>> > >>>>> Anyone have success with S3 on amd64 or i386 with if_bge cards? > >>>> Did you post the register states before and after? > >>>> > >>> Attached are the before and after snapshots of the device's PCI > >>> register > >>> space. I need to track down a good table to mate these with. In this > >>> case, I didn't unload the driver, as the if_bge driver is supposed > >>> to be > >>> able to properly handle suspend/resume now. > >>> > >>> These are dumps of the whole 256-byte register space, using: > >>> pciconf -r -b pci0:16:0:0 0:0x100 > >> > >> Great. So far in FreeBSD, anything after the first 64 bytes is the > >> driver's responsibility. According to your dump, that is where all > >> the > >> differences are. > >> > > > > So, my guess is that the bge_suspend and bge_resume methods in the bge > > driver need some tweaking to support my hardware (the BCM5754/5787) > > when > > it comes out of resume... > > > > Any pointers on who I might be able to work on this with? > > Dumb observation: driver maintainer? > -Garrett Yeah, bge isn't listed in MAINTAINERS so I was hoping someone here might know. The original author is wpaul, but marius, jhb, and others have been working on it since then... I'll just ping them and try to find out who's today's contact on bge. -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20090102/cc173f12/attachment.pgp From cokane at FreeBSD.org Fri Jan 2 20:34:39 2009 From: cokane at FreeBSD.org (Coleman Kane) Date: Fri Jan 2 20:34:46 2009 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <1230915992.4841.4.camel@localhost> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> <1230915992.4841.4.camel@localhost> Message-ID: <1230928477.4841.21.camel@localhost> On Fri, 2009-01-02 at 12:06 -0500, Coleman Kane wrote: > On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: > > Coleman Kane wrote: > > > On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: > > >> Coleman Kane wrote: > > >>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: > > >>>> Coleman Kane wrote: > > >>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on my HP > > >>>>> notebook, and it seems to be very close to working well. > > >>>>> > > >>>>> The notebook goes into S3 state properly, but when it comes back out it > > >>>>> seems that the hardware is left in a bad state. I cannot attach my > > >>>>> if_bge and if_ndis network drivers after a resume. > > >>>> Dump the pci config register states for those devices both before and > > >>>> after the resume. Where the bits differ is probably where you'll find > > >>>> the problem. > > >>>> > > >>>> Example to read 256 bytes: > > >>>> pciconf -r pci0:4:0 0:256 > > >>>> > > >>> Tried that, and I also tried to use pciconf -w to set the registers to > > >>> the initial state of the hardware before if_bge is loaded. I still get > > >>> the following messages when I attempt to reload the kld after the > > >>> resume, followed by a failed attach: > > >>> > > >>> bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 > > >>> bge0: firmware handshake timed out, found 0x4b657654 > > >>> bge0: firmware handshake timed out, found 0x4b657654 > > >>> bge0: RX CPU self-diagnostics failed! > > >>> bge0: chip initialization failed > > >>> device_attach: bge0 attach returned 6 > > >>> > > >>> Anyone have success with S3 on amd64 or i386 with if_bge cards? > > >> Did you post the register states before and after? > > >> > > > Attached are the before and after snapshots of the device's PCI register > > > space. I need to track down a good table to mate these with. In this > > > case, I didn't unload the driver, as the if_bge driver is supposed to be > > > able to properly handle suspend/resume now. > > > > > > These are dumps of the whole 256-byte register space, using: > > > pciconf -r -b pci0:16:0:0 0:0x100 > > > > Great. So far in FreeBSD, anything after the first 64 bytes is the > > driver's responsibility. According to your dump, that is where all the > > differences are. > > > > So, my guess is that the bge_suspend and bge_resume methods in the bge > driver need some tweaking to support my hardware (the BCM5754/5787) when > it comes out of resume... > > Any pointers on who I might be able to work on this with? > I did find that one register that does get trashed by the resume is the high-part of the MSI Address Register (0x5C, BGE_PCI_MSI_ADDR_HIGH from sys/dev/bge/if_bgereg.h). Am I correct in assuming that the PCI 2.2 register addresses in the middle of if_bgereg.h correlate to the addresses in these reg dumps? -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20090102/3eceaa1c/attachment.pgp From dvg at tjc.ru Sat Jan 3 17:26:27 2009 From: dvg at tjc.ru (dvg_lab) Date: Sat Jan 3 17:26:34 2009 Subject: ACPI errors on MSI MegaBook PR300 (aka MS1313) Message-ID: <21267094.post@talk.nabble.com> I run amd64 CURRENT from 31 dec 2008, here are errors at boot time Jan 3 13:42:38 dvg-nb kernel: acpi0: on motherboard Jan 3 13:42:38 dvg-nb kernel: acpi0: [ITHREAD] Jan 3 13:42:38 dvg-nb kernel: acpi0: Power Button (fixed) Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [EmbeddedControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: acpi0: reservation of 0, a0000 (3) failed Jan 3 13:42:38 dvg-nb kernel: acpi0: reservation of 100000, bf700000 (3) failed Jan 3 13:42:38 dvg-nb kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Jan 3 13:42:38 dvg-nb kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 Jan 3 13:42:38 dvg-nb kernel: acpi_ec0: port 0x62,0x66 on acpi0 Jan 3 13:42:38 dvg-nb kernel: acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 from time to time acpi sysctl variables looks buggy hw.acpi.acline: 0 hw.acpi.battery.life: 54 hw.acpi.battery.time: 100 hw.acpi.battery.state: 1 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 the 2nd and the 3d params sometimes sets to 0 or -1, I can't get the dependency. I can't configure kdeutils-klaptopdaemon to shutdown the laptop if batt level less then 5%, it shutdowns the laptop when acpi sysctls gets buggy values. -- View this message in context: http://www.nabble.com/ACPI-errors-on-MSI-MegaBook-PR300-%28aka-MS1313%29-tp21267094p21267094.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From invite+a2=690a6 at facebookmail.com Sat Jan 3 18:46:05 2009 From: invite+a2=690a6 at facebookmail.com (Maitri Karuna R) Date: Sat Jan 3 18:46:11 2009 Subject: Check out my Facebook profile Message-ID: <99ed546838f3c5b8aadf77bde8f806ed@localhost.localdomain> Hi Freebsd-acpi, I invited you to join Facebook a while back and wanted to remind you that once you join, we'll be able to connect online, share photos, organize groups and events, and more. Thanks, Maitri To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=1005079607&k=63D2425ZQZYM5BE1Q1VUTV&r From bugmaster at FreeBSD.org Mon Jan 5 11:06:47 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 5 11:07:14 2009 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200901051106.n05B6kPR002684@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [ACPI] sleep broken on IBM/Lenovo T61 [amd64] o kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/89411 acpi [acpi] acpiconf bug o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 f kern/67309 acpi zzz reboot computer (ACPI S3) o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 46 problems total. From andrnils at gmail.com Thu Jan 8 09:51:51 2009 From: andrnils at gmail.com (Andreas Nilsson) Date: Thu Jan 8 09:51:56 2009 Subject: Lenovo t61p suspend/resume Message-ID: Hello, I installed 7.1-realease on my Lenovo Thinkpad t61p and most things works really good. Not suspend to ram, though, which is a must for me. When I do 'acpiconf -s3' from console or X the machine hard locks before going to sleep. Doing it in the console gives no further debuging clues. I've searched a bit but I can't seem to find any information. I've read everything from 'suspend not supported on SMP' to 'works fine'. The install is a i386 because I want nVidias binary drivers. They were however not loaded/used during testing. Suspend works great on GNU/Linux ( Gentoo ) and OpenSolaris, so the machine is capable of suspend. Any ideas what I should try to get this to work? I'm new to FreeBSD, but have been using unix-like OS's for the last for years. Best regards Andreas Nilsson From yanefbsd at gmail.com Thu Jan 8 10:22:30 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Jan 8 10:22:35 2009 Subject: Lenovo t61p suspend/resume In-Reply-To: References: Message-ID: On Jan 8, 2009, at 1:28 AM, Andreas Nilsson wrote: > Hello, > > I installed 7.1-realease on my Lenovo Thinkpad t61p and most things > works > really good. Not suspend to ram, though, which is a must for me. > > When I do 'acpiconf -s3' from console or X the machine hard locks > before > going to sleep. Doing it in the console gives no further debuging > clues. > > I've searched a bit but I can't seem to find any information. I've > read > everything from 'suspend not supported on SMP' to 'works fine'. The > install > is a i386 because I want nVidias binary drivers. They were however not > loaded/used during testing. > > Suspend works great on GNU/Linux ( Gentoo ) and OpenSolaris, so the > machine > is capable of suspend. Any ideas what I should try to get this to > work? > > I'm new to FreeBSD, but have been using unix-like OS's for the last > for > years. > > Best regards > Andreas Nilsson While amd64 suspend is still in alpha stage, I'm not sure what the status was for x86 suspend... I have a T61p as well, and unfortunately not having proper ACPI is holding me back from dumping Windows on my work laptop ;\. I'll defer to someone else that knows more about it than me :). Also, what version did you install (x86 or amd64)? Cheers, -Garrett From andrnils at gmail.com Thu Jan 8 11:17:36 2009 From: andrnils at gmail.com (Andreas Nilsson) Date: Thu Jan 8 11:17:43 2009 Subject: Lenovo t61p suspend/resume Message-ID: On Thu, Jan 8, 2009 at 11:26 AM, Garrett Cooper wrote: > On Jan 8, 2009, at 1:28 AM, Andreas Nilsson wrote: > > Hello, >> >> I installed 7.1-realease on my Lenovo Thinkpad t61p and most things works >> really good. Not suspend to ram, though, which is a must for me. >> >> When I do 'acpiconf -s3' from console or X the machine hard locks before >> going to sleep. Doing it in the console gives no further debuging clues. >> >> I've searched a bit but I can't seem to find any information. I've read >> everything from 'suspend not supported on SMP' to 'works fine'. The >> install >> is a i386 because I want nVidias binary drivers. They were however not >> loaded/used during testing. >> >> Suspend works great on GNU/Linux ( Gentoo ) and OpenSolaris, so the >> machine >> is capable of suspend. Any ideas what I should try to get this to work? >> >> I'm new to FreeBSD, but have been using unix-like OS's for the last for >> years. >> >> Best regards >> Andreas Nilsson >> > > While amd64 suspend is still in alpha stage, I'm not sure what the > status was for x86 suspend... I have a T61p as well, and unfortunately not > having proper ACPI is holding me back from dumping Windows on my work laptop > ;\. I'll defer to someone else that knows more about it than me :). > Also, what version did you install (x86 or amd64)? > Cheers, > -Garrett It is x86 ( i386 ). I seem to recall that some documentation states that if it works on linux it is resonable to expect it to work in FreeBSD... As I'm a student, I can choose whichever OS i prefer ;) I now have Win XP, GNU/Linux and FreeBSD installed. Before FreeBSD I had OpenSolaris. Hope someone can clarify the suspend situation. On a side note, what rpm can you set your fan to? In windows and GNU/Linux I can get it up to 4500+, but not in FreeBSD. Have you succeded with this? /Andreas From takawata at init-main.com Thu Jan 8 11:22:13 2009 From: takawata at init-main.com (Takanori Watanabe) Date: Thu Jan 8 11:22:20 2009 Subject: Lenovo t61p suspend/resume In-Reply-To: Your message of "Thu, 08 Jan 2009 12:17:34 +0100." Message-ID: <200901081120.n08BKDCc035157@sana.init-main.com> In message , "Andrea s Nilsson" さんいわく: >On Thu, Jan 8, 2009 at 11:26 AM, Garrett Cooper wrote: > >> On Jan 8, 2009, at 1:28 AM, Andreas Nilsson wrote: >> >> Hello, >>> >>> I installed 7.1-realease on my Lenovo Thinkpad t61p and most things works >>> really good. Not suspend to ram, though, which is a must for me. >>> >>> When I do 'acpiconf -s3' from console or X the machine hard locks before >>> going to sleep. Doing it in the console gives no further debuging clues. >>> >>> I've searched a bit but I can't seem to find any information. I've read >>> everything from 'suspend not supported on SMP' to 'works fine'. The >>> install >>> is a i386 because I want nVidias binary drivers. They were however not >>> loaded/used during testing. >>> >>> Suspend works great on GNU/Linux ( Gentoo ) and OpenSolaris, so the >>> machine >>> is capable of suspend. Any ideas what I should try to get this to work? >>> >>> I'm new to FreeBSD, but have been using unix-like OS's for the last for >>> years. >>> >>> Best regards >>> Andreas Nilsson >>> >> >> While amd64 suspend is still in alpha stage, I'm not sure what the >> status was for x86 suspend... I have a T61p as well, and unfortunately not >> having proper ACPI is holding me back from dumping Windows on my work laptop >> ;\. I'll defer to someone else that knows more about it than me :). >> Also, what version did you install (x86 or amd64)? >> Cheers, >> -Garrett > > >It is x86 ( i386 ). I seem to recall that some documentation states that if >it works on linux it is resonable to expect it to work in FreeBSD... > >As I'm a student, I can choose whichever OS i prefer ;) I now have Win XP, >GNU/Linux and FreeBSD installed. Before FreeBSD I had OpenSolaris. > >Hope someone can clarify the suspend situation. > >On a side note, what rpm can you set your fan to? In windows and GNU/Linux I >can get it up to 4500+, but not in FreeBSD. Have you succeded with this? > I posted alpha quality patch for SMP suspend/resume on last May, though I don't update it then. http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html From andrnils at gmail.com Thu Jan 8 11:47:41 2009 From: andrnils at gmail.com (Andreas Nilsson) Date: Thu Jan 8 11:47:47 2009 Subject: Lenovo t61p suspend/resume Message-ID: In message >, "Andrea s Nilsson" さんいわく: >*On Thu, Jan 8, 2009 at 11:26 AM, Garrett Cooper > wrote: *>* *>>* On Jan 8, 2009, at 1:28 AM, Andreas Nilsson wrote: *>>* *>>* Hello, *>>>* *>>>* I installed 7.1-realease on my Lenovo Thinkpad t61p and most things works *>>>* really good. Not suspend to ram, though, which is a must for me. *>>>* *>>>* When I do 'acpiconf -s3' from console or X the machine hard locks before *>>>* going to sleep. Doing it in the console gives no further debuging clues. *>>>* *>>>* I've searched a bit but I can't seem to find any information. I've read *>>>* everything from 'suspend not supported on SMP' to 'works fine'. The *>>>* install *>>>* is a i386 because I want nVidias binary drivers. They were however not *>>>* loaded/used during testing. *>>>* *>>>* Suspend works great on GNU/Linux ( Gentoo ) and OpenSolaris, so the *>>>* machine *>>>* is capable of suspend. Any ideas what I should try to get this to work? *>>>* *>>>* I'm new to FreeBSD, but have been using unix-like OS's for the last for *>>>* years. *>>>* *>>>* Best regards *>>>* Andreas Nilsson *>>>* *>>* *>>* While amd64 suspend is still in alpha stage, I'm not sure what the *>>* status was for x86 suspend... I have a T61p as well, and unfortunately not *>>* having proper ACPI is holding me back from dumping Windows on my work laptop *>>* ;\. I'll defer to someone else that knows more about it than me :). *>>* Also, what version did you install (x86 or amd64)? *>>* Cheers, *>>* -Garrett *>* *>* *>*It is x86 ( i386 ). I seem to recall that some documentation states that if *>*it works on linux it is resonable to expect it to work in FreeBSD... *>* *>*As I'm a student, I can choose whichever OS i prefer ;) I now have Win XP, *>*GNU/Linux and FreeBSD installed. Before FreeBSD I had OpenSolaris. *>* *>*Hope someone can clarify the suspend situation. *>* *>*On a side note, what rpm can you set your fan to? In windows and GNU/Linux I *>*can get it up to 4500+, but not in FreeBSD. Have you succeded with this? *>* * I posted alpha quality patch for SMP suspend/resume on last May, though I don't update it then. http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html Ok, thanks. I'll have a look at them. I guess I was hoping that this would be available as a 'standard' feature. >From the posts in the above list it seems possible that 8.x will have suspend for SMP. /Andreas From glavoie at gmail.com Fri Jan 9 00:20:35 2009 From: glavoie at gmail.com (Gabriel Lavoie) Date: Fri Jan 9 00:20:42 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 Message-ID: Hello, I recently built a small home server using an Inten 45nm E5200 @ 2.5 GHz. With FreeBSD 7.0, the "est" driver had problems pooling for the CPU frequency/voltage pairs and automatically disabled itself. It left the CPU at the frequency the BIOS put it after startup, 1.25 GHz because I have EIST enabled. I had to manually change the frequency or use powerd to put it at maximum. Now I upgraded to FreeBSD 7.1 and everything in my systems seems supported correctly. The est driver now recognize the CPU and load the correct information. Also, after bootup, the frequency of the CPU is at max (2.5 GHz). What I would like is to get the behaviour of EIST found under Windows and Linux where the CPU is automatically downclocked to 1.25 GHz when the system isn't under any load, but comes back to 2.5 GHz as soon as there is some load. I also get this behaviour under Linux on my Core 2 Duo and I really like it. What I found interesting is that it seems the Intel 45nm CPUs use under 5W of power when they are idle and EIST downclocked them. I would really like to take profit of this low power consumption. I found about "estctrl" on this page http://www.daemonology.net/freebsd-est/ but it seems outdated and when I try to build the port, it tells me that it is only supported on the i386 architecture. Why not amd64? Thanks Gabriel -- Gabriel Lavoie glavoie@gmail.com From yanefbsd at gmail.com Fri Jan 9 05:51:09 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Jan 9 05:51:14 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: References: Message-ID: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> On Thu, Jan 8, 2009 at 3:51 PM, Gabriel Lavoie wrote: > Hello, > I recently built a small home server using an Inten 45nm E5200 @ > 2.5 GHz. With FreeBSD 7.0, the "est" driver had problems pooling for > the CPU frequency/voltage pairs and automatically disabled itself. It > left the CPU at the frequency the BIOS put it after startup, 1.25 GHz > because I have EIST enabled. I had to manually change the frequency or > use powerd to put it at maximum. Now I upgraded to FreeBSD 7.1 and > everything in my systems seems supported correctly. The est driver now > recognize the CPU and load the correct information. Also, after > bootup, the frequency of the CPU is at max (2.5 GHz). What I would > like is to get the behaviour of EIST found under Windows and Linux > where the CPU is automatically downclocked to 1.25 GHz when the system > isn't under any load, but comes back to 2.5 GHz as soon as there is > some load. I also get this behaviour under Linux on my Core 2 Duo and > I really like it. What I found interesting is that it seems the Intel > 45nm CPUs use under 5W of power when they are idle and EIST > downclocked them. I would really like to take profit of this low power > consumption. I found about "estctrl" on this page > http://www.daemonology.net/freebsd-est/ but it seems outdated and when > I try to build the port, it tells me that it is only supported on the > i386 architecture. Why not amd64? > > Thanks > > Gabriel > > -- > Gabriel Lavoie > glavoie@gmail.com Maybe this comment says why (from .../sys/i386/cpufreq/est.c)? /* * Frequency (MHz) and voltage (mV) settings. Data from the * Intel Pentium M Processor Datasheet (Order Number 252612), Table 5. * * Dothan processors have multiple VID#s with different settings for * each VID#. Since we can't uniquely identify this info * without undisclosed methods from Intel, we can't support newer * processors with this table method. If ACPI Px states are supported, * we get info from them. */ Colin could give you the definite answer, but I'm pretty sure that's it... Cheers, -Garrett From mav at mavhome.dp.ua Fri Jan 9 09:51:33 2009 From: mav at mavhome.dp.ua (Alexander Motin) Date: Fri Jan 9 09:51:40 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <1231471393.00057821.1231461001@10.7.7.3> References: <1231471393.00057821.1231461001@10.7.7.3> Message-ID: <4967100F.8040303@mavhome.dp.ua> Gabriel Lavoie wrote: > I recently built a small home server using an Inten 45nm E5200 @ > 2.5 GHz. With FreeBSD 7.0, the "est" driver had problems pooling for > the CPU frequency/voltage pairs and automatically disabled itself. It > left the CPU at the frequency the BIOS put it after startup, 1.25 GHz > because I have EIST enabled. I had to manually change the frequency or > use powerd to put it at maximum. Now I upgraded to FreeBSD 7.1 and > everything in my systems seems supported correctly. The est driver now > recognize the CPU and load the correct information. Also, after > bootup, the frequency of the CPU is at max (2.5 GHz). What I would > like is to get the behaviour of EIST found under Windows and Linux > where the CPU is automatically downclocked to 1.25 GHz when the system > isn't under any load, but comes back to 2.5 GHz as soon as there is > some load. I also get this behaviour under Linux on my Core 2 Duo and > I really like it. What I found interesting is that it seems the Intel > 45nm CPUs use under 5W of power when they are idle and EIST > downclocked them. I would really like to take profit of this low power > consumption. I found about "estctrl" on this page > http://www.daemonology.net/freebsd-est/ but it seems outdated and when > I try to build the port, it tells me that it is only supported on the > i386 architecture. Why not amd64? man powerd? -- Alexander Motin From glavoie at gmail.com Fri Jan 9 11:58:00 2009 From: glavoie at gmail.com (Gabriel Lavoie) Date: Fri Jan 9 11:58:05 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> References: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> Message-ID: My processor seems correctly recognized by est under 7.1, I get the correct frequency/value pairs. What I would like is the automatic behaviour where the CPU is downclocked to 50% under no load, found under Windows/Linux and I would also like to know why estctrl isn't supported under amd64. I already contacted Colin. :) Gabriel > > Maybe this comment says why (from .../sys/i386/cpufreq/est.c)? > > /* > * Frequency (MHz) and voltage (mV) settings. Data from the > * Intel Pentium M Processor Datasheet (Order Number 252612), Table 5. > * > * Dothan processors have multiple VID#s with different settings for > * each VID#. Since we can't uniquely identify this info > * without undisclosed methods from Intel, we can't support newer > * processors with this table method. If ACPI Px states are supported, > * we get info from them. > */ > > Colin could give you the definite answer, but I'm pretty sure that's it... > Cheers, > -Garrett > -- Gabriel Lavoie glavoie@gmail.com From nate at root.org Fri Jan 9 16:51:55 2009 From: nate at root.org (Nate Lawson) Date: Fri Jan 9 16:52:04 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: References: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> Message-ID: <496780A8.7070801@root.org> Gabriel Lavoie wrote: > My processor seems correctly recognized by est under 7.1, I get the > correct frequency/value pairs. What I would like is the automatic > behaviour where the CPU is downclocked to 50% under no load, found > under Windows/Linux and I would also like to know why estctrl isn't > supported under amd64. I already contacted Colin. :) powerd(8) is what you want. You can set an absolute frequency for idle. -- Nate From glavoie at gmail.com Fri Jan 9 18:40:08 2009 From: glavoie at gmail.com (Gabriel Lavoie) Date: Fri Jan 9 18:40:15 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <496780A8.7070801@root.org> References: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> <496780A8.7070801@root.org> Message-ID: Using debug.cpufreq.lowest? 2009/1/9 Nate Lawson : > Gabriel Lavoie wrote: >> My processor seems correctly recognized by est under 7.1, I get the >> correct frequency/value pairs. What I would like is the automatic >> behaviour where the CPU is downclocked to 50% under no load, found >> under Windows/Linux and I would also like to know why estctrl isn't >> supported under amd64. I already contacted Colin. :) > > powerd(8) is what you want. You can set an absolute frequency for idle. > > -- > Nate > -- Gabriel Lavoie glavoie@gmail.com From glavoie at gmail.com Fri Jan 9 20:00:17 2009 From: glavoie at gmail.com (Gabriel Lavoie) Date: Fri Jan 9 20:00:24 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <496780A8.7070801@root.org> References: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> <496780A8.7070801@root.org> Message-ID: Another question. Any reason why powerd doesn't use dev.est.0.freq_settings when it is available instead of dev.cpu.0.freq_levels? On my system: dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125 600/20900 450/15675 300/10450 150/5225 dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 If I don't lower the polling time of powerd to 100ms, my system becomes way too much unresponsive because powerd takes too much time to increase the frequency, step by step and there are a lot of settings with dev.est.0.freq_settings (14). With dev.est.0.freq_settings, the minimal setting is high enough so the system stays responsive and powerd would bring it up to max frequency quickly enough, even if the polling time is still kept at 500ms. This would work more like Windows or Linux where the lowest frequency at which the CPU will drop is the lowest EIST gives (here 1200 MHz). Gabriel 2009/1/9 Nate Lawson : > Gabriel Lavoie wrote: >> My processor seems correctly recognized by est under 7.1, I get the >> correct frequency/value pairs. What I would like is the automatic >> behaviour where the CPU is downclocked to 50% under no load, found >> under Windows/Linux and I would also like to know why estctrl isn't >> supported under amd64. I already contacted Colin. :) > > powerd(8) is what you want. You can set an absolute frequency for idle. > > -- > Nate > -- Gabriel Lavoie glavoie@gmail.com From nate at root.org Fri Jan 9 21:14:36 2009 From: nate at root.org (Nate Lawson) Date: Fri Jan 9 21:14:42 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: References: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> <496780A8.7070801@root.org> Message-ID: <4967BE39.9020205@root.org> Gabriel Lavoie wrote: > Another question. Any reason why powerd doesn't use > dev.est.0.freq_settings when it is available instead of > dev.cpu.0.freq_levels? > > On my system: > dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657 > 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125 > 600/20900 450/15675 300/10450 150/5225 > dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 > > If I don't lower the polling time of powerd to 100ms, my system > becomes way too much unresponsive because powerd takes too much time > to increase the frequency, step by step and there are a lot of > settings with dev.est.0.freq_settings (14). With > dev.est.0.freq_settings, the minimal setting is high enough so the > system stays responsive and powerd would bring it up to max frequency > quickly enough, even if the polling time is still kept at 500ms. This > would work more like Windows or Linux where the lowest frequency at > which the CPU will drop is the lowest EIST gives (here 1200 MHz). > levels is derived from settings. Set a lower bound with the sysctl for freq_lowest. -- Nate From glavoie at gmail.com Fri Jan 9 22:31:51 2009 From: glavoie at gmail.com (Gabriel Lavoie) Date: Fri Jan 9 22:31:57 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <4967BE39.9020205@root.org> References: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> <496780A8.7070801@root.org> <4967BE39.9020205@root.org> Message-ID: This is what I did by setting freq_lowest to 1200 but it would also be nice if we could configure the steps, or at least, be able to configure more powerd. Some setting like going from lowest frequency to highest frequency in one step if load is over 10% without having to wait a few msec for every steps between would be useful. Gabriel 2009/1/9 Nate Lawson : > Gabriel Lavoie wrote: >> Another question. Any reason why powerd doesn't use >> dev.est.0.freq_settings when it is available instead of >> dev.cpu.0.freq_levels? >> >> On my system: >> dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657 >> 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125 >> 600/20900 450/15675 300/10450 150/5225 >> dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 >> >> If I don't lower the polling time of powerd to 100ms, my system >> becomes way too much unresponsive because powerd takes too much time >> to increase the frequency, step by step and there are a lot of >> settings with dev.est.0.freq_settings (14). With >> dev.est.0.freq_settings, the minimal setting is high enough so the >> system stays responsive and powerd would bring it up to max frequency >> quickly enough, even if the polling time is still kept at 500ms. This >> would work more like Windows or Linux where the lowest frequency at >> which the CPU will drop is the lowest EIST gives (here 1200 MHz). >> > > levels is derived from settings. Set a lower bound with the sysctl for > freq_lowest. > > -- > Nate > -- Gabriel Lavoie glavoie@gmail.com From bahamasfranks at gmail.com Fri Jan 9 22:59:41 2009 From: bahamasfranks at gmail.com (Steve Franks) Date: Fri Jan 9 22:59:47 2009 Subject: best way to debug intermittent system freezes? In-Reply-To: <3a142e750901091334x3f648260md5f5d8402b350d34@mail.gmail.com> References: <539c60b90901090950j3bbd28q22b50d09fec18023@mail.gmail.com> <3a142e750901091334x3f648260md5f5d8402b350d34@mail.gmail.com> Message-ID: <539c60b90901091437w5de7e615yd171573ca194dd59@mail.gmail.com> > What happens if you disable acpi? Well, my use-paradigm for the computer is seriously impaired for one. Also, it's intermittent enough, I can't really prove any particular item "fixes" it by simply disabling that item. Any way to stick one's fingers into acpi or do some kind of logging on it instead? Well, certainly something to try anyway, since it's pretty much of a coaster at the moment.... Steve From mav at FreeBSD.org Fri Jan 9 23:55:27 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Fri Jan 9 23:55:33 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <1231543382.00058245.1231531801@10.7.7.3> References: <1231471393.00057821.1231461001@10.7.7.3> <1231492987.00057896.1231480801@10.7.7.3> <1231514587.00058037.1231502401@10.7.7.3> <1231532583.00058199.1231520401@10.7.7.3> <1231543382.00058245.1231531801@10.7.7.3> Message-ID: <4967E3F1.3050002@FreeBSD.org> Gabriel Lavoie wrote: > Another question. Any reason why powerd doesn't use > dev.est.0.freq_settings when it is available instead of > dev.cpu.0.freq_levels? > > On my system: > dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657 > 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125 > 600/20900 450/15675 300/10450 150/5225 > dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 dev.cpu.0.freq_levels is just a mix of est and p4tcc levels. By default powerd uses all of them. If you really wish, you can disable p4tcc with: hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 then dev.cpu.0.freq_levels will be equal to dev.est.0.freq_settings. > If I don't lower the polling time of powerd to 100ms, my system > becomes way too much unresponsive because powerd takes too much time > to increase the frequency, step by step and there are a lot of > settings with dev.est.0.freq_settings (14). With > dev.est.0.freq_settings, the minimal setting is high enough so the > system stays responsive and powerd would bring it up to max frequency > quickly enough, even if the polling time is still kept at 500ms. This > would work more like Windows or Linux where the lowest frequency at > which the CPU will drop is the lowest EIST gives (here 1200 MHz). I have just merged updated powerd to 7-STABLE to address this issue. -- Alexander Motin From glavoie at gmail.com Sat Jan 10 00:10:43 2009 From: glavoie at gmail.com (Gabriel Lavoie) Date: Sat Jan 10 00:10:49 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <4967E3F1.3050002@FreeBSD.org> References: <1231471393.00057821.1231461001@10.7.7.3> <1231492987.00057896.1231480801@10.7.7.3> <1231514587.00058037.1231502401@10.7.7.3> <1231532583.00058199.1231520401@10.7.7.3> <1231543382.00058245.1231531801@10.7.7.3> <4967E3F1.3050002@FreeBSD.org> Message-ID: 2009/1/9 Alexander Motin : > Gabriel Lavoie wrote: >> >> Another question. Any reason why powerd doesn't use >> dev.est.0.freq_settings when it is available instead of >> dev.cpu.0.freq_levels? >> >> On my system: >> dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657 >> 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125 >> 600/20900 450/15675 300/10450 150/5225 >> dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 > > dev.cpu.0.freq_levels is just a mix of est and p4tcc levels. By default > powerd uses all of them. If you really wish, you can disable p4tcc with: > hint.p4tcc.0.disabled=1 > hint.acpi_throttle.0.disabled=1 > then dev.cpu.0.freq_levels will be equal to dev.est.0.freq_settings. Working like a charm! I wasn't sure so I added both 0 and 1 for both cores and it seems to be correct. I had to add them in loader.conf or device.hints? Put them in loader.conf and it seems to be OK. > >> If I don't lower the polling time of powerd to 100ms, my system >> becomes way too much unresponsive because powerd takes too much time >> to increase the frequency, step by step and there are a lot of >> settings with dev.est.0.freq_settings (14). With >> dev.est.0.freq_settings, the minimal setting is high enough so the >> system stays responsive and powerd would bring it up to max frequency >> quickly enough, even if the polling time is still kept at 500ms. This >> would work more like Windows or Linux where the lowest frequency at >> which the CPU will drop is the lowest EIST gives (here 1200 MHz). > > I have just merged updated powerd to 7-STABLE to address this issue. If I run release, it means it will be available in 7.2? > > -- > Alexander Motin > Thanks Gabriel -- Gabriel Lavoie glavoie@gmail.com From mav at FreeBSD.org Sat Jan 10 00:13:11 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Sat Jan 10 00:13:16 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: References: <1231471393.00057821.1231461001@10.7.7.3> <1231492987.00057896.1231480801@10.7.7.3> <1231514587.00058037.1231502401@10.7.7.3> <1231532583.00058199.1231520401@10.7.7.3> <1231543382.00058245.1231531801@10.7.7.3> <4967E3F1.3050002@FreeBSD.org> Message-ID: <4967E819.6010305@FreeBSD.org> Gabriel Lavoie wrote: > 2009/1/9 Alexander Motin : >> Gabriel Lavoie wrote: >>> Another question. Any reason why powerd doesn't use >>> dev.est.0.freq_settings when it is available instead of >>> dev.cpu.0.freq_levels? >>> >>> On my system: >>> dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657 >>> 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125 >>> 600/20900 450/15675 300/10450 150/5225 >>> dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 >> dev.cpu.0.freq_levels is just a mix of est and p4tcc levels. By default >> powerd uses all of them. If you really wish, you can disable p4tcc with: >> hint.p4tcc.0.disabled=1 >> hint.acpi_throttle.0.disabled=1 >> then dev.cpu.0.freq_levels will be equal to dev.est.0.freq_settings. > > Working like a charm! I wasn't sure so I added both 0 and 1 for both > cores and it seems to be correct. I had to add them in loader.conf or > device.hints? Put them in loader.conf and it seems to be OK. Whatever you prefer, >>> If I don't lower the polling time of powerd to 100ms, my system >>> becomes way too much unresponsive because powerd takes too much time >>> to increase the frequency, step by step and there are a lot of >>> settings with dev.est.0.freq_settings (14). With >>> dev.est.0.freq_settings, the minimal setting is high enough so the >>> system stays responsive and powerd would bring it up to max frequency >>> quickly enough, even if the polling time is still kept at 500ms. This >>> would work more like Windows or Linux where the lowest frequency at >>> which the CPU will drop is the lowest EIST gives (here 1200 MHz). >> I have just merged updated powerd to 7-STABLE to address this issue. > > If I run release, it means it will be available in 7.2? 7.2 and 8.0. -- Alexander Motin From Miracle_Marketing at mail.vresp.com Sat Jan 10 06:46:29 2009 From: Miracle_Marketing at mail.vresp.com (Miracle Marketing) Date: Sat Jan 10 06:46:39 2009 Subject: Recession Proof Yourself in a Bad Economy Message-ID: Click to view this email in a browser http://hosted.verticalresponse.com/352016/c3325f30a2/1424003284/12c070f26f/ Attention: Internet Marketers ********************************************************************** UNDBELIEVABLE! 40 Big Blasters Are Making Me A Killing! Get In NOW! http://cts.vresp.com/c/?InstantPaysites/c3325f30a2/12c070f26f/5211b27c8c HOLD ON To Your Seat ...This One Is FIRE HOT! We are now offering 40 & I said 40 of the TOP all-time email blasters on the internet, to date EVER! One Amazing Bundle that is ready to use to submit your ads! These are the same blasters that have easily sold for up to $59.95 each. If you purchased these items seperately you would easily spend over $1000! But we decided to bring them to you in one F.A.N.T.A.S.T.I.C. bundle, but only for a LIMITED TIME Only. Nobody needs to tell you how GREAT & how BIG this is! You can even use the remarkable blasting submitters to blow-out resales on the affiliate end if you choose, for $100 per sale directly to your PayPal account. Don't let someone else steal your thunder! Why pay the individual price for these blasters ... Get 1st movers advantage now by finally being FIRST! ********************************************************************** http://www.Firesale-Ads.com Over 764 Million Fresh Email Leads Get in before it's to late ______________________________________________________________________ If you no longer wish to receive these emails, please reply to this message with "Remove" in the subject line or simply click on the following link: http://cts.vresp.com/u?c3325f30a2/12c070f26f/9f11daf ______________________________________________________________________ This message was sent by Miracle Marketing using VerticalResponse PO Box 522 Torrance CA 90502 Read the VerticalResponse marketing policy: http://www.verticalresponse.com/content/pm_policy.html From ivakras1 at gmail.com Sat Jan 10 07:59:55 2009 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Sat Jan 10 08:00:02 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: References: <496780A8.7070801@root.org> Message-ID: <200901101059.31131.ivakras1@gmail.com> On Friday 09 January 2009 23:00:03 Gabriel Lavoie wrote: > Another question. Any reason why powerd doesn't use > dev.est.0.freq_settings when it is available instead of > dev.cpu.0.freq_levels? > > On my system: > dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657 > 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125 > 600/20900 450/15675 300/10450 150/5225 > dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 > > If I don't lower the polling time of powerd to 100ms, my system > becomes way too much unresponsive because powerd takes too much time > to increase the frequency, step by step and there are a lot of > settings with dev.est.0.freq_settings (14). With > dev.est.0.freq_settings, the minimal setting is high enough so the > system stays responsive and powerd would bring it up to max frequency > quickly enough, even if the polling time is still kept at 500ms. This > would work more like Windows or Linux where the lowest frequency at > which the CPU will drop is the lowest EIST gives (here 1200 MHz). > > Gabriel > > 2009/1/9 Nate Lawson : > > Gabriel Lavoie wrote: > >> My processor seems correctly recognized by est under 7.1, I get the > >> correct frequency/value pairs. What I would like is the automatic > >> behaviour where the CPU is downclocked to 50% under no load, found > >> under Windows/Linux and I would also like to know why estctrl isn't > >> supported under amd64. I already contacted Colin. :) > > > > powerd(8) is what you want. You can set an absolute frequency for idle. > > > > -- > > Nate What this settings for in defaults/rc.conf? performance_cx_lowest="HIGH" # Online CPU idle state performance_cpu_freq="NONE" # Online CPU frequency economy_cx_lowest="HIGH" # Offline CPU idle state economy_cpu_freq="NONE" # Offline CPU frequency Im using it with powerd at the same time and it runs just smoothly. From avg at icyb.net.ua Sat Jan 10 15:16:48 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Sat Jan 10 15:16:55 2009 Subject: WDTT Message-ID: <4968B843.8020108@icyb.net.ua> This is just out of curiosity - does anybody know what a table with 'WDTT' signature is? I see its presence, for instance, on Intel DG33TL: /* WDTT: Length=716, Revision=1, Checksum=38, OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, Creator ID=MSFT, Creator Revision=0x1000013 */ P.S. please do not confuse with 'WDDT' :-) -- Andriy Gapon From glavoie at gmail.com Sat Jan 10 15:18:34 2009 From: glavoie at gmail.com (Gabriel Lavoie) Date: Sat Jan 10 15:18:40 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <200901101059.31131.ivakras1@gmail.com> References: <496780A8.7070801@root.org> <200901101059.31131.ivakras1@gmail.com> Message-ID: I have these settings in my rc.conf and /boot/loader.conf now: /etc/rc.conf: powerd_enable="YES" powerd_flags="-i 90 -r 90 -p 250" /boot/loader.conf: hint.p4tcc.0.disabled=1 hint.p4tcc.1.disabled=1 hint.acpi_throttle.0.disabled=1 hint.acpi_throttle.1.disabled=1 This way I only have the list of frequencies EST gives and powerd will raise/lower the frequency as soon as the load goes above/under 10%. I also find my system to be more responsive with a polling time under 500ms. This is why I lowered it to 250ms. I'm quite satisfied with this setup and this is what I was looking for when I installed this server. About the settings in /etc/default/rc.conf, I don't know where they are used... CPU info from sysctl: dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU1 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 1200 dev.cpu.0.freq_levels: 2500/88000 2000/47608 1600/44616 1200/41800 dev.cpu.0.cx_supported: C1/0 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU2 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/0 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% dev.acpi_perf.0.%driver: acpi_perf dev.acpi_perf.0.%parent: cpu0 dev.acpi_perf.1.%driver: acpi_perf dev.acpi_perf.1.%parent: cpu1 dev.est.0.%desc: Enhanced SpeedStep Frequency Control dev.est.0.%driver: est dev.est.0.%parent: cpu0 dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 dev.est.1.%desc: Enhanced SpeedStep Frequency Control dev.est.1.%driver: est dev.est.1.%parent: cpu1 dev.est.1.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 dev.cpufreq.0.%driver: cpufreq dev.cpufreq.0.%parent: cpu0 dev.cpufreq.1.%driver: cpufreq dev.cpufreq.1.%parent: cpu1 Gabriel 2009/1/10 Dmitry Kolosov : > On Friday 09 January 2009 23:00:03 Gabriel Lavoie wrote: >> Another question. Any reason why powerd doesn't use >> dev.est.0.freq_settings when it is available instead of >> dev.cpu.0.freq_levels? >> >> On my system: >> dev.cpu.0.freq_levels: 2500/88000 2187/77000 2000/47608 1750/41657 >> 1600/44616 1400/39039 1200/41800 1050/36575 900/31350 750/26125 >> 600/20900 450/15675 300/10450 150/5225 >> dev.est.0.freq_settings: 2500/88000 2000/47608 1600/44616 1200/41800 >> >> If I don't lower the polling time of powerd to 100ms, my system >> becomes way too much unresponsive because powerd takes too much time >> to increase the frequency, step by step and there are a lot of >> settings with dev.est.0.freq_settings (14). With >> dev.est.0.freq_settings, the minimal setting is high enough so the >> system stays responsive and powerd would bring it up to max frequency >> quickly enough, even if the polling time is still kept at 500ms. This >> would work more like Windows or Linux where the lowest frequency at >> which the CPU will drop is the lowest EIST gives (here 1200 MHz). >> >> Gabriel >> >> 2009/1/9 Nate Lawson : >> > Gabriel Lavoie wrote: >> >> My processor seems correctly recognized by est under 7.1, I get the >> >> correct frequency/value pairs. What I would like is the automatic >> >> behaviour where the CPU is downclocked to 50% under no load, found >> >> under Windows/Linux and I would also like to know why estctrl isn't >> >> supported under amd64. I already contacted Colin. :) >> > >> > powerd(8) is what you want. You can set an absolute frequency for idle. >> > >> > -- >> > Nate > > What this settings for in defaults/rc.conf? > performance_cx_lowest="HIGH" # Online CPU idle state > performance_cpu_freq="NONE" # Online CPU frequency > economy_cx_lowest="HIGH" # Offline CPU idle state > economy_cpu_freq="NONE" # Offline CPU frequency > > Im using it with powerd at the same time and it runs just smoothly. > _______________________________________________ > 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" > -- Gabriel Lavoie glavoie@gmail.com From smithi at nimnet.asn.au Sat Jan 10 16:21:22 2009 From: smithi at nimnet.asn.au (Ian Smith) Date: Sat Jan 10 16:21:29 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: <200901101059.31131.ivakras1@gmail.com> References: <496780A8.7070801@root.org> <200901101059.31131.ivakras1@gmail.com> Message-ID: <20090110202341.R96980@sola.nimnet.asn.au> On Sat, 10 Jan 2009, Dmitry Kolosov wrote: > > What this settings for in defaults/rc.conf? > performance_cx_lowest="HIGH" # Online CPU idle state > performance_cpu_freq="NONE" # Online CPU frequency > economy_cx_lowest="HIGH" # Offline CPU idle state > economy_cpu_freq="NONE" # Offline CPU frequency > > Im using it with powerd at the same time and it runs just smoothly. These default settings are good for use with powerd. They're only applied by /etc/rc.d/power_profile as invoked by devd when power state changes to AC or to Battery, and perhaps? also after boot. See power_profile and /etc/devd.conf for default configuration. *_cpu_freq=NONE has power_profile leave cpu frequency alone, so it won't be altered just until powerd next shifts frequency according to load. powerd also detects power state changes to select its configured mode, which may conflict with a different power_profile setting, momentarily. powerd doesn't care about the *_cx_lowest settings, just power_profile. cheers, Ian From avg at icyb.net.ua Sat Jan 10 10:32:05 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Sat Jan 10 10:32:25 2009 Subject: intel heci/mei Message-ID: <4968E9A1.3080006@icyb.net.ua> First of all, some relevant terms to google for. Intel AMT - Active Management Technology ME - Management Engine MEI - ME Interface HECI - Host Embedded Controller Interface, I believe that this is a different (older?) name for MEI What this is not about. This is not about AMT in general; not about remote access/control that by-passes OS. What this is about. Providing a kernel driver and interface that would enable user-land programs (and/or kernel) to communicate with "agents" residing in ME. Provided, of course, that those agents are designed to support such communication. For me, personally, "Quiet System Technology (QST), formerly Advanced Fan Speed Control (AFSC)" is of the most interest. Prior art. http://openamt.org Open-sourced GPL/BSD Linux driver developed by Intel that provides in principle exactly what I want. http://mail.opensolaris.org/pipermail/opensolaris-arc/2007-October/004572.html Lengthy discussion of a similar driver for OpenSolaris plus general AMT issues. My understanding. There is a dedicated micro-controller built into a chipset. This is Management Engine. The micro-controller can execute various firmware programs that perform control/monitoring/management tasks. There is a PCI device/function in the chipset that allows host software (run on main CPU) to communicate with the firmware running in ME. This is HECI. There are several memory-mapped registers for the communication. The communication seems to be symmetric (on the lowest level). The communication occurs by writing data into a circular buffer and then writing a bit that causes an interrupt to occur to the peer. Thus, there are two circular buffers to send data in the opposite directions. There are can be multiple peers on the host side and on the firmware side. Peers are addressed by simple 1-byte numbers. Firmware peers are further uniquely identified by GUIDs. There is a certain message protocol. There are so called bus messages and then there are application specific messages. Via bus messages the following can be done: 1. discover firmware clients (only from the host side) 2. query identities and capabilities/properties of a fw client (only from the host side) 3. establish or close a connection between a host client and a fw client (only from the host side [?]) 4. send a flow control message to a connected peer which gives it a permission to send one application-specific message All messages have a 4-byte header that specifies peer addresses and length of message body. Bus messages use broadcast addresses of zero in the header, peer information (if any) is provided in message body. Bus messages have a well defined structure. One logical application message can be consist of several HECI messages, there is a flag in the message header telling if a message is complete. Typical communication session can look like this: 1. query fw peers (their addresses) 2. query properties of each available peer until the one of interest is found 3. send connect message 4. receive connect status message 5. receive flow control message [gives permission for the next step] 6. send application request 7. send flow control message [gives permission for the next step] 8. receive application response 9. receive flow control message [peer is ready for next request] [...] 10. send disconnect message 11. receive disconnect response How OpenAMT driver currently works. Omitting low level details - it enumerates fw clients and creates a single heci character device. Then there ioctls for userland programs to connect to client with a specific GUID and then the program can communicate with it via read and write calls. What I have in mind. The driver would enumerate fw clients and create a character device for each one discovered. Device name could be a stringified GUID and/or some short name for well-known GUIDs. A userland program would simple open/close such a device to establish/terminate communication. There is something I am not sure about, I see 2 possibilities: 1. there will be one driver with multiple character devices, all devices would behave identically, knowledge of how to talk to each fw client would lie in userland programs; 2. there will be a heci bus with individual drivers for well-know fw clients plus maybe a generic driver to talk to unknown clients; each character device would have a documented API for communication with the corresponding fw client; For now I am leaning towards approach #1. There are also other issues. Like, for example, what is the best API for exchanging application messages. I assume that there could be different modes of talking to fw client, typically it is simple request/response, but it is possible that client might provide something like streaming data. Also, a messages fro fw client could be multi-part - how do we tell userland that there is more data and when the message ends. I have some very very simple code that puts all (really all) the communication logic into the userland, it only provides a way to talk to the hardware (correctly reading/writing registers, handling interrupts). I have some small successes using that code. I hope to produce something more mature, but as usual the time is the biggest constraint. If you have an advice for me or some interest in this area - please write me. P.S. I am also thinking about more-or-less porting the OpenAMT code, but the changes would be quite huge and the code is frequently quite hard for me to grok. -- Andriy Gapon From demelier.david at gmail.com Sun Jan 11 09:01:33 2009 From: demelier.david at gmail.com (David DEMELIER) Date: Sun Jan 11 09:02:06 2009 Subject: Acpi errors on pavilion laptop Message-ID: Hi, I installed FreeBSD on my laptop, and upgraded it to 7-STABLE, at the boot time and after I got these ACPI errors. I don't know what these errors are about. Do you need more informations ? -------------- next part -------------- acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.TZS0._TMP] (Node 0xc6450540), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE ACPI Error (uteval-0309): Method execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._STA] (Node 0xc645dac0), AE_NO_HARDWARE_RESPONSE acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc645dbc0), AE_NO_HARDWARE_RESPONSE ACPI Error (psparse-0626): Method parse/execution failed [\\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc645da80), AE_NO_HARDWARE_RESPONSE -------------- next part -------------- 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c) 00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c) 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev a1) 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8039 PCI-E Fast Ethernet Controller (rev 14) 07:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) 08:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) 08:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 08:09.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12) 08:09.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 08:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12) From ivakras1 at gmail.com Sun Jan 11 09:31:19 2009 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Sun Jan 11 09:31:25 2009 Subject: Acpi errors on pavilion laptop In-Reply-To: References: Message-ID: <200901112030.52922.ivakras1@gmail.com> On Sunday 11 January 2009 19:28:24 David DEMELIER wrote: > Hi, > > I installed FreeBSD on my laptop, and upgraded it to 7-STABLE, at the boot > time and after I got these ACPI errors. > > I don't know what these errors are about. > > Do you need more informations ? 1. ACPI Embedded Controller (EC) problem. I have it to on Acer 5720. Not solved,but disabled by: debug.acpi.disabled="ec cmbat" 2. System cooling and heat management problem (thermal). Try to disable this part of ACPI by adding 'thermal' to debug.acpi.disabled BUT be carefull cuz of system overheat!. After this it will looks like: debug.acpi.disabled="ec cmbat thermal" From matheus at eternamente.info Sun Jan 11 11:24:05 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Sun Jan 11 11:24:12 2009 Subject: mini itx from via - acpi issues on 7.1R Message-ID: <623575f542995109fc455005855b4083.squirrel@lamneth> I sent this friday to stable@, but nothing as far. I'm trying this one now, hope better luck :) matheus hail, I'm running 7.1R (tried 8.0-CURRENT also) on a via mini itx (dmesg bellow) and if I load acpi module, I have no lan. it appears, I can set IP, even the led would blink when I ping. but no signal of bits on the other pc whatsoever. tcpdump sees nothing in both endpoints. if acpi is not loaded, vr0 works as it should. i really think acpi would help this box, on power purposes, so here I am asking. thanks, matheus ps: should I mail acpi@ with, or instead ? $ dmesg Copyright (c) 1992-2009 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 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Transmeta(tm) Crusoe(tm) Processor TM5700 (798.13-MHz 586-class CPU) Origin = "GenuineTMx86" Id = 0x543 Stepping = 3 Features=0x84893f real memory = 117374976 (111 MB) avail memory = 100737024 (96 MB) kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) uhci0: port 0xe000-0xe01f irq 15 at device 9.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe100-0xe11f irq 5 at device 9.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xe8131000-0xe81310ff irq 10 at device 9.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 4 ports with 4 removable, self powered vgapci0: port 0xe200-0xe2ff mem 0xe0000000-0xe7ffffff,0xe8120000-0xe812ffff irq 11 at device 13.0 on pci0 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe300-0xe30f at device 17.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 17.4 (no driver attached) vr0: port 0xe600-0xe6ff mem 0xe8130000-0xe81300ff irq 15 at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x51 miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:11:85:e3:2a:17 vr0: [ITHREAD] cpu0 on motherboard pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc8fff,0xcc000-0xd5fff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (memory) Timecounter "TSC" frequency 798129274 Hz quality 800 Timecounters tick every 1.000 msec ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 19464MB at ata0-master UDMA33 Trying to mount root from ufs:/dev/ad0s2a vr0@pci0:0:18:0: class=0x020000 card=0x01021106 chip=0x30651106 rev=0x51 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6102 Rhine II PCI Fast Ethernet Controller||Used by GERICOM in laptop Webengine Advanced' class = network subclass = ethernet -- We will call you cygnus, The God of balance you shall be -- We will call you cygnus, The God of balance you shall be From bugmaster at FreeBSD.org Mon Jan 12 03:06:48 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 12 03:06:54 2009 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200901121106.n0CB6lZO091895@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [ACPI] sleep broken on IBM/Lenovo T61 [amd64] o kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/89411 acpi [acpi] acpiconf bug o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 f kern/67309 acpi zzz reboot computer (ACPI S3) o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 46 problems total. From cwhiteh at onetel.com Mon Jan 12 07:24:16 2009 From: cwhiteh at onetel.com (Chris Whitehouse) Date: Mon Jan 12 07:24:22 2009 Subject: pr kern/105537 Message-ID: <496B5B21.1080709@onetel.com> hi, Please would you cc me in any reply as I'm not subscribed, thanks. I have the same problem noted in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/105537 of frequent messages saying acpi_tz0: _CRT value is absurd, ignored (256.0C) on my HP nc6320 laptop, model RH383ET. Is there any progress on this PR? Would it help if I arranged root access on this machine for someone to have a look at it? Currently has PCBSD but I can replace that with something else if required. FreeBSD muji 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon Nov 24 20:22:16 EST 2008 root@pcbsdx32-7:/usr/obj/pcbsd-build/cvs/7.0.2-src/sys/PCBSD i386 thanks Chris From rpaulo at freebsd.org Mon Jan 12 12:13:32 2009 From: rpaulo at freebsd.org (Rui Paulo) Date: Mon Jan 12 12:13:38 2009 Subject: WDTT In-Reply-To: <4968B843.8020108@icyb.net.ua> References: <4968B843.8020108@icyb.net.ua> Message-ID: <24E2EB6D-235D-44DD-AC2C-405E910DBE02@freebsd.org> On 10 Jan 2009, at 15:01, Andriy Gapon wrote: > > This is just out of curiosity - does anybody know what a table with > 'WDTT' signature is? > I see its presence, for instance, on Intel DG33TL: > /* > WDTT: Length=716, Revision=1, Checksum=38, > OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, > Creator ID=MSFT, Creator Revision=0x1000013 > */ No idea. Could it be ACPI 4.0? -- Rui Paulo From aragon at phat.za.net Tue Jan 13 02:25:25 2009 From: aragon at phat.za.net (Aragon Gouveia) Date: Tue Jan 13 02:25:31 2009 Subject: EST (Enhanced Intel SpeedStep(R) Technology) on amd64 In-Reply-To: References: <7d6fde3d0901082151t4901824cv84eb6c2be2658b15@mail.gmail.com> <496780A8.7070801@root.org> Message-ID: <20090113095425.GA99826@phat.za.net> | By Gabriel Lavoie | [ 2009-01-09 22:01 +0200 ] > If I don't lower the polling time of powerd to 100ms, my system > becomes way too much unresponsive because powerd takes too much time > to increase the frequency, step by step and there are a lot of > settings with dev.est.0.freq_settings (14). With http://lists.freebsd.org/pipermail/freebsd-mobile/2008-November/011188.html Works very well. Regards, Aragon From robert.moore at intel.com Tue Jan 13 13:16:46 2009 From: robert.moore at intel.com (Moore, Robert) Date: Tue Jan 13 13:16:53 2009 Subject: WDTT In-Reply-To: <4968B843.8020108@icyb.net.ua> References: <4968B843.8020108@icyb.net.ua> Message-ID: <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> Could you send/post the acpidump for this machine? This "looks" like a watchdog timer table, but it is not one that I'm familiar with. Thanks, Bob >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Andriy Gapon >Sent: Saturday, January 10, 2009 7:01 AM >To: freebsd-acpi@freebsd.org >Subject: WDTT > > >This is just out of curiosity - does anybody know what a table with >'WDTT' signature is? >I see its presence, for instance, on Intel DG33TL: >/* > WDTT: Length=716, Revision=1, Checksum=38, > OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, > Creator ID=MSFT, Creator Revision=0x1000013 > */ > >P.S. please do not confuse with 'WDDT' :-) > >-- >Andriy Gapon >_______________________________________________ >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" From matheus at eternamente.info Tue Jan 13 15:39:08 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Tue Jan 13 15:39:15 2009 Subject: mini itx from via - acpi issues on 7.1R Message-ID: <452cf39aff90a0ec092c5606aa55e975.squirrel@lamneth> I sent this friday to stable@, but nothing as far. I'm trying this one now, hope better luck :) matheus hail, I'm running 7.1R (tried 8.0-CURRENT also) on a via mini itx (dmesg bellow) and if I load acpi module, I have no lan. it appears, I can set IP, even the led would blink when I ping. but no signal of bits on the other pc whatsoever. tcpdump sees nothing in both endpoints. if acpi is not loaded, vr0 works as it should. i really think acpi would help this box, on power purposes, so here I am asking. thanks, matheus ps: should I mail acpi@ with, or instead ? $ dmesg Copyright (c) 1992-2009 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 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Transmeta(tm) Crusoe(tm) Processor TM5700 (798.13-MHz 586-class CPU) Origin = "GenuineTMx86" Id = 0x543 Stepping = 3 Features=0x84893f real memory = 117374976 (111 MB) avail memory = 100737024 (96 MB) kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) uhci0: port 0xe000-0xe01f irq 15 at device 9.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe100-0xe11f irq 5 at device 9.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xe8131000-0xe81310ff irq 10 at device 9.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 4 ports with 4 removable, self powered vgapci0: port 0xe200-0xe2ff mem 0xe0000000-0xe7ffffff,0xe8120000-0xe812ffff irq 11 at device 13.0 on pci0 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe300-0xe30f at device 17.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 17.4 (no driver attached) vr0: port 0xe600-0xe6ff mem 0xe8130000-0xe81300ff irq 15 at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x51 miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:11:85:e3:2a:17 vr0: [ITHREAD] cpu0 on motherboard pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc8fff,0xcc000-0xd5fff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (memory) Timecounter "TSC" frequency 798129274 Hz quality 800 Timecounters tick every 1.000 msec ad0: DMA limited to UDMA33, device found non-ATA66 cable ad0: 19464MB at ata0-master UDMA33 Trying to mount root from ufs:/dev/ad0s2a vr0@pci0:0:18:0: class=0x020000 card=0x01021106 chip=0x30651106 rev=0x51 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT6102 Rhine II PCI Fast Ethernet Controller||Used by GERICOM in laptop Webengine Advanced' class = network subclass = ethernet -- We will call you cygnus, The God of balance you shall be -- We will call you cygnus, The God of balance you shall be -- We will call you cygnus, The God of balance you shall be From nate at root.org Tue Jan 13 16:00:18 2009 From: nate at root.org (Nate Lawson) Date: Tue Jan 13 16:00:26 2009 Subject: mini itx from via - acpi issues on 7.1R In-Reply-To: <452cf39aff90a0ec092c5606aa55e975.squirrel@lamneth> References: <452cf39aff90a0ec092c5606aa55e975.squirrel@lamneth> Message-ID: <496D2B09.6040608@root.org> Nenhum_de_Nos wrote: > I sent this friday to stable@, but nothing as far. I'm trying this one > now, hope better luck :) > > matheus > > hail, > > I'm running 7.1R (tried 8.0-CURRENT also) on a via mini itx (dmesg bellow) > and if I load acpi module, I have no lan. it appears, I can set IP, even > the led would blink when I ping. but no signal of bits on the other pc > whatsoever. tcpdump sees nothing in both endpoints. if acpi is not loaded, > vr0 works as it should. > > i really think acpi would help this box, on power purposes, so here I am > asking. > > thanks, > > matheus > > ps: should I mail acpi@ with, or instead ? > pci0: at device 17.4 (no driver attached) > vr0: port 0xe600-0xe6ff mem > 0xe8130000-0xe81300ff irq 15 at device 18.0 on pci0 > vr0: Quirks: 0x0 > vr0: Revision: 0x51 > miibus0: on vr0 > ukphy0: PHY 1 on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > vr0: Ethernet address: 00:11:85:e3:2a:17 > vr0: [ITHREAD] > > vr0@pci0:0:18:0: class=0x020000 card=0x01021106 chip=0x30651106 rev=0x51 > hdr=0x00 > vendor = 'VIA Technologies Inc' > device = 'VT6102 Rhine II PCI Fast Ethernet Controller||Used by > GERICOM in laptop Webengine Advanced' > class = network > subclass = ethernet Maybe it's a PCI irq routing problem. -- Nate From matheus at eternamente.info Tue Jan 13 21:27:03 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Tue Jan 13 21:27:10 2009 Subject: mini itx from via - acpi issues on 7.1R In-Reply-To: <496D2B09.6040608@root.org> References: <452cf39aff90a0ec092c5606aa55e975.squirrel@lamneth> <496D2B09.6040608@root.org> Message-ID: On Tue, January 13, 2009 22:00, Nate Lawson wrote: > Nenhum_de_Nos wrote: >> I sent this friday to stable@, but nothing as far. I'm trying this one >> now, hope better luck :) >> >> matheus >> >> hail, >> >> I'm running 7.1R (tried 8.0-CURRENT also) on a via mini itx (dmesg >> bellow) >> and if I load acpi module, I have no lan. it appears, I can set IP, even >> the led would blink when I ping. but no signal of bits on the other pc >> whatsoever. tcpdump sees nothing in both endpoints. if acpi is not >> loaded, >> vr0 works as it should. >> >> i really think acpi would help this box, on power purposes, so here I am >> asking. >> >> thanks, >> >> matheus >> >> ps: should I mail acpi@ with, or instead ? > >> pci0: at device 17.4 (no driver attached) >> vr0: port 0xe600-0xe6ff mem >> 0xe8130000-0xe81300ff irq 15 at device 18.0 on pci0 >> vr0: Quirks: 0x0 >> vr0: Revision: 0x51 >> miibus0: on vr0 >> ukphy0: PHY 1 on miibus0 >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >> vr0: Ethernet address: 00:11:85:e3:2a:17 >> vr0: [ITHREAD] >> >> vr0@pci0:0:18:0: class=0x020000 card=0x01021106 chip=0x30651106 rev=0x51 >> hdr=0x00 >> vendor = 'VIA Technologies Inc' >> device = 'VT6102 Rhine II PCI Fast Ethernet Controller||Used by >> GERICOM in laptop Webengine Advanced' >> class = network >> subclass = ethernet > > Maybe it's a PCI irq routing problem. is there anything I can do ? (you can think of) thanks, matheus -- We will call you cygnus, The God of balance you shall be From avg at icyb.net.ua Wed Jan 14 01:34:23 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Jan 14 01:34:31 2009 Subject: WDTT In-Reply-To: <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> Message-ID: <496DB197.5020100@icyb.net.ua> Bob, will an output of FreeBSD acpidump (on stable/7) be sufficient or should I use something newer/different? FreeBSD acpidump -dt output is here: http://www.icyb.net.ua/~avg/dg33tl.asl.gz on 13/01/2009 22:46 Moore, Robert said the following: > Could you send/post the acpidump for this machine? > > This "looks" like a watchdog timer table, but it is not one that I'm familiar with. > > Thanks, > Bob > > >> -----Original Message----- >> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >> acpi@freebsd.org] On Behalf Of Andriy Gapon >> Sent: Saturday, January 10, 2009 7:01 AM >> To: freebsd-acpi@freebsd.org >> Subject: WDTT >> >> >> This is just out of curiosity - does anybody know what a table with >> 'WDTT' signature is? >> I see its presence, for instance, on Intel DG33TL: >> /* >> WDTT: Length=716, Revision=1, Checksum=38, >> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >> Creator ID=MSFT, Creator Revision=0x1000013 >> */ >> >> P.S. please do not confuse with 'WDDT' :-) >> >> -- >> Andriy Gapon >> _______________________________________________ >> 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" -- Andriy Gapon From robert.moore at intel.com Wed Jan 14 08:08:26 2009 From: robert.moore at intel.com (Moore, Robert) Date: Wed Jan 14 08:08:33 2009 Subject: WDTT In-Reply-To: <496DB197.5020100@icyb.net.ua> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> Message-ID: <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> This file contains the disassembly of the DSDT, not a real acpidump of all tables. I need to see the contents of the WDTT. >-----Original Message----- >From: Andriy Gapon [mailto:avg@icyb.net.ua] >Sent: Wednesday, January 14, 2009 1:34 AM >To: Moore, Robert >Cc: freebsd-acpi@freebsd.org >Subject: Re: WDTT > > >Bob, > >will an output of FreeBSD acpidump (on stable/7) be sufficient or should >I use something newer/different? > >FreeBSD acpidump -dt output is here: >http://www.icyb.net.ua/~avg/dg33tl.asl.gz > >on 13/01/2009 22:46 Moore, Robert said the following: >> Could you send/post the acpidump for this machine? >> >> This "looks" like a watchdog timer table, but it is not one that I'm >familiar with. >> >> Thanks, >> Bob >> >> >>> -----Original Message----- >>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>> acpi@freebsd.org] On Behalf Of Andriy Gapon >>> Sent: Saturday, January 10, 2009 7:01 AM >>> To: freebsd-acpi@freebsd.org >>> Subject: WDTT >>> >>> >>> This is just out of curiosity - does anybody know what a table with >>> 'WDTT' signature is? >>> I see its presence, for instance, on Intel DG33TL: >>> /* >>> WDTT: Length=716, Revision=1, Checksum=38, >>> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >>> Creator ID=MSFT, Creator Revision=0x1000013 >>> */ >>> >>> P.S. please do not confuse with 'WDDT' :-) >>> >>> -- >>> Andriy Gapon >>> _______________________________________________ >>> 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" > > >-- >Andriy Gapon From avg at icyb.net.ua Wed Jan 14 08:15:21 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Jan 14 08:15:28 2009 Subject: WDTT In-Reply-To: <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> Message-ID: <496E0F90.3000507@icyb.net.ua> on 14/01/2009 18:08 Moore, Robert said the following: > This file contains the disassembly of the DSDT, not a real acpidump of all tables. I need to see the contents of the WDTT. I see - what's the easiest way to get it? Maybe hack acpidump? >> -----Original Message----- >> From: Andriy Gapon [mailto:avg@icyb.net.ua] >> Sent: Wednesday, January 14, 2009 1:34 AM >> To: Moore, Robert >> Cc: freebsd-acpi@freebsd.org >> Subject: Re: WDTT >> >> >> Bob, >> >> will an output of FreeBSD acpidump (on stable/7) be sufficient or should >> I use something newer/different? >> >> FreeBSD acpidump -dt output is here: >> http://www.icyb.net.ua/~avg/dg33tl.asl.gz >> >> on 13/01/2009 22:46 Moore, Robert said the following: >>> Could you send/post the acpidump for this machine? >>> >>> This "looks" like a watchdog timer table, but it is not one that I'm >> familiar with. >>> Thanks, >>> Bob >>> >>> >>>> -----Original Message----- >>>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>>> acpi@freebsd.org] On Behalf Of Andriy Gapon >>>> Sent: Saturday, January 10, 2009 7:01 AM >>>> To: freebsd-acpi@freebsd.org >>>> Subject: WDTT >>>> >>>> >>>> This is just out of curiosity - does anybody know what a table with >>>> 'WDTT' signature is? >>>> I see its presence, for instance, on Intel DG33TL: >>>> /* >>>> WDTT: Length=716, Revision=1, Checksum=38, >>>> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >>>> Creator ID=MSFT, Creator Revision=0x1000013 >>>> */ >>>> >>>> P.S. please do not confuse with 'WDDT' :-) >>>> >>>> -- >>>> Andriy Gapon >>>> _______________________________________________ >>>> 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" >> >> -- >> Andriy Gapon -- Andriy Gapon From robert.moore at intel.com Wed Jan 14 08:18:25 2009 From: robert.moore at intel.com (Moore, Robert) Date: Wed Jan 14 08:18:32 2009 Subject: WDTT In-Reply-To: <496E0F90.3000507@icyb.net.ua> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> Message-ID: <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> I don't know how to do it on freebsd. On Linux, acpidump provides an ascii dump of all tables present in the RSDT/XSDT. From there, acpixtract can be used to extract the binary tables. There should be a way to do this on freebsd, perhaps someone on this list can help. >-----Original Message----- >From: Andriy Gapon [mailto:avg@icyb.net.ua] >Sent: Wednesday, January 14, 2009 8:15 AM >To: Moore, Robert >Cc: freebsd-acpi@freebsd.org >Subject: Re: WDTT > >on 14/01/2009 18:08 Moore, Robert said the following: >> This file contains the disassembly of the DSDT, not a real acpidump of >all tables. I need to see the contents of the WDTT. > >I see - what's the easiest way to get it? >Maybe hack acpidump? > >>> -----Original Message----- >>> From: Andriy Gapon [mailto:avg@icyb.net.ua] >>> Sent: Wednesday, January 14, 2009 1:34 AM >>> To: Moore, Robert >>> Cc: freebsd-acpi@freebsd.org >>> Subject: Re: WDTT >>> >>> >>> Bob, >>> >>> will an output of FreeBSD acpidump (on stable/7) be sufficient or should >>> I use something newer/different? >>> >>> FreeBSD acpidump -dt output is here: >>> http://www.icyb.net.ua/~avg/dg33tl.asl.gz >>> >>> on 13/01/2009 22:46 Moore, Robert said the following: >>>> Could you send/post the acpidump for this machine? >>>> >>>> This "looks" like a watchdog timer table, but it is not one that I'm >>> familiar with. >>>> Thanks, >>>> Bob >>>> >>>> >>>>> -----Original Message----- >>>>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>>>> acpi@freebsd.org] On Behalf Of Andriy Gapon >>>>> Sent: Saturday, January 10, 2009 7:01 AM >>>>> To: freebsd-acpi@freebsd.org >>>>> Subject: WDTT >>>>> >>>>> >>>>> This is just out of curiosity - does anybody know what a table with >>>>> 'WDTT' signature is? >>>>> I see its presence, for instance, on Intel DG33TL: >>>>> /* >>>>> WDTT: Length=716, Revision=1, Checksum=38, >>>>> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >>>>> Creator ID=MSFT, Creator Revision=0x1000013 >>>>> */ >>>>> >>>>> P.S. please do not confuse with 'WDDT' :-) >>>>> >>>>> -- >>>>> Andriy Gapon >>>>> _______________________________________________ >>>>> 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" >>> >>> -- >>> Andriy Gapon > > >-- >Andriy Gapon From nate at root.org Wed Jan 14 09:06:29 2009 From: nate at root.org (Nate Lawson) Date: Wed Jan 14 09:07:39 2009 Subject: WDTT In-Reply-To: <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> Message-ID: <496E1B90.8080406@root.org> You need both the -t and -d flags. See the man page. Maybe that should be made the default, although I didn't like the idea of a command dumping out pages of output when run with no flags. -Nate Moore, Robert wrote: > I don't know how to do it on freebsd. On Linux, acpidump provides an ascii dump of all tables present in the RSDT/XSDT. From there, acpixtract can be used to extract the binary tables. > > There should be a way to do this on freebsd, perhaps someone on this list can help. > > >> -----Original Message----- >> From: Andriy Gapon [mailto:avg@icyb.net.ua] >> Sent: Wednesday, January 14, 2009 8:15 AM >> To: Moore, Robert >> Cc: freebsd-acpi@freebsd.org >> Subject: Re: WDTT >> >> on 14/01/2009 18:08 Moore, Robert said the following: >>> This file contains the disassembly of the DSDT, not a real acpidump of >> all tables. I need to see the contents of the WDTT. >> >> I see - what's the easiest way to get it? >> Maybe hack acpidump? >> >>>> -----Original Message----- >>>> From: Andriy Gapon [mailto:avg@icyb.net.ua] >>>> Sent: Wednesday, January 14, 2009 1:34 AM >>>> To: Moore, Robert >>>> Cc: freebsd-acpi@freebsd.org >>>> Subject: Re: WDTT >>>> >>>> >>>> Bob, >>>> >>>> will an output of FreeBSD acpidump (on stable/7) be sufficient or should >>>> I use something newer/different? >>>> >>>> FreeBSD acpidump -dt output is here: >>>> http://www.icyb.net.ua/~avg/dg33tl.asl.gz >>>> >>>> on 13/01/2009 22:46 Moore, Robert said the following: >>>>> Could you send/post the acpidump for this machine? >>>>> >>>>> This "looks" like a watchdog timer table, but it is not one that I'm >>>> familiar with. >>>>> Thanks, >>>>> Bob >>>>> >>>>> >>>>>> -----Original Message----- >>>>>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>>>>> acpi@freebsd.org] On Behalf Of Andriy Gapon >>>>>> Sent: Saturday, January 10, 2009 7:01 AM >>>>>> To: freebsd-acpi@freebsd.org >>>>>> Subject: WDTT >>>>>> >>>>>> >>>>>> This is just out of curiosity - does anybody know what a table with >>>>>> 'WDTT' signature is? >>>>>> I see its presence, for instance, on Intel DG33TL: >>>>>> /* >>>>>> WDTT: Length=716, Revision=1, Checksum=38, >>>>>> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >>>>>> Creator ID=MSFT, Creator Revision=0x1000013 >>>>>> */ >>>>>> >>>>>> P.S. please do not confuse with 'WDDT' :-) >>>>>> >>>>>> -- >>>>>> Andriy Gapon >>>>>> _______________________________________________ >>>>>> 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" >>>> -- >>>> Andriy Gapon >> >> -- >> Andriy Gapon > _______________________________________________ > 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" -- Nate From robert.moore at intel.com Wed Jan 14 09:16:06 2009 From: robert.moore at intel.com (Moore, Robert) Date: Wed Jan 14 09:16:13 2009 Subject: WDTT In-Reply-To: <496E1B90.8080406@root.org> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> Message-ID: <4911F71203A09E4D9981D27F9D8308580E4EAAE9@orsmsx503.amr.corp.intel.com> But it appears that this gives a summary of the tables, not the actual tables themselves: >> /* >> WDTT: Length=716, Revision=1, Checksum=38, >> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >> Creator ID=MSFT, Creator Revision=0x1000013 >> */ >-----Original Message----- >From: Nate Lawson [mailto:nate@root.org] >Sent: Wednesday, January 14, 2009 9:06 AM >To: Moore, Robert >Cc: Andriy Gapon; freebsd-acpi@freebsd.org >Subject: Re: WDTT > >You need both the -t and -d flags. See the man page. Maybe that should >be made the default, although I didn't like the idea of a command >dumping out pages of output when run with no flags. > >-Nate > >Moore, Robert wrote: >> I don't know how to do it on freebsd. On Linux, acpidump provides an >ascii dump of all tables present in the RSDT/XSDT. From there, acpixtract >can be used to extract the binary tables. >> >> There should be a way to do this on freebsd, perhaps someone on this list >can help. >> >> >>> -----Original Message----- >>> From: Andriy Gapon [mailto:avg@icyb.net.ua] >>> Sent: Wednesday, January 14, 2009 8:15 AM >>> To: Moore, Robert >>> Cc: freebsd-acpi@freebsd.org >>> Subject: Re: WDTT >>> >>> on 14/01/2009 18:08 Moore, Robert said the following: >>>> This file contains the disassembly of the DSDT, not a real acpidump of >>> all tables. I need to see the contents of the WDTT. >>> >>> I see - what's the easiest way to get it? >>> Maybe hack acpidump? >>> >>>>> -----Original Message----- >>>>> From: Andriy Gapon [mailto:avg@icyb.net.ua] >>>>> Sent: Wednesday, January 14, 2009 1:34 AM >>>>> To: Moore, Robert >>>>> Cc: freebsd-acpi@freebsd.org >>>>> Subject: Re: WDTT >>>>> >>>>> >>>>> Bob, >>>>> >>>>> will an output of FreeBSD acpidump (on stable/7) be sufficient or >should >>>>> I use something newer/different? >>>>> >>>>> FreeBSD acpidump -dt output is here: >>>>> http://www.icyb.net.ua/~avg/dg33tl.asl.gz >>>>> >>>>> on 13/01/2009 22:46 Moore, Robert said the following: >>>>>> Could you send/post the acpidump for this machine? >>>>>> >>>>>> This "looks" like a watchdog timer table, but it is not one that I'm >>>>> familiar with. >>>>>> Thanks, >>>>>> Bob >>>>>> >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>>>>>> acpi@freebsd.org] On Behalf Of Andriy Gapon >>>>>>> Sent: Saturday, January 10, 2009 7:01 AM >>>>>>> To: freebsd-acpi@freebsd.org >>>>>>> Subject: WDTT >>>>>>> >>>>>>> >>>>>>> This is just out of curiosity - does anybody know what a table with >>>>>>> 'WDTT' signature is? >>>>>>> I see its presence, for instance, on Intel DG33TL: >>>>>>> /* >>>>>>> WDTT: Length=716, Revision=1, Checksum=38, >>>>>>> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >>>>>>> Creator ID=MSFT, Creator Revision=0x1000013 >>>>>>> */ >>>>>>> >>>>>>> P.S. please do not confuse with 'WDDT' :-) >>>>>>> >>>>>>> -- >>>>>>> Andriy Gapon >>>>>>> _______________________________________________ >>>>>>> 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" >>>>> -- >>>>> Andriy Gapon >>> >>> -- >>> Andriy Gapon >> _______________________________________________ >> 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" > >-- >Nate From avg at icyb.net.ua Wed Jan 14 09:16:22 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Jan 14 09:16:29 2009 Subject: WDTT In-Reply-To: <496E1B90.8080406@root.org> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> Message-ID: <496E1DE0.5080305@icyb.net.ua> on 14/01/2009 19:06 Nate Lawson said the following: > You need both the -t and -d flags. See the man page. Maybe that should > be made the default, although I didn't like the idea of a command > dumping out pages of output when run with no flags. Nate, This doesn't work for me, at least on stable/7. The tables are not "dumped", they are "pretty-printed", but that happens only for a subset of tables - for unknown tables just a standard header is printed, the actual data is not. And it seems that while there is a way to dump "raw" DSDT, there is no way to dump other tables in a raw form. > Moore, Robert wrote: >> I don't know how to do it on freebsd. On Linux, acpidump provides an ascii dump of all tables present in the RSDT/XSDT. From there, acpixtract can be used to extract the binary tables. >> >> There should be a way to do this on freebsd, perhaps someone on this list can help. >> >> >>> -----Original Message----- >>> From: Andriy Gapon [mailto:avg@icyb.net.ua] >>> Sent: Wednesday, January 14, 2009 8:15 AM >>> To: Moore, Robert >>> Cc: freebsd-acpi@freebsd.org >>> Subject: Re: WDTT >>> >>> on 14/01/2009 18:08 Moore, Robert said the following: >>>> This file contains the disassembly of the DSDT, not a real acpidump of >>> all tables. I need to see the contents of the WDTT. >>> >>> I see - what's the easiest way to get it? >>> Maybe hack acpidump? >>> >>>>> -----Original Message----- >>>>> From: Andriy Gapon [mailto:avg@icyb.net.ua] >>>>> Sent: Wednesday, January 14, 2009 1:34 AM >>>>> To: Moore, Robert >>>>> Cc: freebsd-acpi@freebsd.org >>>>> Subject: Re: WDTT >>>>> >>>>> >>>>> Bob, >>>>> >>>>> will an output of FreeBSD acpidump (on stable/7) be sufficient or should >>>>> I use something newer/different? >>>>> >>>>> FreeBSD acpidump -dt output is here: >>>>> http://www.icyb.net.ua/~avg/dg33tl.asl.gz >>>>> >>>>> on 13/01/2009 22:46 Moore, Robert said the following: >>>>>> Could you send/post the acpidump for this machine? >>>>>> >>>>>> This "looks" like a watchdog timer table, but it is not one that I'm >>>>> familiar with. >>>>>> Thanks, >>>>>> Bob >>>>>> >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>>>>>> acpi@freebsd.org] On Behalf Of Andriy Gapon >>>>>>> Sent: Saturday, January 10, 2009 7:01 AM >>>>>>> To: freebsd-acpi@freebsd.org >>>>>>> Subject: WDTT >>>>>>> >>>>>>> >>>>>>> This is just out of curiosity - does anybody know what a table with >>>>>>> 'WDTT' signature is? >>>>>>> I see its presence, for instance, on Intel DG33TL: >>>>>>> /* >>>>>>> WDTT: Length=716, Revision=1, Checksum=38, >>>>>>> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >>>>>>> Creator ID=MSFT, Creator Revision=0x1000013 >>>>>>> */ >>>>>>> >>>>>>> P.S. please do not confuse with 'WDDT' :-) >>>>>>> >>>>>>> -- >>>>>>> Andriy Gapon >>>>>>> _______________________________________________ >>>>>>> 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" >>>>> -- >>>>> Andriy Gapon >>> -- >>> Andriy Gapon >> _______________________________________________ >> 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" > -- Andriy Gapon From avg at icyb.net.ua Wed Jan 14 09:24:07 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Jan 14 09:24:14 2009 Subject: WDTT In-Reply-To: <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> Message-ID: <496E1FB0.70001@icyb.net.ua> Here's output that should be similar to that of Linux pmtools acpidump. I must say that it doesn't look too interesting - mostly zeros. /* WDTT: Length=716, Revision=1, Checksum=38, OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, Creator ID=MSFT, Creator Revision=0x1000013 0000: 57 44 54 54 cc 02 00 00 01 26 49 4e 54 45 4c 20 WDTT.....&INTEL 0010: 44 47 33 33 54 4c 20 20 f1 01 00 00 4d 53 46 54 DG33TL ....MSFT 0020: 13 00 00 01 20 00 00 00 ff ff ff ff ff 00 00 00 .... ........... 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 01a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 01b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 01c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 01d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 01e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 01f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0210: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0230: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0240: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0250: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0260: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0270: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0280: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0290: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 02a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 02b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 02c0: 00 00 00 00 00 00 00 00 00 00 00 00 ............ */ on 14/01/2009 18:18 Moore, Robert said the following: > I don't know how to do it on freebsd. On Linux, acpidump provides an ascii dump of all tables present in the RSDT/XSDT. From there, acpixtract can be used to extract the binary tables. > > There should be a way to do this on freebsd, perhaps someone on this list can help. > > >> -----Original Message----- >> From: Andriy Gapon [mailto:avg@icyb.net.ua] >> Sent: Wednesday, January 14, 2009 8:15 AM >> To: Moore, Robert >> Cc: freebsd-acpi@freebsd.org >> Subject: Re: WDTT >> >> on 14/01/2009 18:08 Moore, Robert said the following: >>> This file contains the disassembly of the DSDT, not a real acpidump of >> all tables. I need to see the contents of the WDTT. >> >> I see - what's the easiest way to get it? >> Maybe hack acpidump? >> >>>> -----Original Message----- >>>> From: Andriy Gapon [mailto:avg@icyb.net.ua] >>>> Sent: Wednesday, January 14, 2009 1:34 AM >>>> To: Moore, Robert >>>> Cc: freebsd-acpi@freebsd.org >>>> Subject: Re: WDTT >>>> >>>> >>>> Bob, >>>> >>>> will an output of FreeBSD acpidump (on stable/7) be sufficient or should >>>> I use something newer/different? >>>> >>>> FreeBSD acpidump -dt output is here: >>>> http://www.icyb.net.ua/~avg/dg33tl.asl.gz >>>> >>>> on 13/01/2009 22:46 Moore, Robert said the following: >>>>> Could you send/post the acpidump for this machine? >>>>> >>>>> This "looks" like a watchdog timer table, but it is not one that I'm >>>> familiar with. >>>>> Thanks, >>>>> Bob >>>>> >>>>> >>>>>> -----Original Message----- >>>>>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>>>>> acpi@freebsd.org] On Behalf Of Andriy Gapon >>>>>> Sent: Saturday, January 10, 2009 7:01 AM >>>>>> To: freebsd-acpi@freebsd.org >>>>>> Subject: WDTT >>>>>> >>>>>> >>>>>> This is just out of curiosity - does anybody know what a table with >>>>>> 'WDTT' signature is? >>>>>> I see its presence, for instance, on Intel DG33TL: >>>>>> /* >>>>>> WDTT: Length=716, Revision=1, Checksum=38, >>>>>> OEMID=INTEL, OEM Table ID=DG33TL, OEM Revision=0x1f1, >>>>>> Creator ID=MSFT, Creator Revision=0x1000013 >>>>>> */ >>>>>> >>>>>> P.S. please do not confuse with 'WDDT' :-) >>>>>> >>>>>> -- >>>>>> Andriy Gapon >>>>>> _______________________________________________ >>>>>> 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" >>>> -- >>>> Andriy Gapon >> >> -- >> Andriy Gapon -- Andriy Gapon From nate at root.org Wed Jan 14 09:32:07 2009 From: nate at root.org (Nate Lawson) Date: Wed Jan 14 09:32:13 2009 Subject: WDTT In-Reply-To: <496E1DE0.5080305@icyb.net.ua> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> <496E1DE0.5080305@icyb.net.ua> Message-ID: <496E2192.5030906@root.org> Andriy Gapon wrote: > on 14/01/2009 19:06 Nate Lawson said the following: >> You need both the -t and -d flags. See the man page. Maybe that should >> be made the default, although I didn't like the idea of a command >> dumping out pages of output when run with no flags. > > Nate, > > This doesn't work for me, at least on stable/7. > The tables are not "dumped", they are "pretty-printed", but that happens > only for a subset of tables - for unknown tables just a standard header > is printed, the actual data is not. > > And it seems that while there is a way to dump "raw" DSDT, there is no > way to dump other tables in a raw form. I see. Yeah, perhaps you could add a patch that does a hex dump of unknown tables or a way to specify a table id and get the raw binary data. Perhaps -i id would be good. Example: acpidump -t See that WDTT is interesting. acpidump -i WDTT -o wdtt.bin What do you think? -- Nate From robert.moore at intel.com Wed Jan 14 09:39:09 2009 From: robert.moore at intel.com (Moore, Robert) Date: Wed Jan 14 09:39:15 2009 Subject: WDTT In-Reply-To: <496E2192.5030906@root.org> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> <496E1DE0.5080305@icyb.net.ua> <496E2192.5030906@root.org> Message-ID: <4911F71203A09E4D9981D27F9D8308580E4EAB6A@orsmsx503.amr.corp.intel.com> What would be most helpful for us over here in ACPICA land is if your acpidump worked exactly like the Linux version. That is the most useful for debugging, and if you look at the linux bugzilla entries, you'll see that it is usually the very first thing we ask for when there is a problem. The acpixtract utility is now provided with the ACPICA source, it is used to pull the binary tables from the acpidump. I would like to make an ACPICA version of acpidump that is OS-independent so that there isn't a duplication of tools. >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Nate Lawson >Sent: Wednesday, January 14, 2009 9:32 AM >To: Andriy Gapon >Cc: freebsd-acpi@freebsd.org >Subject: Re: WDTT > >Andriy Gapon wrote: >> on 14/01/2009 19:06 Nate Lawson said the following: >>> You need both the -t and -d flags. See the man page. Maybe that should >>> be made the default, although I didn't like the idea of a command >>> dumping out pages of output when run with no flags. >> >> Nate, >> >> This doesn't work for me, at least on stable/7. >> The tables are not "dumped", they are "pretty-printed", but that happens >> only for a subset of tables - for unknown tables just a standard header >> is printed, the actual data is not. >> >> And it seems that while there is a way to dump "raw" DSDT, there is no >> way to dump other tables in a raw form. > >I see. Yeah, perhaps you could add a patch that does a hex dump of >unknown tables or a way to specify a table id and get the raw binary >data. Perhaps -i id would be good. > >Example: > acpidump -t >See that WDTT is interesting. > acpidump -i WDTT -o wdtt.bin > >What do you think? > >-- >Nate >_______________________________________________ >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" From nate at root.org Wed Jan 14 09:45:41 2009 From: nate at root.org (Nate Lawson) Date: Wed Jan 14 09:45:47 2009 Subject: WDTT In-Reply-To: <4911F71203A09E4D9981D27F9D8308580E4EAB6A@orsmsx503.amr.corp.intel.com> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> <496E1DE0.5080305@icyb.net.ua> <496E2192.5030906@root.org> <4911F71203A09E4D9981D27F9D8308580E4EAB6A@orsmsx503.amr.corp.intel.com> Message-ID: <496E24BF.50206@root.org> Last time I looked, the Linux one did no parsing of extended tables, just dumped binary data. It only parsed ASL. This was not very useful since our PRs are mostly email based, and decoding a binary attachment just to find the SCI irq settings in the MADT was untenable. Has that changed? -Nate Moore, Robert wrote: > What would be most helpful for us over here in ACPICA land is if your acpidump worked exactly like the Linux version. That is the most useful for debugging, and if you look at the linux bugzilla entries, you'll see that it is usually the very first thing we ask for when there is a problem. > > The acpixtract utility is now provided with the ACPICA source, it is used to pull the binary tables from the acpidump. > > I would like to make an ACPICA version of acpidump that is OS-independent so that there isn't a duplication of tools. > > > >> -----Original Message----- >> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >> acpi@freebsd.org] On Behalf Of Nate Lawson >> Sent: Wednesday, January 14, 2009 9:32 AM >> To: Andriy Gapon >> Cc: freebsd-acpi@freebsd.org >> Subject: Re: WDTT >> >> Andriy Gapon wrote: >>> on 14/01/2009 19:06 Nate Lawson said the following: >>>> You need both the -t and -d flags. See the man page. Maybe that should >>>> be made the default, although I didn't like the idea of a command >>>> dumping out pages of output when run with no flags. >>> Nate, >>> >>> This doesn't work for me, at least on stable/7. >>> The tables are not "dumped", they are "pretty-printed", but that happens >>> only for a subset of tables - for unknown tables just a standard header >>> is printed, the actual data is not. >>> >>> And it seems that while there is a way to dump "raw" DSDT, there is no >>> way to dump other tables in a raw form. >> I see. Yeah, perhaps you could add a patch that does a hex dump of >> unknown tables or a way to specify a table id and get the raw binary >> data. Perhaps -i id would be good. >> >> Example: >> acpidump -t >> See that WDTT is interesting. >> acpidump -i WDTT -o wdtt.bin >> >> What do you think? >> >> -- >> Nate >> _______________________________________________ >> 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" -- Nate From avg at icyb.net.ua Wed Jan 14 09:49:38 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Jan 14 09:49:45 2009 Subject: WDTT In-Reply-To: <496E24BF.50206@root.org> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> <496E1DE0.5080305@icyb.net.ua> <496E2192.5030906@root.org> <4911F71203A09E4D9981D27F9D8308580E4EAB6A@orsmsx503.amr.corp.intel.com> <496E24BF.50206@root.org> Message-ID: <496E25AB.8050900@icyb.net.ua> on 14/01/2009 19:45 Nate Lawson said the following: > Last time I looked, the Linux one did no parsing of extended tables, > just dumped binary data. It only parsed ASL. This was not very useful > since our PRs are mostly email based, and decoding a binary attachment > just to find the SCI irq settings in the MADT was untenable. > > Has that changed? Yes, it looks like binary data piped through hd/hexdump with small headings for each table. > Moore, Robert wrote: >> What would be most helpful for us over here in ACPICA land is if your acpidump worked exactly like the Linux version. That is the most useful for debugging, and if you look at the linux bugzilla entries, you'll see that it is usually the very first thing we ask for when there is a problem. >> >> The acpixtract utility is now provided with the ACPICA source, it is used to pull the binary tables from the acpidump. >> >> I would like to make an ACPICA version of acpidump that is OS-independent so that there isn't a duplication of tools. >> >> >> >>> -----Original Message----- >>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>> acpi@freebsd.org] On Behalf Of Nate Lawson >>> Sent: Wednesday, January 14, 2009 9:32 AM >>> To: Andriy Gapon >>> Cc: freebsd-acpi@freebsd.org >>> Subject: Re: WDTT >>> >>> Andriy Gapon wrote: >>>> on 14/01/2009 19:06 Nate Lawson said the following: >>>>> You need both the -t and -d flags. See the man page. Maybe that should >>>>> be made the default, although I didn't like the idea of a command >>>>> dumping out pages of output when run with no flags. >>>> Nate, >>>> >>>> This doesn't work for me, at least on stable/7. >>>> The tables are not "dumped", they are "pretty-printed", but that happens >>>> only for a subset of tables - for unknown tables just a standard header >>>> is printed, the actual data is not. >>>> >>>> And it seems that while there is a way to dump "raw" DSDT, there is no >>>> way to dump other tables in a raw form. >>> I see. Yeah, perhaps you could add a patch that does a hex dump of >>> unknown tables or a way to specify a table id and get the raw binary >>> data. Perhaps -i id would be good. >>> >>> Example: >>> acpidump -t >>> See that WDTT is interesting. >>> acpidump -i WDTT -o wdtt.bin >>> >>> What do you think? >>> >>> -- >>> Nate >>> _______________________________________________ >>> 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" > -- Andriy Gapon From nate at root.org Wed Jan 14 10:19:15 2009 From: nate at root.org (Nate Lawson) Date: Wed Jan 14 10:19:26 2009 Subject: WDTT In-Reply-To: <496E25AB.8050900@icyb.net.ua> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> <496E1DE0.5080305@icyb.net.ua> <496E2192.5030906@root.org> <4911F71203A09E4D9981D27F9D8308580E4EAB6A@orsmsx503.amr.corp.intel.com> <496E24BF.50206@root.org> <496E25AB.8050900@icyb.net.ua> Message-ID: <496E2C9B.3000907@root.org> Andriy Gapon wrote: > on 14/01/2009 19:45 Nate Lawson said the following: >> Last time I looked, the Linux one did no parsing of extended tables, >> just dumped binary data. It only parsed ASL. This was not very useful >> since our PRs are mostly email based, and decoding a binary attachment >> just to find the SCI irq settings in the MADT was untenable. >> >> Has that changed? > > Yes, it looks like binary data piped through hd/hexdump with small > headings for each table. > >> Moore, Robert wrote: >>> What would be most helpful for us over here in ACPICA land is if your acpidump worked exactly like the Linux version. That is the most useful for debugging, and if you look at the linux bugzilla entries, you'll see that it is usually the very first thing we ask for when there is a problem. >>> >>> The acpixtract utility is now provided with the ACPICA source, it is used to pull the binary tables from the acpidump. >>> >>> I would like to make an ACPICA version of acpidump that is OS-independent so that there isn't a duplication of tools. Then I'd prefer we just keep our nice parsing for tables we know of and print a hexdump by default for tables we don't. Seems simple and compatible enough. Care to provide a patch? -- Nate From robert.moore at intel.com Wed Jan 14 10:33:56 2009 From: robert.moore at intel.com (Moore, Robert) Date: Wed Jan 14 10:34:03 2009 Subject: WDTT In-Reply-To: <496E2C9B.3000907@root.org> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> <496E1DE0.5080305@icyb.net.ua> <496E2192.5030906@root.org> <4911F71203A09E4D9981D27F9D8308580E4EAB6A@orsmsx503.amr.corp.intel.com> <496E24BF.50206@root.org> <496E25AB.8050900@icyb.net.ua> <496E2C9B.3000907@root.org> Message-ID: <4911F71203A09E4D9981D27F9D8308580E4EAC9F@orsmsx503.amr.corp.intel.com> >Then I'd prefer we just keep our nice parsing for tables we know of and I think that even this may be obsolete. iASL -d will now disassemble all known ACPI tables, including both tables that contain AML and those that contain only data. For example, /* * Intel ACPI Component Architecture * AML Disassembler version 20081204 * * Disassembly of MCFG.dat, Wed Jan 14 10:32:45 2009 * * ACPI Data Table [MCFG] * * Format: [HexOffset DecimalOffset ByteLength] FieldName : FieldValue */ [000h 000 4] Signature : "MCFG" /* Memory Mapped Configuration table */ [004h 004 4] Table Length : 0000003C [008h 008 1] Revision : 01 [009h 009 1] Checksum : 84 [00Ah 010 6] Oem ID : "HP " [010h 016 8] Oem Table ID : "0944 " [018h 024 4] Oem Revision : 00000001 [01Ch 028 4] Asl Compiler ID : "HP " [020h 032 4] Asl Compiler Revision : 00000001 [024h 036 8] Reserved : 0000000000000000 [02Ch 044 8] Base Address : 00000000E0000000 [034h 052 2] Segment Group Number : 0000 [036h 054 1] Start Bus Number : 00 [037h 055 1] End Bus Number : FF [038h 056 4] Reserved : 00000000 Raw Table Data 0000: 4D 43 46 47 3C 00 00 00 01 84 48 50 20 20 20 20 MCFG<.....HP 0010: 30 39 34 34 20 20 20 20 01 00 00 00 48 50 20 20 0944 ....HP 0020: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 E0 ................ 0030: 00 00 00 00 00 00 00 FF 00 00 00 00 ............ >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Nate Lawson >Sent: Wednesday, January 14, 2009 10:19 AM >To: Andriy Gapon >Cc: freebsd-acpi@freebsd.org; Moore, Robert >Subject: Re: WDTT > >Andriy Gapon wrote: >> on 14/01/2009 19:45 Nate Lawson said the following: >>> Last time I looked, the Linux one did no parsing of extended tables, >>> just dumped binary data. It only parsed ASL. This was not very useful >>> since our PRs are mostly email based, and decoding a binary attachment >>> just to find the SCI irq settings in the MADT was untenable. >>> >>> Has that changed? >> >> Yes, it looks like binary data piped through hd/hexdump with small >> headings for each table. >> >>> Moore, Robert wrote: >>>> What would be most helpful for us over here in ACPICA land is if your >acpidump worked exactly like the Linux version. That is the most useful for >debugging, and if you look at the linux bugzilla entries, you'll see that >it is usually the very first thing we ask for when there is a problem. >>>> >>>> The acpixtract utility is now provided with the ACPICA source, it is >used to pull the binary tables from the acpidump. >>>> >>>> I would like to make an ACPICA version of acpidump that is OS- >independent so that there isn't a duplication of tools. > >Then I'd prefer we just keep our nice parsing for tables we know of and >print a hexdump by default for tables we don't. Seems simple and >compatible enough. > >Care to provide a patch? > >-- >Nate >_______________________________________________ >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" From robert.moore at intel.com Wed Jan 14 09:51:11 2009 From: robert.moore at intel.com (Moore, Robert) Date: Wed Jan 14 10:45:18 2009 Subject: WDTT In-Reply-To: <496E24BF.50206@root.org> References: <4968B843.8020108@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA343@orsmsx503.amr.corp.intel.com> <496DB197.5020100@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9B3@orsmsx503.amr.corp.intel.com> <496E0F90.3000507@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308580E4EA9D1@orsmsx503.amr.corp.intel.com> <496E1B90.8080406@root.org> <496E1DE0.5080305@icyb.net.ua> <496E2192.5030906@root.org> <4911F71203A09E4D9981D27F9D8308580E4EAB6A@orsmsx503.amr.corp.intel.com> <496E24BF.50206@root.org> Message-ID: <4911F71203A09E4D9981D27F9D8308580E4EABB9@orsmsx503.amr.corp.intel.com> The linux acpidump will dump all tables contained in both the RSDT and the XSDT, in hex/ascii format (not binary). Acpixtract is then used to recreate the actual binary tables from the acpidump. I've attached an example linux acpidump. >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Nate Lawson >Sent: Wednesday, January 14, 2009 9:46 AM >To: Moore, Robert >Cc: freebsd-acpi@freebsd.org; Andriy Gapon >Subject: Re: WDTT > >Last time I looked, the Linux one did no parsing of extended tables, >just dumped binary data. It only parsed ASL. This was not very useful >since our PRs are mostly email based, and decoding a binary attachment >just to find the SCI irq settings in the MADT was untenable. > >Has that changed? > >-Nate > >Moore, Robert wrote: >> What would be most helpful for us over here in ACPICA land is if your >acpidump worked exactly like the Linux version. That is the most useful for >debugging, and if you look at the linux bugzilla entries, you'll see that >it is usually the very first thing we ask for when there is a problem. >> >> The acpixtract utility is now provided with the ACPICA source, it is used >to pull the binary tables from the acpidump. >> >> I would like to make an ACPICA version of acpidump that is OS-independent >so that there isn't a duplication of tools. >> >> >> >>> -----Original Message----- >>> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>> acpi@freebsd.org] On Behalf Of Nate Lawson >>> Sent: Wednesday, January 14, 2009 9:32 AM >>> To: Andriy Gapon >>> Cc: freebsd-acpi@freebsd.org >>> Subject: Re: WDTT >>> >>> Andriy Gapon wrote: >>>> on 14/01/2009 19:06 Nate Lawson said the following: >>>>> You need both the -t and -d flags. See the man page. Maybe that should >>>>> be made the default, although I didn't like the idea of a command >>>>> dumping out pages of output when run with no flags. >>>> Nate, >>>> >>>> This doesn't work for me, at least on stable/7. >>>> The tables are not "dumped", they are "pretty-printed", but that >happens >>>> only for a subset of tables - for unknown tables just a standard header >>>> is printed, the actual data is not. >>>> >>>> And it seems that while there is a way to dump "raw" DSDT, there is no >>>> way to dump other tables in a raw form. >>> I see. Yeah, perhaps you could add a patch that does a hex dump of >>> unknown tables or a way to specify a table id and get the raw binary >>> data. Perhaps -i id would be good. >>> >>> Example: >>> acpidump -t >>> See that WDTT is interesting. >>> acpidump -i WDTT -o wdtt.bin >>> >>> What do you think? >>> >>> -- >>> Nate >>> _______________________________________________ >>> 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" > >-- >Nate >_______________________________________________ >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" -------------- next part -------------- DSDT @ 0x3def3180 0000: 44 53 44 54 a9 7f 00 00 01 04 4e 56 49 44 49 41 DSDT......NVIDIA 0010: 41 57 52 44 41 43 50 49 00 10 00 00 4d 53 46 54 AWRDACPI....MSFT 0020: 0e 00 00 01 10 2c 5c 5f 50 52 5f 5b 83 11 5c 2e .....,\_PR_[..\. 0030: 5f 50 52 5f 43 50 55 30 00 00 00 00 00 00 5b 83 _PR_CPU0......[. 0040: 11 5c 2e 5f 50 52 5f 43 50 55 31 01 00 00 00 00 .\._PR_CPU1..... 0050: 00 08 5c 5f 53 30 5f 12 0a 04 0a 00 0a 00 0a 00 ..\_S0_......... 0060: 0a 00 08 5c 5f 53 31 5f 12 0a 04 0a 01 0a 00 0a ...\_S1_........ 0070: 00 0a 00 08 5c 5f 53 33 5f 12 0a 04 0a 05 0a 00 ....\_S3_....... 0080: 0a 00 0a 00 08 5c 5f 53 34 5f 12 0a 04 0a 06 0a .....\_S4_...... 0090: 00 0a 00 0a 00 08 5c 5f 53 35 5f 12 0a 04 0a 07 ......\_S5_..... 00a0: 0a 00 0a 00 0a 00 5b 80 5c 44 45 42 47 01 0b 80 ......[.\DEBG... 00b0: 10 0a 01 5b 81 0c 5c 44 45 42 47 01 44 42 47 31 ...[..\DEBG.DBG1 00c0: 08 5b 80 4b 42 43 5f 01 0a 64 0a 01 5b 81 0b 4b .[.KBC_..d..[..K 00d0: 42 43 5f 01 4b 43 4d 44 08 5b 80 4b 42 43 44 01 BC_.KCMD.[.KBCD. 00e0: 0a 60 0a 01 5b 81 0b 4b 42 43 44 01 4b 44 41 54 .`..[..KBCD.KDAT 00f0: 08 5b 80 45 58 54 4d 00 0c 30 f8 0f 00 0a 10 5b .[.EXTM..0.....[ 0100: 81 29 45 58 54 4d 02 52 4f 4d 31 10 52 4d 53 31 .)EXTM.ROM1.RMS1 0110: 10 52 4f 4d 32 10 52 4d 53 32 10 52 4f 4d 33 10 .ROM2.RMS2.ROM3. 0120: 52 4d 53 33 10 41 4d 45 4d 20 5b 80 5c 50 4d 31 RMS3.AMEM [.\PM1 0130: 53 01 0b 00 40 0a 02 5b 81 1c 5c 50 4d 31 53 01 S...@..[..\PM1S. 0140: 00 08 50 42 54 53 01 00 01 52 54 43 53 01 00 04 ..PBTS...RTCS... 0150: 57 41 4b 53 01 5b 80 45 4c 43 52 01 0b d0 04 0a WAKS.[.ELCR..... 0160: 02 5b 81 10 45 4c 43 52 01 45 4c 43 31 08 45 4c .[..ELCR.ELC1.EL 0170: 43 32 08 5b 80 5c 53 54 55 53 01 0b 00 44 0a 04 C2.[.\STUS...D.. 0180: 5b 81 0c 5c 53 54 55 53 01 47 5f 53 54 20 5b 80 [..\STUS.G_ST [. 0190: 5c 47 50 53 30 01 0b 20 40 0a 04 5b 81 1b 5c 47 \GPS0.. @..[..\G 01a0: 50 53 30 01 47 53 30 30 08 47 53 30 31 08 47 53 PS0.GS00.GS01.GS 01b0: 30 32 08 47 53 30 33 08 5b 80 5c 50 32 30 53 01 02.GS03.[.\P20S. 01c0: 0b 20 40 0a 04 5b 81 0c 5c 50 32 30 53 01 50 5f . @..[..\P20S.P_ 01d0: 32 30 20 5b 80 5c 53 4d 49 43 01 0b 2e 44 0a 01 20 [.\SMIC...D.. 01e0: 5b 81 0c 5c 53 4d 49 43 01 53 43 50 5f 08 5b 80 [..\SMIC.SCP_.[. 01f0: 5c 47 50 31 5f 01 0b c0 44 0a 3d 5b 81 46 13 5c \GP1_...D.=[.F.\ 0200: 47 50 31 5f 01 47 50 30 30 08 47 50 30 31 08 47 GP1_.GP00.GP01.G 0210: 50 30 32 08 47 50 30 33 08 47 50 30 34 08 47 50 P02.GP03.GP04.GP 0220: 30 35 08 47 50 30 36 08 47 50 30 37 08 47 50 30 05.GP06.GP07.GP0 0230: 38 08 47 50 30 39 08 47 50 31 30 08 47 50 31 31 8.GP09.GP10.GP11 0240: 08 47 50 31 32 08 47 50 31 33 08 47 50 31 34 08 .GP12.GP13.GP14. 0250: 47 50 31 35 08 47 50 31 36 08 47 50 31 37 08 47 GP15.GP16.GP17.G 0260: 50 31 38 08 47 50 31 39 08 47 50 32 30 08 47 50 P18.GP19.GP20.GP 0270: 32 31 08 47 50 32 32 08 00 08 47 50 32 34 08 47 21.GP22...GP24.G 0280: 50 32 35 08 47 50 32 36 08 47 50 32 37 08 47 50 P25.GP26.GP27.GP 0290: 32 38 08 47 50 32 39 08 47 50 33 30 08 47 50 33 28.GP29.GP30.GP3 02a0: 31 08 47 50 33 32 08 47 50 33 33 08 47 50 33 34 1.GP32.GP33.GP34 02b0: 08 47 50 33 35 08 47 50 33 36 08 47 50 33 37 08 .GP35.GP36.GP37. 02c0: 47 50 33 38 08 47 50 33 39 08 47 50 34 30 08 47 GP38.GP39.GP40.G 02d0: 50 34 31 08 47 50 34 32 08 47 50 34 33 08 47 50 P41.GP42.GP43.GP 02e0: 34 34 08 47 50 34 35 08 47 50 34 36 08 47 50 34 44.GP45.GP46.GP4 02f0: 37 08 47 50 34 38 08 47 50 34 39 08 47 50 35 30 7.GP48.GP49.GP50 0300: 08 47 50 35 31 08 47 50 35 32 08 47 50 35 33 08 .GP51.GP52.GP53. 0310: 47 50 35 34 08 47 50 35 35 08 47 50 35 36 08 47 GP54.GP55.GP56.G 0320: 50 35 37 08 47 50 35 38 08 47 50 35 39 08 47 50 P57.GP58.GP59.GP 0330: 36 30 08 08 4f 53 46 58 0a 01 08 4f 53 46 4c 0a 60..OSFX...OSFL. 0340: 01 14 41 05 53 54 52 43 02 a0 0a 92 93 87 68 87 ..A.STRC......h. 0350: 69 a4 0a 00 72 87 68 0a 01 60 08 42 55 46 30 11 i...r.h..`.BUF0. 0360: 02 60 08 42 55 46 31 11 02 60 70 68 42 55 46 30 .`.BUF1..`phBUF0 0370: 70 69 42 55 46 31 a2 1a 60 76 60 a0 15 92 93 83 piBUF1..`v`..... 0380: 88 42 55 46 30 60 00 83 88 42 55 46 31 60 00 a4 .BUF0`...BUF1`.. 0390: 00 a4 01 5b 80 52 54 43 4d 01 0a 70 0a 02 5b 81 ...[.RTCM..p..[. 03a0: 10 52 54 43 4d 01 43 4d 49 4e 08 43 4d 44 41 08 .RTCM.CMIN.CMDA. 03b0: 5b 86 12 43 4d 49 4e 43 4d 44 41 01 00 48 07 53 [..CMINCMDA..H.S 03c0: 48 55 54 08 5b 80 49 4e 46 4f 00 0c 40 f8 0f 00 HUT.[.INFO..@... 03d0: 0a 01 5b 81 24 49 4e 46 4f 01 4b 42 44 49 01 52 ..[.$INFO.KBDI.R 03e0: 54 43 57 01 50 53 32 46 01 49 52 46 4c 02 44 49 TCW.PS2F.IRFL.DI 03f0: 53 45 01 53 53 48 55 01 5b 80 42 45 45 50 01 0a SE.SSHU.[.BEEP.. 0400: 61 0a 01 5b 81 0b 42 45 45 50 01 53 31 42 5f 08 a..[..BEEP.S1B_. 0410: 5b 80 43 4f 4e 54 01 0a 40 0a 04 5b 81 1a 43 4f [.CONT..@..[..CO 0420: 4e 54 01 43 4e 54 30 08 43 4e 54 31 08 43 4e 54 NT.CNT0.CNT1.CNT 0430: 32 08 43 54 52 4c 08 14 43 06 53 50 4b 52 01 70 2.CTRL..C.SPKR.p 0440: 53 31 42 5f 60 70 0a b6 43 54 52 4c 70 0a 55 43 S1B_`p..CTRLp.UC 0450: 4e 54 32 70 0a 03 43 4e 54 32 70 68 62 a2 37 94 NT2p..CNT2phb.7. 0460: 62 0a 00 7d 53 31 42 5f 0a 03 53 31 42 5f 70 0b b..}S1B_..S1B_p. 0470: ff 5f 63 a2 07 94 63 0a 00 76 63 7b 53 31 42 5f ._c...c..vc{S1B_ 0480: 0a fc 53 31 42 5f 70 0b ff 0e 63 a2 07 94 63 0a ..S1B_p...c...c. 0490: 00 76 63 76 62 70 60 53 31 42 5f 5b 80 41 4d 44 .vcvbp`S1B_[.AMD 04a0: 4c 00 0c ea ff 0f 00 0a 01 5b 81 19 41 4d 44 4c L........[..AMDL 04b0: 01 00 01 41 57 45 4e 01 00 01 00 01 00 01 00 01 ...AWEN......... 04c0: 00 01 00 01 10 39 5c 5f 53 42 5f 5b 82 31 5c 41 .....9\_SB_[.1\A 04d0: 57 59 5f 08 5f 48 49 44 0d 41 57 59 30 30 30 31 WY_._HID.AWY0001 04e0: 00 14 06 53 4d 4f 44 01 14 15 5f 53 54 41 00 a0 ...SMOD..._STA.. 04f0: 0b 93 41 57 45 4e 0a 00 a4 0a 00 a4 0a 0f 10 17 ..AWEN.......... 0500: 5c 00 08 50 49 43 46 0a 00 14 0c 5f 50 49 43 01 \..PICF...._PIC. 0510: 70 68 50 49 43 46 08 53 49 44 34 0a 00 08 53 4c phPICF.SID4...SL 0520: 47 30 0a 00 08 53 4c 47 31 0a 00 08 53 4c 47 32 G0...SLG1...SLG2 0530: 0a 00 08 53 4c 47 33 0a 00 08 53 4c 47 34 0a 00 ...SLG3...SLG4.. 0540: 08 53 4c 47 35 0a 00 08 53 4c 47 36 0a 00 08 53 .SLG5...SLG6...S 0550: 4c 47 37 0a 00 08 53 4c 47 38 0a 00 08 53 4c 47 LG7...SLG8...SLG 0560: 39 0a 00 08 53 4c 47 41 0a 00 08 53 49 44 35 0a 9...SLGA...SID5. 0570: 00 08 53 53 4d 30 0a 00 08 53 53 4d 31 0a 00 08 ..SSM0...SSM1... 0580: 53 53 4d 32 0a 00 08 53 53 4d 33 0a 00 08 53 53 SSM2...SSM3...SS 0590: 4d 34 0a 00 08 53 55 41 30 0a 00 08 53 55 42 30 M4...SUA0...SUB0 05a0: 0a 00 08 53 58 5f 5f 0a 00 08 53 46 4c 47 0a 00 ...SX__...SFLG.. 05b0: 08 53 49 44 30 0a 00 08 53 49 44 31 0a 00 08 53 .SID0...SID1...S 05c0: 49 44 32 0a 00 08 53 49 44 33 0a 00 14 47 0d 5c ID2...SID3...G.\ 05d0: 5f 50 54 53 01 70 68 60 70 60 53 58 5f 5f 7d 68 _PTS.ph`p`SX__}h 05e0: 0a f0 60 70 60 44 42 47 31 4f 53 54 50 70 5c 2f ..`p`DBG1OSTPp\/ 05f0: 04 5f 53 42 5f 50 43 49 30 49 44 45 30 49 44 32 ._SB_PCI0IDE0ID2 0600: 30 53 49 44 30 70 5c 2f 04 5f 53 42 5f 50 43 49 0SID0p\/._SB_PCI 0610: 30 49 44 45 30 49 44 54 53 53 49 44 31 70 5c 2f 0IDE0IDTSSID1p\/ 0620: 04 5f 53 42 5f 50 43 49 30 49 44 45 30 49 44 54 ._SB_PCI0IDE0IDT 0630: 50 53 49 44 32 70 5c 2f 04 5f 53 42 5f 50 43 49 PSID2p\/._SB_PCI 0640: 30 49 44 45 30 49 44 32 32 53 49 44 33 70 5c 2f 0IDE0ID22SID3p\/ 0650: 04 5f 53 42 5f 50 43 49 30 49 44 45 30 55 4d 53 ._SB_PCI0IDE0UMS 0660: 53 53 49 44 34 70 5c 2f 04 5f 53 42 5f 50 43 49 SSID4p\/._SB_PCI 0670: 30 49 44 45 30 55 4d 53 50 53 49 44 35 a0 05 93 0IDE0UMSPSID5... 0680: 68 0a 01 a0 05 93 68 0a 03 a0 05 93 68 0a 04 a0 h.....h.....h... 0690: 14 93 68 0a 05 a0 0e 92 93 4f 53 46 4c 0a 00 5b ..h......OSFL..[ 06a0: 22 0b f4 01 14 4e 05 5c 5f 57 41 4b 01 70 0a ff "....N.\_WAK.p.. 06b0: 44 42 47 31 70 0a 00 53 46 4c 47 a0 15 93 52 54 DBG1p..SFLG...RT 06c0: 43 57 0a 00 86 5c 2e 5f 53 42 5f 50 57 52 42 0a CW...\._SB_PWRB. 06d0: 02 86 5c 2f 03 5f 53 42 5f 50 43 49 30 55 53 42 ..\/._SB_PCI0USB 06e0: 30 0a 00 a0 1f 92 95 4f 53 46 4c 0a 01 70 0a 00 0......OSFL..p.. 06f0: 5c 2f 04 5f 53 42 5f 50 43 49 30 53 4d 42 30 53 \/._SB_PCI0SMB0S 0700: 4d 50 4d 10 49 04 5c 5f 53 49 5f 14 20 5f 4d 53 MPM.I.\_SI_. _MS 0710: 47 01 70 0d 3d 3d 3d 3d 20 4d 53 47 20 57 6f 72 G.p.==== MSG Wor 0720: 6b 69 6e 67 20 3d 3d 3d 3d 00 5b 31 14 20 5f 53 king ====.[1. _S 0730: 53 54 01 70 0d 3d 3d 3d 3d 20 53 53 54 20 57 6f ST.p.==== SST Wo 0740: 72 6b 69 6e 67 20 3d 3d 3d 3d 00 5b 31 10 4d 17 rking ====.[1.M. 0750: 5c 5f 47 50 45 14 4e 09 5f 4c 31 31 00 70 0a 02 \_GPE.N._L11.p.. 0760: 47 53 30 32 a0 2f 92 93 50 45 56 41 0b ff ff a0 GS02./..PEVA.... 0770: 24 50 45 53 41 a2 0c 50 45 53 41 70 0a 01 50 45 $PESA..PESAp..PE 0780: 53 41 86 5c 2f 03 5f 53 42 5f 50 43 49 30 58 56 SA.\/._SB_PCI0XV 0790: 52 41 0a 02 a0 2f 92 93 50 45 56 42 0b ff ff a0 RA.../..PEVB.... 07a0: 24 50 45 53 42 a2 0c 50 45 53 42 70 0a 01 50 45 $PESB..PESBp..PE 07b0: 53 42 86 5c 2f 03 5f 53 42 5f 50 43 49 30 58 56 SB.\/._SB_PCI0XV 07c0: 52 42 0a 02 a0 2f 92 93 50 45 56 43 0b ff ff a0 RB.../..PEVC.... 07d0: 24 50 45 53 43 a2 0c 50 45 53 43 70 0a 01 50 45 $PESC..PESCp..PE 07e0: 53 43 86 5c 2f 03 5f 53 42 5f 50 43 49 30 58 56 SC.\/._SB_PCI0XV 07f0: 52 43 0a 02 14 18 5f 4c 30 30 00 86 5c 2f 03 5f RC...._L00..\/._ 0800: 53 42 5f 50 43 49 30 48 55 42 30 0a 02 14 2a 5f SB_PCI0HUB0...*_ 0810: 4c 30 33 00 86 5c 2f 03 5f 53 42 5f 50 43 49 30 L03..\/._SB_PCI0 0820: 55 41 52 31 0a 02 86 5c 2f 03 5f 53 42 5f 50 43 UAR1...\/._SB_PC 0830: 49 30 55 41 52 32 0a 02 14 18 5f 4c 30 42 00 86 I0UAR2...._L0B.. 0840: 5c 2f 03 5f 53 42 5f 50 43 49 30 4d 4d 41 43 0a \/._SB_PCI0MMAC. 0850: 02 14 18 5f 4c 30 44 00 86 5c 2f 03 5f 53 42 5f ..._L0D..\/._SB_ 0860: 50 43 49 30 55 53 42 30 0a 02 14 18 5f 4c 30 35 PCI0USB0...._L05 0870: 00 86 5c 2f 03 5f 53 42 5f 50 43 49 30 55 53 42 ..\/._SB_PCI0USB 0880: 32 0a 02 14 18 5f 4c 30 37 00 86 5c 2f 03 5f 53 2...._L07..\/._S 0890: 42 5f 50 43 49 30 4d 4d 43 49 0a 02 14 15 5f 4c B_PCI0MMCI...._L 08a0: 31 30 00 5c 2f 03 5f 53 42 5f 50 43 49 30 50 53 10.\/._SB_PCI0PS 08b0: 32 57 14 18 5f 4c 31 35 00 86 5c 2f 03 5f 53 42 2W.._L15..\/._SB 08c0: 5f 50 43 49 30 41 5a 41 44 0a 02 10 82 39 07 5c _PCI0AZAD....9.\ 08d0: 5f 53 42 5f 5b 82 19 50 57 52 42 08 5f 48 49 44 _SB_[..PWRB._HID 08e0: 0c 41 d0 0c 0c 14 09 5f 53 54 41 00 a4 0a 0b 5b .A....._STA....[ 08f0: 82 85 03 07 50 43 49 30 08 5f 48 49 44 0c 41 d0 ....PCI0._HID.A. 0900: 0a 08 08 5f 43 49 44 0c 41 d0 0a 03 08 5f 41 44 ..._CID.A...._AD 0910: 52 0a 00 08 5f 55 49 44 0a 01 08 5f 42 42 4e 0a R..._UID..._BBN. 0920: 00 08 50 43 49 41 0a 00 14 12 5f 52 45 47 02 a0 ..PCIA...._REG.. 0930: 0b 93 68 0a 02 70 69 50 43 49 41 5b 82 4f 0b 4d ..h..piPCIA[.O.M 0940: 42 49 4f 08 5f 48 49 44 0c 41 d0 0c 02 08 5f 55 BIO._HID.A...._U 0950: 49 44 0a 05 14 47 0a 5f 43 52 53 00 08 42 55 46 ID...G._CRS..BUF 0960: 30 11 42 05 0a 4e 47 01 00 40 00 40 01 80 47 01 0.B..NG..@.@..G. 0970: 80 40 80 40 01 80 47 01 00 44 00 44 01 80 47 01 .@.@..G..D.D..G. 0980: 80 44 80 44 01 80 47 01 00 48 00 48 01 80 47 01 .D.D..G..H.H..G. 0990: 80 48 80 48 01 80 86 09 00 01 00 00 00 00 00 00 .H.H............ 09a0: 00 00 47 01 00 20 00 20 01 80 47 01 80 20 80 20 ..G.. . ..G.. . 09b0: 01 80 79 00 8a 42 55 46 30 0a 34 47 55 42 41 8a ..y..BUF0.4GUBA. 09c0: 42 55 46 30 0a 38 47 55 42 4c a0 2c 92 93 49 47 BUF0.8GUBL.,..IG 09d0: 55 42 0c ff ff ff ff a0 1f 49 47 55 42 70 49 47 UB.......IGUBpIG 09e0: 55 42 60 79 60 0a 07 60 70 60 47 55 42 41 70 49 UB`y`..`p`GUBApI 09f0: 47 55 4c 47 55 42 4c a4 42 55 46 30 08 4e 41 54 GULGUBL.BUF0.NAT 0a00: 41 12 07 01 0c 00 00 0d 00 14 17 5f 53 33 44 00 A.........._S3D. 0a10: a0 0b 93 4f 53 46 4c 0a 02 a4 0a 02 a1 04 a4 0a ...OSFL......... 0a20: 03 14 09 5f 53 54 41 00 a4 0a 0f 5b 80 4c 44 54 ..._STA....[.LDT 0a30: 33 02 0a 6c 0a 04 5b 81 0b 4c 44 54 33 03 55 43 3..l..[..LDT3.UC 0a40: 46 47 20 14 8d 24 01 5f 43 52 53 00 08 42 55 46 FG ..$._CRS..BUF 0a50: 30 11 48 0e 0a e4 88 0d 00 02 00 00 00 00 00 00 0.H............. 0a60: 00 00 00 00 00 00 47 01 f8 0c f8 0c 01 08 88 0d ......G......... 0a70: 00 01 0c 03 00 00 00 00 af 03 00 00 b0 03 88 0d ................ 0a80: 00 01 0c 03 00 00 e0 03 f7 0c 00 00 18 09 88 0d ................ 0a90: 00 01 0c 03 00 00 00 00 00 00 00 00 00 00 88 0d ................ 0aa0: 00 01 0c 03 00 00 00 00 00 00 00 00 00 00 8a 2b ...............+ 0ab0: 00 00 0c 03 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0ac0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0ad0: 00 00 00 00 00 00 00 00 00 00 00 00 8a 2b 00 00 .............+.. 0ae0: 0c 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0af0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0b00: 00 00 00 00 00 00 00 00 00 00 8a 2b 00 00 0c 03 ...........+.... 0b10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0b20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0b30: 00 00 00 00 00 00 00 00 79 00 8b 42 55 46 30 0a ........y..BUF0. 0b40: 08 42 31 4d 4e 8b 42 55 46 30 0a 0a 42 31 4d 58 .B1MN.BUF0..B1MX 0b50: 8b 42 55 46 30 0a 0e 42 31 4c 4e 7b 5c 2f 04 5f .BUF0..B1LN{\/._ 0b60: 53 42 5f 50 43 49 30 4b 38 30 31 4c 30 45 4e 0a SB_PCI0K801L0EN. 0b70: 03 60 a0 46 06 93 60 0a 03 7b 5c 2f 04 5f 53 42 .`.F..`..{\/._SB 0b80: 5f 50 43 49 30 4b 38 30 31 44 4c 30 30 0a 03 60 _PCI0K801DL00..` 0b90: a0 48 04 93 60 0a 00 70 5c 2f 04 5f 53 42 5f 50 .H..`..p\/._SB_P 0ba0: 43 49 30 4b 38 30 31 42 4e 42 30 42 31 4d 4e 70 CI0K801BNB0B1MNp 0bb0: 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 42 \/._SB_PCI0K801B 0bc0: 4e 4c 30 42 31 4d 58 74 42 31 4d 58 42 31 4d 4e NL0B1MXtB1MXB1MN 0bd0: 61 72 0a 01 61 42 31 4c 4e 7b 5c 2f 04 5f 53 42 ar..aB1LN{\/._SB 0be0: 5f 50 43 49 30 4b 38 30 31 4c 31 45 4e 0a 03 60 _PCI0K801L1EN..` 0bf0: a0 46 06 93 60 0a 03 7b 5c 2f 04 5f 53 42 5f 50 .F..`..{\/._SB_P 0c00: 43 49 30 4b 38 30 31 44 4c 30 31 0a 03 60 a0 48 CI0K801DL01..`.H 0c10: 04 93 60 0a 00 70 5c 2f 04 5f 53 42 5f 50 43 49 ..`..p\/._SB_PCI 0c20: 30 4b 38 30 31 42 4e 42 31 42 31 4d 4e 70 5c 2f 0K801BNB1B1MNp\/ 0c30: 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 42 4e 4c ._SB_PCI0K801BNL 0c40: 31 42 31 4d 58 74 42 31 4d 58 42 31 4d 4e 61 72 1B1MXtB1MXB1MNar 0c50: 0a 01 61 42 31 4c 4e 7b 5c 2f 04 5f 53 42 5f 50 ..aB1LN{\/._SB_P 0c60: 43 49 30 4b 38 30 31 4c 32 45 4e 0a 03 60 a0 46 CI0K801L2EN..`.F 0c70: 06 93 60 0a 03 7b 5c 2f 04 5f 53 42 5f 50 43 49 ..`..{\/._SB_PCI 0c80: 30 4b 38 30 31 44 4c 30 32 0a 03 60 a0 48 04 93 0K801DL02..`.H.. 0c90: 60 0a 00 70 5c 2f 04 5f 53 42 5f 50 43 49 30 4b `..p\/._SB_PCI0K 0ca0: 38 30 31 42 4e 42 32 42 31 4d 4e 70 5c 2f 04 5f 801BNB2B1MNp\/._ 0cb0: 53 42 5f 50 43 49 30 4b 38 30 31 42 4e 4c 32 42 SB_PCI0K801BNL2B 0cc0: 31 4d 58 74 42 31 4d 58 42 31 4d 4e 61 72 0a 01 1MXtB1MXB1MNar.. 0cd0: 61 42 31 4c 4e 7b 5c 2f 04 5f 53 42 5f 50 43 49 aB1LN{\/._SB_PCI 0ce0: 30 4b 38 30 31 4c 33 45 4e 0a 03 60 a0 46 06 93 0K801L3EN..`.F.. 0cf0: 60 0a 03 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 4b `..{\/._SB_PCI0K 0d00: 38 30 31 44 4c 30 33 0a 03 60 a0 48 04 93 60 0a 801DL03..`.H..`. 0d10: 00 70 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 .p\/._SB_PCI0K80 0d20: 31 42 4e 42 33 42 31 4d 4e 70 5c 2f 04 5f 53 42 1BNB3B1MNp\/._SB 0d30: 5f 50 43 49 30 4b 38 30 31 42 4e 4c 33 42 31 4d _PCI0K801BNL3B1M 0d40: 58 74 42 31 4d 58 42 31 4d 4e 61 72 0a 01 61 42 XtB1MXB1MNar..aB 0d50: 31 4c 4e 8b 42 55 46 30 0a 40 49 4f 4d 4e 8b 42 1LN.BUF0.@IOMN.B 0d60: 55 46 30 0a 42 49 4f 4d 58 8b 42 55 46 30 0a 46 UF0.BIOMX.BUF0.F 0d70: 49 4f 4c 4e 8b 42 55 46 30 0a 50 56 49 4d 4e 8b IOLN.BUF0.PVIMN. 0d80: 42 55 46 30 0a 52 56 49 4d 58 8b 42 55 46 30 0a BUF0.RVIMX.BUF0. 0d90: 56 56 49 4c 4e 7b 5c 2f 04 5f 53 42 5f 50 43 49 VVILN{\/._SB_PCI 0da0: 30 4b 38 30 31 49 42 30 30 0a 03 60 7b 5c 2f 04 0K801IB00..`{\/. 0db0: 5f 53 42 5f 50 43 49 30 4b 38 30 31 49 4c 30 30 _SB_PCI0K801IL00 0dc0: 0a 30 61 7a 61 0a 04 61 a0 43 09 93 60 0a 03 a0 .0aza..a.C..`... 0dd0: 4c 08 93 61 0a 00 7b 5c 2f 04 5f 53 42 5f 50 43 L..a..{\/._SB_PC 0de0: 49 30 4b 38 30 31 49 42 30 30 0a 10 61 79 5c 2f I0K801IB00..ay\/ 0df0: 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 49 42 56 ._SB_PCI0K801IBV 0e00: 30 0a 0c 49 4f 4d 4e 79 5c 2f 04 5f 53 42 5f 50 0..IOMNy\/._SB_P 0e10: 43 49 30 4b 38 30 31 49 4c 56 30 0a 0c 49 4f 4d CI0K801ILV0..IOM 0e20: 58 7d 49 4f 4d 58 0b ff 0f 49 4f 4d 58 74 49 4f X}IOMX...IOMXtIO 0e30: 4d 58 49 4f 4d 4e 49 4f 4c 4e 75 49 4f 4c 4e a0 MXIOMNIOLNuIOLN. 0e40: 1c 93 61 0a 10 70 0b b0 03 56 49 4d 4e 70 0b df ..a..p...VIMNp.. 0e50: 03 56 49 4d 58 70 0a 30 56 49 4c 4e 7b 5c 2f 04 .VIMXp.0VILN{\/. 0e60: 5f 53 42 5f 50 43 49 30 4b 38 30 31 49 42 30 31 _SB_PCI0K801IB01 0e70: 0a 03 60 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 4b ..`{\/._SB_PCI0K 0e80: 38 30 31 49 4c 30 31 0a 30 61 7a 61 0a 04 61 a0 801IL01.0aza..a. 0e90: 43 09 93 60 0a 03 a0 4c 08 93 61 0a 00 7b 5c 2f C..`...L..a..{\/ 0ea0: 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 49 42 30 ._SB_PCI0K801IB0 0eb0: 31 0a 10 61 79 5c 2f 04 5f 53 42 5f 50 43 49 30 1..ay\/._SB_PCI0 0ec0: 4b 38 30 31 49 42 56 31 0a 0c 49 4f 4d 4e 79 5c K801IBV1..IOMNy\ 0ed0: 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 49 4c /._SB_PCI0K801IL 0ee0: 56 31 0a 0c 49 4f 4d 58 7d 49 4f 4d 58 0b ff 0f V1..IOMX}IOMX... 0ef0: 49 4f 4d 58 74 49 4f 4d 58 49 4f 4d 4e 49 4f 4c IOMXtIOMXIOMNIOL 0f00: 4e 75 49 4f 4c 4e a0 1c 93 61 0a 10 70 0b b0 03 NuIOLN...a..p... 0f10: 56 49 4d 4e 70 0b df 03 56 49 4d 58 70 0a 30 56 VIMNp...VIMXp.0V 0f20: 49 4c 4e 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 4b ILN{\/._SB_PCI0K 0f30: 38 30 31 49 42 30 32 0a 03 60 7b 5c 2f 04 5f 53 801IB02..`{\/._S 0f40: 42 5f 50 43 49 30 4b 38 30 31 49 4c 30 32 0a 30 B_PCI0K801IL02.0 0f50: 61 7a 61 0a 04 61 a0 43 09 93 60 0a 03 a0 4c 08 aza..a.C..`...L. 0f60: 93 61 0a 00 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 .a..{\/._SB_PCI0 0f70: 4b 38 30 31 49 42 30 32 0a 10 61 79 5c 2f 04 5f K801IB02..ay\/._ 0f80: 53 42 5f 50 43 49 30 4b 38 30 31 49 42 56 32 0a SB_PCI0K801IBV2. 0f90: 0c 49 4f 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 .IOMNy\/._SB_PCI 0fa0: 30 4b 38 30 31 49 4c 56 32 0a 0c 49 4f 4d 58 7d 0K801ILV2..IOMX} 0fb0: 49 4f 4d 58 0b ff 0f 49 4f 4d 58 74 49 4f 4d 58 IOMX...IOMXtIOMX 0fc0: 49 4f 4d 4e 49 4f 4c 4e 75 49 4f 4c 4e a0 1c 93 IOMNIOLNuIOLN... 0fd0: 61 0a 10 70 0b b0 03 56 49 4d 4e 70 0b df 03 56 a..p...VIMNp...V 0fe0: 49 4d 58 70 0a 30 56 49 4c 4e 7b 5c 2f 04 5f 53 IMXp.0VILN{\/._S 0ff0: 42 5f 50 43 49 30 4b 38 30 31 49 42 30 33 0a 03 B_PCI0K801IB03.. 1000: 60 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 `{\/._SB_PCI0K80 1010: 31 49 4c 30 33 0a 30 61 7a 61 0a 04 61 a0 43 09 1IL03.0aza..a.C. 1020: 93 60 0a 03 a0 4c 08 93 61 0a 00 7b 5c 2f 04 5f .`...L..a..{\/._ 1030: 53 42 5f 50 43 49 30 4b 38 30 31 49 42 30 33 0a SB_PCI0K801IB03. 1040: 10 61 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 .ay\/._SB_PCI0K8 1050: 30 31 49 42 56 33 0a 0c 49 4f 4d 4e 79 5c 2f 04 01IBV3..IOMNy\/. 1060: 5f 53 42 5f 50 43 49 30 4b 38 30 31 49 4c 56 33 _SB_PCI0K801ILV3 1070: 0a 0c 49 4f 4d 58 7d 49 4f 4d 58 0b ff 0f 49 4f ..IOMX}IOMX...IO 1080: 4d 58 74 49 4f 4d 58 49 4f 4d 4e 49 4f 4c 4e 75 MXtIOMXIOMNIOLNu 1090: 49 4f 4c 4e a0 1c 93 61 0a 10 70 0b b0 03 56 49 IOLN...a..p...VI 10a0: 4d 4e 70 0b df 03 56 49 4d 58 70 0a 30 56 49 4c MNp...VIMXp.0VIL 10b0: 4e 8a 42 55 46 30 0a 66 4d 30 4d 4e 8a 42 55 46 N.BUF0.fM0MN.BUF 10c0: 30 0a 6e 4d 30 4d 58 8a 42 55 46 30 0a 7e 4d 30 0.nM0MX.BUF0.~M0 10d0: 4c 4e 8a 42 55 46 30 0a 94 4d 31 4d 4e 8a 42 55 LN.BUF0..M1MN.BU 10e0: 46 30 0a 9c 4d 31 4d 58 8a 42 55 46 30 0a ac 4d F0..M1MX.BUF0..M 10f0: 31 4c 4e 8a 42 55 46 30 0a c2 4d 32 4d 4e 8a 42 1LN.BUF0..M2MN.B 1100: 55 46 30 0a ca 4d 32 4d 58 8a 42 55 46 30 0a da UF0..M2MX.BUF0.. 1110: 4d 32 4c 4e 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 M2LN{\/._SB_PCI0 1120: 4b 38 30 31 4d 42 30 30 0a 03 60 7b 5c 2f 04 5f K801MB00..`{\/._ 1130: 53 42 5f 50 43 49 30 4b 38 30 31 4d 4c 30 30 0a SB_PCI0K801ML00. 1140: 30 61 7a 61 0a 04 61 a0 4b 13 93 60 0a 03 7b 5c 0aza..a.K..`..{\ 1150: 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 4c /._SB_PCI0K801ML 1160: 30 30 0a 80 60 a0 4d 11 93 60 0a 00 a0 46 11 93 00..`.M..`...F.. 1170: 61 0a 00 a0 4b 05 93 4d 30 4c 4e 0a 00 79 5c 2f a...K..M0LN..y\/ 1180: 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 ._SB_PCI0K801MBV 1190: 30 0a 10 4d 30 4d 4e 79 5c 2f 04 5f 53 42 5f 50 0..M0MNy\/._SB_P 11a0: 43 49 30 4b 38 30 31 4d 4c 56 30 0a 10 4d 30 4d CI0K801MLV0..M0M 11b0: 58 7d 4d 30 4d 58 0b ff ff 4d 30 4d 58 74 4d 30 X}M0MX...M0MXtM0 11c0: 4d 58 4d 30 4d 4e 4d 30 4c 4e 75 4d 30 4c 4e a1 MXM0MNM0LNuM0LN. 11d0: 43 0b a0 4b 05 93 4d 31 4c 4e 0a 00 79 5c 2f 04 C..K..M1LN..y\/. 11e0: 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 30 _SB_PCI0K801MBV0 11f0: 0a 10 4d 31 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 ..M1MNy\/._SB_PC 1200: 49 30 4b 38 30 31 4d 4c 56 30 0a 10 4d 31 4d 58 I0K801MLV0..M1MX 1210: 7d 4d 31 4d 58 0b ff ff 4d 31 4d 58 74 4d 31 4d }M1MX...M1MXtM1M 1220: 58 4d 31 4d 4e 4d 31 4c 4e 75 4d 31 4c 4e a1 44 XM1MNM1LNuM1LN.D 1230: 05 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 .y\/._SB_PCI0K80 1240: 31 4d 42 56 30 0a 10 4d 32 4d 4e 79 5c 2f 04 5f 1MBV0..M2MNy\/._ 1250: 53 42 5f 50 43 49 30 4b 38 30 31 4d 4c 56 30 0a SB_PCI0K801MLV0. 1260: 10 4d 32 4d 58 7d 4d 32 4d 58 0b ff ff 4d 32 4d .M2MX}M2MX...M2M 1270: 58 74 4d 32 4d 58 4d 32 4d 4e 4d 32 4c 4e 75 4d XtM2MXM2MNM2LNuM 1280: 32 4c 4e 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 2LN{\/._SB_PCI0K 1290: 38 30 31 4d 42 30 31 0a 03 60 7b 5c 2f 04 5f 53 801MB01..`{\/._S 12a0: 42 5f 50 43 49 30 4b 38 30 31 4d 4c 30 31 0a 30 B_PCI0K801ML01.0 12b0: 61 7a 61 0a 04 61 a0 4b 13 93 60 0a 03 7b 5c 2f aza..a.K..`..{\/ 12c0: 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 4c 30 ._SB_PCI0K801ML0 12d0: 31 0a 80 60 a0 4d 11 93 60 0a 00 a0 46 11 93 61 1..`.M..`...F..a 12e0: 0a 00 a0 4b 05 93 4d 30 4c 4e 0a 00 79 5c 2f 04 ...K..M0LN..y\/. 12f0: 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 31 _SB_PCI0K801MBV1 1300: 0a 10 4d 30 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 ..M0MNy\/._SB_PC 1310: 49 30 4b 38 30 31 4d 4c 56 31 0a 10 4d 30 4d 58 I0K801MLV1..M0MX 1320: 7d 4d 30 4d 58 0b ff ff 4d 30 4d 58 74 4d 30 4d }M0MX...M0MXtM0M 1330: 58 4d 30 4d 4e 4d 30 4c 4e 75 4d 30 4c 4e a1 43 XM0MNM0LNuM0LN.C 1340: 0b a0 4b 05 93 4d 31 4c 4e 0a 00 79 5c 2f 04 5f ..K..M1LN..y\/._ 1350: 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 31 0a SB_PCI0K801MBV1. 1360: 10 4d 31 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 .M1MNy\/._SB_PCI 1370: 30 4b 38 30 31 4d 4c 56 31 0a 10 4d 31 4d 58 7d 0K801MLV1..M1MX} 1380: 4d 31 4d 58 0b ff ff 4d 31 4d 58 74 4d 31 4d 58 M1MX...M1MXtM1MX 1390: 4d 31 4d 4e 4d 31 4c 4e 75 4d 31 4c 4e a1 44 05 M1MNM1LNuM1LN.D. 13a0: 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 y\/._SB_PCI0K801 13b0: 4d 42 56 31 0a 10 4d 32 4d 4e 79 5c 2f 04 5f 53 MBV1..M2MNy\/._S 13c0: 42 5f 50 43 49 30 4b 38 30 31 4d 4c 56 31 0a 10 B_PCI0K801MLV1.. 13d0: 4d 32 4d 58 7d 4d 32 4d 58 0b ff ff 4d 32 4d 58 M2MX}M2MX...M2MX 13e0: 74 4d 32 4d 58 4d 32 4d 4e 4d 32 4c 4e 75 4d 32 tM2MXM2MNM2LNuM2 13f0: 4c 4e 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 LN{\/._SB_PCI0K8 1400: 30 31 4d 42 30 32 0a 03 60 7b 5c 2f 04 5f 53 42 01MB02..`{\/._SB 1410: 5f 50 43 49 30 4b 38 30 31 4d 4c 30 32 0a 30 61 _PCI0K801ML02.0a 1420: 7a 61 0a 04 61 a0 4b 13 93 60 0a 03 7b 5c 2f 04 za..a.K..`..{\/. 1430: 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 4c 30 32 _SB_PCI0K801ML02 1440: 0a 80 60 a0 4d 11 93 60 0a 00 a0 46 11 93 61 0a ..`.M..`...F..a. 1450: 00 a0 4b 05 93 4d 30 4c 4e 0a 00 79 5c 2f 04 5f ..K..M0LN..y\/._ 1460: 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 32 0a SB_PCI0K801MBV2. 1470: 10 4d 30 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 .M0MNy\/._SB_PCI 1480: 30 4b 38 30 31 4d 4c 56 32 0a 10 4d 30 4d 58 7d 0K801MLV2..M0MX} 1490: 4d 30 4d 58 0b ff ff 4d 30 4d 58 74 4d 30 4d 58 M0MX...M0MXtM0MX 14a0: 4d 30 4d 4e 4d 30 4c 4e 75 4d 30 4c 4e a1 43 0b M0MNM0LNuM0LN.C. 14b0: a0 4b 05 93 4d 31 4c 4e 0a 00 79 5c 2f 04 5f 53 .K..M1LN..y\/._S 14c0: 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 32 0a 10 B_PCI0K801MBV2.. 14d0: 4d 31 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 M1MNy\/._SB_PCI0 14e0: 4b 38 30 31 4d 4c 56 32 0a 10 4d 31 4d 58 7d 4d K801MLV2..M1MX}M 14f0: 31 4d 58 0b ff ff 4d 31 4d 58 74 4d 31 4d 58 4d 1MX...M1MXtM1MXM 1500: 31 4d 4e 4d 31 4c 4e 75 4d 31 4c 4e a1 44 05 79 1MNM1LNuM1LN.D.y 1510: 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d \/._SB_PCI0K801M 1520: 42 56 32 0a 10 4d 32 4d 4e 79 5c 2f 04 5f 53 42 BV2..M2MNy\/._SB 1530: 5f 50 43 49 30 4b 38 30 31 4d 4c 56 32 0a 10 4d _PCI0K801MLV2..M 1540: 32 4d 58 7d 4d 32 4d 58 0b ff ff 4d 32 4d 58 74 2MX}M2MX...M2MXt 1550: 4d 32 4d 58 4d 32 4d 4e 4d 32 4c 4e 75 4d 32 4c M2MXM2MNM2LNuM2L 1560: 4e 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 N{\/._SB_PCI0K80 1570: 31 4d 42 30 33 0a 03 60 7b 5c 2f 04 5f 53 42 5f 1MB03..`{\/._SB_ 1580: 50 43 49 30 4b 38 30 31 4d 4c 30 33 0a 30 61 7a PCI0K801ML03.0az 1590: 61 0a 04 61 a0 4b 13 93 60 0a 03 7b 5c 2f 04 5f a..a.K..`..{\/._ 15a0: 53 42 5f 50 43 49 30 4b 38 30 31 4d 4c 30 33 0a SB_PCI0K801ML03. 15b0: 80 60 a0 4d 11 93 60 0a 00 a0 46 11 93 61 0a 00 .`.M..`...F..a.. 15c0: a0 4b 05 93 4d 30 4c 4e 0a 00 79 5c 2f 04 5f 53 .K..M0LN..y\/._S 15d0: 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 33 0a 10 B_PCI0K801MBV3.. 15e0: 4d 30 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 M0MNy\/._SB_PCI0 15f0: 4b 38 30 31 4d 4c 56 33 0a 10 4d 30 4d 58 7d 4d K801MLV3..M0MX}M 1600: 30 4d 58 0b ff ff 4d 30 4d 58 74 4d 30 4d 58 4d 0MX...M0MXtM0MXM 1610: 30 4d 4e 4d 30 4c 4e 75 4d 30 4c 4e a1 43 0b a0 0MNM0LNuM0LN.C.. 1620: 4b 05 93 4d 31 4c 4e 0a 00 79 5c 2f 04 5f 53 42 K..M1LN..y\/._SB 1630: 5f 50 43 49 30 4b 38 30 31 4d 42 56 33 0a 10 4d _PCI0K801MBV3..M 1640: 31 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 1MNy\/._SB_PCI0K 1650: 38 30 31 4d 4c 56 33 0a 10 4d 31 4d 58 7d 4d 31 801MLV3..M1MX}M1 1660: 4d 58 0b ff ff 4d 31 4d 58 74 4d 31 4d 58 4d 31 MX...M1MXtM1MXM1 1670: 4d 4e 4d 31 4c 4e 75 4d 31 4c 4e a1 44 05 79 5c MNM1LNuM1LN.D.y\ 1680: 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 /._SB_PCI0K801MB 1690: 56 33 0a 10 4d 32 4d 4e 79 5c 2f 04 5f 53 42 5f V3..M2MNy\/._SB_ 16a0: 50 43 49 30 4b 38 30 31 4d 4c 56 33 0a 10 4d 32 PCI0K801MLV3..M2 16b0: 4d 58 7d 4d 32 4d 58 0b ff ff 4d 32 4d 58 74 4d MX}M2MX...M2MXtM 16c0: 32 4d 58 4d 32 4d 4e 4d 32 4c 4e 75 4d 32 4c 4e 2MXM2MNM2LNuM2LN 16d0: 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 {\/._SB_PCI0K801 16e0: 4d 42 30 34 0a 03 60 7b 5c 2f 04 5f 53 42 5f 50 MB04..`{\/._SB_P 16f0: 43 49 30 4b 38 30 31 4d 4c 30 34 0a 30 61 7a 61 CI0K801ML04.0aza 1700: 0a 04 61 a0 4b 13 93 60 0a 03 7b 5c 2f 04 5f 53 ..a.K..`..{\/._S 1710: 42 5f 50 43 49 30 4b 38 30 31 4d 4c 30 34 0a 80 B_PCI0K801ML04.. 1720: 60 a0 4d 11 93 60 0a 00 a0 46 11 93 61 0a 00 a0 `.M..`...F..a... 1730: 4b 05 93 4d 30 4c 4e 0a 00 79 5c 2f 04 5f 53 42 K..M0LN..y\/._SB 1740: 5f 50 43 49 30 4b 38 30 31 4d 42 56 34 0a 10 4d _PCI0K801MBV4..M 1750: 30 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 0MNy\/._SB_PCI0K 1760: 38 30 31 4d 4c 56 34 0a 10 4d 30 4d 58 7d 4d 30 801MLV4..M0MX}M0 1770: 4d 58 0b ff ff 4d 30 4d 58 74 4d 30 4d 58 4d 30 MX...M0MXtM0MXM0 1780: 4d 4e 4d 30 4c 4e 75 4d 30 4c 4e a1 43 0b a0 4b MNM0LNuM0LN.C..K 1790: 05 93 4d 31 4c 4e 0a 00 79 5c 2f 04 5f 53 42 5f ..M1LN..y\/._SB_ 17a0: 50 43 49 30 4b 38 30 31 4d 42 56 34 0a 10 4d 31 PCI0K801MBV4..M1 17b0: 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 MNy\/._SB_PCI0K8 17c0: 30 31 4d 4c 56 34 0a 10 4d 31 4d 58 7d 4d 31 4d 01MLV4..M1MX}M1M 17d0: 58 0b ff ff 4d 31 4d 58 74 4d 31 4d 58 4d 31 4d X...M1MXtM1MXM1M 17e0: 4e 4d 31 4c 4e 75 4d 31 4c 4e a1 44 05 79 5c 2f NM1LNuM1LN.D.y\/ 17f0: 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 ._SB_PCI0K801MBV 1800: 34 0a 10 4d 32 4d 4e 79 5c 2f 04 5f 53 42 5f 50 4..M2MNy\/._SB_P 1810: 43 49 30 4b 38 30 31 4d 4c 56 34 0a 10 4d 32 4d CI0K801MLV4..M2M 1820: 58 7d 4d 32 4d 58 0b ff ff 4d 32 4d 58 74 4d 32 X}M2MX...M2MXtM2 1830: 4d 58 4d 32 4d 4e 4d 32 4c 4e 75 4d 32 4c 4e 7b MXM2MNM2LNuM2LN{ 1840: 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d \/._SB_PCI0K801M 1850: 42 30 35 0a 03 60 7b 5c 2f 04 5f 53 42 5f 50 43 B05..`{\/._SB_PC 1860: 49 30 4b 38 30 31 4d 4c 30 35 0a 30 61 7a 61 0a I0K801ML05.0aza. 1870: 04 61 a0 4b 13 93 60 0a 03 7b 5c 2f 04 5f 53 42 .a.K..`..{\/._SB 1880: 5f 50 43 49 30 4b 38 30 31 4d 4c 30 35 0a 80 60 _PCI0K801ML05..` 1890: a0 4d 11 93 60 0a 00 a0 46 11 93 61 0a 00 a0 4b .M..`...F..a...K 18a0: 05 93 4d 30 4c 4e 0a 00 79 5c 2f 04 5f 53 42 5f ..M0LN..y\/._SB_ 18b0: 50 43 49 30 4b 38 30 31 4d 42 56 35 0a 10 4d 30 PCI0K801MBV5..M0 18c0: 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 MNy\/._SB_PCI0K8 18d0: 30 31 4d 4c 56 35 0a 10 4d 30 4d 58 7d 4d 30 4d 01MLV5..M0MX}M0M 18e0: 58 0b ff ff 4d 30 4d 58 74 4d 30 4d 58 4d 30 4d X...M0MXtM0MXM0M 18f0: 4e 4d 30 4c 4e 75 4d 30 4c 4e a1 43 0b a0 4b 05 NM0LNuM0LN.C..K. 1900: 93 4d 31 4c 4e 0a 00 79 5c 2f 04 5f 53 42 5f 50 .M1LN..y\/._SB_P 1910: 43 49 30 4b 38 30 31 4d 42 56 35 0a 10 4d 31 4d CI0K801MBV5..M1M 1920: 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 Ny\/._SB_PCI0K80 1930: 31 4d 4c 56 35 0a 10 4d 31 4d 58 7d 4d 31 4d 58 1MLV5..M1MX}M1MX 1940: 0b ff ff 4d 31 4d 58 74 4d 31 4d 58 4d 31 4d 4e ...M1MXtM1MXM1MN 1950: 4d 31 4c 4e 75 4d 31 4c 4e a1 44 05 79 5c 2f 04 M1LNuM1LN.D.y\/. 1960: 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 35 _SB_PCI0K801MBV5 1970: 0a 10 4d 32 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 ..M2MNy\/._SB_PC 1980: 49 30 4b 38 30 31 4d 4c 56 35 0a 10 4d 32 4d 58 I0K801MLV5..M2MX 1990: 7d 4d 32 4d 58 0b ff ff 4d 32 4d 58 74 4d 32 4d }M2MX...M2MXtM2M 19a0: 58 4d 32 4d 4e 4d 32 4c 4e 75 4d 32 4c 4e 7b 5c XM2MNM2LNuM2LN{\ 19b0: 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 /._SB_PCI0K801MB 19c0: 30 36 0a 03 60 7b 5c 2f 04 5f 53 42 5f 50 43 49 06..`{\/._SB_PCI 19d0: 30 4b 38 30 31 4d 4c 30 36 0a 30 61 7a 61 0a 04 0K801ML06.0aza.. 19e0: 61 a0 4b 13 93 60 0a 03 7b 5c 2f 04 5f 53 42 5f a.K..`..{\/._SB_ 19f0: 50 43 49 30 4b 38 30 31 4d 4c 30 36 0a 80 60 a0 PCI0K801ML06..`. 1a00: 4d 11 93 60 0a 00 a0 46 11 93 61 0a 00 a0 4b 05 M..`...F..a...K. 1a10: 93 4d 30 4c 4e 0a 00 79 5c 2f 04 5f 53 42 5f 50 .M0LN..y\/._SB_P 1a20: 43 49 30 4b 38 30 31 4d 42 56 36 0a 10 4d 30 4d CI0K801MBV6..M0M 1a30: 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 Ny\/._SB_PCI0K80 1a40: 31 4d 4c 56 36 0a 10 4d 30 4d 58 7d 4d 30 4d 58 1MLV6..M0MX}M0MX 1a50: 0b ff ff 4d 30 4d 58 74 4d 30 4d 58 4d 30 4d 4e ...M0MXtM0MXM0MN 1a60: 4d 30 4c 4e 75 4d 30 4c 4e a1 43 0b a0 4b 05 93 M0LNuM0LN.C..K.. 1a70: 4d 31 4c 4e 0a 00 79 5c 2f 04 5f 53 42 5f 50 43 M1LN..y\/._SB_PC 1a80: 49 30 4b 38 30 31 4d 42 56 36 0a 10 4d 31 4d 4e I0K801MBV6..M1MN 1a90: 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 y\/._SB_PCI0K801 1aa0: 4d 4c 56 36 0a 10 4d 31 4d 58 7d 4d 31 4d 58 0b MLV6..M1MX}M1MX. 1ab0: ff ff 4d 31 4d 58 74 4d 31 4d 58 4d 31 4d 4e 4d ..M1MXtM1MXM1MNM 1ac0: 31 4c 4e 75 4d 31 4c 4e a1 44 05 79 5c 2f 04 5f 1LNuM1LN.D.y\/._ 1ad0: 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 36 0a SB_PCI0K801MBV6. 1ae0: 10 4d 32 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 .M2MNy\/._SB_PCI 1af0: 30 4b 38 30 31 4d 4c 56 36 0a 10 4d 32 4d 58 7d 0K801MLV6..M2MX} 1b00: 4d 32 4d 58 0b ff ff 4d 32 4d 58 74 4d 32 4d 58 M2MX...M2MXtM2MX 1b10: 4d 32 4d 4e 4d 32 4c 4e 75 4d 32 4c 4e 7b 5c 2f M2MNM2LNuM2LN{\/ 1b20: 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d 42 30 ._SB_PCI0K801MB0 1b30: 37 0a 03 60 7b 5c 2f 04 5f 53 42 5f 50 43 49 30 7..`{\/._SB_PCI0 1b40: 4b 38 30 31 4d 4c 30 37 0a 30 61 7a 61 0a 04 61 K801ML07.0aza..a 1b50: a0 4b 13 93 60 0a 03 7b 5c 2f 04 5f 53 42 5f 50 .K..`..{\/._SB_P 1b60: 43 49 30 4b 38 30 31 4d 4c 30 37 0a 80 60 a0 4d CI0K801ML07..`.M 1b70: 11 93 60 0a 00 a0 46 11 93 61 0a 00 a0 4b 05 93 ..`...F..a...K.. 1b80: 4d 30 4c 4e 0a 00 79 5c 2f 04 5f 53 42 5f 50 43 M0LN..y\/._SB_PC 1b90: 49 30 4b 38 30 31 4d 42 56 37 0a 10 4d 30 4d 4e I0K801MBV7..M0MN 1ba0: 79 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 y\/._SB_PCI0K801 1bb0: 4d 4c 56 37 0a 10 4d 30 4d 58 7d 4d 30 4d 58 0b MLV7..M0MX}M0MX. 1bc0: ff ff 4d 30 4d 58 74 4d 30 4d 58 4d 30 4d 4e 4d ..M0MXtM0MXM0MNM 1bd0: 30 4c 4e 75 4d 30 4c 4e a1 43 0b a0 4b 05 93 4d 0LNuM0LN.C..K..M 1be0: 31 4c 4e 0a 00 79 5c 2f 04 5f 53 42 5f 50 43 49 1LN..y\/._SB_PCI 1bf0: 30 4b 38 30 31 4d 42 56 37 0a 10 4d 31 4d 4e 79 0K801MBV7..M1MNy 1c00: 5c 2f 04 5f 53 42 5f 50 43 49 30 4b 38 30 31 4d \/._SB_PCI0K801M 1c10: 4c 56 37 0a 10 4d 31 4d 58 7d 4d 31 4d 58 0b ff LV7..M1MX}M1MX.. 1c20: ff 4d 31 4d 58 74 4d 31 4d 58 4d 31 4d 4e 4d 31 .M1MXtM1MXM1MNM1 1c30: 4c 4e 75 4d 31 4c 4e a1 44 05 79 5c 2f 04 5f 53 LNuM1LN.D.y\/._S 1c40: 42 5f 50 43 49 30 4b 38 30 31 4d 42 56 37 0a 10 B_PCI0K801MBV7.. 1c50: 4d 32 4d 4e 79 5c 2f 04 5f 53 42 5f 50 43 49 30 M2MNy\/._SB_PCI0 1c60: 4b 38 30 31 4d 4c 56 37 0a 10 4d 32 4d 58 7d 4d K801MLV7..M2MX}M 1c70: 32 4d 58 0b ff ff 4d 32 4d 58 74 4d 32 4d 58 4d 2MX...M2MXtM2MXM 1c80: 32 4d 4e 4d 32 4c 4e 75 4d 32 4c 4e a4 42 55 46 2MNM2LNuM2LN.BUF 1c90: 30 08 50 49 43 4d 12 47 2f 1c 12 1a 04 0c ff ff 0.PICM.G/....... 1ca0: 0a 00 0a 00 5c 2f 03 5f 53 42 5f 50 43 49 30 4c ....\/._SB_PCI0L 1cb0: 53 4d 42 0a 00 12 1a 04 0c ff ff 0a 00 0a 01 5c SMB............\ 1cc0: 2f 03 5f 53 42 5f 50 43 49 30 4c 50 4d 55 0a 00 /._SB_PCI0LPMU.. 1cd0: 12 1a 04 0c ff ff 0b 00 0a 00 5c 2f 03 5f 53 42 ..........\/._SB 1ce0: 5f 50 43 49 30 4c 55 42 41 0a 00 12 1a 04 0c ff _PCI0LUBA....... 1cf0: ff 0b 00 0a 01 5c 2f 03 5f 53 42 5f 50 43 49 30 .....\/._SB_PCI0 1d00: 4c 55 42 32 0a 00 12 1a 04 0c ff ff 14 00 0a 00 LUB2............ 1d10: 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 4d 41 43 0a \/._SB_PCI0LMAC. 1d20: 00 12 1a 04 0c ff ff 10 00 0a 00 5c 2f 03 5f 53 ...........\/._S 1d30: 42 5f 50 43 49 30 4c 41 43 49 0a 00 12 1a 04 0c B_PCI0LACI...... 1d40: ff ff 10 00 0a 01 5c 2f 03 5f 53 42 5f 50 43 49 ......\/._SB_PCI 1d50: 30 4c 41 5a 41 0a 00 12 1a 04 0c ff ff 10 00 0a 0LAZA........... 1d60: 02 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 41 43 49 .\/._SB_PCI0LACI 1d70: 0a 00 12 1a 04 0c ff ff 10 00 0a 03 5c 2f 03 5f ............\/._ 1d80: 53 42 5f 50 43 49 30 4c 4d 43 49 0a 00 12 1a 04 SB_PCI0LMCI..... 1d90: 0c ff ff 0d 00 0a 00 5c 2f 03 5f 53 42 5f 50 43 .......\/._SB_PC 1da0: 49 30 4c 49 44 45 0a 00 12 1a 04 0c ff ff 0e 00 I0LIDE.......... 1db0: 0a 00 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 53 49 ..\/._SB_PCI0LSI 1dc0: 44 0a 00 12 1a 04 0c ff ff 0f 00 0a 00 5c 2f 03 D............\/. 1dd0: 5f 53 42 5f 50 43 49 30 4c 46 49 44 0a 00 12 1a _SB_PCI0LFID.... 1de0: 04 0c ff ff 04 00 0a 00 5c 2f 03 5f 53 42 5f 50 ........\/._SB_P 1df0: 43 49 30 4c 4e 4b 35 0a 00 12 1a 04 0c ff ff 04 CI0LNK5......... 1e00: 00 0a 01 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 4e ...\/._SB_PCI0LN 1e10: 4b 36 0a 00 12 1a 04 0c ff ff 04 00 0a 02 5c 2f K6............\/ 1e20: 03 5f 53 42 5f 50 43 49 30 4c 4e 4b 37 0a 00 12 ._SB_PCI0LNK7... 1e30: 1a 04 0c ff ff 04 00 0a 03 5c 2f 03 5f 53 42 5f .........\/._SB_ 1e40: 50 43 49 30 4c 4e 4b 38 0a 00 12 1a 04 0c ff ff PCI0LNK8........ 1e50: 03 00 0a 00 5c 2f 03 5f 53 42 5f 50 43 49 30 4c ....\/._SB_PCI0L 1e60: 4e 4b 35 0a 00 12 1a 04 0c ff ff 03 00 0a 01 5c NK5............\ 1e70: 2f 03 5f 53 42 5f 50 43 49 30 4c 4e 4b 36 0a 00 /._SB_PCI0LNK6.. 1e80: 12 1a 04 0c ff ff 03 00 0a 02 5c 2f 03 5f 53 42 ..........\/._SB 1e90: 5f 50 43 49 30 4c 4e 4b 37 0a 00 12 1a 04 0c ff _PCI0LNK7....... 1ea0: ff 03 00 0a 03 5c 2f 03 5f 53 42 5f 50 43 49 30 .....\/._SB_PCI0 1eb0: 4c 4e 4b 38 0a 00 12 1a 04 0c ff ff 02 00 0a 00 LNK8............ 1ec0: 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 4e 4b 36 0a \/._SB_PCI0LNK6. 1ed0: 00 12 1a 04 0c ff ff 02 00 0a 01 5c 2f 03 5f 53 ...........\/._S 1ee0: 42 5f 50 43 49 30 4c 4e 4b 37 0a 00 12 1a 04 0c B_PCI0LNK7...... 1ef0: ff ff 02 00 0a 02 5c 2f 03 5f 53 42 5f 50 43 49 ......\/._SB_PCI 1f00: 30 4c 4e 4b 38 0a 00 12 1a 04 0c ff ff 02 00 0a 0LNK8........... 1f10: 03 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 4e 4b 35 .\/._SB_PCI0LNK5 1f20: 0a 00 12 1a 04 0c ff ff 05 00 0a 00 5c 2f 03 5f ............\/._ 1f30: 53 42 5f 50 43 49 30 4c 4e 4b 37 0a 00 12 1a 04 SB_PCI0LNK7..... 1f40: 0c ff ff 05 00 0a 01 5c 2f 03 5f 53 42 5f 50 43 .......\/._SB_PC 1f50: 49 30 4c 4e 4b 38 0a 00 12 1a 04 0c ff ff 05 00 I0LNK8.......... 1f60: 0a 02 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 4e 4b ..\/._SB_PCI0LNK 1f70: 35 0a 00 12 1a 04 0c ff ff 05 00 0a 03 5c 2f 03 5............\/. 1f80: 5f 53 42 5f 50 43 49 30 4c 4e 4b 36 0a 00 08 41 _SB_PCI0LNK6...A 1f90: 50 49 43 12 47 2f 1c 12 1a 04 0c ff ff 0a 00 0a PIC.G/.......... 1fa0: 00 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 53 .\/._SB_PCI0APCS 1fb0: 0a 00 12 1a 04 0c ff ff 0a 00 0a 01 5c 2f 03 5f ............\/._ 1fc0: 53 42 5f 50 43 49 30 41 50 4d 55 0a 00 12 1a 04 SB_PCI0APMU..... 1fd0: 0c ff ff 0b 00 0a 00 5c 2f 03 5f 53 42 5f 50 43 .......\/._SB_PC 1fe0: 49 30 41 50 43 46 0a 00 12 1a 04 0c ff ff 0b 00 I0APCF.......... 1ff0: 0a 01 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 ..\/._SB_PCI0APC 2000: 4c 0a 00 12 1a 04 0c ff ff 14 00 0a 00 5c 2f 03 L............\/. 2010: 5f 53 42 5f 50 43 49 30 41 50 43 48 0a 00 12 1a _SB_PCI0APCH.... 2020: 04 0c ff ff 10 00 0a 00 5c 2f 03 5f 53 42 5f 50 ........\/._SB_P 2030: 43 49 30 41 50 43 4a 0a 00 12 1a 04 0c ff ff 10 CI0APCJ......... 2040: 00 0a 01 5c 2f 03 5f 53 42 5f 50 43 49 30 41 41 ...\/._SB_PCI0AA 2050: 5a 41 0a 00 12 1a 04 0c ff ff 10 00 0a 02 5c 2f ZA............\/ 2060: 03 5f 53 42 5f 50 43 49 30 41 50 43 4a 0a 00 12 ._SB_PCI0APCJ... 2070: 1a 04 0c ff ff 10 00 0a 03 5c 2f 03 5f 53 42 5f .........\/._SB_ 2080: 50 43 49 30 41 50 43 4b 0a 00 12 1a 04 0c ff ff PCI0APCK........ 2090: 0d 00 0a 00 5c 2f 03 5f 53 42 5f 50 43 49 30 41 ....\/._SB_PCI0A 20a0: 50 43 5a 0a 00 12 1a 04 0c ff ff 0e 00 0a 00 5c PCZ............\ 20b0: 2f 03 5f 53 42 5f 50 43 49 30 41 50 53 49 0a 00 /._SB_PCI0APSI.. 20c0: 12 1a 04 0c ff ff 0f 00 0a 00 5c 2f 03 5f 53 42 ..........\/._SB 20d0: 5f 50 43 49 30 41 50 53 4a 0a 00 12 1a 04 0c ff _PCI0APSJ....... 20e0: ff 04 00 0a 00 5c 2f 03 5f 53 42 5f 50 43 49 30 .....\/._SB_PCI0 20f0: 41 50 43 35 0a 00 12 1a 04 0c ff ff 04 00 0a 01 APC5............ 2100: 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 36 0a \/._SB_PCI0APC6. 2110: 00 12 1a 04 0c ff ff 04 00 0a 02 5c 2f 03 5f 53 ...........\/._S 2120: 42 5f 50 43 49 30 41 50 43 37 0a 00 12 1a 04 0c B_PCI0APC7...... 2130: ff ff 04 00 0a 03 5c 2f 03 5f 53 42 5f 50 43 49 ......\/._SB_PCI 2140: 30 41 50 43 38 0a 00 12 1a 04 0c ff ff 03 00 0a 0APC8........... 2150: 00 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 35 .\/._SB_PCI0APC5 2160: 0a 00 12 1a 04 0c ff ff 03 00 0a 01 5c 2f 03 5f ............\/._ 2170: 53 42 5f 50 43 49 30 41 50 43 36 0a 00 12 1a 04 SB_PCI0APC6..... 2180: 0c ff ff 03 00 0a 02 5c 2f 03 5f 53 42 5f 50 43 .......\/._SB_PC 2190: 49 30 41 50 43 37 0a 00 12 1a 04 0c ff ff 03 00 I0APC7.......... 21a0: 0a 03 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 ..\/._SB_PCI0APC 21b0: 38 0a 00 12 1a 04 0c ff ff 02 00 0a 00 5c 2f 03 8............\/. 21c0: 5f 53 42 5f 50 43 49 30 41 50 43 36 0a 00 12 1a _SB_PCI0APC6.... 21d0: 04 0c ff ff 02 00 0a 01 5c 2f 03 5f 53 42 5f 50 ........\/._SB_P 21e0: 43 49 30 41 50 43 37 0a 00 12 1a 04 0c ff ff 02 CI0APC7......... 21f0: 00 0a 02 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 ...\/._SB_PCI0AP 2200: 43 38 0a 00 12 1a 04 0c ff ff 02 00 0a 03 5c 2f C8............\/ 2210: 03 5f 53 42 5f 50 43 49 30 41 50 43 35 0a 00 12 ._SB_PCI0APC5... 2220: 1a 04 0c ff ff 05 00 0a 00 5c 2f 03 5f 53 42 5f .........\/._SB_ 2230: 50 43 49 30 41 50 43 37 0a 00 12 1a 04 0c ff ff PCI0APC7........ 2240: 05 00 0a 01 5c 2f 03 5f 53 42 5f 50 43 49 30 41 ....\/._SB_PCI0A 2250: 50 43 38 0a 00 12 1a 04 0c ff ff 05 00 0a 02 5c PC8............\ 2260: 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 35 0a 00 /._SB_PCI0APC5.. 2270: 12 1a 04 0c ff ff 05 00 0a 03 5c 2f 03 5f 53 42 ..........\/._SB 2280: 5f 50 43 49 30 41 50 43 36 0a 00 14 19 5f 50 52 _PCI0APC6...._PR 2290: 54 00 a0 0b 92 50 49 43 46 a4 50 49 43 4d a1 06 T....PICF.PICM.. 22a0: a4 41 50 49 43 5b 82 4a 2d 48 55 42 30 08 5f 41 .APIC[.J-HUB0._A 22b0: 44 52 0c 00 00 10 00 14 09 5f 53 54 41 00 a4 0a DR......._STA... 22c0: 0f 08 50 49 43 4d 12 47 14 0c 12 1a 04 0c ff ff ..PICM.G........ 22d0: 08 00 0a 00 5c 2f 03 5f 53 42 5f 50 43 49 30 4c ....\/._SB_PCI0L 22e0: 4e 4b 31 0a 00 12 1a 04 0c ff ff 08 00 0a 01 5c NK1............\ 22f0: 2f 03 5f 53 42 5f 50 43 49 30 4c 4e 4b 32 0a 00 /._SB_PCI0LNK2.. 2300: 12 1a 04 0c ff ff 08 00 0a 02 5c 2f 03 5f 53 42 ..........\/._SB 2310: 5f 50 43 49 30 4c 4e 4b 33 0a 00 12 1a 04 0c ff _PCI0LNK3....... 2320: ff 08 00 0a 03 5c 2f 03 5f 53 42 5f 50 43 49 30 .....\/._SB_PCI0 2330: 4c 4e 4b 34 0a 00 12 1a 04 0c ff ff 09 00 0a 00 LNK4............ 2340: 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 4e 4b 32 0a \/._SB_PCI0LNK2. 2350: 00 12 1a 04 0c ff ff 09 00 0a 01 5c 2f 03 5f 53 ...........\/._S 2360: 42 5f 50 43 49 30 4c 4e 4b 33 0a 00 12 1a 04 0c B_PCI0LNK3...... 2370: ff ff 09 00 0a 02 5c 2f 03 5f 53 42 5f 50 43 49 ......\/._SB_PCI 2380: 30 4c 4e 4b 34 0a 00 12 1a 04 0c ff ff 09 00 0a 0LNK4........... 2390: 03 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 4e 4b 31 .\/._SB_PCI0LNK1 23a0: 0a 00 12 1a 04 0c ff ff 05 00 0a 00 5c 2f 03 5f ............\/._ 23b0: 53 42 5f 50 43 49 30 4c 4e 4b 34 0a 00 12 1a 04 SB_PCI0LNK4..... 23c0: 0c ff ff 05 00 0a 01 5c 2f 03 5f 53 42 5f 50 43 .......\/._SB_PC 23d0: 49 30 4c 4e 4b 34 0a 00 12 1a 04 0c ff ff 05 00 I0LNK4.......... 23e0: 0a 02 5c 2f 03 5f 53 42 5f 50 43 49 30 4c 4e 4b ..\/._SB_PCI0LNK 23f0: 34 0a 00 12 1a 04 0c ff ff 05 00 0a 03 5c 2f 03 4............\/. 2400: 5f 53 42 5f 50 43 49 30 4c 4e 4b 34 0a 00 08 41 _SB_PCI0LNK4...A 2410: 50 49 43 12 47 14 0c 12 1a 04 0c ff ff 08 00 0a PIC.G........... 2420: 00 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 31 .\/._SB_PCI0APC1 2430: 0a 00 12 1a 04 0c ff ff 08 00 0a 01 5c 2f 03 5f ............\/._ 2440: 53 42 5f 50 43 49 30 41 50 43 32 0a 00 12 1a 04 SB_PCI0APC2..... 2450: 0c ff ff 08 00 0a 02 5c 2f 03 5f 53 42 5f 50 43 .......\/._SB_PC 2460: 49 30 41 50 43 33 0a 00 12 1a 04 0c ff ff 08 00 I0APC3.......... 2470: 0a 03 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 ..\/._SB_PCI0APC 2480: 34 0a 00 12 1a 04 0c ff ff 09 00 0a 00 5c 2f 03 4............\/. 2490: 5f 53 42 5f 50 43 49 30 41 50 43 32 0a 00 12 1a _SB_PCI0APC2.... 24a0: 04 0c ff ff 09 00 0a 01 5c 2f 03 5f 53 42 5f 50 ........\/._SB_P 24b0: 43 49 30 41 50 43 33 0a 00 12 1a 04 0c ff ff 09 CI0APC3......... 24c0: 00 0a 02 5c 2f 03 5f 53 42 5f 50 43 49 30 41 50 ...\/._SB_PCI0AP 24d0: 43 34 0a 00 12 1a 04 0c ff ff 09 00 0a 03 5c 2f C4............\/ 24e0: 03 5f 53 42 5f 50 43 49 30 41 50 43 31 0a 00 12 ._SB_PCI0APC1... 24f0: 1a 04 0c ff ff 05 00 0a 00 5c 2f 03 5f 53 42 5f .........\/._SB_ 2500: 50 43 49 30 41 50 43 34 0a 00 12 1a 04 0c ff ff PCI0APC4........ 2510: 05 00 0a 01 5c 2f 03 5f 53 42 5f 50 43 49 30 41 ....\/._SB_PCI0A 2520: 50 43 34 0a 00 12 1a 04 0c ff ff 05 00 0a 02 5c PC4............\ 2530: 2f 03 5f 53 42 5f 50 43 49 30 41 50 43 34 0a 00 /._SB_PCI0APC4.. 2540: 12 1a 04 0c ff ff 05 00 0a 03 5c 2f 03 5f 53 42 ..........\/._SB 2550: 5f 50 43 49 30 41 50 43 34 0a 00 14 19 5f 50 52 _PCI0APC4...._PR 2560: 54 00 a0 0b 92 50 49 43 46 a4 50 49 43 4d a1 06 T....PICF.PICM.. 2570: a4 41 50 49 43 08 5f 50 52 57 12 06 02 0a 00 0a .APIC._PRW...... 2580: 05 5b 82 4b 10 53 41 54 31 08 5f 41 44 52 0c 00 .[.K.SAT1._ADR.. 2590: 00 0e 00 5b 82 4e 06 50 52 49 30 08 5f 41 44 52 ...[.N.PRI0._ADR 25a0: 0a 00 08 53 50 54 4d 11 17 0a 14 78 00 00 00 0f ...SPTM....x.... 25b0: 00 00 00 ff ff ff ff ff ff ff ff 13 00 00 00 14 ................ 25c0: 0b 5f 47 54 4d 00 a4 53 50 54 4d 14 0c 5f 53 54 ._GTM..SPTM.._ST 25d0: 4d 03 70 68 53 50 54 4d 5b 82 29 4d 41 53 54 08 M.phSPTM[.)MAST. 25e0: 5f 41 44 52 0a 00 14 1c 5f 47 54 46 00 70 0a b1 _ADR...._GTF.p.. 25f0: 53 4d 49 50 70 11 0a 0a 07 03 46 00 00 00 a0 ef SMIPp.....F..... 2600: 60 a4 60 5b 82 4e 06 53 45 43 30 08 5f 41 44 52 `.`[.N.SEC0._ADR 2610: 0a 01 08 53 53 54 4d 11 17 0a 14 78 00 00 00 0f ...SSTM....x.... 2620: 00 00 00 ff ff ff ff ff ff ff ff 13 00 00 00 14 ................ 2630: 0b 5f 47 54 4d 00 a4 53 53 54 4d 14 0c 5f 53 54 ._GTM..SSTM.._ST 2640: 4d 03 70 68 53 53 54 4d 5b 82 29 4d 41 53 54 08 M.phSSTM[.)MAST. 2650: 5f 41 44 52 0a 00 14 1c 5f 47 54 46 00 70 0a b1 _ADR...._GTF.p.. 2660: 53 4d 49 50 70 11 0a 0a 07 03 46 00 00 00 a0 ef SMIPp.....F..... 2670: 60 a4 60 14 1a 44 52 4d 50 00 a4 5c 2f 04 5f 53 `.`..DRMP..\/._S 2680: 42 5f 50 43 49 30 4e 56 52 42 52 5f 53 30 5b 82 B_PCI0NVRBR_S0[. 2690: 4b 10 53 41 54 32 08 5f 41 44 52 0c 00 00 0f 00 K.SAT2._ADR..... 26a0: 5b 82 4e 06 50 52 49 30 08 5f 41 44 52 0a 00 08 [.N.PRI0._ADR... 26b0: 53 50 54 4d 11 17 0a 14 78 00 00 00 0f 00 00 00 SPTM....x....... 26c0: ff ff ff ff ff ff ff ff 13 00 00 00 14 0b 5f 47 .............._G 26d0: 54 4d 00 a4 53 50 54 4d 14 0c 5f 53 54 4d 03 70 TM..SPTM.._STM.p 26e0: 68 53 50 54 4d 5b 82 29 4d 41 53 54 08 5f 41 44 hSPTM[.)MAST._AD 26f0: 52 0a 00 14 1c 5f 47 54 46 00 70 0a b1 53 4d 49 R...._GTF.p..SMI 2700: 50 70 11 0a 0a 07 03 46 00 00 00 a0 ef 60 a4 60 Pp.....F.....`.` 2710: 5b 82 4e 06 53 45 43 30 08 5f 41 44 52 0a 01 08 [.N.SEC0._ADR... 2720: 53 53 54 4d 11 17 0a 14 78 00 00 00 0f 00 00 00 SSTM....x....... 2730: ff ff ff ff ff ff ff ff 13 00 00 00 14 0b 5f 47 .............._G 2740: 54 4d 00 a4 53 53 54 4d 14 0c 5f 53 54 4d 03 70 TM..SSTM.._STM.p 2750: 68 53 53 54 4d 5b 82 29 4d 41 53 54 08 5f 41 44 hSSTM[.)MAST._AD 2760: 52 0a 00 14 1c 5f 47 54 46 00 70 0a b1 53 4d 49 R...._GTF.p..SMI 2770: 50 70 11 0a 0a 07 03 46 00 00 00 a0 ef 60 a4 60 Pp.....F.....`.` 2780: 14 1a 44 52 4d 50 00 a4 5c 2f 04 5f 53 42 5f 50 ..DRMP..\/._SB_P 2790: 43 49 30 4e 56 52 42 52 5f 53 31 5b 82 40 6a 49 CI0NVRBR_S1[.@jI 27a0: 44 45 30 08 5f 41 44 52 0c 00 00 0d 00 5b 80 41 DE0._ADR.....[.A 27b0: 30 39 30 02 0a 50 0a 18 5b 81 26 41 30 39 30 03 090..P..[.&A090. 27c0: 49 44 32 30 10 00 30 49 44 54 53 10 49 44 54 50 ID20..0IDTS.IDTP 27d0: 10 49 44 32 32 20 55 4d 53 53 10 55 4d 53 50 10 .ID22 UMSS.UMSP. 27e0: 08 49 44 45 50 11 03 0a 14 08 49 44 45 53 11 03 .IDEP.....IDES.. 27f0: 0a 14 14 4e 14 47 54 4d 5f 01 a0 17 93 68 0a 00 ...N.GTM_....h.. 2800: 70 49 44 54 50 60 70 55 4d 53 50 61 70 49 44 45 pIDTP`pUMSPapIDE 2810: 50 62 a1 13 70 49 44 54 53 60 70 55 4d 53 53 61 Pb..pIDTS`pUMSSa 2820: 70 49 44 45 53 62 8a 62 0a 00 50 49 4f 30 8a 62 pIDESb.b..PIO0.b 2830: 0a 04 44 4d 41 30 8a 62 0a 08 50 49 4f 31 8a 62 ..DMA0.b..PIO1.b 2840: 0a 0c 44 4d 41 31 8a 62 0a 10 46 4c 41 47 70 0a ..DMA1.b..FLAGp. 2850: 10 46 4c 41 47 7b 60 0b 00 0f 63 7b 60 0b 00 f0 .FLAG{`...c{`... 2860: 64 7a 63 0a 08 63 7a 64 0a 0c 64 72 63 64 63 77 dzc..czd..drcdcw 2870: 72 63 0a 02 00 0a 1e 50 49 4f 30 a0 14 92 94 50 rc.....PIO0....P 2880: 49 4f 30 0a b4 7d 46 4c 41 47 0a 02 46 4c 41 47 IO0..}FLAG..FLAG 2890: a0 27 7b 61 0b 00 40 00 7d 46 4c 41 47 0a 01 46 .'{a..@.}FLAG..F 28a0: 4c 41 47 7b 61 0b 00 07 63 7a 63 0a 08 63 70 55 LAG{a...czc..cpU 28b0: 32 54 5f 63 44 4d 41 30 a1 0a 70 50 49 4f 30 44 2T_cDMA0..pPIO0D 28c0: 4d 41 30 7b 60 0a 0f 63 7b 60 0a f0 64 7a 64 0a MA0{`..c{`..dzd. 28d0: 04 64 72 63 64 63 77 72 63 0a 02 00 0a 1e 50 49 .drcdcwrc.....PI 28e0: 4f 31 a0 14 92 94 50 49 4f 31 0a b4 7d 46 4c 41 O1....PIO1..}FLA 28f0: 47 0a 08 46 4c 41 47 a0 20 7b 61 0a 40 00 7d 46 G..FLAG. {a.@.}F 2900: 4c 41 47 0a 04 46 4c 41 47 7b 61 0a 07 63 70 55 LAG..FLAG{a..cpU 2910: 32 54 5f 63 44 4d 41 31 a1 0a 70 50 49 4f 31 44 2T_cDMA1..pPIO1D 2920: 4d 41 31 a0 10 93 68 0a 00 70 62 49 44 45 50 a4 MA1...h..pbIDEP. 2930: 49 44 45 50 a1 0c 70 62 49 44 45 53 a4 49 44 45 IDEP..pbIDES.IDE 2940: 53 14 49 04 55 32 54 5f 01 a0 08 93 68 0a 00 a4 S.I.U2T_....h... 2950: 0a 3c a0 08 93 68 0a 01 a4 0a 5a a0 08 93 68 0a .<...h....Z...h. 2960: 02 a4 0a 78 a0 08 93 68 0a 03 a4 0a 96 a0 08 93 ...x...h........ 2970: 68 0a 04 a4 0a 2d a0 08 93 68 0a 05 a4 0a 1e a0 h....-...h...... 2980: 08 93 68 0a 06 a4 0a 14 a4 0a 0f 14 49 04 54 32 ..h.........I.T2 2990: 55 5f 01 a0 08 94 68 0a 78 a4 0a 03 a0 08 94 68 U_....h.x......h 29a0: 0a 5a a4 0a 02 a0 08 94 68 0a 3c a4 0a 01 a0 08 .Z......h.<..... 29b0: 94 68 0a 2d a4 0a 00 a0 08 94 68 0a 1e a4 0a 04 .h.-......h..... 29c0: a0 08 94 68 0a 14 a4 0a 05 a0 08 94 68 0a 0f a4 ...h........h... 29d0: 0a 06 a4 0a 07 14 42 04 54 32 44 5f 01 a0 09 94 ......B.T2D_.... 29e0: 68 0b e0 01 a4 0a a8 a0 09 94 68 0b 86 01 a4 0a h.........h..... 29f0: 77 a0 08 94 68 0a f0 a4 0a 47 a0 08 94 68 0a b4 w...h....G...h.. 2a00: a4 0a 33 a0 08 94 68 0a 96 a4 0a 22 a0 08 94 68 ..3...h...."...h 2a10: 0a 78 a4 0a 21 a4 0a 20 14 43 1b 53 54 4d 5f 04 .x..!.. .C.STM_. 2a20: a0 3b 53 58 5f 5f 70 53 49 44 30 49 44 32 30 70 .;SX__pSID0ID20p 2a30: 53 49 44 31 49 44 54 53 70 53 49 44 32 49 44 54 SID1IDTSpSID2IDT 2a40: 50 70 53 49 44 33 49 44 32 32 70 53 49 44 34 55 PpSID3ID22pSID4U 2a50: 4d 53 53 70 53 49 44 35 55 4d 53 50 a1 37 70 49 MSSpSID5UMSP.7pI 2a60: 44 32 30 53 49 44 30 70 49 44 54 53 53 49 44 31 D20SID0pIDTSSID1 2a70: 70 49 44 54 50 53 49 44 32 70 49 44 32 32 53 49 pIDTPSID2pID22SI 2a80: 44 33 70 55 4d 53 53 53 49 44 34 70 55 4d 53 50 D3pUMSSSID4pUMSP 2a90: 53 49 44 35 70 0a 00 53 58 5f 5f 8a 68 0a 00 50 SID5p..SX__.h..P 2aa0: 49 4f 30 8a 68 0a 04 44 4d 41 30 8a 68 0a 08 50 IO0.h..DMA0.h..P 2ab0: 49 4f 31 8a 68 0a 0c 44 4d 41 31 8a 68 0a 10 46 IO1.h..DMA1.h..F 2ac0: 4c 41 47 a0 11 93 6b 0a 00 70 53 49 44 32 60 70 LAG...k..pSID2`p 2ad0: 53 49 44 35 61 a1 0d 70 53 49 44 31 60 70 53 49 SID5a..pSID1`pSI 2ae0: 44 34 61 a0 21 92 93 50 49 4f 30 0c ff ff ff ff D4a.!..PIO0..... 2af0: 7b 60 0a ff 60 79 54 32 44 5f 50 49 4f 30 0a 08 {`..`yT2D_PIO0.. 2b00: 62 7d 60 62 60 a0 1d 92 93 50 49 4f 31 0c ff ff b}`b`....PIO1... 2b10: ff ff 7b 60 0b 00 ff 60 7d 60 54 32 44 5f 50 49 ..{`...`}`T2D_PI 2b20: 4f 31 60 a0 24 7b 46 4c 41 47 0a 01 00 7b 61 0a O1`.${FLAG...{a. 2b30: ff 61 79 54 32 55 5f 44 4d 41 30 0a 08 62 7d 0b .ayT2U_DMA0..b}. 2b40: 00 c0 62 62 7d 62 61 61 a1 23 a0 21 92 93 44 4d ..bb}baa.#.!..DM 2b50: 41 30 0c ff ff ff ff 7b 60 0a ff 60 79 54 32 44 A0.....{`..`yT2D 2b60: 5f 44 4d 41 30 0a 08 62 7d 60 62 60 a0 1f 7b 46 _DMA0..b}`b`..{F 2b70: 4c 41 47 0a 04 00 7b 61 0b 00 ff 61 7d 0a c0 54 LAG...{a...a}..T 2b80: 32 55 5f 44 4d 41 31 62 7d 62 61 61 a1 1f a0 1d 2U_DMA1b}baa.... 2b90: 92 93 44 4d 41 31 0c ff ff ff ff 7b 60 0b 00 ff ..DMA1.....{`... 2ba0: 60 7d 60 54 32 44 5f 44 4d 41 31 60 a0 11 93 6b `}`T2D_DMA1`...k 2bb0: 0a 00 70 60 49 44 54 50 70 61 55 4d 53 50 a1 0d ..p`IDTPpaUMSP.. 2bc0: 70 60 49 44 54 53 70 61 55 4d 53 53 14 47 17 47 p`IDTSpaUMSS.G.G 2bd0: 54 46 5f 02 70 11 0a 0a 07 03 00 00 00 00 a0 ef TF_.p........... 2be0: 60 8c 60 0a 01 4d 4f 44 45 8c 60 0a 05 44 52 49 `.`..MODE.`..DRI 2bf0: 56 70 69 44 52 49 56 a0 0b 93 68 0a 00 70 49 44 VpiDRIV...h..pID 2c00: 45 50 61 a1 07 70 49 44 45 53 61 8a 61 0a 00 50 EPa..pIDESa.a..P 2c10: 49 4f 30 8a 61 0a 04 44 4d 41 30 8a 61 0a 08 50 IO0.a..DMA0.a..P 2c20: 49 4f 31 8a 61 0a 0c 44 4d 41 31 8a 61 0a 10 46 IO1.a..DMA1.a..F 2c30: 4c 47 58 a0 1c 93 69 0a a0 70 50 49 4f 30 62 70 LGX...i..pPIO0bp 2c40: 44 4d 41 30 63 7b 46 4c 47 58 0a 01 46 4c 47 58 DMA0c{FLGX..FLGX 2c50: a1 18 70 50 49 4f 31 62 70 44 4d 41 31 63 7b 46 ..pPIO1bpDMA1c{F 2c60: 4c 47 58 0a 04 46 4c 47 58 70 46 4c 47 58 61 a0 LGX..FLGXpFLGXa. 2c70: 0a 94 62 0b 86 01 70 0a 00 62 a1 29 a0 09 94 62 ..b...p..b.)...b 2c80: 0a f0 70 0a 01 62 a1 1d a0 09 94 62 0a b4 70 0a ..p..b.....b..p. 2c90: 02 62 a1 11 a0 09 94 62 0a 78 70 0a 03 62 a1 05 .b.....b.xp..b.. 2ca0: 70 0a 04 62 7d 0a 08 62 4d 4f 44 45 70 60 62 a0 p..b}..bMODEp`b. 2cb0: 4b 05 46 4c 47 58 a0 09 94 63 0a 5a 70 0a 00 63 K.FLGX...c.Zp..c 2cc0: a1 42 04 a0 09 94 63 0a 3c 70 0a 01 63 a1 35 a0 .B....c. Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [ACPI] sleep broken on IBM/Lenovo T61 [amd64] o kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/89411 acpi [acpi] acpiconf bug o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 f kern/67309 acpi zzz reboot computer (ACPI S3) o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 46 problems total. From avg at icyb.net.ua Mon Jan 19 04:11:57 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Jan 19 04:12:04 2009 Subject: ich watchdog vs intel smm code Message-ID: <49746E05.1070109@icyb.net.ua> Some time earlier I reported that ichwd driver doesn't produce any effect on my system with Intel DG33TL motherboard when watchdog timer is allowed to expire. I did some investigation and also discussed the issue with a maintainer of Linux iTCO_wdt driver, Wim Van Sebroeck. He told me that the issue is present on most of Intel motherboards with ICH9 chipset. All evidence seems to point in one direction - Intel SMM code. It seems that ICH9 always gets configured by BIOS to produce an SMI when a watchdog timer expires. Also, ICH watchdog has a logic to cause a reboot if its timer expires twice in a row, this is to avoid a potential hang in SMI handler. ICH9 allows SMI to be globally enabled and disabled. BIOS configures it to be enabled. Sometimes this bit is locked down (by BIOS), so it's not possible to change it, but sometimes it is not locked. So, if we globally disable SMI, then the watchdog in ICH9 does indeed cause a reboot. Evidently this happens after the timer expires twice in row. My conclusion is that SMI handler installed by BIOS somehow acknowledges watchdog SMI (e.g. clears a certain status bit, or performs watchdog timer reload). But it doesn't execute any "corrective" action. My guess is there might some configuration (or some other form of massaging) that needs to be done in order to convince SMM code to perform a reboot upon watchdog SMI. It would be nice if we had some Intel insiders who could provide a glimpse into Intel SMM code logic with respect to the watchdog. Finally some technical details: NMI2SMI_EN and TCO_LOCK bits of TCO1_CNT are set 1: pmbase+0x0068: 0x1200 (TCO1_CNT) in SMI_EN register TCO_EN bit is 1, GBL_SMI_EN is 1, "End of SMI (EOS)" bit is 1 and (not sure if this matters) LEGACY_USB_EN is 1: pmbase+0x0030: 0x0000203b (SMI_EN) "No Reboot (NR)" bit of GCS register is zero: 0x3410: 0x00c01444 -- Andriy Gapon From ken at mthelicon.com Mon Jan 19 04:27:25 2009 From: ken at mthelicon.com (Pegasus Mc Cleaft) Date: Mon Jan 19 04:27:37 2009 Subject: ich watchdog vs intel smm code In-Reply-To: <49746E05.1070109@icyb.net.ua> References: <49746E05.1070109@icyb.net.ua> Message-ID: ----- Original Message ----- From: "Andriy Gapon" To: ; Sent: Monday, January 19, 2009 12:11 PM Subject: ich watchdog vs intel smm code > > Some time earlier I reported that ichwd driver doesn't produce any > effect on my system with Intel DG33TL motherboard when watchdog timer is > allowed to expire. > I did some investigation and also discussed the issue with a maintainer > of Linux iTCO_wdt driver, Wim Van Sebroeck. He told me that the issue is > present on most of Intel motherboards with ICH9 chipset. > > All evidence seems to point in one direction - Intel SMM code. > It seems that ICH9 always gets configured by BIOS to produce an SMI when > a watchdog timer expires. Also, ICH watchdog has a logic to cause a > reboot if its timer expires twice in a row, this is to avoid a potential > hang in SMI handler. > ICH9 allows SMI to be globally enabled and disabled. BIOS configures it > to be enabled. Sometimes this bit is locked down (by BIOS), so it's not > possible to change it, but sometimes it is not locked. > So, if we globally disable SMI, then the watchdog in ICH9 does indeed > cause a reboot. Evidently this happens after the timer expires twice in > row. > > My conclusion is that SMI handler installed by BIOS somehow acknowledges > watchdog SMI (e.g. clears a certain status bit, or performs watchdog > timer reload). But it doesn't execute any "corrective" action. > > My guess is there might some configuration (or some other form of > massaging) that needs to be done in order to convince SMM code to > perform a reboot upon watchdog SMI. > > It would be nice if we had some Intel insiders who could provide a > glimpse into Intel SMM code logic with respect to the watchdog. > > Finally some technical details: > > NMI2SMI_EN and TCO_LOCK bits of TCO1_CNT are set 1: > pmbase+0x0068: 0x1200 (TCO1_CNT) > > in SMI_EN register TCO_EN bit is 1, GBL_SMI_EN is 1, "End of SMI > (EOS)" bit is 1 and (not sure if this matters) LEGACY_USB_EN is 1: > pmbase+0x0030: 0x0000203b (SMI_EN) > > "No Reboot (NR)" bit of GCS register is zero: > 0x3410: 0x00c01444 I have a simmilar problem on my gigabyte motherboard (one of the X48 ones), however, I believe the fault to be in hardware and not in firmware or software.. Mentioned in the datasheet for the ICH9, the speaker pin is used as a configuration pin while reset it asserted. If a logic 1 is present on this pin when reset is deasserted, the ICH9 chip locks out the ability for software to enable the watchdog. With the ichwd driver for BSD, this condition is announced with a message like "Watchdog present, but disabled in BIOS". (Well.. something close to that) ~Peg From avg at icyb.net.ua Mon Jan 19 04:37:17 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Jan 19 04:37:24 2009 Subject: ich watchdog vs intel smm code In-Reply-To: References: <49746E05.1070109@icyb.net.ua> Message-ID: <497473F5.4030506@icyb.net.ua> on 19/01/2009 14:27 Pegasus Mc Cleaft said the following: > > ----- Original Message ----- From: "Andriy Gapon" [snip] >> So, if we globally disable SMI, then the watchdog in ICH9 does indeed >> cause a reboot. Evidently this happens after the timer expires twice >> in row. [snip] > Mentioned in the datasheet for the ICH9, the speaker pin is used as a > configuration pin while reset it asserted. If a logic 1 is present on > this pin when reset is deasserted, the ICH9 chip locks out the ability > for software to enable the watchdog. With the ichwd driver for BSD, this > condition is announced with a message like "Watchdog present, but > disabled in BIOS". (Well.. something close to that) "ICH WDT present but disabled in BIOS or hardware" I believe your issue is quite a different one, it is older and known and explicitly reported by the driver. In this case the watchdog does work and does seem to generate SMI. -- Andriy Gapon From jakub_lach at mailplus.pl Mon Jan 19 17:25:08 2009 From: jakub_lach at mailplus.pl (Jakub Lach) Date: Mon Jan 19 17:25:15 2009 Subject: ACPI error, No pointer back to NS node in buffer obj In-Reply-To: <494DBF33.7040301@micom.mng.net> References: <494DBF33.7040301@micom.mng.net> Message-ID: <21555335.post@talk.nabble.com> Hi, I have observed similar errors on amd64 7.1 RELEASE LiveDVD. http://forums.freebsd.org/showthread.php?t=1533 These looks T400 specific. I'm looking forward to using this machine with FreeBSD stable, so I hope these issues will be adressed in current soon.. All best, Jakub Lach Ganbold wrote: > > Hi, > > These messages are appearing on CURRENT. > ... > cpu0: on acpi0 > ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj > 0x854857c0 [20070320] > ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands > for [OpcodeName unavailable] [20070320] > ACPI Error (psparse-0626): Method parse/execution failed > [\_PR_.CPU0._OSC] (Node 0x852c2620), AE_AML_INTERNAL > est0: on cpu0 > p4tcc0: on cpu0 > cpu1: on acpi0 > ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj > 0x85477c00 [20070320] > ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands > for [OpcodeName unavailable] [20070320] > ACPI Error (psparse-0626): Method parse/execution failed > [\_PR_.CPU1._OSC] (Node 0x852c2540), AE_AML_INTERNAL > est1: on cpu1 > ... > > Are above messages harmful? > > Additional infos at: > > http://people.freebsd.org/~ganbold/acpi.txt > > thanks, > > Ganbold > > > > > -- > Being popular is important. Otherwise people might not like you. > > _______________________________________________ > 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" > > -- View this message in context: http://www.nabble.com/ACPI-error%2C-No-pointer-back-to-NS-node-in-buffer-obj-tp21112077p21555335.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From robert.moore at intel.com Tue Jan 20 12:52:57 2009 From: robert.moore at intel.com (Moore, Robert) Date: Tue Jan 20 12:53:04 2009 Subject: ACPI error, No pointer back to NS node in buffer obj In-Reply-To: <21555335.post@talk.nabble.com> References: <494DBF33.7040301@micom.mng.net> <21555335.post@talk.nabble.com> Message-ID: <4911F71203A09E4D9981D27F9D8308580E629F09@orsmsx503.amr.corp.intel.com> Please post the acpidump for the machine. Thanks. >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Jakub Lach >Sent: Monday, January 19, 2009 5:25 PM >To: freebsd-acpi@freebsd.org >Subject: Re: ACPI error, No pointer back to NS node in buffer obj > > >Hi, > >I have observed similar errors on amd64 7.1 RELEASE LiveDVD. > >http://forums.freebsd.org/showthread.php?t=1533 > >These looks T400 specific. > >I'm looking forward to using this machine >with FreeBSD stable, so I hope these issues will be adressed in current >soon.. > >All best, > >Jakub Lach > > >Ganbold wrote: >> >> Hi, >> >> These messages are appearing on CURRENT. >> ... >> cpu0: on acpi0 >> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >> 0x854857c0 [20070320] >> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands >> for [OpcodeName unavailable] [20070320] >> ACPI Error (psparse-0626): Method parse/execution failed >> [\_PR_.CPU0._OSC] (Node 0x852c2620), AE_AML_INTERNAL >> est0: on cpu0 >> p4tcc0: on cpu0 >> cpu1: on acpi0 >> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >> 0x85477c00 [20070320] >> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands >> for [OpcodeName unavailable] [20070320] >> ACPI Error (psparse-0626): Method parse/execution failed >> [\_PR_.CPU1._OSC] (Node 0x852c2540), AE_AML_INTERNAL >> est1: on cpu1 >> ... >> >> Are above messages harmful? >> >> Additional infos at: >> >> http://people.freebsd.org/~ganbold/acpi.txt >> >> thanks, >> >> Ganbold >> >> >> >> >> -- >> Being popular is important. Otherwise people might not like you. >> >> _______________________________________________ >> 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" >> >> > >-- >View this message in context: http://www.nabble.com/ACPI-error%2C-No- >pointer-back-to-NS-node-in-buffer-obj-tp21112077p21555335.html >Sent from the freebsd-acpi mailing list archive at Nabble.com. > >_______________________________________________ >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" From jakub_lach at mailplus.pl Wed Jan 21 00:31:43 2009 From: jakub_lach at mailplus.pl (Jakub Lach) Date: Wed Jan 21 00:31:50 2009 Subject: ACPI error, No pointer back to NS node in buffer obj In-Reply-To: <4911F71203A09E4D9981D27F9D8308580E629F09@orsmsx503.amr.corp.intel.com> References: <494DBF33.7040301@micom.mng.net> <21555335.post@talk.nabble.com> <4911F71203A09E4D9981D27F9D8308580E629F09@orsmsx503.amr.corp.intel.com> Message-ID: <21578866.post@talk.nabble.com> Hello. Output of acpidump -dtv http://www.nabble.com/file/p21578866/acpi.txt acpi.txt Moore, Robert wrote: > > Please post the acpidump for the machine. > Thanks. > > >>-----Original Message----- >>From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>acpi@freebsd.org] On Behalf Of Jakub Lach >>Sent: Monday, January 19, 2009 5:25 PM >>To: freebsd-acpi@freebsd.org >>Subject: Re: ACPI error, No pointer back to NS node in buffer obj >> >> >>Hi, >> >>I have observed similar errors on amd64 7.1 RELEASE LiveDVD. >> >>http://forums.freebsd.org/showthread.php?t=1533 >> >>These looks T400 specific. >> >>I'm looking forward to using this machine >>with FreeBSD stable, so I hope these issues will be adressed in current >>soon.. >> >>All best, >> >>Jakub Lach >> >> >>Ganbold wrote: >>> >>> Hi, >>> >>> These messages are appearing on CURRENT. >>> ... >>> cpu0: on acpi0 >>> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >>> 0x854857c0 [20070320] >>> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands >>> for [OpcodeName unavailable] [20070320] >>> ACPI Error (psparse-0626): Method parse/execution failed >>> [\_PR_.CPU0._OSC] (Node 0x852c2620), AE_AML_INTERNAL >>> est0: on cpu0 >>> p4tcc0: on cpu0 >>> cpu1: on acpi0 >>> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >>> 0x85477c00 [20070320] >>> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands >>> for [OpcodeName unavailable] [20070320] >>> ACPI Error (psparse-0626): Method parse/execution failed >>> [\_PR_.CPU1._OSC] (Node 0x852c2540), AE_AML_INTERNAL >>> est1: on cpu1 >>> ... >>> >>> Are above messages harmful? >>> >>> Additional infos at: >>> >>> http://people.freebsd.org/~ganbold/acpi.txt >>> >>> thanks, >>> >>> Ganbold >>> >>> >>> >>> >>> -- >>> Being popular is important. Otherwise people might not like you. >>> >>> _______________________________________________ >>> 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" >>> >>> >> >>-- >>View this message in context: http://www.nabble.com/ACPI-error%2C-No- >>pointer-back-to-NS-node-in-buffer-obj-tp21112077p21555335.html >>Sent from the freebsd-acpi mailing list archive at Nabble.com. >> >>_______________________________________________ >>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" > > -- View this message in context: http://www.nabble.com/ACPI-error%2C-No-pointer-back-to-NS-node-in-buffer-obj-tp21112077p21578866.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From robert.moore at intel.com Fri Jan 23 14:58:58 2009 From: robert.moore at intel.com (Moore, Robert) Date: Fri Jan 23 15:59:48 2009 Subject: ACPICA version 20090123 released Message-ID: <4911F71203A09E4D9981D27F9D830858119E92C4@orsmsx503.amr.corp.intel.com> 23 January 2009. Summary of changes for version 20090123: This release is available at www.acpica.org/downloads. 1) ACPI CA Core Subsystem: Added the 2009 copyright to all module headers and signons. This affects virtually every file in the ACPICA core subsystem, the iASL compiler, and the tools/utilities. Implemented a change to allow the host to override any ACPI table, including dynamically loaded tables. Previously, only the DSDT could be replaced by the host. With this change, the AcpiOsTableOverride interface is called for each table found in the RSDT/XSDT during ACPICA initialization, and also whenever a table is dynamically loaded via the AML Load operator. Updated FADT flag definitions, especially the Boot Architecture flags. Debugger: For the Find command, automatically pad the input ACPI name with underscores if the name is shorter than 4 characters. This enables a match with the actual namespace entry which is itself padded with underscores. Example Code and Data Size: These are the sizes for the OS-independent acpica.lib produced by the Microsoft Visual C++ 6.0 32-bit compiler. The debug version of the code includes the debug output trace mechanism and has a much larger code and data size. Previous Release: Non-Debug Version: 82.3K Code, 17.4K Data, 99.7K Total Debug Version: 157.1K Code, 49.7K Data, 206.8K Total Current Release: Non-Debug Version: 82.3K Code, 17.5K Data, 99.8K Total Debug Version: 157.3K Code, 49.8K Data, 207.1K Total 2) iASL Compiler/Disassembler and Tools: Fix build error under Bison-2.4. Dissasembler: Enhanced FADT support. Added decoding of the Boot Architecture flags. Now decode all flags, regardless of the FADT version. Flag output includes the FADT version which first defined each flag. The iASL -g option now dumps the RSDT to a file (in addition to the FADT and DSDT). Windows only. From ivakras1 at gmail.com Sat Jan 24 10:14:39 2009 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Sat Jan 24 10:14:45 2009 Subject: ACPICA version 20090123 released In-Reply-To: <4911F71203A09E4D9981D27F9D830858119E92C4@orsmsx503.amr.corp.intel.com> References: <4911F71203A09E4D9981D27F9D830858119E92C4@orsmsx503.amr.corp.intel.com> Message-ID: <200901242113.43379.ivakras1@gmail.com> On Saturday 24 January 2009 01:30:23 Moore, Robert wrote: > 23 January 2009. Summary of changes for version 20090123: > > This release is available at www.acpica.org/downloads. > > 1) ACPI CA Core Subsystem: > > Added the 2009 copyright to all module headers and signons. This affects > virtually every file in the ACPICA core subsystem, the iASL compiler, and > the tools/utilities. > > Implemented a change to allow the host to override any ACPI table, > including dynamically loaded tables. Previously, only the DSDT could be > replaced by the host. With this change, the AcpiOsTableOverride interface > is called for each table found in the RSDT/XSDT during ACPICA > initialization, and also whenever a table is dynamically loaded via the AML > Load operator. > > Updated FADT flag definitions, especially the Boot Architecture flags. > > Debugger: For the Find command, automatically pad the input ACPI name with > underscores if the name is shorter than 4 characters. This enables a match > with the actual namespace entry which is itself padded with underscores. > > Example Code and Data Size: These are the sizes for the OS-independent > acpica.lib produced by the Microsoft Visual C++ 6.0 32-bit compiler. The > debug version of the code includes the debug output trace mechanism and has > a much larger code and data size. > > Previous Release: > Non-Debug Version: 82.3K Code, 17.4K Data, 99.7K Total > Debug Version: 157.1K Code, 49.7K Data, 206.8K Total > Current Release: > Non-Debug Version: 82.3K Code, 17.5K Data, 99.8K Total > Debug Version: 157.3K Code, 49.8K Data, 207.1K Total > > 2) iASL Compiler/Disassembler and Tools: > > Fix build error under Bison-2.4. > > Dissasembler: Enhanced FADT support. Added decoding of the Boot > Architecture flags. Now decode all flags, regardless of the FADT version. > Flag output includes the FADT version which first defined each flag. > > The iASL -g option now dumps the RSDT to a file (in addition to the FADT > and DSDT). Windows only. > > _______________________________________________ > 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" Can i integrate this new release into my 7-STABLE environment? May be some `how to` or other instructions? From peterjeremy at optushome.com.au Sat Jan 24 23:00:17 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sat Jan 24 23:00:25 2009 Subject: ACPICA version 20090123 released In-Reply-To: <200901242113.43379.ivakras1@gmail.com> References: <4911F71203A09E4D9981D27F9D830858119E92C4@orsmsx503.amr.corp.intel.com> <200901242113.43379.ivakras1@gmail.com> Message-ID: <20090125030600.GA1755@server.vk2pj.dyndns.org> On 2009-Jan-24 21:13:43 +0300, Dmitry Kolosov wrote: >On Saturday 24 January 2009 01:30:23 Moore, Robert wrote: >> 23 January 2009. Summary of changes for version 20090123: >Can i integrate this new release into my 7-STABLE environment? May be some `how >to` or other instructions? Robert Moore's mail is a vendor head's up that a new ACPI version has been released. It will be integrated into FreeBSD at some stage and possibly back-ported to 7.x. - depending on free time and exactly what has been changed. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20090125/fa3e170a/attachment.pgp From webmaster at kibab.com Sun Jan 25 00:47:52 2009 From: webmaster at kibab.com (Ilya Bakulin) Date: Sun Jan 25 00:48:00 2009 Subject: ACPI AE_NO_HARDWARE_RESPONSE workaround Message-ID: <1232873276.3689.2.camel@kibab-nb.kibab.com> Skipped content of type multipart/signed-------------- next part -------------- !DSPAM:497c2735967001263114152! From jakub_lach at mailplus.pl Sun Jan 25 07:27:40 2009 From: jakub_lach at mailplus.pl (Jakub Lach) Date: Sun Jan 25 07:27:47 2009 Subject: ACPICA version 20090123 released In-Reply-To: <20090125030600.GA1755@server.vk2pj.dyndns.org> References: <4911F71203A09E4D9981D27F9D830858119E92C4@orsmsx503.amr.corp.intel.com> <200901242113.43379.ivakras1@gmail.com> <20090125030600.GA1755@server.vk2pj.dyndns.org> Message-ID: <21652756.post@talk.nabble.com> Hello. Will new ACPI solve my acpi errors mentioned in http://forums.freebsd.org/showthread.php?t=1533 ? If so, I'm eagerly looking forward to having it integrated in STABLE branch. Best regards, -Jakub Lach Peter Jeremy wrote: > > On 2009-Jan-24 21:13:43 +0300, Dmitry Kolosov wrote: >>On Saturday 24 January 2009 01:30:23 Moore, Robert wrote: >>> 23 January 2009. Summary of changes for version 20090123: > >>Can i integrate this new release into my 7-STABLE environment? May be some `how >>to` or other instructions? > > Robert Moore's mail is a vendor head's up that a new ACPI version has > been released. It will be integrated into FreeBSD at some stage and > possibly back-ported to 7.x. - depending on free time and exactly what > has been changed. > > -- > Peter Jeremy > Please excuse any delays as the result of my ISP's inability to implement > an MTA that is either RFC2821-compliant or matches their claimed > behaviour. > > > -- View this message in context: http://www.nabble.com/ACPICA-version-20090123-released-tp21635129p21652756.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From yanefbsd at gmail.com Sun Jan 25 12:34:14 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Jan 25 12:34:21 2009 Subject: ACPICA version 20090123 released In-Reply-To: <21652756.post@talk.nabble.com> References: <4911F71203A09E4D9981D27F9D830858119E92C4@orsmsx503.amr.corp.intel.com> <200901242113.43379.ivakras1@gmail.com> <20090125030600.GA1755@server.vk2pj.dyndns.org> <21652756.post@talk.nabble.com> Message-ID: On Jan 25, 2009, at 7:27, Jakub Lach wrote: > > Hello. > > Will new ACPI solve my acpi errors mentioned in > http://forums.freebsd.org/showthread.php?t=1533 ? > If so, I'm eagerly looking forward to having it integrated in STABLE > branch. > > Best regards, > -Jakub Lach > > > > Peter Jeremy wrote: >> >> On 2009-Jan-24 21:13:43 +0300, Dmitry Kolosov >> wrote: >>> On Saturday 24 January 2009 01:30:23 Moore, Robert wrote: >>>> 23 January 2009. Summary of changes for version 20090123: >> >>> Can i integrate this new release into my 7-STABLE environment? May >>> be some > `how >>> to` or other instructions? >> >> Robert Moore's mail is a vendor head's up that a new ACPI version has >> been released. It will be integrated into FreeBSD at some stage and >> possibly back-ported to 7.x. - depending on free time and exactly >> what >> has been changed. >> >> -- >> Peter Jeremy >> Please excuse any delays as the result of my ISP's inability to >> implement >> an MTA that is either RFC2821-compliant or matches their claimed >> behaviour. >> >> >> *shakes magic eightball* Answer: Maybe. Seriously though? I'd read the release notes to get a better idea of whether or not this was fixed by this update.... Cheers, -Garrett From pisymbol at gmail.com Sun Jan 25 18:02:02 2009 From: pisymbol at gmail.com (Alexander Sack) Date: Sun Jan 25 18:02:09 2009 Subject: Reset register flag versus the actual register Message-ID: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> Hi Everybody: I've ran into the quintessential "it works on Linux but does not work on FreeBSD" vendor comment regarding the boxes ability to reboot successfully. I'm running FreeBSD-6.1 but this also applies the FreeBSD-CURRENT as well. The problem boils down to the fact that the BIOS does set the ResetRegister bit in the FADT feature flags. However, I've noticed that latest stable Linux kernel has the following logic with respect to the reset register: acpi_reboot(): 18 /* Is the reset register supported? */ 19 if (!(acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER) || 20 rr->bit_width != 8 || rr->bit_offset != 0) 21 return; http://lxr.linux.no/linux+v2.6.28/drivers/acpi/reboot.c CURRENT looks like this via the shutdown_final EVENTHANDLE: acpi_shutdown_final(): 1821 } else if ((howto & RB_HALT) == 0 && 1822 (AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) && 1823 sc->acpi_handle_reboot) { 1824 /* Reboot using the reset register. */ http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/acpica/acpi.c?rev=1.254 Two questions: 1) Why is the sysctl acpi_handle_reboot zero by default? Shouldn't it be more prudent to rely on the ACPI reboot hook than the legacy keyboard controller methods? I realize there is some history here but it would seem to me that the "&&" should be an "||" which would allow me to override the ACPI_FADT_RESET_REGISTER flag and force an ACPI reset? 2) Is there something to be said for a patch like this: -- acpi.c.0 2009-01-25 19:56:48.000000000 -0500 +++ acpi.c 2009-01-25 20:10:34.000000000 -0500 @@ -1818,18 +1818,20 @@ DELAY(1000000); printf("ACPI power-off failed - timeout\n"); } - } else if ((howto & RB_HALT) == 0 && - (AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) && - sc->acpi_handle_reboot) { - /* Reboot using the reset register. */ - status = AcpiHwLowLevelWrite( - AcpiGbl_FADT.ResetRegister.BitWidth, - AcpiGbl_FADT.ResetValue, &AcpiGbl_FADT.ResetRegister); - if (ACPI_FAILURE(status)) { - printf("ACPI reset failed - %s\n", AcpiFormatException(status)); - } else { - DELAY(1000000); - printf("ACPI reset failed - timeout\n"); + } else if ((howto & RB_HALT) == 0 && sc->acpi_handle_reboot) { + if ((AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) || + (AcpiGbl_FADT.ResetRegister.BitWidth != 8) || + (AcpiGbl_FADT.ResetRegister.BitOffset != 0)) { + /* Reboot using the reset register. */ + status = AcpiHwLowLevelWrite( + AcpiGbl_FADT.ResetRegister.BitWidth, + AcpiGbl_FADT.ResetValue, &AcpiGbl_FADT.ResetRegister); + if (ACPI_FAILURE(status)) { + printf("ACPI reset failed - %s\n", AcpiFormatException(status)); + } else { + DELAY(1000000); + printf("ACPI reset failed - timeout\n"); + } } } else if (sc->acpi_do_disable && panicstr == NULL) { /* Basically, if the ResetRegister is filled in despite the FADT feature flags bit, trust it and move forward (Linux logic). That's the reason why my box reboots correctly on Linux and utterly hangs miserably on FreeBSD. I understand this is a BIOS/ACPI bug, I understand the keyboard controller reboot method should probably be emulated in the BIOS (though the vendor could argue they no longer support legacy methods which is to me not necessarily a bad thing), and I understand that FreeBSD is not Linux. With that all said, I don't see the downside here with respect to reboot with respect to either points (allow the user to force the issue or believe the ResetRegister values themselves as a test for validity). Feedback most appreciated! Thanks! -aps From pisymbol at gmail.com Sun Jan 25 18:23:45 2009 From: pisymbol at gmail.com (Alexander Sack) Date: Sun Jan 25 18:23:56 2009 Subject: Reset register flag versus the actual register In-Reply-To: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> References: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> Message-ID: <3c0b01820901251823p5c4536fcy3924d7a1209bfe71@mail.gmail.com> Whoops!!! I had a brain fart... On Sun, Jan 25, 2009 at 8:35 PM, Alexander Sack wrote: > Hi Everybody: > > I've ran into the quintessential "it works on Linux but does not work > on FreeBSD" vendor comment regarding the boxes ability to reboot > successfully. I'm running FreeBSD-6.1 but this also applies the > FreeBSD-CURRENT as well. The problem boils down to the fact that the > BIOS does set the ResetRegister bit in the FADT feature flags. > However, I've noticed that latest stable Linux kernel has the > following logic with respect to the reset register: > > acpi_reboot(): > > 18 /* Is the reset register supported? */ > 19 if (!(acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER) || > 20 rr->bit_width != 8 || rr->bit_offset != 0) > 21 return; This checks the flag. I didn't see the NOT for some odd reason. Uggh, weird, I got to go back and now find out why on Linux uses the hook and FreeBSD does not. -aps From bugmaster at FreeBSD.org Mon Jan 26 03:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 26 03:07:08 2009 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200901261106.n0QB6of1024166@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [acpi] sleep broken on IBM/Lenovo T61 in amd64 mode o kern/128639 acpi [patch] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/89411 acpi [acpi] acpiconf bug o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 f kern/67309 acpi zzz reboot computer (ACPI S3) o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 46 problems total. From tom at khubla.com Tue Jan 27 10:22:33 2009 From: tom at khubla.com (Tom Everett) Date: Tue Jan 27 10:22:40 2009 Subject: SMP Problem on IBM x330 Server Message-ID: <497F4857.1060005@khubla.com> I originally posted this to "FreeBSD Questions" but was told that the ACPI list might be more appropriate. I'm running the "stock" FreeBSD 7.1 kernel on an IBM x330 machine. The machine has two physical processors but it seems that FreeBSD 7.1 only sees one. I downloaded the kernel source and it seems that the GENERIC kernel has SMP installed. Is there something else I can try? Thanks in advance for your wisdom. $ sysctl -a | grep cpu kern.threads.virtual_cpu: 1 kern.ccpu: 0 kern.smp.cpus: 1 kern.smp.maxcpus: 16 debug.cpufreq.verbose: 0 debug.cpufreq.lowest: 0 debug.kdb.stop_cpus: 1 debug.stop_cpus_with_nmi: 1 debug.PMAP1changedcpu: 0 hw.ncpu: 1 hw.acpi.cpu.cx_lowest: C1 machdep.cpu_idle_hlt: 1 machdep.hlt_cpus: 0 dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU1 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.cx_supported: C1/0 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% Copyright (c) 1992-2009 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 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III CPU family 1133MHz (1128.54-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff real memory = 1073659904 (1023 MB) avail memory = 1036943360 (988 MB) ACPI APIC Table: ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 3 to IRQ 30 acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4e8-0x4eb on acpi0 pcib0: on acpi0 pci0: on pcib0 vgapci0: mem 0xfeb80000-0xfebfffff,0xf0000000-0xf7ffffff at device 1.0 on pci0 fxp0: port 0x2200-0x223f mem 0xfeb7f000-0xfeb7ffff,0xfea00000-0xfeafffff irq 27 at device 2.0 on pci0 fxp0: Disabling dynamic standby mode in EEPROM fxp0: New EEPROM ID: 0x48a0 fxp0: EEPROM checksum @ 0x3f: 0xbe76 -> 0xbe76 miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:02:55:c6:69:58 fxp0: [ITHREAD] fxp1: port 0x2240-0x227f mem 0xfeb7e000-0xfeb7efff,0xfe900000-0xfe9fffff irq 25 at device 10.0 on pci0 fxp1: Disabling dynamic standby mode in EEPROM fxp1: New EEPROM ID: 0x48a0 fxp1: EEPROM checksum @ 0x3f: 0x2d79 -> 0x2d79 miibus1: on fxp1 inphy1: PHY 1 on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:02:55:c6:69:59 fxp1: [ITHREAD] isab0: port 0x440-0x44f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x700-0x70f at device 15.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] ohci0: mem 0xfeb7d000-0xfeb7dfff irq 7 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 2 ports with 2 removable, self powered pcib1: on acpi0 pci1: on pcib1 ahc0: port 0x2300-0x23ff mem 0xeffff000-0xefffffff irq 28 at device 3.0 on pci1 ahc0: [ITHREAD] aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs atapci1: port 0x2280-0x22ff,0x2400-0x24ff mem 0xefffe000-0xefffefff,0xeffc0000-0xeffdffff irq 20 at device 5.0 on pci1 atapci1: [ITHREAD] atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] fdc0: port 0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] cpu0: on acpi0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcafff,0xcb000-0xcc7ff,0xcc800-0xd4fff pnpid ORM0000 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1128539539 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDROM at ata1-master UDMA33 ad4: 476940MB at ata2-master SATA150 ad6: 476940MB at ata3-master SATA300 Waiting 5 seconds for SCSI devices to settle ar0: 476939MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master Trying to mount root from ufs:/dev/ar0s1a From yanefbsd at gmail.com Tue Jan 27 10:32:48 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Tue Jan 27 10:32:54 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <497F4857.1060005@khubla.com> References: <497F4857.1060005@khubla.com> Message-ID: <243FF450-D8B0-491D-A341-8758F8EF20D4@gmail.com> On Jan 27, 2009, at 9:45 AM, Tom Everett wrote: > > I originally posted this to "FreeBSD Questions" but was told that > the ACPI list might be more appropriate. > > I'm running the "stock" FreeBSD 7.1 kernel on an IBM x330 machine. > The machine has two physical processors but it seems that FreeBSD > 7.1 only sees one. I downloaded the kernel source and it seems that > the GENERIC kernel has SMP installed. Is there something else I can > try? Thanks in advance for your wisdom. > > $ sysctl -a | grep cpu > kern.threads.virtual_cpu: 1 > kern.ccpu: 0 > kern.smp.cpus: 1 > kern.smp.maxcpus: 16 > debug.cpufreq.verbose: 0 > debug.cpufreq.lowest: 0 > debug.kdb.stop_cpus: 1 > debug.stop_cpus_with_nmi: 1 > debug.PMAP1changedcpu: 0 > hw.ncpu: 1 > hw.acpi.cpu.cx_lowest: C1 > machdep.cpu_idle_hlt: 1 > machdep.hlt_cpus: 0 > dev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_PR_.CPU1 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.cx_supported: C1/0 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% Did you install the SMP kernel from sysinstall? There's a difference. Thanks, -Garrett From Juergen.Dankoweit at t-online.de Tue Jan 27 10:41:56 2009 From: Juergen.Dankoweit at t-online.de (=?ISO-8859-15?Q?J=FCrgen_Dankoweit?=) Date: Tue Jan 27 10:42:02 2009 Subject: Questions about some acpi-warnings Message-ID: <497F51C7.206@FreeBSD-Onkel.de> Hello to the list, on my Thinkpad T43 I get the following warning in /var/log/messages while the notebook is in suspend mode: acpi_ec0: warning: EC done before starting event wait acpi_ec0: wait timed out (response), forcing polled mode These two messages are displayed during boot time: ACPI APIC Table: ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address or length: 0 102C/0 [20070320] What do this messages mean? Many thanks for your answers. JD From tom at khubla.com Tue Jan 27 11:23:49 2009 From: tom at khubla.com (Tom Everett) Date: Tue Jan 27 11:23:54 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <243FF450-D8B0-491D-A341-8758F8EF20D4@gmail.com> References: <497F4857.1060005@khubla.com> <243FF450-D8B0-491D-A341-8758F8EF20D4@gmail.com> Message-ID: <497F5DB4.2080701@khubla.com> Um..... I doubt it. *blush* Can I fix that via sysinstall? Garrett Cooper wrote: > On Jan 27, 2009, at 9:45 AM, Tom Everett wrote: > >> >> I originally posted this to "FreeBSD Questions" but was told that the >> ACPI list might be more appropriate. >> >> I'm running the "stock" FreeBSD 7.1 kernel on an IBM x330 machine. >> The machine has two physical processors but it seems that FreeBSD 7.1 >> only sees one. I downloaded the kernel source and it seems that the >> GENERIC kernel has SMP installed. Is there something else I can >> try? Thanks in advance for your wisdom. >> >> $ sysctl -a | grep cpu >> kern.threads.virtual_cpu: 1 >> kern.ccpu: 0 >> kern.smp.cpus: 1 >> kern.smp.maxcpus: 16 >> debug.cpufreq.verbose: 0 >> debug.cpufreq.lowest: 0 >> debug.kdb.stop_cpus: 1 >> debug.stop_cpus_with_nmi: 1 >> debug.PMAP1changedcpu: 0 >> hw.ncpu: 1 >> hw.acpi.cpu.cx_lowest: C1 >> machdep.cpu_idle_hlt: 1 >> machdep.hlt_cpus: 0 >> dev.cpu.0.%desc: ACPI CPU >> dev.cpu.0.%driver: cpu >> dev.cpu.0.%location: handle=\_PR_.CPU1 >> dev.cpu.0.%pnpinfo: _HID=none _UID=0 >> dev.cpu.0.%parent: acpi0 >> dev.cpu.0.cx_supported: C1/0 >> dev.cpu.0.cx_lowest: C1 >> dev.cpu.0.cx_usage: 100.00% > > Did you install the SMP kernel from sysinstall? There's a difference. > Thanks, > -Garrett From tom at khubla.com Tue Jan 27 12:06:20 2009 From: tom at khubla.com (Tom Everett) Date: Tue Jan 27 12:06:26 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <243FF450-D8B0-491D-A341-8758F8EF20D4@gmail.com> References: <497F4857.1060005@khubla.com> <243FF450-D8B0-491D-A341-8758F8EF20D4@gmail.com> Message-ID: <497F67B0.70609@khubla.com> ok, two problems. I don't remember that I had the option to explicitly install an SMP kernl, and looking back here (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install.html) , I don't see that sysinstall gave me that option. Additionally, I have the kernel source and I see that in GENERIC, SMP is enabled. Am I missing something? Garrett Cooper wrote: > On Jan 27, 2009, at 9:45 AM, Tom Everett wrote: > >> >> I originally posted this to "FreeBSD Questions" but was told that the >> ACPI list might be more appropriate. >> >> I'm running the "stock" FreeBSD 7.1 kernel on an IBM x330 machine. >> The machine has two physical processors but it seems that FreeBSD 7.1 >> only sees one. I downloaded the kernel source and it seems that the >> GENERIC kernel has SMP installed. Is there something else I can >> try? Thanks in advance for your wisdom. >> >> $ sysctl -a | grep cpu >> kern.threads.virtual_cpu: 1 >> kern.ccpu: 0 >> kern.smp.cpus: 1 >> kern.smp.maxcpus: 16 >> debug.cpufreq.verbose: 0 >> debug.cpufreq.lowest: 0 >> debug.kdb.stop_cpus: 1 >> debug.stop_cpus_with_nmi: 1 >> debug.PMAP1changedcpu: 0 >> hw.ncpu: 1 >> hw.acpi.cpu.cx_lowest: C1 >> machdep.cpu_idle_hlt: 1 >> machdep.hlt_cpus: 0 >> dev.cpu.0.%desc: ACPI CPU >> dev.cpu.0.%driver: cpu >> dev.cpu.0.%location: handle=\_PR_.CPU1 >> dev.cpu.0.%pnpinfo: _HID=none _UID=0 >> dev.cpu.0.%parent: acpi0 >> dev.cpu.0.cx_supported: C1/0 >> dev.cpu.0.cx_lowest: C1 >> dev.cpu.0.cx_usage: 100.00% > > Did you install the SMP kernel from sysinstall? There's a difference. > Thanks, > -Garrett From yanefbsd at gmail.com Tue Jan 27 12:24:28 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Tue Jan 27 12:24:34 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <497F67B0.70609@khubla.com> References: <497F4857.1060005@khubla.com> <243FF450-D8B0-491D-A341-8758F8EF20D4@gmail.com> <497F67B0.70609@khubla.com> Message-ID: <7d6fde3d0901271224h3b77d59et88fc032857365700@mail.gmail.com> On Tue, Jan 27, 2009 at 11:59 AM, Tom Everett wrote: > ok, two problems. I don't remember that I had the option to explicitly > install an SMP kernl, and looking back here > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install.html) , I > don't see that sysinstall gave me that option. Additionally, I have the > kernel source and I see that in GENERIC, SMP is enabled. Am I missing > something? > > > Garrett Cooper wrote: >> >> On Jan 27, 2009, at 9:45 AM, Tom Everett wrote: >> >>> >>> I originally posted this to "FreeBSD Questions" but was told that the >>> ACPI list might be more appropriate. >>> >>> I'm running the "stock" FreeBSD 7.1 kernel on an IBM x330 machine. The >>> machine has two physical processors but it seems that FreeBSD 7.1 only sees >>> one. I downloaded the kernel source and it seems that the GENERIC kernel >>> has SMP installed. Is there something else I can try? Thanks in advance >>> for your wisdom. >>> >>> $ sysctl -a | grep cpu >>> kern.threads.virtual_cpu: 1 >>> kern.ccpu: 0 >>> kern.smp.cpus: 1 >>> kern.smp.maxcpus: 16 >>> debug.cpufreq.verbose: 0 >>> debug.cpufreq.lowest: 0 >>> debug.kdb.stop_cpus: 1 >>> debug.stop_cpus_with_nmi: 1 >>> debug.PMAP1changedcpu: 0 >>> hw.ncpu: 1 >>> hw.acpi.cpu.cx_lowest: C1 >>> machdep.cpu_idle_hlt: 1 >>> machdep.hlt_cpus: 0 >>> dev.cpu.0.%desc: ACPI CPU >>> dev.cpu.0.%driver: cpu >>> dev.cpu.0.%location: handle=\_PR_.CPU1 >>> dev.cpu.0.%pnpinfo: _HID=none _UID=0 >>> dev.cpu.0.%parent: acpi0 >>> dev.cpu.0.cx_supported: C1/0 >>> dev.cpu.0.cx_lowest: C1 >>> dev.cpu.0.cx_usage: 100.00% >> >> Did you install the SMP kernel from sysinstall? There's a difference. >> Thanks, >> -Garrett Nope -- that would be it. Is one CPU not active in the BIOS? Do you have the latest BIOS flashed from IBM? Does a Linux disk see both CPU's? Cheers, -Garrett From tom at khubla.com Tue Jan 27 12:54:53 2009 From: tom at khubla.com (Tom Everett) Date: Tue Jan 27 12:55:08 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <7d6fde3d0901271224h3b77d59et88fc032857365700@mail.gmail.com> References: <497F4857.1060005@khubla.com> <243FF450-D8B0-491D-A341-8758F8EF20D4@gmail.com> <497F67B0.70609@khubla.com> <7d6fde3d0901271224h3b77d59et88fc032857365700@mail.gmail.com> Message-ID: <497F730A.7050402@khubla.com> the CPUs are active in the BIOS. The BIOS is v 1.05. with 1.06 being the very latest. According to IBM the changes from 1.0.5 to 1.0.6 are * Added in serial remote console redirection * Fixed PXE ROM execution failure when using PXE on planar Ethernet #2 * Removed the "Auto Configure" IRQ option for the System Service Processor IRQ setting in POST/BIOS setup to prevent erroneous configuration change and diskette drive failure messages I have a number of these machines running linux with no problems. ? Garrett Cooper wrote: > On Tue, Jan 27, 2009 at 11:59 AM, Tom Everett wrote: > >> ok, two problems. I don't remember that I had the option to explicitly >> install an SMP kernl, and looking back here >> (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install.html) , I >> don't see that sysinstall gave me that option. Additionally, I have the >> kernel source and I see that in GENERIC, SMP is enabled. Am I missing >> something? >> >> >> Garrett Cooper wrote: >> >>> On Jan 27, 2009, at 9:45 AM, Tom Everett wrote: >>> >>> >>>> I originally posted this to "FreeBSD Questions" but was told that the >>>> ACPI list might be more appropriate. >>>> >>>> I'm running the "stock" FreeBSD 7.1 kernel on an IBM x330 machine. The >>>> machine has two physical processors but it seems that FreeBSD 7.1 only sees >>>> one. I downloaded the kernel source and it seems that the GENERIC kernel >>>> has SMP installed. Is there something else I can try? Thanks in advance >>>> for your wisdom. >>>> >>>> $ sysctl -a | grep cpu >>>> kern.threads.virtual_cpu: 1 >>>> kern.ccpu: 0 >>>> kern.smp.cpus: 1 >>>> kern.smp.maxcpus: 16 >>>> debug.cpufreq.verbose: 0 >>>> debug.cpufreq.lowest: 0 >>>> debug.kdb.stop_cpus: 1 >>>> debug.stop_cpus_with_nmi: 1 >>>> debug.PMAP1changedcpu: 0 >>>> hw.ncpu: 1 >>>> hw.acpi.cpu.cx_lowest: C1 >>>> machdep.cpu_idle_hlt: 1 >>>> machdep.hlt_cpus: 0 >>>> dev.cpu.0.%desc: ACPI CPU >>>> dev.cpu.0.%driver: cpu >>>> dev.cpu.0.%location: handle=\_PR_.CPU1 >>>> dev.cpu.0.%pnpinfo: _HID=none _UID=0 >>>> dev.cpu.0.%parent: acpi0 >>>> dev.cpu.0.cx_supported: C1/0 >>>> dev.cpu.0.cx_lowest: C1 >>>> dev.cpu.0.cx_usage: 100.00% >>>> >>> Did you install the SMP kernel from sysinstall? There's a difference. >>> Thanks, >>> -Garrett >>> > > Nope -- that would be it. Is one CPU not active in the BIOS? Do > you have the latest BIOS flashed from IBM? Does a Linux disk see both > CPU's? > Cheers, > -Garrett > From pisymbol at gmail.com Tue Jan 27 14:37:14 2009 From: pisymbol at gmail.com (Alexander Sack) Date: Tue Jan 27 14:39:37 2009 Subject: Reset register flag versus the actual register Message-ID: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> Hi Everybody: I've ran into the quintessential "it works on Linux but does not work on FreeBSD" vendor comment regarding the boxes ability to reboot successfully. I'm running FreeBSD-6.1 but this also applies the FreeBSD-CURRENT as well. The problem boils down to the fact that the BIOS does set the ResetRegister bit in the FADT feature flags. However, I've noticed that latest stable Linux kernel has the following logic with respect to the reset register: acpi_reboot(): 18 /* Is the reset register supported? */ 19 if (!(acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER) || 20 rr->bit_width != 8 || rr->bit_offset != 0) 21 return; http://lxr.linux.no/linux+v2.6.28/drivers/acpi/reboot.c CURRENT looks like this via the shutdown_final EVENTHANDLE: acpi_shutdown_final(): 1821 } else if ((howto & RB_HALT) == 0 && 1822 (AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) && 1823 sc->acpi_handle_reboot) { 1824 /* Reboot using the reset register. */ http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/acpica/acpi.c?rev=1.254 Two questions: 1) Why is the sysctl acpi_handle_reboot zero by default? Shouldn't it be more prudent to rely on the ACPI reboot hook than the legacy keyboard controller methods? I realize there is some history here but it would seem to me that the "&&" should be an "||" which would allow me to override the ACPI_FADT_RESET_REGISTER flag and force an ACPI reset? 2) Is there something to be said for a patch like this: -- acpi.c.0 2009-01-25 19:56:48.000000000 -0500 +++ acpi.c 2009-01-25 20:10:34.000000000 -0500 @@ -1818,18 +1818,20 @@ DELAY(1000000); printf("ACPI power-off failed - timeout\n"); } - } else if ((howto & RB_HALT) == 0 && - (AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) && - sc->acpi_handle_reboot) { - /* Reboot using the reset register. */ - status = AcpiHwLowLevelWrite( - AcpiGbl_FADT.ResetRegister.BitWidth, - AcpiGbl_FADT.ResetValue, &AcpiGbl_FADT.ResetRegister); - if (ACPI_FAILURE(status)) { - printf("ACPI reset failed - %s\n", AcpiFormatException(status)); - } else { - DELAY(1000000); - printf("ACPI reset failed - timeout\n"); + } else if ((howto & RB_HALT) == 0 && sc->acpi_handle_reboot) { + if ((AcpiGbl_FADT.Flags & ACPI_FADT_RESET_REGISTER) || + (AcpiGbl_FADT.ResetRegister.BitWidth != 8) || + (AcpiGbl_FADT.ResetRegister.BitOffset != 0)) { + /* Reboot using the reset register. */ + status = AcpiHwLowLevelWrite( + AcpiGbl_FADT.ResetRegister.BitWidth, + AcpiGbl_FADT.ResetValue, &AcpiGbl_FADT.ResetRegister); + if (ACPI_FAILURE(status)) { + printf("ACPI reset failed - %s\n", AcpiFormatException(status)); + } else { + DELAY(1000000); + printf("ACPI reset failed - timeout\n"); + } } } else if (sc->acpi_do_disable && panicstr == NULL) { /* Basically, if the ResetRegister is filled in despite the FADT feature flags bit, trust it and move forward (Linux logic). That's the reason why my box reboots correctly on Linux and utterly hangs miserably on FreeBSD. I understand this is a BIOS/ACPI bug, I understand the keyboard controller reboot method should probably be emulated in the BIOS (though the vendor could argue they no longer support legacy methods which is to me not necessarily a bad thing), and I understand that FreeBSD is not Linux. With that all said, I don't see the downside here with respect to reboot with respect to either points (allow the user to force the issue or believe the ResetRegister values themselves as a test for validity). Feedback most appreciated! Thanks! -aps _______________________________________________ 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" From pisymbol at gmail.com Tue Jan 27 14:37:17 2009 From: pisymbol at gmail.com (Alexander Sack) Date: Tue Jan 27 14:39:38 2009 Subject: Reset register flag versus the actual register In-Reply-To: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> References: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com> Message-ID: <3c0b01820901251823p5c4536fcy3924d7a1209bfe71@mail.gmail.com> Whoops!!! I had a brain fart... On Sun, Jan 25, 2009 at 8:35 PM, Alexander Sack wrote: > Hi Everybody: > > I've ran into the quintessential "it works on Linux but does not work > on FreeBSD" vendor comment regarding the boxes ability to reboot > successfully. I'm running FreeBSD-6.1 but this also applies the > FreeBSD-CURRENT as well. The problem boils down to the fact that the > BIOS does set the ResetRegister bit in the FADT feature flags. > However, I've noticed that latest stable Linux kernel has the > following logic with respect to the reset register: > > acpi_reboot(): > > 18 /* Is the reset register supported? */ > 19 if (!(acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER) || > 20 rr->bit_width != 8 || rr->bit_offset != 0) > 21 return; This checks the flag. I didn't see the NOT for some odd reason. Uggh, weird, I got to go back and now find out why on Linux uses the hook and FreeBSD does not. -aps _______________________________________________ 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" From jhb at freebsd.org Wed Jan 28 06:31:19 2009 From: jhb at freebsd.org (John Baldwin) Date: Wed Jan 28 06:31:26 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <497F4857.1060005@khubla.com> References: <497F4857.1060005@khubla.com> Message-ID: <200901280911.30748.jhb@freebsd.org> On Tuesday 27 January 2009 12:45:59 pm Tom Everett wrote: > > I originally posted this to "FreeBSD Questions" but was told that the > ACPI list might be more appropriate. > > I'm running the "stock" FreeBSD 7.1 kernel on an IBM x330 machine. The > machine has two physical processors but it seems that FreeBSD 7.1 only > sees one. I downloaded the kernel source and it seems that the GENERIC > kernel has SMP installed. Is there something else I can try? Thanks in > advance for your wisdom. Please provide the output of 'acpidump -t'. It seems the BIOS is not including both CPUs in the table it gives to the OS. -- John Baldwin From tom at khubla.com Wed Jan 28 08:58:37 2009 From: tom at khubla.com (Tom Everett) Date: Wed Jan 28 08:58:45 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <200901280911.30748.jhb@freebsd.org> References: <497F4857.1060005@khubla.com> <200901280911.30748.jhb@freebsd.org> Message-ID: <49808D1D.8030709@khubla.com> John Baldwin wrote: > On Tuesday 27 January 2009 12:45:59 pm Tom Everett wrote: > >> I originally posted this to "FreeBSD Questions" but was told that the >> ACPI list might be more appropriate. >> >> I'm running the "stock" FreeBSD 7.1 kernel on an IBM x330 machine. The >> machine has two physical processors but it seems that FreeBSD 7.1 only >> sees one. I downloaded the kernel source and it seems that the GENERIC >> kernel has SMP installed. Is there something else I can try? Thanks in >> advance for your wisdom. >> > > Please provide the output of 'acpidump -t'. It seems the BIOS is not > including both CPUs in the table it gives to the OS. > > After running the BIOS diagnostics, it seems that the BIOS has disabled the processor. Interestingly, in the normal BIOS config screen and the boot POST screen, everything appears normal. So, I have a number of other identical machines and I'll try a different one, in case the problem is this particular x330. Additionally, the normal BIOS config screen doesn't provide an option to "un-disable" the processor. Below is the dmesg and output of acpidump -t. Thanks everyone who responded and tried to help. /* RSD PTR: OEM=IBM, ACPI_Rev=1.0x (0) RSDT=0x3ffeff80, cksum=237 */ /* RSDT: Length=44, Revision=1, Checksum=230, OEMID=IBM, OEM Table ID=SEREMRLD, OEM Revision=0x1000, Creator ID=IBM, Creator Revision=0x45444f43 Entries={ 0x3ffeff00, 0x3ffefe80 } */ /* FACP: Length=116, Revision=1, Checksum=84, OEMID=IBM, OEM Table ID=SEREMRLD, OEM Revision=0x1000, Creator ID=IBM, Creator Revision=0x45444f43 FACS=0x3ffefe40, DSDT=0x3ffec340 INT_MODEL=APIC Preferred_PM_Profile=Unspecified (0) SCI_INT=3 SMI_CMD=0x600, ACPI_ENABLE=0xf0, ACPI_DISABLE=0xf1, S4BIOS_REQ=0x0 PSTATE_CNT=0x0 PM1a_EVT_BLK=0x4e0-0x4e3 PM1a_CNT_BLK=0x4e4-0x4e5 PM_TMR_BLK=0x4e8-0x4eb GPE0_BLK=0x4f0-0x4f7 P_LVL2_LAT=101 us, P_LVL3_LAT=1001 us FLUSH_SIZE=0, FLUSH_STRIDE=0 DUTY_OFFSET=1, DUTY_WIDTH=0 DAY_ALRM=68, MON_ALRM=69, CENTURY=0 IAPC_BOOT_ARCH= Flags={WBINVD,PROC_C1,SLP_BUTTON} */ /* FACS: Length=64, HwSig=0x8222800a, Firm_Wake_Vec=0x00000000 Global_Lock= Flags= Version=0 */ /* DSDT: Length=15020, Revision=1, Checksum=109, OEMID=IBM, OEM Table ID=SEREMRLD, OEM Revision=0x1000, Creator ID=MSFT, Creator Revision=0x100000b */ /* APIC: Length=94, Revision=1, Checksum=217, OEMID=IBM, OEM Table ID=SEREMRLD, OEM Revision=0x1000, Creator ID=IBM, Creator Revision=0x45444f43 Local APIC ADDR=0xfee00000 Flags={PC-AT} Type=Local APIC ACPI CPU=0 Flags={ENABLED} APIC ID=3 Type=Local APIC ACPI CPU=1 Flags={DISABLED} APIC ID=0 Type=IO APIC APIC ID=14 INT BASE=0 ADDR=0x00000000fec00000 Type=IO APIC APIC ID=13 INT BASE=16 ADDR=0x00000000fec01000 Type=INT Override BUS=0 IRQ=3 INTR=30 Flags={Polarity=conforming, Trigger=conforming} */ Copyright (c) 1992-2009 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 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0dec000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0dec160. Calibrating clock(s) ... i8254 clock: 1192986 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1128539600 Hz CPU: Intel(R) Pentium(R) III CPU family 1133MHz (1128.54-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff Instruction TLB: 4 KB pages, 4-way set associative, 32 entries Instruction TLB: 4 MB pages, fully associative, 2 entries Data TLB: 4 KB pages, 4-way set associative, 64 entries 2nd-level cache: 512 KB, 8-way set associative, 32 byte line size 1st-level instruction cache: 16 KB, 4-way set associative, 32 byte line size Data TLB: 4 MB Pages, 4-way set associative, 8 entries 1st-level data cache: 16 KB, 4-way set associative, 32 byte line size real memory = 1073659904 (1023 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000096fff, 614400 bytes (150 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001025000 - 0x000000003eda3fff, 1037561856 bytes (253311 pages) avail memory = 1036943360 (988 MB) Table 'FACP' at 0x3ffeff00 Table 'APIC' at 0x3ffefe80 MADT: Found table at 0x3ffefe80 MP Configuration Table version 1.4 found at 0xc00981e0 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 3 ACPI ID 0: enabled SMP: Added CPU 3 (AP) MADT: Found CPU APIC ID 0 ACPI ID 1: disabled ACPI APIC Table: bios32: Found BIOS32 Service Directory header at 0xc00fd5d0 bios32: Entry = 0xfd5e1 (c00fd5e1) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xd61c pnpbios: Found PnP BIOS data at 0xc00fde40 pnpbios: Entry = f0000:3a09 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 ULE: setup cpu group 0 ULE: setup cpu 0 ULE: adding cpu 0 to group 0: cpus 1 mask 0x1 ACPI: RSDP @ 0x0xfdfd0/0x0014 (v 0 IBM ) ACPI: RSDT @ 0x0x3ffeff80/0x002C (v 1 IBM SEREMRLD 0x00001000 IBM 0x45444F43) ACPI: FACP @ 0x0x3ffeff00/0x0074 (v 1 IBM SEREMRLD 0x00001000 IBM 0x45444F43) ACPI: DSDT @ 0x0x3ffec340/0x3AAC (v 1 IBM SEREMRLD 0x00001000 MSFT 0x0100000B) ACPI: FACS @ 0x0x3ffefe40/0x0040 ACPI: APIC @ 0x0x3ffefe80/0x005E (v 1 IBM SEREMRLD 0x00001000 IBM 0x45444F43) MADT: Found IO APIC ID 14, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 MADT: Found IO APIC ID 13, Interrupt 16 at 0xfec01000 MADT: Interrupt override: source 3, irq 30 ioapic0: intpin 3 disabled ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard cpu0 BSP: ID: 0x03000000 VER: 0x00040011 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00000000 err: 0x00010000 pcm: 0x00010000 ath_rate: version 1.2 wlan_amrr: wlan: <802.11 Link Layer> random: nfslock: pseudo-device io: kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support enabled null: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Jan 1 2009 14:37:00) npx0: INT 16 interface acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 3 to IRQ 30 ioapic1: routing intpin 14 (PCI IRQ 30) to vector 48 acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: wakeup code va 0xd7e92000 pa 0x1000 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000070 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00091166) pcibios: BIOS version 2.10 AcpiOsDerivePciId: \\_SB_.PCI0.RCNB -> bus 0 dev 0 func 0 AcpiOsDerivePciId: \\_SB_.PCI0.USB0.CFG2 -> bus 0 dev 15 func 2 AcpiOsDerivePciId: \\_SB_.PCI0.CIO1.IOB2 -> bus 0 dev 0 func 1 ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 0/16777200 0/16777200 -> 8 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4e8-0x4eb on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 10 Validation 0 10 N 0 10 After Disable 0 255 N 0 10 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 10 Validation 0 10 N 0 10 After Disable 0 255 N 0 10 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 none Validation 0 255 N 0 none After Disable 0 255 N 0 none pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 7 N 0 7 Validation 0 7 N 0 7 After Disable 0 255 N 0 7 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 9 Validation 0 9 N 0 9 After Disable 0 255 N 0 9 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 none Validation 0 255 N 0 none After Disable 0 255 N 0 none pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 none Validation 0 255 N 0 none After Disable 0 255 N 0 none pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 9 Validation 0 9 N 0 9 After Disable 0 255 N 0 9 pci_link8: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 none Validation 0 255 N 0 none After Disable 0 255 N 0 none pcib0: on acpi0 ACPI: Found matching pin for 0.15.INTA at func 2: 7 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x1166, dev=0x0009, revid=0x06 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0147, statreg=0x2200, cachelnsz=8 (dwords) lattimer=0x60 (2880 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0009, revid=0x06 domain=0, bus=0, slot=0, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0147, statreg=0x0200, cachelnsz=8 (dwords) lattimer=0x60 (2880 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x5333, dev=0x8a22, revid=0x06 domain=0, bus=0, slot=1, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xf8 (7440 ns), mingnt=0x04 (1000 ns), maxlat=0xff (63750 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfeb80000, size 19, enabled map[14]: type Prefetchable Memory, range 32, base 0xf0000000, size 27, enabled found-> vendor=0x8086, dev=0x1229, revid=0x08 domain=0, bus=0, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x64 (3000 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfeb7f000, size 12, enabled map[14]: type I/O Port, range 32, base 0x2200, size 6, enabled map[18]: type Memory, range 32, base 0xfea00000, size 20, enabled pcib0: matched entry for 0.2.INTA pcib0: slot 2 INTA hardwired to IRQ 27 found-> vendor=0x8086, dev=0x1229, revid=0x08 domain=0, bus=0, slot=10, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x64 (3000 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfeb7e000, size 12, enabled map[14]: type I/O Port, range 32, base 0x2240, size 6, enabled map[18]: type Memory, range 32, base 0xfe900000, size 20, enabled pcib0: matched entry for 0.10.INTA pcib0: slot 10 INTA hardwired to IRQ 25 found-> vendor=0x1166, dev=0x0200, revid=0x51 domain=0, bus=0, slot=15, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[90]: type I/O Port, range 32, base 0x440, size 4, enabled found-> vendor=0x1166, dev=0x0211, revid=0x00 domain=0, bus=0, slot=15, func=1 class=01-01-8a, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x64 (3000 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type I/O Port, range 32, base 0x700, size 4, enabled found-> vendor=0x1166, dev=0x0220, revid=0x04 domain=0, bus=0, slot=15, func=2 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0017, statreg=0x0280, cachelnsz=8 (dwords) lattimer=0x60 (2880 ns), mingnt=0x00 (0 ns), maxlat=0x50 (20000 ns) intpin=a, irq=7 map[10]: type Memory, range 32, base 0xfeb7d000, size 12, enabled pcib0: matched entry for 0.15.INTA (src \\_SB_.PCI0.LPUS:0) ioapic0: Changing trigger for pin 7 to level ioapic0: Changing polarity for pin 7 to low pcib0: slot 15 INTA routed to irq 7 via \\_SB_.PCI0.LPUS vgapci0: mem 0xfeb80000-0xfebfffff,0xf0000000-0xf7ffffff at device 1.0 on pci0 fxp0: port 0x2200-0x223f mem 0xfeb7f000-0xfeb7ffff,0xfea00000-0xfeafffff irq 27 at device 2.0 on pci0 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfeb7f000 fxp0: using memory space register mapping fxp0: Disabling dynamic standby mode in EEPROM fxp0: New EEPROM ID: 0x48a0 fxp0: EEPROM checksum @ 0x3f: 0xbe76 -> 0xbe76 fxp0: PCI IDs: 8086 1229 1014 105c 0008 fxp0: Dynamic Standby mode is enabled miibus0: on fxp0 inphy0: PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached fxp0: Ethernet address: 00:02:55:c6:69:58 ioapic1: routing intpin 11 (PCI IRQ 27) to vector 49 fxp0: [MPSAFE] fxp0: [ITHREAD] fxp1: port 0x2240-0x227f mem 0xfeb7e000-0xfeb7efff,0xfe900000-0xfe9fffff irq 25 at device 10.0 on pci0 fxp1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfeb7e000 fxp1: using memory space register mapping fxp1: Disabling dynamic standby mode in EEPROM fxp1: New EEPROM ID: 0x48a0 fxp1: EEPROM checksum @ 0x3f: 0x2d79 -> 0x2d79 fxp1: PCI IDs: 8086 1229 1014 105c 0008 fxp1: Dynamic Standby mode is enabled miibus1: on fxp1 inphy1: PHY 1 on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: bpf attached fxp1: Ethernet address: 00:02:55:c6:69:59 ioapic1: routing intpin 9 (PCI IRQ 25) to vector 50 fxp1: [MPSAFE] fxp1: [ITHREAD] isab0: port 0x440-0x44f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x700-0x70f at device 15.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x700 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=7f ostat1=7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat1=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: reset tp2 stat0=ff stat1=ff devices=0x0 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 51 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 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 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 52 ata1: [MPSAFE] ata1: [ITHREAD] ohci0: mem 0xfeb7d000-0xfeb7dfff irq 7 at device 15.2 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfeb7d000 ohci0: (New OHCI DeviceId=0x02201166) ioapic0: routing intpin 7 (ISA IRQ 7) to vector 53 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 2 ports with 2 removable, self powered pcib1: on acpi0 pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x9005, dev=0x008f, revid=0x02 domain=0, bus=1, slot=3, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0157, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x64 (3000 ns), mingnt=0x28 (10000 ns), maxlat=0x19 (6250 ns) intpin=a, irq=9 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x2300, size 8, enabled map[14]: type Memory, range 64, base 0xeffff000, size 12, enabled pcib1: matched entry for 1.3.INTA pcib1: slot 3 INTA hardwired to IRQ 28 found-> vendor=0x105a, dev=0x3577, revid=0x02 domain=0, bus=1, slot=5, func=0 class=01-04-00, hdrtype=0x00, mfdev=0 cmdreg=0x0157, statreg=0x0230, cachelnsz=1 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0x12 (4500 ns) intpin=a, irq=9 powerspec 2 supports D0 D1 D3 current D0 map[10]: type I/O Port, range 32, base 0x2280, size 7, enabled map[18]: type I/O Port, range 32, base 0x2400, size 8, enabled map[1c]: type Memory, range 32, base 0xefffe000, size 12, enabled map[20]: type Memory, range 32, base 0xeffc0000, size 17, enabled pcib1: matched entry for 1.5.INTA pcib1: slot 5 INTA hardwired to IRQ 20 ahc0: port 0x2300-0x23ff mem 0xeffff000-0xefffffff irq 28 at device 3.0 on pci1 ahc0: Defaulting to MEMIO off ahc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x2300 ahc0: Reading SEEPROM...done. ahc0: Manual LVD Termination ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: Downloading Sequencer Program... 423 instructions downloaded ahc0: Features 0x1def6, Bugs 0x40, Flags 0x28485560 ioapic1: routing intpin 12 (PCI IRQ 28) to vector 54 ahc0: [MPSAFE] ahc0: [ITHREAD] aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs atapci1: port 0x2280-0x22ff,0x2400-0x24ff mem 0xefffe000-0xefffefff,0xeffc0000-0xeffdffff irq 20 at device 5.0 on pci1 pci1: child atapci1 requested type 4 for rid 0x20, but the BAR says it is an memio ioapic1: routing intpin 4 (PCI IRQ 20) to vector 55 atapci1: [MPSAFE] atapci1: [ITHREAD] atapci1: Reserved 0x20000 bytes for rid 0x20 type 3 at 0xeffc0000 atapci1: Reserved 0x1000 bytes for rid 0x1c type 3 at 0xefffe000 ioapic1: routing intpin 4 (PCI IRQ 20) to vector 55 atapci1: [MPSAFE] atapci1: [ITHREAD] ata2: on atapci1 ata2: SATA connect time=0ms ata2: reset tp1 mask=01 ostat0=50 ostat1=00 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci1 ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=50 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: [MPSAFE] ata3: [ITHREAD] ata4: on atapci1 ata4: SATA connect status=00000000 ata4: [MPSAFE] ata4: [ITHREAD] ata5: on atapci1 ata5: SATA connect status=00000000 ata5: [MPSAFE] ata5: [ITHREAD] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 56 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0065 psm0: failed to reset the aux device. fdc0: port 0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 73 ioapic0: routing intpin 6 (ISA IRQ 6) to vector 57 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x8001 0x8011 0x8001 0x8001 sio0: irq maps: 0x8001 0x8011 0x8001 0x8001 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ioapic0: routing intpin 4 (ISA IRQ 4) to vector 58 sio0: [FILTER] cpu0: on acpi0 cpu0: switching to generic Cx mode unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff ex_isa_identify() ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcafff,0xcb000-0xcc7ff,0xcc800-0xd4fff pnpid ORM0000 on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fe0: not probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) ppc0: parallel port not found. ppc0: failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x8001 0x8001 0x8001 0x8001 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. procfs registered lapic: Divisor 2, Frequency 66384702 hz Timecounter "TSC" frequency 1128539600 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached hptrr: no controller detected. ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on ROSB4 chip acd0: setting UDMA33 on ROSB4 chip acd0: CDROM drive at ata1 as master acd0: read 4125KB/s (4125KB/s), 128KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 476940MB at ata2-master SATA150 ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue ********* ATA Promise FastTrak Metadata ********* promise_id dummy_0 0x00020000 magic_0 0x0000000049686815 magic_1 0x4968 magic_2 0x49686815 integrity 0x00000080 80 flags 0x07 7 disk_number 0 channel 0x00 device 0x00 magic_0 0x0000000049686815 disk_offset 0 disk_sectors 976773105 rebuild_lba 0x00000000 generation 0x0001 status 0x8f 8f type RAID1 total_disks 2 stripe_shift 1 array_width 1 array_number 0 total_sectors 976773105 cylinders 60800 heads 254 sectors 63 magic_1 0x0000496868154968 DISK# flags dummy_0 channel device magic_0 0 7 0x00 0x00 0x00 0x0000000049686815 1 7 0x00 0x01 0x00 0x0001000049686815 2 0 0x00 0x00 0x00 0x0000000000000000 3 0 0x00 0x00 0x00 0x0000000000000000 4 0 0x00 0x00 0x00 0x0000000000000000 5 0 0x00 0x00 0x00 0x0000000000000000 6 0 0x00 0x00 0x00 0x0000000000000000 7 0 0x00 0x00 0x00 0x0000000000000000 checksum 0x1389968a ================================================= ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad6: 476940MB at ata3-master SATA300 ad6: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue ********* ATA Promise FastTrak Metadata ********* promise_id dummy_0 0x00020000 magic_0 0x0001000049686815 magic_1 0x4968 magic_2 0x49686815 integrity 0x00000080 80 flags 0x07 7 disk_number 1 channel 0x01 device 0x00 magic_0 0x0001000049686815 disk_offset 0 disk_sectors 976773105 rebuild_lba 0x00000000 generation 0x0001 status 0x8f 8f type RAID1 total_disks 2 stripe_shift 1 array_width 1 array_number 0 total_sectors 976773105 cylinders 60800 heads 254 sectors 63 magic_1 0x0000496868154968 DISK# flags dummy_0 channel device magic_0 0 7 0x00 0x00 0x00 0x0000000049686815 1 7 0x00 0x01 0x00 0x0001000049686815 2 0 0x00 0x00 0x00 0x0000000000000000 3 0 0x00 0x00 0x00 0x0000000000000000 4 0 0x00 0x00 0x00 0x0000000000000000 5 0 0x00 0x00 0x00 0x0000000000000000 6 0 0x00 0x00 0x00 0x0000000000000000 7 0 0x00 0x00 0x00 0x0000000000000000 checksum 0x138c978a ================================================= Waiting 5 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:1. 0 SCBs aborted ahc0: Selection Timeout on A:3. 0 SCBs aborted ahc0: Selection Timeout on A:5. 0 SCBs aborted ahc0: Selection Timeout on A:6. 0 SCBs aborted ahc0: Selection Timeout on A:8. 0 SCBs aborted ahc0: Selection Timeout on A:9. 0 SCBs aborted ahc0: Selection Timeout on A:10. 0 SCBs aborted ahc0: Selection Timeout on A:11. 0 SCBs aborted ahc0: Selection Timeout on A:12. 0 SCBs aborted ahc0: Selection Timeout on A:13. 0 SCBs aborted ahc0: Selection Timeout on A:14. 0 SCBs aborted ahc0: Selection Timeout on A:15. 0 SCBs aborted ahc0: Selection Timeout on A:0. 0 SCBs aborted ahc0: Selection Timeout on A:2. 0 SCBs aborted ahc0: Selection Timeout on A:4. 0 SCBs aborted ATA PseudoRAID loaded ********** ATA PseudoRAID ar0 Metadata ********** ================================================= format Promise Fasttrak type RAID1 flags 0x01 1 magic_0 0x0000000000000000 magic_1 0x0000496868154968 generation 1 total_sectors 976773105 offset_sectors 0 heads 255 sectors 63 cylinders 60801 width 1 interleave 2 total_disks 2 disk 0: flags = 0x0b b ad4: sectors 976773105 disk 1: flags = 0x0b b ad6: sectors 976773105 ================================================= ar0: 476939MB status: READY ar0: 976773105 sectors [60801C/255H/63S] <> subdisks defined as: ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master GEOM: new disk ad4 GEOM: new disk ad6 GEOM: new disk ar0 Trying to mount root from ufs:/dev/ar0s1a start_init: trying /sbin/init From dan at obluda.cz Wed Jan 28 09:21:36 2009 From: dan at obluda.cz (Dan Lukes) Date: Wed Jan 28 09:21:43 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <49808D1D.8030709@khubla.com> References: <497F4857.1060005@khubla.com> <200901280911.30748.jhb@freebsd.org> <49808D1D.8030709@khubla.com> Message-ID: <49809418.1000802@obluda.cz> >> Please provide the output of 'acpidump -t'. It seems the BIOS is not >> including both CPUs in the table it gives to the OS. > After running the BIOS diagnostics, it seems that the BIOS has disabled > the processor. True: > APIC: Length=94, Revision=1, Checksum=217, > Type=Local APIC > ACPI CPU=0 > Flags={ENABLED} > APIC ID=3 > > Type=Local APIC > ACPI CPU=1 > Flags={DISABLED} > APIC ID=0 Second CPU is disabled. The FreeBSD say so: > APIC: Using the MADT enumerator. > MADT: Found CPU APIC ID 3 ACPI ID 0: enabled > SMP: Added CPU 3 (AP) > MADT: Found CPU APIC ID 0 ACPI ID 1: disabled It may be CPU failure detected during POST. Or broken CMOS content, sometime (try clear CMOS content). Dan From tom at khubla.com Wed Jan 28 10:10:46 2009 From: tom at khubla.com (Tom Everett) Date: Wed Jan 28 10:10:52 2009 Subject: SMP Problem on IBM x330 Server In-Reply-To: <49809418.1000802@obluda.cz> References: <497F4857.1060005@khubla.com> <200901280911.30748.jhb@freebsd.org> <49808D1D.8030709@khubla.com> <49809418.1000802@obluda.cz> Message-ID: <49809DEC.9030004@khubla.com> Dan Lukes wrote: >>> Please provide the output of 'acpidump -t'. It seems the BIOS is >>> not including both CPUs in the table it gives to the OS. > >> After running the BIOS diagnostics, it seems that the BIOS has >> disabled the processor. > > True: > >> APIC: Length=94, Revision=1, Checksum=217, > >> Type=Local APIC >> ACPI CPU=0 >> Flags={ENABLED} >> APIC ID=3 >> >> Type=Local APIC >> ACPI CPU=1 >> Flags={DISABLED} >> APIC ID=0 > > > Second CPU is disabled. > > The FreeBSD say so: > >> APIC: Using the MADT enumerator. >> MADT: Found CPU APIC ID 3 ACPI ID 0: enabled >> SMP: Added CPU 3 (AP) >> MADT: Found CPU APIC ID 0 ACPI ID 1: disabled > > > It may be CPU failure detected during POST. Or broken CMOS content, > sometime (try clear CMOS content). > > Dan Thanks! From robert.moore at intel.com Wed Jan 28 13:54:28 2009 From: robert.moore at intel.com (Moore, Robert) Date: Wed Jan 28 13:54:41 2009 Subject: ACPI error, No pointer back to NS node in buffer obj In-Reply-To: <21555335.post@talk.nabble.com> References: <494DBF33.7040301@micom.mng.net> <21555335.post@talk.nabble.com> Message-ID: <4911F71203A09E4D9981D27F9D83085811C41320@orsmsx503.amr.corp.intel.com> I believe that this problem may be fixed in ACPICA version 20080213: 13 February 2008. Summary of changes for version 20080213: commit 24a3157a90ddf851a0880c0b8963bc43481cd85b Author: Bob Moore Date: Thu Apr 10 19:06:43 2008 +0400 ACPICA: Fix for possible error when packages/buffers are passed to methods externally Fixed a problem where buffer and package objects passed as arguments to a control method via the external AcpiEvaluateObject interface could cause an AE_AML_INTERNAL exception depending on the order and type of operators executed by the target control method. Signed-off-by: Bob Moore Signed-off-by: Alexey Starikovskiy Signed-off-by: Len Brown >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Jakub Lach >Sent: Monday, January 19, 2009 5:25 PM >To: freebsd-acpi@freebsd.org >Subject: Re: ACPI error, No pointer back to NS node in buffer obj > > >Hi, > >I have observed similar errors on amd64 7.1 RELEASE LiveDVD. > >http://forums.freebsd.org/showthread.php?t=1533 > >These looks T400 specific. > >I'm looking forward to using this machine >with FreeBSD stable, so I hope these issues will be adressed in current >soon.. > >All best, > >Jakub Lach > > >Ganbold wrote: >> >> Hi, >> >> These messages are appearing on CURRENT. >> ... >> cpu0: on acpi0 >> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >> 0x854857c0 [20070320] >> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands >> for [OpcodeName unavailable] [20070320] >> ACPI Error (psparse-0626): Method parse/execution failed >> [\_PR_.CPU0._OSC] (Node 0x852c2620), AE_AML_INTERNAL >> est0: on cpu0 >> p4tcc0: on cpu0 >> cpu1: on acpi0 >> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >> 0x85477c00 [20070320] >> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands >> for [OpcodeName unavailable] [20070320] >> ACPI Error (psparse-0626): Method parse/execution failed >> [\_PR_.CPU1._OSC] (Node 0x852c2540), AE_AML_INTERNAL >> est1: on cpu1 >> ... >> >> Are above messages harmful? >> >> Additional infos at: >> >> http://people.freebsd.org/~ganbold/acpi.txt >> >> thanks, >> >> Ganbold >> >> >> >> >> -- >> Being popular is important. Otherwise people might not like you. >> >> _______________________________________________ >> 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" >> >> > >-- >View this message in context: http://www.nabble.com/ACPI-error%2C-No- >pointer-back-to-NS-node-in-buffer-obj-tp21112077p21555335.html >Sent from the freebsd-acpi mailing list archive at Nabble.com. > >_______________________________________________ >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" From robert.moore at intel.com Wed Jan 28 14:06:58 2009 From: robert.moore at intel.com (Moore, Robert) Date: Wed Jan 28 14:07:11 2009 Subject: ACPI error, No pointer back to NS node in buffer obj In-Reply-To: <4911F71203A09E4D9981D27F9D83085811C41320@orsmsx503.amr.corp.intel.com> References: <494DBF33.7040301@micom.mng.net> <21555335.post@talk.nabble.com> <4911F71203A09E4D9981D27F9D83085811C41320@orsmsx503.amr.corp.intel.com> Message-ID: <4911F71203A09E4D9981D27F9D83085811C41358@orsmsx503.amr.corp.intel.com> Our git repository is at git.acpica.org/repos/acpica.git >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Moore, Robert >Sent: Wednesday, January 28, 2009 1:54 PM >To: Jakub Lach; freebsd-acpi@freebsd.org >Subject: RE: ACPI error, No pointer back to NS node in buffer obj > > >I believe that this problem may be fixed in ACPICA version 20080213: > > >13 February 2008. Summary of changes for version 20080213: > > >commit 24a3157a90ddf851a0880c0b8963bc43481cd85b >Author: Bob Moore >Date: Thu Apr 10 19:06:43 2008 +0400 > > ACPICA: Fix for possible error when packages/buffers are passed to >methods externally > > Fixed a problem where buffer and package objects passed as > arguments to a control method via the external AcpiEvaluateObject > interface could cause an AE_AML_INTERNAL exception depending on the > order and type of operators executed by the target control method. > > Signed-off-by: Bob Moore > Signed-off-by: Alexey Starikovskiy > Signed-off-by: Len Brown > > > > > > >>-----Original Message----- >>From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>acpi@freebsd.org] On Behalf Of Jakub Lach >>Sent: Monday, January 19, 2009 5:25 PM >>To: freebsd-acpi@freebsd.org >>Subject: Re: ACPI error, No pointer back to NS node in buffer obj >> >> >>Hi, >> >>I have observed similar errors on amd64 7.1 RELEASE LiveDVD. >> >>http://forums.freebsd.org/showthread.php?t=1533 >> >>These looks T400 specific. >> >>I'm looking forward to using this machine >>with FreeBSD stable, so I hope these issues will be adressed in current >>soon.. >> >>All best, >> >>Jakub Lach >> >> >>Ganbold wrote: >>> >>> Hi, >>> >>> These messages are appearing on CURRENT. >>> ... >>> cpu0: on acpi0 >>> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >>> 0x854857c0 [20070320] >>> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands >>> for [OpcodeName unavailable] [20070320] >>> ACPI Error (psparse-0626): Method parse/execution failed >>> [\_PR_.CPU0._OSC] (Node 0x852c2620), AE_AML_INTERNAL >>> est0: on cpu0 >>> p4tcc0: on cpu0 >>> cpu1: on acpi0 >>> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >>> 0x85477c00 [20070320] >>> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands >>> for [OpcodeName unavailable] [20070320] >>> ACPI Error (psparse-0626): Method parse/execution failed >>> [\_PR_.CPU1._OSC] (Node 0x852c2540), AE_AML_INTERNAL >>> est1: on cpu1 >>> ... >>> >>> Are above messages harmful? >>> >>> Additional infos at: >>> >>> http://people.freebsd.org/~ganbold/acpi.txt >>> >>> thanks, >>> >>> Ganbold >>> >>> >>> >>> >>> -- >>> Being popular is important. Otherwise people might not like you. >>> >>> _______________________________________________ >>> 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" >>> >>> >> >>-- >>View this message in context: http://www.nabble.com/ACPI-error%2C-No- >>pointer-back-to-NS-node-in-buffer-obj-tp21112077p21555335.html >>Sent from the freebsd-acpi mailing list archive at Nabble.com. >> >>_______________________________________________ >>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" From jakub_lach at mailplus.pl Wed Jan 28 17:36:51 2009 From: jakub_lach at mailplus.pl (Jakub Lach) Date: Wed Jan 28 17:36:57 2009 Subject: ACPI error, No pointer back to NS node in buffer obj In-Reply-To: <4911F71203A09E4D9981D27F9D83085811C41358@orsmsx503.amr.corp.intel.com> References: <494DBF33.7040301@micom.mng.net> <21555335.post@talk.nabble.com> <4911F71203A09E4D9981D27F9D83085811C41320@orsmsx503.amr.corp.intel.com> <4911F71203A09E4D9981D27F9D83085811C41358@orsmsx503.amr.corp.intel.com> Message-ID: <21719238.post@talk.nabble.com> Thanks for information and kind assistance. If I understand correctly, Jung-uk Kim provides FreeBSD specific diffs of ACPICA. I will certainly try them. http://people.freebsd.org/~jkim/ Moore, Robert wrote: > > Our git repository is at git.acpica.org/repos/acpica.git > > >>-----Original Message----- >>From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>acpi@freebsd.org] On Behalf Of Moore, Robert >>Sent: Wednesday, January 28, 2009 1:54 PM >>To: Jakub Lach; freebsd-acpi@freebsd.org >>Subject: RE: ACPI error, No pointer back to NS node in buffer obj >> >> >>I believe that this problem may be fixed in ACPICA version 20080213: >> >> >>13 February 2008. Summary of changes for version 20080213: >> >> >>commit 24a3157a90ddf851a0880c0b8963bc43481cd85b >>Author: Bob Moore >>Date: Thu Apr 10 19:06:43 2008 +0400 >> >> ACPICA: Fix for possible error when packages/buffers are passed to >>methods externally >> >> Fixed a problem where buffer and package objects passed as >> arguments to a control method via the external AcpiEvaluateObject >> interface could cause an AE_AML_INTERNAL exception depending on the >> order and type of operators executed by the target control method. >> >> Signed-off-by: Bob Moore >> Signed-off-by: Alexey Starikovskiy >> Signed-off-by: Len Brown >> >> >> >> >> >> >>>-----Original Message----- >>>From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >>>acpi@freebsd.org] On Behalf Of Jakub Lach >>>Sent: Monday, January 19, 2009 5:25 PM >>>To: freebsd-acpi@freebsd.org >>>Subject: Re: ACPI error, No pointer back to NS node in buffer obj >>> >>> >>>Hi, >>> >>>I have observed similar errors on amd64 7.1 RELEASE LiveDVD. >>> >>>http://forums.freebsd.org/showthread.php?t=1533 >>> >>>These looks T400 specific. >>> >>>I'm looking forward to using this machine >>>with FreeBSD stable, so I hope these issues will be adressed in current >>>soon.. >>> >>>All best, >>> >>>Jakub Lach >>> >>> >>>Ganbold wrote: >>>> >>>> Hi, >>>> >>>> These messages are appearing on CURRENT. >>>> ... >>>> cpu0: on acpi0 >>>> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >>>> 0x854857c0 [20070320] >>>> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving >>>> operands >>>> for [OpcodeName unavailable] [20070320] >>>> ACPI Error (psparse-0626): Method parse/execution failed >>>> [\_PR_.CPU0._OSC] (Node 0x852c2620), AE_AML_INTERNAL >>>> est0: on cpu0 >>>> p4tcc0: on cpu0 >>>> cpu1: on acpi0 >>>> ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj >>>> 0x85477c00 [20070320] >>>> ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving >>>> operands >>>> for [OpcodeName unavailable] [20070320] >>>> ACPI Error (psparse-0626): Method parse/execution failed >>>> [\_PR_.CPU1._OSC] (Node 0x852c2540), AE_AML_INTERNAL >>>> est1: on cpu1 >>>> ... >>>> >>>> Are above messages harmful? >>>> >>>> Additional infos at: >>>> >>>> http://people.freebsd.org/~ganbold/acpi.txt >>>> >>>> thanks, >>>> >>>> Ganbold >>>> >>>> >>>> >>>> >>>> -- >>>> Being popular is important. Otherwise people might not like you. >>>> >>>> _______________________________________________ >>>> 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" >>>> >>>> >>> >>>-- >>>View this message in context: http://www.nabble.com/ACPI-error%2C-No- >>>pointer-back-to-NS-node-in-buffer-obj-tp21112077p21555335.html >>>Sent from the freebsd-acpi mailing list archive at Nabble.com. >>> >>>_______________________________________________ >>>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" > > -- View this message in context: http://www.nabble.com/ACPI-error%2C-No-pointer-back-to-NS-node-in-buffer-obj-tp21112077p21719238.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From y.k.thalib at gmail.com Wed Jan 28 23:31:23 2009 From: y.k.thalib at gmail.com (Yasir Khalid) Date: Wed Jan 28 23:31:29 2009 Subject: ACPI problem: Installing FreeBSD 7.0 in Pentium3 machine, Message-ID: Hai guys, I have acer machine which I will install with FreeBSD 7.0, but its failed during the boot-up, The error was > /boot/kernel/acpi.ko text=0x520e8 data=0x23a0+0x186c > syms=[0x4+0x85c0+0x4+0xb056] more specific, just after I select the first option*(Boot FreeBSD [default]) * in* FreeBSD Welcome Menu* *Machine detail *(from bios) Processor : Pentium III 866 Mhz Product Name: Acer Veriton 5100 MainBoard ID: S50M I have tried to disable the acpi, and same without good result, the error with acpi disabled was > | Yes, just a line symbol and hang. Is there anyhing i can do with this ? Let me know i need to put more info for thus problem, Looking forward for your help. - Yasir - From yanefbsd at gmail.com Thu Jan 29 00:00:05 2009 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Jan 29 00:00:11 2009 Subject: ACPI problem: Installing FreeBSD 7.0 in Pentium3 machine, In-Reply-To: References: Message-ID: <841E3245-1B63-4AB6-AEA9-9E09BECCCC2E@gmail.com> On Jan 28, 2009, at 11:08 PM, Yasir Khalid wrote: > Hai guys, > I have acer machine which I will install with FreeBSD 7.0, but its > failed > during the boot-up, > The error was > >> /boot/kernel/acpi.ko text=0x520e8 data=0x23a0+0x186c >> syms=[0x4+0x85c0+0x4+0xb056] > > > more specific, just after I select the first option*(Boot FreeBSD > [default]) > * in* FreeBSD Welcome Menu* > > *Machine detail *(from bios) > Processor : Pentium III 866 Mhz > Product Name: Acer Veriton 5100 > MainBoard ID: S50M > > I have tried to disable the acpi, and same without good result, > the error with acpi disabled was > >> | > > Yes, just a line symbol and hang. > Is there anyhing i can do with this ? > Let me know i need to put more info for thus problem, > > Looking forward for your help. > > - Yasir - Yasir, Could you try a 7.1 CD please? Thanks, -Garrett From jhb at freebsd.org Thu Jan 29 06:09:41 2009 From: jhb at freebsd.org (John Baldwin) Date: Thu Jan 29 06:09:47 2009 Subject: ACPI problem: Installing FreeBSD 7.0 in Pentium3 machine, In-Reply-To: References: Message-ID: <200901290814.07882.jhb@freebsd.org> On Thursday 29 January 2009 2:08:02 am Yasir Khalid wrote: > Hai guys, > I have acer machine which I will install with FreeBSD 7.0, but its failed > during the boot-up, > The error was > > > /boot/kernel/acpi.ko text=0x520e8 data=0x23a0+0x186c > > syms=[0x4+0x85c0+0x4+0xb056] > > > more specific, just after I select the first option*(Boot FreeBSD [default]) > * in* FreeBSD Welcome Menu* > > *Machine detail *(from bios) > Processor : Pentium III 866 Mhz > Product Name: Acer Veriton 5100 > MainBoard ID: S50M > > I have tried to disable the acpi, and same without good result, > the error with acpi disabled was > > > | > > Yes, just a line symbol and hang. > Is there anyhing i can do with this ? > Let me know i need to put more info for thus problem, > > Looking forward for your help. What are you using for your console? (e.g. serial console, VGA + keyboard, or both) -- John Baldwin From andrnils at gmail.com Fri Jan 30 02:38:14 2009 From: andrnils at gmail.com (Andreas Nilsson) Date: Fri Jan 30 02:38:20 2009 Subject: acpi_ibm on t61p Message-ID: Hello, I've been using 7.1-RELEASE i386 for some time now, and I have noticed some minor issuses with the acpi_ibm driver. The fan does not reach it's full potential: with dev.acpi_ibm.0.fan=0 and dev.acpi_ibm.0.fan_level=7 i get ~3300 RPM, whereas with dev.acpi_ibm.0.fan=1 I get ~3100 RPM. During a long compile this get the temperature up over 90 degrees Centigrade, which is not so nice. On linux and windows I can get the fan up to 4600 RPM if i disable the fan controller and just let the fan run att full speed. In FreeBSD I can't disable the fan controller. The lcd_brightness is not updated if I use Fn+Home or Fn+End to change the brightness, but setting the values via sysctl changes the brightness. The volume is not updated when sound level is changed, nor does the volume up/down/mute have any effect. The sound and brightness are not as important, just annoying... Best regards Andreas Nilsson From ghostp at dzsy.org Fri Jan 30 12:55:41 2009 From: ghostp at dzsy.org (=?ISO-8859-1?Q?Sz=E9kv=F6lgyi_P=E9ter?=) Date: Fri Jan 30 12:55:48 2009 Subject: acpi_ibm on t61p In-Reply-To: References: Message-ID: <49836343.8040804@dzsy.org> Hello, Andreas Nilsson wrote: > The lcd_brightness is not updated if I use Fn+Home or Fn+End to change the > brightness, but setting the values via sysctl changes the brightness. > > The volume is not updated when sound level is changed, nor does the volume > up/down/mute have any effect I have the same problem with Acer Extensa 5620 laptop. How you can change the lcd_brightness with sysctl? I can'nt find the brightness controll sysctl name. I run on XOrg the xev program and it send me keycode for the volume up/down, brightness up/down. And I use lineakd for controll the sound level with mixer. And I thinks i use also for brightness level. Best regards, Peter From mav at FreeBSD.org Sat Jan 31 05:06:04 2009 From: mav at FreeBSD.org (mav@FreeBSD.org) Date: Sat Jan 31 05:06:11 2009 Subject: kern/89411: [acpi] acpiconf bug Message-ID: <200901311306.n0VD63bD049287@freefall.freebsd.org> Synopsis: [acpi] acpiconf bug State-Changed-From-To: open->feedback State-Changed-By: mav State-Changed-When: Sat Jan 31 12:58:52 UTC 2009 State-Changed-Why: This is probably not acpiconf, but ACPI AML code problem. I had the same problem on my ACER TM6292. Due to bug in AML code, it returned negative current value when battery charging, which was interpreted as positive. Small AML fix solved it for me. Also I have just merged to 7-STABLE patch that fixes mA rate indication. http://www.freebsd.org/cgi/query-pr.cgi?pr=89411 From brd at FreeBSD.org Sat Jan 31 23:58:45 2009 From: brd at FreeBSD.org (brd@FreeBSD.org) Date: Sat Jan 31 23:58:56 2009 Subject: kern/130683: [ACPI] shutdown hangs after syncing disks - ACPI race? Message-ID: <200902010758.n117wiHe095633@freefall.freebsd.org> Synopsis: [ACPI] shutdown hangs after syncing disks - ACPI race? Responsible-Changed-From-To: freebsd-bugs->freebsd-acpi Responsible-Changed-By: brd Responsible-Changed-When: Sun Feb 1 07:57:43 UTC 2009 Responsible-Changed-Why: Over to maintainer. http://www.freebsd.org/cgi/query-pr.cgi?pr=130683