From mav at FreeBSD.org Sun Nov 2 10:46:34 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Sun Nov 2 10:49:40 2008 Subject: Is the C3 possible with SMP? Message-ID: <490DF584.5080506@FreeBSD.org> Hi. I have tried to enable C3 state on my Core2Duo laptop and found that it is not working good. System HZ timer stops during CPU sleep. After some investigation I have found that it is due to LAPIC timer used for HZ stopped during C3 state (same as during AMD's C1E). So the question is: Is it possible (or planned) to make it work somehow? For example, by using some external timer instead of LAPIC's one? ACPI reports about 20% less idle power consumption with C3 state comparing to C2. It would be interesting to get additional half an hour on battery. -- Alexander Motin From gaijin.k at gmail.com Sun Nov 2 12:16:05 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sun Nov 2 12:16:11 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <490DF584.5080506@FreeBSD.org> References: <490DF584.5080506@FreeBSD.org> Message-ID: <1225656933.1202.2.camel@RabbitsDen> On Sun, 2008-11-02 at 20:46 +0200, Alexander Motin wrote: > Hi. > > I have tried to enable C3 state on my Core2Duo laptop and found that it > is not working good. System HZ timer stops during CPU sleep. After some > investigation I have found that it is due to LAPIC timer used for HZ > stopped during C3 state (same as during AMD's C1E). > > So the question is: Is it possible (or planned) to make it work somehow? > For example, by using some external timer instead of LAPIC's one? > > ACPI reports about 20% less idle power consumption with C3 state > comparing to C2. It would be interesting to get additional half an hour > on battery. > You can get half way there by adding dev.cpu.1.cx_lowest=C3 to /etc/sysctl.conf I do realize that this is not The Solution, but it still saves battery. HTH, -- Alexandre "Sunny" Kovalenko (????????? ?????????) From amistry at am-productions.biz Sun Nov 2 13:30:04 2008 From: amistry at am-productions.biz (Anish Mistry) Date: Sun Nov 2 13:30:13 2008 Subject: kern/121504: [patch] Correctly set hw.acpi.osname on certain machines Message-ID: <200811022130.mA2LU4ja063200@freefall.freebsd.org> The following reply was made to PR kern/121504; it has been noted by GNATS. From: Anish Mistry To: Jung-uk Kim Cc: bug-followup@freebsd.org, John Baldwin Subject: Re: kern/121504: [patch] Correctly set hw.acpi.osname on certain machines Date: Sun, 2 Nov 2008 16:59:02 -0400 --nextPart19176370.nKuXPQD2aR Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 31 October 2008, Jung-uk Kim wrote: > If you are still feeling adventurous, please try the attached > patch. Note that _OSI is very different from _OS_ and we cannot > reuse "hw.acpi.osname" tunable here. First of all, _OSI method > must be able to match multiple entries, not just predefined OS > strings, e.g., "3.0 Thermal Model", "Extended Address Space > Descriptor", etc. although nobody really uses these 'feature group > strings' for their BIOS implementations. (Ideally, if there is a > device driver which implemented the feature, the driver is > responsible for registering its capabilities to this table.) > > With the attached patch, you can add multiple entries by setting > "hw.acpi.supported_osi" tunable and they must be comma-separated, > e.g.: Still no change on my system, but it seems that this would be good to=20 get in as it might help other people. =2D-=20 Anish Mistry amistry@am-productions.biz AM Productions http://am-productions.biz/ --nextPart19176370.nKuXPQD2aR Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkkOFJcACgkQxqA5ziudZT04VwCdEw8KJL/kTofrccYWCAJIfLq0 shsAoK9wWQe3cR/pP6ARj5tbveUvdovx =UHQt -----END PGP SIGNATURE----- --nextPart19176370.nKuXPQD2aR-- From mav at FreeBSD.org Sun Nov 2 14:06:24 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Sun Nov 2 14:06:37 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <1225656933.1202.2.camel@RabbitsDen> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> Message-ID: <490E245C.7070900@FreeBSD.org> Alexandre "Sunny" Kovalenko wrote: >> I have tried to enable C3 state on my Core2Duo laptop and found that it >> is not working good. System HZ timer stops during CPU sleep. After some >> investigation I have found that it is due to LAPIC timer used for HZ >> stopped during C3 state (same as during AMD's C1E). >> >> So the question is: Is it possible (or planned) to make it work somehow? >> For example, by using some external timer instead of LAPIC's one? >> >> ACPI reports about 20% less idle power consumption with C3 state >> comparing to C2. It would be interesting to get additional half an hour >> on battery. >> > You can get half way there by adding > > dev.cpu.1.cx_lowest=C3 > > to /etc/sysctl.conf Thanks. 1. Looks like it does not kill the timer. 2. I haven't got any benefit from it in idle state. According to `acpiconf -i 0` I have about 13 Amps (IMHO more looks like Watts) with both C2 and this half-to-C3, but only 11 Amps in full C3 (but without timer). 3. I have got about 10% benefit (33 Amps against 36) when cpu0 is 100% busy while cpu1 is idle. -- Alexander Motin From gaijin.k at gmail.com Sun Nov 2 14:27:25 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sun Nov 2 14:27:39 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <490E245C.7070900@FreeBSD.org> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> <490E245C.7070900@FreeBSD.org> Message-ID: <1225664813.1202.5.camel@RabbitsDen> On Mon, 2008-11-03 at 00:06 +0200, Alexander Motin wrote: > Alexandre "Sunny" Kovalenko wrote: > >> I have tried to enable C3 state on my Core2Duo laptop and found that it > >> is not working good. System HZ timer stops during CPU sleep. After some > >> investigation I have found that it is due to LAPIC timer used for HZ > >> stopped during C3 state (same as during AMD's C1E). > >> > >> So the question is: Is it possible (or planned) to make it work somehow? > >> For example, by using some external timer instead of LAPIC's one? > >> > >> ACPI reports about 20% less idle power consumption with C3 state > >> comparing to C2. It would be interesting to get additional half an hour > >> on battery. > >> > > You can get half way there by adding > > > > dev.cpu.1.cx_lowest=C3 > > > > to /etc/sysctl.conf > > Thanks. > > 1. Looks like it does not kill the timer. > 2. I haven't got any benefit from it in idle state. According to > `acpiconf -i 0` I have about 13 Amps (IMHO more looks like Watts) with > both C2 and this half-to-C3, but only 11 Amps in full C3 (but without > timer). > 3. I have got about 10% benefit (33 Amps against 36) when cpu0 is 100% > busy while cpu1 is idle. > You would not happen to have USB loaded or built into kernel? If you do, you will practically never go into C3. What does sysctl dev.cpu | grep cx_usage say? -- Alexandre "Sunny" Kovalenko (????????? ?????????) From mav at FreeBSD.org Sun Nov 2 14:43:41 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Sun Nov 2 14:44:08 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <1225664813.1202.5.camel@RabbitsDen> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> <490E245C.7070900@FreeBSD.org> <1225664813.1202.5.camel@RabbitsDen> Message-ID: <490E2D19.1030502@FreeBSD.org> Alexandre "Sunny" Kovalenko wrote: > You would not happen to have USB loaded or built into kernel? If you do, At home I have external USB keyboard and mouse, so yes, it is built in. It would be difficult to unload and reload it each time I connect something. I have read in ICH8M datasheet about special feature of reducing USB busmaster activity on idle periods to support C3 state. Do you know something about it? > you will practically never go into C3. What does > > sysctl dev.cpu | grep cx_usage > > say? %sysctl -a | grep cx_ hw.acpi.cpu.cx_lowest: C2 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% 0.43% 99.56% -- Alexander Motin From gaijin.k at gmail.com Sun Nov 2 16:05:19 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sun Nov 2 16:05:25 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <490E2D19.1030502@FreeBSD.org> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> <490E245C.7070900@FreeBSD.org> <1225664813.1202.5.camel@RabbitsDen> <490E2D19.1030502@FreeBSD.org> Message-ID: <1225670686.1153.8.camel@RabbitsDen> On Mon, 2008-11-03 at 00:43 +0200, Alexander Motin wrote: > Alexandre "Sunny" Kovalenko wrote: > > You would not happen to have USB loaded or built into kernel? If you do, > > At home I have external USB keyboard and mouse, so yes, it is built in. > It would be difficult to unload and reload it each time I connect something. I am not sure, I follow. When my laptop is on my desk (and plugged into the power supply), I am loading usb modules for all the necessary devices, including, but not limited to my mouse and keyboard. At this point, I do not get much of C3: dev.cpu.0.cx_usage: 0.00% 100.00% 0.00% dev.cpu.1.cx_usage: 0.00% 99.76% 0.23% When laptop is moving around with me, all USB modules are unloaded and I get about 4 hours of battery life with wireless on, admittedly on the light usage (reading/writing E-mails, browsing web, typing up occasional document). I consider this good for 4.4lbs (<2kg) laptop. My Kill-A-Watt device shows miniscule (~4%) even if stable difference between C3 and no-C3 when plugged into the outlet. > > I have read in ICH8M datasheet about special feature of reducing USB > busmaster activity on idle periods to support C3 state. Do you know > something about it? Unfortunately, I do not. > > > you will practically never go into C3. What does > > > > sysctl dev.cpu | grep cx_usage > > > > say? > > %sysctl -a | grep cx_ > hw.acpi.cpu.cx_lowest: C2 > 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% 0.43% 99.56% > OK, so we have C3. Is this the machine you see no difference in power consumption between C3 and no C3? How did you measure it? -- Alexandre "Sunny" Kovalenko (????????? ?????????) From pyunyh at gmail.com Sun Nov 2 20:11:04 2008 From: pyunyh at gmail.com (Pyun YongHyeon) Date: Sun Nov 2 20:11:18 2008 Subject: can not wake on lan after halt -p (or shutdown -p now) on releng_7 and releng_7_0 In-Reply-To: <20081014064456.GE14769@cdnetworks.co.kr> References: <596673353.20081006181334@pulsar.bg> <20081010012058.GA99376@cdnetworks.co.kr> <1948191744.20081010114326@pulsar.bg> <20081014064456.GE14769@cdnetworks.co.kr> Message-ID: <20081103040859.GD94302@cdnetworks.co.kr> On Tue, Oct 14, 2008 at 03:44:56PM +0900, To Georgi Iovchev wrote: > On Fri, Oct 10, 2008 at 11:43:26AM +0300, Georgi Iovchev wrote: > > > > > > -- > > Friday, October 10, 2008, 4:20:58 AM: > > > > > On Mon, Oct 06, 2008 at 06:13:34PM +0300, Georgi Iovchev wrote: > > >> Hello list > > >> > > >> I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R > > >> motherboard. Integrated network card is Realtek 8111B. > > >> I can not wake the computer after I shutdown it from FreeBSD. > > >> It is a dualboot system - windows xp and freebsd. If I shutdown the > > >> computer from windows - later I can wake it up with magic packet. Even > > >> if i shutdown the machine on the boot menu with the power button - than > > >> later I can wake on lan. The only situation where I CANNOT wake it is > > >> when I shutdown the machine from freebsd (halt -p). > > >> > > >> First I tested with 7.0-RELEASE-p5 amd64 (RELENG_7_0) and than I > > >> upgraded to 7.1 PRERELASE amd64 (RELENG_7). I also tested with two > > >> network cards - the integrated one Realtek 8111B and another one Intel > > >> PRO1000PT PCI-E with WOL enabled. > > >> > > > > > Don't know WOL issue of em(4) but re(4) should respond to WOL. > > > 7.0-RELEASE had no support for WOL so RELENG_7 or 7.1-PRERELEASE > > > should be used to experiment WOL. > > Now I am using 7.1-prerelase > > > > >> With both nics and both freebsd versions the situation is the same - > > >> after shutdown from bsd the computer is not able to wake on lan. The > > > > > Because you can wake up your sytem from Windows shutdown I think > > > your BIOS is already configured to allow wakeup from WOL. Would > > > you compare ethernet address of re(4) to Winwods? Have you tried to > > > send Magic packets to FreeBSD box? > > I have tried sending magic packets from another bsd machine. I am > > using net/wol. I also tried to send magic packets from windows machine > > using 3 different programs. > > > > > You may also try suspend your box with acpiconf and resume from WOL. > > I cant. > > > > [root@backup ~]# acpiconf -s 5 > > acpiconf: invalid sleep type (5) > > > > Actually I cant enter in any sleep state > > [root@backup ~]# acpiconf -s 4 > > acpiconf: request sleep type (4) failed: Operation not supported > > [root@backup ~]# acpiconf -s 3 > > acpiconf: request sleep type (3) failed: Operation not supported > > [root@backup ~]# acpiconf -s 2 > > acpiconf: request sleep type (2) failed: Operation not supported > > [root@backup ~]# acpiconf -s 1 > > acpiconf: request sleep type (1) failed: Operation not supported > > > > I am using generic kernel with little modifications, (generally i have > > commented many unused drivers - raid, if_....) Acpi is in generic > > kernel now. > > > > I even tried to wake the machine with magic packet after shutdown -h. > > But still no luck. > > > > > > >> indication on the switch port says that after shut down there is > > >> active link. > > >> > > > > > That indicates the controller is alive so it shall respond to WOL > > > if it was correctly configured to receive WOL packets. Have you > > > tried to send Magic packets to FreeBSD box? > > > > >> Here is some information after last update: > > >> > > >> [root@backup ~]# uname -a > > >> FreeBSD backup.pulsar.bg 7.1-PRERELEASE FreeBSD > > >> 7.1-PRERELEASE #1: Mon Oct 6 17:01:26 EEST 2008 > > >> root@backup.pulsar.bg:/usr/obj/usr/src/sys/MYCONF amd64 > > >> > > >> [root@backup ~]# pciconf -lv > > >> ... > > >> re0@pci0:3:0:0: class=0x020000 card=0xe0001458 > > >> chip=0x816810ec rev=0x01 hdr=0x00 > > >> vendor = 'Realtek Semiconductor' > > >> device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > >> class = network > > >> subclass = ethernet > > >> ... > > > > > Show me dmesg output pertinent to re(4). > > > > re0: port 0xd000-0xd0ff mem 0xf2000000-0xf2000fff irq 17 at device 0.0 on pci3 > > re0: turning off MSI enable bit. > > re0: Chip rev. 0x38000000 > > re0: MAC rev. 0x00000000 > > miibus0: on re0 > > rgephy0: PHY 1 on miibus0 > > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > re0: Ethernet address: 00:1f:d0:24:19:e9 > > re0: [FILTER] > > > > It looks like your chip is RTL8168B and I don't see any errors in > WOL related code of re(4). :-( > Can you check the resolved link speed/duplex of FreeBSD box after > shutdown?(You can enter to your switch menu and see the port > status.) > How about sending WOL packets over direct-connected UTP cable > without using switch? > Here is WOL patch which may fix the issye. Would you try the following patch and let me know whether WOL works or not? http://people.freebsd.org/~yongari/re/re.phy.patch.20081103 -- Regards, Pyun YongHyeon From mav at FreeBSD.org Mon Nov 3 01:16:07 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Nov 3 01:26:19 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <1225670686.1153.8.camel@RabbitsDen> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> <490E245C.7070900@FreeBSD.org> <1225664813.1202.5.camel@RabbitsDen> <490E2D19.1030502@FreeBSD.org> <1225670686.1153.8.camel@RabbitsDen> Message-ID: <490EC154.9020801@FreeBSD.org> Alexandre "Sunny" Kovalenko wrote: > When laptop is moving around with me, all USB modules are unloaded and I I will try to unload USB later today. > get about 4 hours of battery life with wireless on, admittedly on the > light usage (reading/writing E-mails, browsing web, typing up occasional > document). I consider this good for 4.4lbs (<2kg) laptop. I have a bit more then 3 hours at the same weight. Which CPU, video and chipset do you have? > OK, so we have C3. Is this the machine you see no difference in power > consumption between C3 and no C3? How did you measure it? Yes. I am using `acpiconf -i 0`. I have no way to measure AC power and I am not sure in precision of such measurements due to limited AC power supply effectiveness. I have some doubts that C3 on only one of two cores could give much benefit. I have already lowered frequency and voltage via EST by powerd. I have turned off most of CPU clocks with Core2Duo C2E state. So, according to what I have read, now only APICs and bus controller are active. As soon as I see timer interrupt on cpu1 it's APIC is not sleeping. Bus controller is shared by cores, so it can't be disabled until at least one core is active. -- Alexander Motin From geo at pulsar.bg Mon Nov 3 02:43:06 2008 From: geo at pulsar.bg (Georgi Iovchev) Date: Mon Nov 3 02:48:27 2008 Subject: can not wake on lan after halt -p (or shutdown -p now) on releng_7 and releng_7_0 In-Reply-To: <20081103040859.GD94302@cdnetworks.co.kr> References: <596673353.20081006181334@pulsar.bg> <20081010012058.GA99376@cdnetworks.co.kr> <1948191744.20081010114326@pulsar.bg> <20081014064456.GE14769@cdnetworks.co.kr> <20081103040859.GD94302@cdnetworks.co.kr> Message-ID: <490ED5E7.40606@pulsar.bg> Pyun YongHyeon wrote: > On Tue, Oct 14, 2008 at 03:44:56PM +0900, To Georgi Iovchev wrote: > > On Fri, Oct 10, 2008 at 11:43:26AM +0300, Georgi Iovchev wrote: > > > > > > > > > -- > > > Friday, October 10, 2008, 4:20:58 AM: > > > > > > > On Mon, Oct 06, 2008 at 06:13:34PM +0300, Georgi Iovchev wrote: > > > >> Hello list > > > >> > > > >> I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R > > > >> motherboard. Integrated network card is Realtek 8111B. > > > >> I can not wake the computer after I shutdown it from FreeBSD. > > > >> It is a dualboot system - windows xp and freebsd. If I shutdown the > > > >> computer from windows - later I can wake it up with magic packet. Even > > > >> if i shutdown the machine on the boot menu with the power button - than > > > >> later I can wake on lan. The only situation where I CANNOT wake it is > > > >> when I shutdown the machine from freebsd (halt -p). > > > >> > > > >> First I tested with 7.0-RELEASE-p5 amd64 (RELENG_7_0) and than I > > > >> upgraded to 7.1 PRERELASE amd64 (RELENG_7). I also tested with two > > > >> network cards - the integrated one Realtek 8111B and another one Intel > > > >> PRO1000PT PCI-E with WOL enabled. > > > >> > > > > > > > Don't know WOL issue of em(4) but re(4) should respond to WOL. > > > > 7.0-RELEASE had no support for WOL so RELENG_7 or 7.1-PRERELEASE > > > > should be used to experiment WOL. > > > Now I am using 7.1-prerelase > > > > > > >> With both nics and both freebsd versions the situation is the same - > > > >> after shutdown from bsd the computer is not able to wake on lan. The > > > > > > > Because you can wake up your sytem from Windows shutdown I think > > > > your BIOS is already configured to allow wakeup from WOL. Would > > > > you compare ethernet address of re(4) to Winwods? Have you tried to > > > > send Magic packets to FreeBSD box? > > > I have tried sending magic packets from another bsd machine. I am > > > using net/wol. I also tried to send magic packets from windows machine > > > using 3 different programs. > > > > > > > You may also try suspend your box with acpiconf and resume from WOL. > > > I cant. > > > > > > [root@backup ~]# acpiconf -s 5 > > > acpiconf: invalid sleep type (5) > > > > > > Actually I cant enter in any sleep state > > > [root@backup ~]# acpiconf -s 4 > > > acpiconf: request sleep type (4) failed: Operation not supported > > > [root@backup ~]# acpiconf -s 3 > > > acpiconf: request sleep type (3) failed: Operation not supported > > > [root@backup ~]# acpiconf -s 2 > > > acpiconf: request sleep type (2) failed: Operation not supported > > > [root@backup ~]# acpiconf -s 1 > > > acpiconf: request sleep type (1) failed: Operation not supported > > > > > > I am using generic kernel with little modifications, (generally i have > > > commented many unused drivers - raid, if_....) Acpi is in generic > > > kernel now. > > > > > > I even tried to wake the machine with magic packet after shutdown -h. > > > But still no luck. > > > > > > > > > >> indication on the switch port says that after shut down there is > > > >> active link. > > > >> > > > > > > > That indicates the controller is alive so it shall respond to WOL > > > > if it was correctly configured to receive WOL packets. Have you > > > > tried to send Magic packets to FreeBSD box? > > > > > > >> Here is some information after last update: > > > >> > > > >> [root@backup ~]# uname -a > > > >> FreeBSD backup.pulsar.bg 7.1-PRERELEASE FreeBSD > > > >> 7.1-PRERELEASE #1: Mon Oct 6 17:01:26 EEST 2008 > > > >> root@backup.pulsar.bg:/usr/obj/usr/src/sys/MYCONF amd64 > > > >> > > > >> [root@backup ~]# pciconf -lv > > > >> ... > > > >> re0@pci0:3:0:0: class=0x020000 card=0xe0001458 > > > >> chip=0x816810ec rev=0x01 hdr=0x00 > > > >> vendor = 'Realtek Semiconductor' > > > >> device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > > >> class = network > > > >> subclass = ethernet > > > >> ... > > > > > > > Show me dmesg output pertinent to re(4). > > > > > > re0: port 0xd000-0xd0ff mem 0xf2000000-0xf2000fff irq 17 at device 0.0 on pci3 > > > re0: turning off MSI enable bit. > > > re0: Chip rev. 0x38000000 > > > re0: MAC rev. 0x00000000 > > > miibus0: on re0 > > > rgephy0: PHY 1 on miibus0 > > > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > > > re0: Ethernet address: 00:1f:d0:24:19:e9 > > > re0: [FILTER] > > > > > > > It looks like your chip is RTL8168B and I don't see any errors in > > WOL related code of re(4). :-( > > Can you check the resolved link speed/duplex of FreeBSD box after > > shutdown?(You can enter to your switch menu and see the port > > status.) > > How about sending WOL packets over direct-connected UTP cable > > without using switch? > > Hello again :) I have resumed my experimets with wol again. I checked the link speed from the switch web gui. It says "100M Full". > Here is WOL patch which may fix the issye. Would you try the > following patch and let me know whether WOL works or not? > http://people.freebsd.org/~yongari/re/re.phy.patch.20081103 > I tried your patch. Just to be sure that I did it correct - here are my steps: cd / patch < /path/re.phy.patch.20081103 cd /sys/modules/re make all install reboot After reboot I shutdown the machine and try to wake it from another computer. Still WOL does not work. From bugmaster at FreeBSD.org Mon Nov 3 03:06:48 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 3 03:07:03 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200811031106.mA3B6l7F010800@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 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 41 problems total. From linimon at FreeBSD.org Mon Nov 3 03:36:35 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Nov 3 03:36:46 2008 Subject: kern/128553: [patch] [acpi] add support for Asus A8Sr notebook Message-ID: <200811031136.mA3BaZrl038100@freefall.freebsd.org> Synopsis: [patch] [acpi] add support for Asus A8Sr notebook Responsible-Changed-From-To: freebsd-bugs->freebsd-acpi Responsible-Changed-By: linimon Responsible-Changed-When: Mon Nov 3 11:36:21 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=128553 From gaijin.k at gmail.com Mon Nov 3 04:23:34 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Mon Nov 3 04:23:46 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <490EC154.9020801@FreeBSD.org> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> <490E245C.7070900@FreeBSD.org> <1225664813.1202.5.camel@RabbitsDen> <490E2D19.1030502@FreeBSD.org> <1225670686.1153.8.camel@RabbitsDen> <490EC154.9020801@FreeBSD.org> Message-ID: <1225714981.1184.7.camel@RabbitsDen> On Mon, 2008-11-03 at 11:16 +0200, Alexander Motin wrote: > Alexandre "Sunny" Kovalenko wrote: > > When laptop is moving around with me, all USB modules are unloaded and I > > I will try to unload USB later today. > > > get about 4 hours of battery life with wireless on, admittedly on the > > light usage (reading/writing E-mails, browsing web, typing up occasional > > document). I consider this good for 4.4lbs (<2kg) laptop. > > I have a bit more then 3 hours at the same weight. Which CPU, video and > chipset do you have? This is CoreDuo T2400 with Intel 945GM video and Atheros 5212 a/b/g wireless part. One other thing, I forgot to mention is: I set hw.pci.do_power_nodriver: 3 I have to be honest: I really do not know how much savings do I get from which settings -- I merely went for most aggressive ones. YMMV. > I have some doubts that C3 on only one of two cores could give much > benefit. You are most likely right -- crude measurement by Kill-A-Watt shows 4% difference which might as well be measurement error. -- Alexandre "Sunny" Kovalenko (????????? ?????????) From peterjeremy at optushome.com.au Mon Nov 3 10:04:38 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Mon Nov 3 10:04:44 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <490E245C.7070900@FreeBSD.org> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> <490E245C.7070900@FreeBSD.org> Message-ID: <20081103074730.GJ99398@server.vk2pj.dyndns.org> On 2008-Nov-03 00:06:20 +0200, Alexander Motin wrote: >2. I haven't got any benefit from it in idle state. According to >`acpiconf -i 0` I have about 13 Amps (IMHO more looks like Watts) with I assumed it was reporting deci-Amps instead of Amps (ie reading an order of magnitude high) but I guess power is an option. -- 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: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081103/4a41253a/attachment.pgp From mav at FreeBSD.org Mon Nov 3 12:56:56 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Nov 3 12:57:08 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <1225714981.1184.7.camel@RabbitsDen> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> <490E245C.7070900@FreeBSD.org> <1225664813.1202.5.camel@RabbitsDen> <490E2D19.1030502@FreeBSD.org> <1225670686.1153.8.camel@RabbitsDen> <490EC154.9020801@FreeBSD.org> <1225714981.1184.7.camel@RabbitsDen> Message-ID: <490F6594.6050802@FreeBSD.org> Alexandre "Sunny" Kovalenko wrote: >>> When laptop is moving around with me, all USB modules are unloaded and I >> I will try to unload USB later today. I have got a bit power on disabling EHCI, but it could happen just because device itself went into the D3 state. C3 stats doesn't changes on that. UHCI and other devices disabling also gave some bits. >>> get about 4 hours of battery life with wireless on, admittedly on the >>> light usage (reading/writing E-mails, browsing web, typing up occasional >>> document). I consider this good for 4.4lbs (<2kg) laptop. >> I have a bit more then 3 hours at the same weight. Which CPU, video and >> chipset do you have? > This is CoreDuo T2400 with Intel 945GM video and Atheros 5212 a/b/g > wireless part. One other thing, I forgot to mention is: I set > > hw.pci.do_power_nodriver: 3 Thanks. With disabling everything possible I was able to reach 4 hours plank! There is one question appeared, is there any way to deny driver attachment for some specific device to left it is D3 state? For example I don't need some specific USB hosts and PATA controller, but I can't disable them with just not loading the driver. There is alike DF_ENABLED flag I have found, but I haven't found any external way to reset it. :( -- Alexander Motin From gaijin.k at gmail.com Mon Nov 3 16:32:02 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Mon Nov 3 16:32:13 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <490F6594.6050802@FreeBSD.org> References: <490DF584.5080506@FreeBSD.org> <1225656933.1202.2.camel@RabbitsDen> <490E245C.7070900@FreeBSD.org> <1225664813.1202.5.camel@RabbitsDen> <490E2D19.1030502@FreeBSD.org> <1225670686.1153.8.camel@RabbitsDen> <490EC154.9020801@FreeBSD.org> <1225714981.1184.7.camel@RabbitsDen> <490F6594.6050802@FreeBSD.org> Message-ID: <1225758689.1244.1.camel@RabbitsDen> On Mon, 2008-11-03 at 22:56 +0200, Alexander Motin wrote: > Alexandre "Sunny" Kovalenko wrote: > >>> When laptop is moving around with me, all USB modules are unloaded and I > >> I will try to unload USB later today. > > I have got a bit power on disabling EHCI, but it could happen just > because device itself went into the D3 state. C3 stats doesn't changes > on that. UHCI and other devices disabling also gave some bits. > > >>> get about 4 hours of battery life with wireless on, admittedly on the > >>> light usage (reading/writing E-mails, browsing web, typing up occasional > >>> document). I consider this good for 4.4lbs (<2kg) laptop. > >> I have a bit more then 3 hours at the same weight. Which CPU, video and > >> chipset do you have? > > This is CoreDuo T2400 with Intel 945GM video and Atheros 5212 a/b/g > > wireless part. One other thing, I forgot to mention is: I set > > > > hw.pci.do_power_nodriver: 3 > > Thanks. With disabling everything possible I was able to reach 4 hours > plank! > > There is one question appeared, is there any way to deny driver > attachment for some specific device to left it is D3 state? For example > I don't need some specific USB hosts and PATA controller, but I can't > disable them with just not loading the driver. There is alike DF_ENABLED > flag I have found, but I haven't found any external way to reset it. :( Well, this is way beyond my knowledge. Hopefully, someone who actually knows how things work will chime in. Sorry. -- Alexandre "Sunny" Kovalenko (????????? ?????????) From rpaulo at FreeBSD.org Tue Nov 4 03:37:37 2008 From: rpaulo at FreeBSD.org (rpaulo@FreeBSD.org) Date: Tue Nov 4 03:37:44 2008 Subject: kern/128553: [patch] [acpi] add support for Asus A8Sr notebook Message-ID: <200811041137.mA4BbbxT050398@freefall.freebsd.org> Synopsis: [patch] [acpi] add support for Asus A8Sr notebook Responsible-Changed-From-To: freebsd-acpi->rpaulo Responsible-Changed-By: rpaulo Responsible-Changed-When: Tue Nov 4 11:37:14 UTC 2008 Responsible-Changed-Why: I'll take care of it. http://www.freebsd.org/cgi/query-pr.cgi?pr=128553 From marcin.nowak at simplusnet.pl Tue Nov 4 15:46:00 2008 From: marcin.nowak at simplusnet.pl (Marcin Nowak) Date: Tue Nov 4 15:46:32 2008 Subject: acpi for asus a6f Message-ID: Hi Some time ago I have reported request for acpi support my asus a6f laptop, and I got the patch from someone on this mailing-list. Patch (*.diff file) works fine so, why isn't in official cvs repo yet? :) Greetings. From rpaulo at freebsd.org Wed Nov 5 06:21:35 2008 From: rpaulo at freebsd.org (Rui Paulo) Date: Wed Nov 5 06:22:09 2008 Subject: acpi for asus a6f In-Reply-To: References: Message-ID: <3C2CC7F6-2B29-4773-BE50-8AE6EDE8A1FA@freebsd.org> On 4 Nov 2008, at 23:05, Marcin Nowak wrote: > Hi > > Some time ago I have reported request for acpi support my asus a6f > laptop, and I got the patch from someone on this mailing-list. Patch > (*.diff file) works fine so, why isn't in official cvs repo yet? :) Please send a PR and Cc me. I'll see what I can do. Thanks, -- Rui Paulo From funa at funa.org Thu Nov 6 02:39:05 2008 From: funa at funa.org (Akira Funahashi) Date: Thu Nov 6 02:39:36 2008 Subject: acpi for asus a6f In-Reply-To: <3C2CC7F6-2B29-4773-BE50-8AE6EDE8A1FA@freebsd.org> References: <3C2CC7F6-2B29-4773-BE50-8AE6EDE8A1FA@freebsd.org> Message-ID: <17e737660811060218s5eab5bb4m45845178829ebcf6@mail.gmail.com> Hi, On Wed, Nov 5, 2008 at 10:51 PM, Rui Paulo wrote: >> Some time ago I have reported request for acpi support my asus a6f >> laptop, and I got the patch from someone on this mailing-list. Patch >> (*.diff file) works fine so, why isn't in official cvs repo yet? :) > > Please send a PR and Cc me. I'll see what I can do. I guess the patch Marcin is talking is the one I wrote before. I've sent PR right now. Thanks, -- Akira Funahashi From linimon at FreeBSD.org Thu Nov 6 03:26:51 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Nov 6 03:26:58 2008 Subject: kern/128634: [patch] fix acpi_asus(4) in asus a6f laptop Message-ID: <200811061126.mA6BQpIM072358@freefall.freebsd.org> Old Synopsis: patch for acpi asus a6f laptop isn't in official repo New Synopsis: [patch] fix acpi_asus(4) in asus a6f laptop Responsible-Changed-From-To: freebsd-bugs->freebsd-acpi Responsible-Changed-By: linimon Responsible-Changed-When: Thu Nov 6 11:25:29 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=128634 From gavin at FreeBSD.org Thu Nov 6 04:27:40 2008 From: gavin at FreeBSD.org (gavin@FreeBSD.org) Date: Thu Nov 6 04:27:46 2008 Subject: kern/128639: [PATCH] [acpi_asus] acpi for ASUS A6F, A3E, A3F, A3N not working Message-ID: <200811061227.mA6CRdOg017321@freefall.freebsd.org> Old Synopsis: [PATCH] acpi for ASUS A6F,A3E,A3F,A3N not working New Synopsis: [PATCH] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not working Responsible-Changed-From-To: freebsd-i386->freebsd-acpi Responsible-Changed-By: gavin Responsible-Changed-When: Thu Nov 6 12:26:08 UTC 2008 Responsible-Changed-Why: Over to maintainer(s) http://www.freebsd.org/cgi/query-pr.cgi?pr=128639 From aturetta at commit.it Thu Nov 6 07:12:13 2008 From: aturetta at commit.it (Angelo Turetta) Date: Thu Nov 6 07:12:20 2008 Subject: Dell PowerEdge 1300/500 - bitten by ACPI quirks Message-ID: <4911BB02.20102@commit.it> I installed RELENG_7 (SNAPSHOT-200805) on an old DELL PowerEdge 1300/500, and everything went well. After I built and installed a recent RELENG_7, suddenly the machine will panic with "ACPI disabled by blacklist." I found a recent commit to fix a bug that was actually disabling the blacklist check on RELENG_7 before Sep.22, and that accounts for the difference I got between the May snapshot and the current RELENG_7. The acpi_quirks file lists my hardware as: # Dell PE1300 name: Dell_PE1300 oem: FADT "Dell " "PE1300 " oem_rev: FADT <= 1 quirks: ACPI_Q_BROKEN # Dell Personal Workstation 1300 name: Dell_PE1300_2 oem: FADT "DELL " "PE1300 " oem_rev: FADT <= 1 quirks: ACPI_Q_BROKEN In particular, my system matches the second case (uppercase DELL), but the comment describes it as a totally different machine which cannot be found on Google Given that I previously used the machine with ACPI enabled without any apparent problems, is there any reference as to why it was put on the black-list? And how can I make my system ignore that quirk? Thanks, Angelo. PS: here is an excerpt form dmesg with ACPI ===================================== FreeBSD 7.0-STABLE-200805 #0: Sun May 11 15:02:57 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (498.47-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 536862720 (511 MB) avail memory = 511438848 (487 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 without ACPI ==================================== FreeBSD 7.1-PRERELEASE #0: Thu Oct 30 18:43:13 CET 2008 aturetta@proxy:/usr/obj/usr/src/sys/PROXY Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (498.47-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 536862720 (511 MB) avail memory = 511397888 (487 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 From mav at FreeBSD.org Fri Nov 7 01:05:06 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Fri Nov 7 01:17:08 2008 Subject: RFC: powerd algorithms enhancements Message-ID: <491404BF.1090807@FreeBSD.org> The discussion of this is going on mobile@: -------- Original Message -------- Subject: RFC: powerd algorithms enhancements Date: Wed, 05 Nov 2008 22:57:55 +0200 From: Alexander Motin To: freebsd-mobile@FreeBSD.org Hi. I would like to propose the patch for powerd that fixes some issues, makes it more universal and on my opinion more usable. The main ideas of mine were: 1. To make it more SMP polite. Previous version uses average CPU load that leads to the often load underestimation. It make powerd with default configuration unusable on systems with more then 2 CPUs. I propose to use summary load instead of average one. IMO this is the best we can do without specially tuned scheduler. Also as soon as measuring total load on SMP systems is more useful then total idle, I have switched to it. 2. To make powerd's operation independent from number and size of frequency levels I have added internal frequency counter which translated into real frequencies only on a last stage and only as good as gone. Some systems may have only several power levels, while mine has 17 of them, so adaptation time in completely different. It would be good if algorithm was not depending on it. 3. As part of previous I have changed adaptive mode to rise frequency on demand up to 2 times and fall on 1/8 per time internal. 4. For desktop (AC-powered) systems I have added one more mode - "hiadaptive". It rises frequency twice faster, drops it 4 times slower, prefers twice lower CPU load and has additional delay before leaving the highest frequency after the period of maximum load. This mode was specially made to improve interactivity of the systems where operation capabilities are more significant then power consumption, but keeping maximum frequency all the time is not needed. 5. I have reduced polling interval from 1/2 to 1/4 of second. It is not important for algorithm math now, but gives better system interactivity. -- Alexander Motin From rpaulo at FreeBSD.org Fri Nov 7 05:54:59 2008 From: rpaulo at FreeBSD.org (rpaulo@FreeBSD.org) Date: Fri Nov 7 05:55:05 2008 Subject: kern/128634: [patch] fix acpi_asus(4) in asus a6f laptop Message-ID: <200811071354.mA7DsvnJ087504@freefall.freebsd.org> Synopsis: [patch] fix acpi_asus(4) in asus a6f laptop State-Changed-From-To: open->feedback State-Changed-By: rpaulo State-Changed-When: Fri Nov 7 13:53:14 UTC 2008 State-Changed-Why: This patch includes Eee PC support, which has been committed already. Can you send a patch that applies cleanly to HEAD? Thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=128634 From bugmaster at FreeBSD.org Mon Nov 10 03:06:46 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 10 03:07:12 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200811101106.mAAB6j0M049615@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 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 43 problems total. From nate at root.org Mon Nov 10 08:28:02 2008 From: nate at root.org (Nate Lawson) Date: Mon Nov 10 08:28:08 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <491404BF.1090807@FreeBSD.org> References: <491404BF.1090807@FreeBSD.org> Message-ID: <49186111.9020103@root.org> Alexander Motin wrote: > The discussion of this is going on mobile@: > > -------- Original Message -------- > Subject: RFC: powerd algorithms enhancements > Date: Wed, 05 Nov 2008 22:57:55 +0200 > From: Alexander Motin > To: freebsd-mobile@FreeBSD.org > > Hi. > > I would like to propose the patch for powerd that fixes some issues, > makes it more universal and on my opinion more usable. The main ideas of > mine were: I have not yet reviewed the patch but have some comments. > 1. To make it more SMP polite. Previous version uses average CPU load > that leads to the often load underestimation. It make powerd with > default configuration unusable on systems with more then 2 CPUs. I > propose to use summary load instead of average one. IMO this is the best > we can do without specially tuned scheduler. Also as soon as measuring > total load on SMP systems is more useful then total idle, I have > switched to it. Ok. > 2. To make powerd's operation independent from number and size of > frequency levels I have added internal frequency counter which > translated into real frequencies only on a last stage and only as good > as gone. Some systems may have only several power levels, while mine has > 17 of them, so adaptation time in completely different. It would be good > if algorithm was not depending on it. I don't understand the advantage of this. > 3. As part of previous I have changed adaptive mode to rise frequency on > demand up to 2 times and fall on 1/8 per time internal. > > 4. For desktop (AC-powered) systems I have added one more mode - > "hiadaptive". It rises frequency twice faster, drops it 4 times slower, > prefers twice lower CPU load and has additional delay before leaving the > highest frequency after the period of maximum load. This mode was > specially made to improve interactivity of the systems where operation > capabilities are more significant then power consumption, but keeping > maximum frequency all the time is not needed. > > 5. I have reduced polling interval from 1/2 to 1/4 of second. It is not > important for algorithm math now, but gives better system interactivity. There's a patch Cyrille Szymanski has sent me to review that implements the FLAT and PAST algorithms in powerd. I think we should not add new modes that are heuristics (including this one) until we have a chance to compare it to algorithms that have been the result of real research. I'll try to get Cyrille to send out an amended patch for public review. -- Nate From mav at FreeBSD.org Mon Nov 10 12:36:46 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Nov 10 12:36:52 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <49186111.9020103@root.org> References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> Message-ID: <49189B47.7090509@FreeBSD.org> Nate Lawson wrote: > Alexander Motin wrote: >> 2. To make powerd's operation independent from number and size of >> frequency levels I have added internal frequency counter which >> translated into real frequencies only on a last stage and only as good >> as gone. Some systems may have only several power levels, while mine has >> 17 of them, so adaptation time in completely different. It would be good >> if algorithm was not depending on it. > > I don't understand the advantage of this. Universality and predictiveness. Systems with 2 and with 32 levels will drop/rise frequency with same absolute rate. If we are trying to speak about some comparing, algorithm should be hardware independent. > There's a patch Cyrille Szymanski has sent me to review that implements > the FLAT and PAST algorithms in powerd. I think we should not add new > modes that are heuristics (including this one) until we have a chance to > compare it to algorithms that have been the result of real research. So show it to us. This area is heuristic by default as there is several opposite criteriums, so any algorithm will be heuristic. -- Alexander Motin From matheusber at gmail.com Mon Nov 10 16:19:23 2008 From: matheusber at gmail.com (Nenhum_de_Nos) Date: Mon Nov 10 16:19:29 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <49186111.9020103@root.org> References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> Message-ID: as all you are talking about the subject, and I read all messages, is there any module to load and make my AthlonXP 1700+ use less power ? running 7-STABLE, just a file server. any acpi-stuff I could enable would be great, as I just use all its power when compiling ... thanks, matheus -- We will call you cygnus, The God of balance you shall be From spawk at acm.poly.edu Mon Nov 10 17:04:03 2008 From: spawk at acm.poly.edu (Boris Kochergin) Date: Mon Nov 10 17:04:10 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> Message-ID: <4918D3B3.1080305@acm.poly.edu> Nenhum_de_Nos wrote: > as all you are talking about the subject, and I read all messages, is > there any module to load and make my AthlonXP 1700+ use less power ? > > running 7-STABLE, just a file server. any acpi-stuff I could enable would > be great, as I just use all its power when compiling ... > > thanks, > > matheus > That CPU is not listed as having PowerNow! support. You may be able to set it to permanently run at a lower frequency in your system's BIOS. -Boris From smithi at nimnet.asn.au Mon Nov 10 21:50:02 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Mon Nov 10 21:50:09 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> Message-ID: <20081111161549.U70117@sola.nimnet.asn.au> On Mon, 10 Nov 2008, Nenhum_de_Nos wrote: > as all you are talking about the subject, and I read all messages, is > there any module to load and make my AthlonXP 1700+ use less power ? > > running 7-STABLE, just a file server. any acpi-stuff I could enable would > be great, as I just use all its power when compiling ... What does 'sysctl hw.acpi dev.cpu' have to say? cheers, Ian From matheus at eternamente.info Tue Nov 11 09:56:12 2008 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Tue Nov 11 09:56:19 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <20081111161549.U70117@sola.nimnet.asn.au> References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> <20081111161549.U70117@sola.nimnet.asn.au> Message-ID: <7d13c992592d1976010179b40b26c057.squirrel@cygnus.homeunix.com> On Tue, November 11, 2008 3:20 am, Ian Smith wrote: > On Mon, 10 Nov 2008, Nenhum_de_Nos wrote: > > as all you are talking about the subject, and I read all messages, is > > there any module to load and make my AthlonXP 1700+ use less power ? > > > > running 7-STABLE, just a file server. any acpi-stuff I could enable > would > > be great, as I just use all its power when compiling ... > > What does 'sysctl hw.acpi dev.cpu' have to say? [root@xxx ~]# sysctl hw.acpi hw.acpi.supported_sleep_state: S1 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: 43.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: 66.0C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 70.0C hw.acpi.thermal.tz0._ACx: 66.0C -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._TC1: 4 hw.acpi.thermal.tz0._TC2: 3 hw.acpi.thermal.tz0._TSP: 60 hw.acpi.cpu.cx_lowest: C1 [root@xxx ~]# sysctl dev.cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.cx_supported: C1/0 C2/90 C3/900 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% [root@xxx ~]# if it rings any bells :) I really forgot the option of lowering the freq the cpu works. but this (as said in this thread) must come together with cpu vcc lowering ... Am I wrong ? and as I remembered I have an imap server and squirrelmail in it (that was slow on a PII 333MHz), I think that changing cpu freq would be great (unfortunatelly impossible as said) well, anything to make it draw less power :) thanks to you all, matheus -- We will call you cygnus, The God of balance you shall be From matheusber at yahoo.com.br Tue Nov 11 09:57:09 2008 From: matheusber at yahoo.com.br (Nenhum_de_Nos) Date: Tue Nov 11 09:57:15 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <20081111161549.U70117@sola.nimnet.asn.au> References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> <20081111161549.U70117@sola.nimnet.asn.au> Message-ID: On Tue, November 11, 2008 3:20 am, Ian Smith wrote: > On Mon, 10 Nov 2008, Nenhum_de_Nos wrote: > > as all you are talking about the subject, and I read all messages, is > > there any module to load and make my AthlonXP 1700+ use less power ? > > > > running 7-STABLE, just a file server. any acpi-stuff I could enable > would > > be great, as I just use all its power when compiling ... > > What does 'sysctl hw.acpi dev.cpu' have to say? [root@xxx ~]# sysctl hw.acpi hw.acpi.supported_sleep_state: S1 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: 43.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: 66.0C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 70.0C hw.acpi.thermal.tz0._ACx: 66.0C -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._TC1: 4 hw.acpi.thermal.tz0._TC2: 3 hw.acpi.thermal.tz0._TSP: 60 hw.acpi.cpu.cx_lowest: C1 [root@xxx ~]# sysctl dev.cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.cx_supported: C1/0 C2/90 C3/900 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% [root@xxx ~]# if it rings any bells :) I really forgot the option of lowering the freq the cpu works. but this (as said in this thread) must come together with cpu vcc lowering ... Am I wrong ? and as I remembered I have an imap server and squirrelmail in it (that was slow on a PII 333MHz), I think that changing cpu freq would be great (unfortunatelly impossible as said) well, anything to make it draw less power :) thanks to you all, matheus -- We will call you cygnus, The God of balance you shall be From gaijin.k at gmail.com Tue Nov 11 16:30:42 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Tue Nov 11 16:30:49 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <7d13c992592d1976010179b40b26c057.squirrel@cygnus.homeunix.com> References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> <20081111161549.U70117@sola.nimnet.asn.au> <7d13c992592d1976010179b40b26c057.squirrel@cygnus.homeunix.com> Message-ID: <1226449830.1244.30.camel@RabbitsDen> On Tue, 2008-11-11 at 15:56 -0200, Nenhum_de_Nos wrote: > On Tue, November 11, 2008 3:20 am, Ian Smith wrote: > > On Mon, 10 Nov 2008, Nenhum_de_Nos wrote: > > > as all you are talking about the subject, and I read all messages, is > > > there any module to load and make my AthlonXP 1700+ use less power ? > > > > > > running 7-STABLE, just a file server. any acpi-stuff I could enable > > would > > > be great, as I just use all its power when compiling ... > > > > What does 'sysctl hw.acpi dev.cpu' have to say? > [...] > [root@xxx ~]# sysctl dev.cpu > dev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_PR_.CPU0 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.cx_supported: C1/0 C2/90 C3/900 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% > [root@xxx ~]# > > if it rings any bells :) All I can suggest here is sysctl dev.cpu.0.cx_lowest="C3" or, if it gets you totally unresponsive machine, sysctl dev.cpu.0.cx_lowest="C2" how much of the power saving you will see from this is the separate question. -- Alexandre "Sunny" Kovalenko (????????? ?????????) From smithi at nimnet.asn.au Tue Nov 11 19:42:22 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Tue Nov 11 19:42:29 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <1226449830.1244.30.camel@RabbitsDen> References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> <20081111161549.U70117@sola.nimnet.asn.au> <7d13c992592d1976010179b40b26c057.squirrel@cygnus.homeunix.com> <1226449830.1244.30.camel@RabbitsDen> Message-ID: <20081112142137.Q70117@sola.nimnet.asn.au> On Tue, 11 Nov 2008, Alexandre "Sunny" Kovalenko wrote: > On Tue, 2008-11-11 at 15:56 -0200, Nenhum_de_Nos wrote: > > On Tue, November 11, 2008 3:20 am, Ian Smith wrote: > > > On Mon, 10 Nov 2008, Nenhum_de_Nos wrote: > > > > as all you are talking about the subject, and I read all messages, is > > > > there any module to load and make my AthlonXP 1700+ use less power ? > > > > > > > > running 7-STABLE, just a file server. any acpi-stuff I could enable > > > would > > > > be great, as I just use all its power when compiling ... > > > > > > What does 'sysctl hw.acpi dev.cpu' have to say? > > > [...] Reinjecting a bit .. > hw.acpi.thermal.user_override: 0 > hw.acpi.thermal.tz0.temperature: 43.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: 66.0C > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 70.0C > hw.acpi.thermal.tz0._ACx: 66.0C -1 -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.thermal.tz0._TC1: 4 > hw.acpi.thermal.tz0._TC2: 3 > hw.acpi.thermal.tz0._TSP: 60 > hw.acpi.cpu.cx_lowest: C1 Certainly no cpu frequency control. Surprisingly low _CRT temperature but unless it ever actually gets too hot, it's not a problem. I don't really follow why .passive-cooling=1 with no cpufreq driver/s attached? > > [root@xxx ~]# sysctl dev.cpu > > dev.cpu.0.%desc: ACPI CPU > > dev.cpu.0.%driver: cpu > > dev.cpu.0.%location: handle=\_PR_.CPU0 > > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > > dev.cpu.0.%parent: acpi0 > > dev.cpu.0.cx_supported: C1/0 C2/90 C3/900 > > dev.cpu.0.cx_lowest: C1 > > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% > > [root@xxx ~]# > > > > if it rings any bells :) > All I can suggest here is > > sysctl dev.cpu.0.cx_lowest="C3" > > or, if it gets you totally unresponsive machine, > > sysctl dev.cpu.0.cx_lowest="C2" > > how much of the power saving you will see from this is the > separate question. If that works to any extent you'll notice some drop in cpu temperature. I do see a slight but noticeable idle temp. drop on my T23 in C2, though nothing compared to the power reduction of lower frequency (about half). cheers, Ian From cnszym at gmail.com Thu Nov 13 17:24:37 2008 From: cnszym at gmail.com (Cyrille Szymanski) Date: Thu Nov 13 17:24:43 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <49189B47.7090509@FreeBSD.org> References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> <49189B47.7090509@FreeBSD.org> Message-ID: 2008/11/11 Alexander Motin : > Universality and predictiveness. Systems with 2 and with 32 levels will > drop/rise frequency with same absolute rate. If we are trying to speak about > some comparing, algorithm should be hardware independent. Hi The heuristics PAST and FLAT are two examples of strategies which do just this : they determine the desired operating frequency (in Hz) and then switch to the closest level available. >> There's a patch Cyrille Szymanski has sent me to review that implements >> the FLAT and PAST algorithms in powerd. I think we should not add new >> modes that are heuristics (including this one) until we have a chance to >> compare it to algorithms that have been the result of real research. > > So show it to us. This area is heuristic by default as there is several > opposite criteriums, so any algorithm will be heuristic. Although I see the benefits of your proposal, and reckon that systems with may levels are more and more common these days. The point is, I think, to avoid adding tuning knobs to powerd that would be too specific to your configuration and which might benefit everyone. Research will (I hope) indicate the way to go. Thanks ! -- Cyrille Szymanski From mav at FreeBSD.org Fri Nov 14 01:14:22 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Fri Nov 14 04:19:35 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> <49189B47.7090509@FreeBSD.org> Message-ID: <491D416C.6030207@FreeBSD.org> Hi. Cyrille Szymanski wrote: >>> There's a patch Cyrille Szymanski has sent me to review that implements >>> the FLAT and PAST algorithms in powerd. I think we should not add new >>> modes that are heuristics (including this one) until we have a chance to >>> compare it to algorithms that have been the result of real research. >> So show it to us. This area is heuristic by default as there is several >> opposite criteriums, so any algorithm will be heuristic. > > Although I see the benefits of your proposal, and reckon that systems > with may levels are more and more common these days. The point is, I > think, to avoid adding tuning knobs to powerd that would be too > specific to your configuration and which might benefit everyone. There is natural trade-off between interactivity and power saving. So I don't think that "hiadaptive" mode is something too specific to my system. I haven't added any other tuning, even reduced amount of tuning that was required to make it work in some cases before. > Research will (I hope) indicate the way to go. So where I can get your patches or algorithms description? -- Alexander Motin From ivan at serezhkin.com Fri Nov 14 11:18:39 2008 From: ivan at serezhkin.com (Ivan B. Serezhkin) Date: Fri Nov 14 11:18:45 2008 Subject: generalized driver for acpi all devices. Message-ID: <491DCAF2.9080507@serezhkin.com> Hello. I now writing device driver for fujitsu siemens notebook hotkeys FUJ02E3, and think, that before understanding how this device works a must write driver, that provide all acpi methods to sysctl and all event to log. I'v done it, but can't understand how this device is working =) I think that it must be musch easy if i already has some ways to call acpi methods and intercept events from userspace by commandline. Now i write driver, that gains, device and methods to provide in sysctl, from kenv, but in some devices this tunablie is too long. Please, explain, how can i access real acpi code from kernel and how can i found devices and methods to provide it ? Also, redirect to good documentation is what i want =) Also, i think to use /dev/acpi as a commandline interface, now there only sysctl acces, i want add some command language to it something like call _SB_.PCI0.LPCB.FEXT.SIRB(1) 0x0 alias _SB_.PCI0.LPCB.FJEX FJEX ok call FJEX.GHKS() 0x0 is this good ? or we must use some other mechanism ? But now i have not enough experience for this =) but i'll try it =) -- Ivan B. Serezhkin Spamooborona, Yandex. http://so.yandex.ru/ From bugmaster at FreeBSD.org Mon Nov 17 03:06:45 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 17 03:07:14 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200811171106.mAHB6iHX082421@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 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 43 problems total. From dlev89 at gmail.com Mon Nov 17 08:01:35 2008 From: dlev89 at gmail.com (Daniel Levine) Date: Mon Nov 17 08:01:43 2008 Subject: Marvell 88E8038 PCI-E controller doesn't appear as device with acpi enabled Message-ID: On my Acer Aspire 3680-2633, the Marvell ethernet controller, which appears like so under Linux lspci: 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E Fast Ethernet Controller (rev 14) Does not show up at all with acpi enabled - no msk0 in ifconfig -a, no device in /dev, nothing. With acpi disabled, it appears and works fine. This is the case under both FreeBSD 6.4 and 7.0, as well as OpenBSD 4.4 and NetBSD 4.0.1. The acpidump output is available here: http://www.mediafire.com/?g4zin4s99b1 If MediaFire isn't cooperating, notify me and I'll upload again somewhere else. I've also attached the outputs of dmesg with acpi enabled and disabled, and the output of 'sysctl hw.acpi'. Hopefully those will be of some help. Also, a brief note - the reason all the filesystems are showing as unclean in dmesg-noacpi.txt is that my (FreeBSD 6.4) system panicked when I removed my USB stick. I've heard this was a known bug in beta versions of 7.0, but haven't heard of it happening in 6.4; I'm not sure if it's that bug again, or just a further result of my ACPI messing up. -------------- next part -------------- Copyright (c) 1992-2008 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 6.4-RC2 #0: Sat Nov 1 19:19:58 UTC 2008 root@palmer.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) M CPU 520 @ 1.60GHz (1600.07-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xafebfbff Features2=0xe31d AMD Features=0x20100800 AMD Features2=0x1 real memory = 526974976 (502 MB) avail memory = 495259648 (472 MB) ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Nov 1 2008 19:18:13) acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported acpi_hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: port 0x1800-0x1807 mem 0xd0300000-0xd037ffff,0xc0000000-0xcfffffff,0xd0400000-0xd043ffff irq 16 at device 2.0 on pci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M pci0: at device 2.1 (no driver attached) pci0: at device 27.0 (no driver attached) pcib1: irq 16 at device 28.0 on pci0 pci2: on pcib1 mskc0: irq 16 at device 0.0 on pci2 mskc0: 0x4000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). mskc0: unknown device: id=0xff, rev=0x0f device_attach: mskc0 attach returned 6 pcib2: irq 17 at device 28.1 on pci0 pci3: on pcib2 ath0: irq 17 at device 0.0 on pci3 ath0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffffffffffff). ath0: cannot map register space device_attach: ath0 attach returned 6 pcib3: irq 18 at device 28.2 on pci0 pci4: on pcib3 uhci0: port 0x1820-0x183f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1840-0x185f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1860-0x187f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x1880-0x189f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xd0644000-0xd06443ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib4: at device 30.0 on pci0 pci10: on pcib4 cbb0: mem 0xd0204000-0xd0204fff irq 20 at device 9.0 on pci10 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci10: at device 9.2 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18b0-0x18bf at device 31.2 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) acpi_acad0: on acpi0 battery0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 orm0: at iomem 0xdf800-0xdffff on isa0 ppc0: cannot reserve I/O port range 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 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding 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 ums0: Logitech USB Trackball, rev 1.10/14.00, addr 2, iclass 3/1 ums0: 5 buttons. Timecounter "TSC" frequency 1600068924 Hz quality 800 Timecounters tick every 1.000 msec hptrr: no controller detected. ad0: 76319MB at ata0-master SATA150 acd0: CDRW at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a -------------- next part -------------- Copyright (c) 1992-2008 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 6.4-RC2 #0: Sat Nov 1 19:19:58 UTC 2008 root@palmer.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) M CPU 520 @ 1.60GHz (1600.07-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xafebfbff Features2=0xe31d AMD Features=0x20100800 AMD Features2=0x1 real memory = 526974976 (502 MB) avail memory = 495259648 (472 MB) kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Nov 1 2008 19:18:13) cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: port 0x1800-0x1807 mem 0xd0300000-0xd037ffff,0xc0000000-0xcfffffff,0xd0400000-0xd043ffff irq 11 at device 2.0 on pci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M pci0: at device 2.1 (no driver attached) pci0: at device 27.0 (no driver attached) pcib1: irq 11 at device 28.0 on pci0 pci2: on pcib1 mskc0: port 0x2000-0x20ff mem 0xd0100000-0xd0103fff irq 11 at device 0.0 on pci2 msk0: on mskc0 msk0: Ethernet address: 00:1b:24:06:bd:5f miibus0: on msk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto mskc0: [FAST] pcib2: irq 11 at device 28.1 on pci0 pci3: on pcib2 ath0: mem 0xd0000000-0xd000ffff irq 11 at device 0.0 on pci3 ath0: unable to attach hardware; HAL status 13 device_attach: ath0 attach returned 6 pcib3: irq 10 at device 28.2 on pci0 pci4: on pcib3 pcib4: irq 10 at device 28.3 on pci0 pci5: on pcib4 uhci0: port 0x1820-0x183f irq 11 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1840-0x185f irq 10 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1860-0x187f irq 10 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x1880-0x189f irq 11 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xd0644000-0xd06443ff irq 11 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib5: at device 30.0 on pci0 pci10: on pcib5 cbb0: mem 0xd0204000-0xd0204fff irq 10 at device 9.0 on pci10 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci10: at device 9.2 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18b0-0x18bf at device 31.2 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) orm0: at iomem 0xdf800-0xdffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 ppc0: cannot reserve I/O port range 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 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding 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 ums0: Logitech USB Trackball, rev 1.10/14.00, addr 2, iclass 3/1 ums0: 5 buttons. Timecounter "TSC" frequency 1600065480 Hz quality 800 Timecounters tick every 1.000 msec hptrr: no controller detected. ad0: 76319MB at ata0-master SATA150 acd0: CDRW at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /home was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /var was not properly dismounted -------------- next part -------------- hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S3 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.cpu.cx_lowest: C1 hw.acpi.acline: 1 hw.acpi.battery.life: -1 hw.acpi.battery.time: -1 hw.acpi.battery.state: 7 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: 54.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: 99.0C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 105.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: 3 hw.acpi.thermal.tz0._TSP: 40 From jhb at freebsd.org Mon Nov 17 09:13:42 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Nov 17 09:13:48 2008 Subject: Marvell 88E8038 PCI-E controller doesn't appear as device with acpi enabled In-Reply-To: References: Message-ID: <200811171157.17556.jhb@freebsd.org> On Monday 17 November 2008 10:30:00 am Daniel Levine wrote: > On my Acer Aspire 3680-2633, the Marvell ethernet controller, which > appears like so under Linux lspci: > > 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 > PCI-E Fast Ethernet Controller (rev 14) > > Does not show up at all with acpi enabled - no msk0 in ifconfig -a, no > device in /dev, nothing. With acpi disabled, it appears and works > fine. This is the case under both FreeBSD 6.4 and 7.0, as well as > OpenBSD 4.4 and NetBSD 4.0.1. > > The acpidump output is available here: > > http://www.mediafire.com/?g4zin4s99b1 > > If MediaFire isn't cooperating, notify me and I'll upload again somewhere else. > > I've also attached the outputs of dmesg with acpi enabled and > disabled, and the output of 'sysctl hw.acpi'. Hopefully those will be > of some help. > > Also, a brief note - the reason all the filesystems are showing as > unclean in dmesg-noacpi.txt is that my (FreeBSD 6.4) system panicked > when I removed my USB stick. I've heard this was a known bug in beta > versions of 7.0, but haven't heard of it happening in 6.4; I'm not > sure if it's that bug again, or just a further result of my ACPI > messing up. Your devices are there, they just can't allocate resources. This is more of a FreeBSD bug in that we don't support fully allocating I/O port and memio resources for PCI devices from scratch, at least we don't handle allocating resources from scratch for devices behind PCI-PCI bridges. -- John Baldwin From dlev89 at gmail.com Mon Nov 17 10:20:45 2008 From: dlev89 at gmail.com (Daniel Levine) Date: Mon Nov 17 10:20:54 2008 Subject: Marvell 88E8038 PCI-E controller doesn't appear as device with acpi enabled In-Reply-To: <200811171157.17556.jhb@freebsd.org> References: <200811171157.17556.jhb@freebsd.org> Message-ID: It doesn't work on NetBSD either, though, nor Open, Dragonfly, etc. Is this bug common to all BSD flavors? Is there any workaround? On 11/17/08, John Baldwin wrote: > On Monday 17 November 2008 10:30:00 am Daniel Levine wrote: >> On my Acer Aspire 3680-2633, the Marvell ethernet controller, which >> appears like so under Linux lspci: >> >> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 >> PCI-E Fast Ethernet Controller (rev 14) >> >> Does not show up at all with acpi enabled - no msk0 in ifconfig -a, no >> device in /dev, nothing. With acpi disabled, it appears and works >> fine. This is the case under both FreeBSD 6.4 and 7.0, as well as >> OpenBSD 4.4 and NetBSD 4.0.1. >> >> The acpidump output is available here: >> >> http://www.mediafire.com/?g4zin4s99b1 >> >> If MediaFire isn't cooperating, notify me and I'll upload again somewhere > else. >> >> I've also attached the outputs of dmesg with acpi enabled and >> disabled, and the output of 'sysctl hw.acpi'. Hopefully those will be >> of some help. >> >> Also, a brief note - the reason all the filesystems are showing as >> unclean in dmesg-noacpi.txt is that my (FreeBSD 6.4) system panicked >> when I removed my USB stick. I've heard this was a known bug in beta >> versions of 7.0, but haven't heard of it happening in 6.4; I'm not >> sure if it's that bug again, or just a further result of my ACPI >> messing up. > > Your devices are there, they just can't allocate resources. This is more of > a > FreeBSD bug in that we don't support fully allocating I/O port and memio > resources for PCI devices from scratch, at least we don't handle allocating > resources from scratch for devices behind PCI-PCI bridges. > > -- > John Baldwin > From jhb at freebsd.org Mon Nov 17 13:14:03 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Nov 17 13:14:14 2008 Subject: Marvell 88E8038 PCI-E controller doesn't appear as device with acpi enabled In-Reply-To: References: <200811171157.17556.jhb@freebsd.org> Message-ID: <200811171610.49614.jhb@freebsd.org> On Monday 17 November 2008 01:20:43 pm Daniel Levine wrote: > It doesn't work on NetBSD either, though, nor Open, Dragonfly, etc. Is > this bug common to all BSD flavors? Is there any workaround? Yes. It's more a missing feature than a bug strictly speaking. It's the same exact problem as PNP OS=YES. Basically, *BSD still depend on the BIOS to do most of the resource allocation for devices. > On 11/17/08, John Baldwin wrote: > > On Monday 17 November 2008 10:30:00 am Daniel Levine wrote: > >> On my Acer Aspire 3680-2633, the Marvell ethernet controller, which > >> appears like so under Linux lspci: > >> > >> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 > >> PCI-E Fast Ethernet Controller (rev 14) > >> > >> Does not show up at all with acpi enabled - no msk0 in ifconfig -a, no > >> device in /dev, nothing. With acpi disabled, it appears and works > >> fine. This is the case under both FreeBSD 6.4 and 7.0, as well as > >> OpenBSD 4.4 and NetBSD 4.0.1. > >> > >> The acpidump output is available here: > >> > >> http://www.mediafire.com/?g4zin4s99b1 > >> > >> If MediaFire isn't cooperating, notify me and I'll upload again somewhere > > else. > >> > >> I've also attached the outputs of dmesg with acpi enabled and > >> disabled, and the output of 'sysctl hw.acpi'. Hopefully those will be > >> of some help. > >> > >> Also, a brief note - the reason all the filesystems are showing as > >> unclean in dmesg-noacpi.txt is that my (FreeBSD 6.4) system panicked > >> when I removed my USB stick. I've heard this was a known bug in beta > >> versions of 7.0, but haven't heard of it happening in 6.4; I'm not > >> sure if it's that bug again, or just a further result of my ACPI > >> messing up. > > > > Your devices are there, they just can't allocate resources. This is more of > > a > > FreeBSD bug in that we don't support fully allocating I/O port and memio > > resources for PCI devices from scratch, at least we don't handle allocating > > resources from scratch for devices behind PCI-PCI bridges. > > > > -- > > John Baldwin > > > -- John Baldwin From oberman at es.net Fri Nov 21 11:57:17 2008 From: oberman at es.net (Kevin Oberman) Date: Fri Nov 21 11:57:29 2008 Subject: Is the C3 possible with SMP? In-Reply-To: Your message of "Thu, 20 Nov 2008 22:32:57 +0100." Message-ID: <20081121195714.CEE4B45010@ptavv.es.net> > From: martinko > Date: Thu, 20 Nov 2008 22:32:57 +0100 > Sender: owner-freebsd-mobile@freebsd.org > > Alexandre "Sunny" Kovalenko wrote: > > On Mon, 2008-11-03 at 00:06 +0200, Alexander Motin wrote: > >> Alexandre "Sunny" Kovalenko wrote: > >>>> I have tried to enable C3 state on my Core2Duo laptop and found that it > >>>> is not working good. System HZ timer stops during CPU sleep. After some > >>>> investigation I have found that it is due to LAPIC timer used for HZ > >>>> stopped during C3 state (same as during AMD's C1E). > >>>> > >>>> So the question is: Is it possible (or planned) to make it work somehow? > >>>> For example, by using some external timer instead of LAPIC's one? > >>>> > >>>> ACPI reports about 20% less idle power consumption with C3 state > >>>> comparing to C2. It would be interesting to get additional half an hour > >>>> on battery. > >>>> > >>> You can get half way there by adding > >>> > >>> dev.cpu.1.cx_lowest=C3 > >>> > >>> to /etc/sysctl.conf > >> Thanks. > >> > >> 1. Looks like it does not kill the timer. > >> 2. I haven't got any benefit from it in idle state. According to > >> `acpiconf -i 0` I have about 13 Amps (IMHO more looks like Watts) with > >> both C2 and this half-to-C3, but only 11 Amps in full C3 (but without > >> timer). > >> 3. I have got about 10% benefit (33 Amps against 36) when cpu0 is 100% > >> busy while cpu1 is idle. > >> > > You would not happen to have USB loaded or built into kernel? If you do, > > you will practically never go into C3. What does > > > > sysctl dev.cpu | grep cx_usage > > > > say? > > > > Hi, > > My laptop reports C1 state only: > > $ sysctl -a | grep cx_ > hw.acpi.cpu.cx_lowest: C1 > dev.cpu.0.cx_supported: C1/1 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% > > But this is Pentium-M and I remember it could use C2 and C3 back with > 5.x kernel and I'm sure I had USB as I have now. > > Do you have any idea why I don't have C2/C3 states available anymore ?? Under 7-Stable, my Pentium-M system (ThinkPad T43) shows C1, C2, and C3. Of course, it's not an SMP. dev.cpu.0.cx_supported: C1/1 C2/1 C3/85 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% cx_supported has nothing to do with the value of cx_lowest. It should simply be what the CPU reports back vi ACPI as to the C states supported on the platform. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081121/3e6c9d66/attachment.pgp From smithi at nimnet.asn.au Fri Nov 21 17:34:19 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Fri Nov 21 17:34:32 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <20081121195714.CEE4B45010@ptavv.es.net> References: <20081121195714.CEE4B45010@ptavv.es.net> Message-ID: <20081122113015.B70117@sola.nimnet.asn.au> On Fri, 21 Nov 2008, Kevin Oberman wrote: > > From: martinko > > > > Alexandre "Sunny" Kovalenko wrote: > > > On Mon, 2008-11-03 at 00:06 +0200, Alexander Motin wrote: > > >> Alexandre "Sunny" Kovalenko wrote: > > >>>> I have tried to enable C3 state on my Core2Duo laptop and found that it > > >>>> is not working good. System HZ timer stops during CPU sleep. After some > > >>>> investigation I have found that it is due to LAPIC timer used for HZ > > >>>> stopped during C3 state (same as during AMD's C1E). > > >>>> > > >>>> So the question is: Is it possible (or planned) to make it work somehow? > > >>>> For example, by using some external timer instead of LAPIC's one? > > >>>> > > >>>> ACPI reports about 20% less idle power consumption with C3 state > > >>>> comparing to C2. It would be interesting to get additional half an hour > > >>>> on battery. > > >>>> > > >>> You can get half way there by adding > > >>> > > >>> dev.cpu.1.cx_lowest=C3 > > >>> > > >>> to /etc/sysctl.conf > > >> Thanks. > > >> > > >> 1. Looks like it does not kill the timer. > > >> 2. I haven't got any benefit from it in idle state. According to > > >> `acpiconf -i 0` I have about 13 Amps (IMHO more looks like Watts) with That'll be Watts, for sure. 13 Amps would be somewhere between ~120W and ~180W depending on the battery voltage, and 36 Amps (below) would be 400W or more .. handy, maybe, for cooking breakfast on your touchpad :) > > >> both C2 and this half-to-C3, but only 11 Amps in full C3 (but without > > >> timer). > > >> 3. I have got about 10% benefit (33 Amps against 36) when cpu0 is 100% > > >> busy while cpu1 is idle. > > >> > > > You would not happen to have USB loaded or built into kernel? If you do, > > > you will practically never go into C3. What does > > > > > > sysctl dev.cpu | grep cx_usage > > > > > > say? > > > > > > > Hi, > > > > My laptop reports C1 state only: > > > > $ sysctl -a | grep cx_ > > hw.acpi.cpu.cx_lowest: C1 > > dev.cpu.0.cx_supported: C1/1 > > dev.cpu.0.cx_lowest: C1 > > dev.cpu.0.cx_usage: 100.00% > > > > But this is Pentium-M and I remember it could use C2 and C3 back with > > 5.x kernel and I'm sure I had USB as I have now. > > > > Do you have any idea why I don't have C2/C3 states available anymore ?? > > Under 7-Stable, my Pentium-M system (ThinkPad T43) shows C1, C2, and > C3. Of course, it's not an SMP. > dev.cpu.0.cx_supported: C1/1 C2/1 C3/85 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% > > cx_supported has nothing to do with the value of cx_lowest. It should > simply be what the CPU reports back vi ACPI as to the C states supported > on the platform. Well, except that cx_supported shows the possible values for cx_lowest; ie you can only select a value for cx_lowest that's in cx_supported .. so it does seem odd that martinko's cx_supported has been limited to C1? Whether the system ever actually uses the cx_lowest value you select, other than C1, is another matter of course. My T23 (P3-M, 7.0-R) allows selection of C3, but only ever uses it if the machine was booted up on battery(!) but that might be a BIOS/EC bug that upgrading these may fix. cheers, Ian From smithi at nimnet.asn.au Fri Nov 21 18:12:22 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Fri Nov 21 18:12:28 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <492763E6.1080808@gmail.com> References: <20081121195714.CEE4B45010@ptavv.es.net> <20081122113015.B70117@sola.nimnet.asn.au> <492763E6.1080808@gmail.com> Message-ID: <20081122130515.K70117@sola.nimnet.asn.au> On Fri, 21 Nov 2008, Dana H. Myers wrote: > Ian Smith wrote: > > On Fri, 21 Nov 2008, Kevin Oberman wrote: > > > > > >> 1. Looks like it does not kill the timer. > > > > >> 2. I haven't got any benefit from it in idle state. According to > > > > >> `acpiconf -i 0` I have about 13 Amps (IMHO more looks like Watts) with > > That'll be Watts, for sure. 13 Amps would be somewhere between ~120W and > > ~180W depending on the battery voltage, and 36 Amps (below) would be 400W > > or more .. handy, maybe, for cooking breakfast on your touchpad :) > > While I suspect the value is indeed Watts, I do not know > why you're thinking 36A would indicate 400W or more. Modern > CPUs typically run at relatively low voltages between 1.0V > and 1.6V and proportionately high current. Unless acpiconf -i has changed between 7.0 and now, it reports Present Rate in mW, at least when running on battery. My T23 right now reports that as 13447mW, ie 13.447W. With a present battery voltage of 12.247V, that'd be 1.097 Amps battery discharge. YMMV. cheers, Ian From dana.myers at gmail.com Fri Nov 21 18:14:53 2008 From: dana.myers at gmail.com (Dana H. Myers) Date: Fri Nov 21 18:14:59 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <20081122113015.B70117@sola.nimnet.asn.au> References: <20081121195714.CEE4B45010@ptavv.es.net> <20081122113015.B70117@sola.nimnet.asn.au> Message-ID: <492763E6.1080808@gmail.com> Ian Smith wrote: > On Fri, 21 Nov 2008, Kevin Oberman wrote: > > > >> 1. Looks like it does not kill the timer. > > > >> 2. I haven't got any benefit from it in idle state. According to > > > >> `acpiconf -i 0` I have about 13 Amps (IMHO more looks like Watts) with > > That'll be Watts, for sure. 13 Amps would be somewhere between ~120W > and ~180W depending on the battery voltage, and 36 Amps (below) would be > 400W or more .. handy, maybe, for cooking breakfast on your touchpad :) While I suspect the value is indeed Watts, I do not know why you're thinking 36A would indicate 400W or more. Modern CPUs typically run at relatively low voltages between 1.0V and 1.6V and proportionately high current. Dana From dana.myers at gmail.com Fri Nov 21 19:32:52 2008 From: dana.myers at gmail.com (Dana H. Myers) Date: Fri Nov 21 19:32:58 2008 Subject: Is the C3 possible with SMP? In-Reply-To: <20081122130515.K70117@sola.nimnet.asn.au> References: <20081121195714.CEE4B45010@ptavv.es.net> <20081122113015.B70117@sola.nimnet.asn.au> <492763E6.1080808@gmail.com> <20081122130515.K70117@sola.nimnet.asn.au> Message-ID: <49277D56.7030202@gmail.com> Ian Smith wrote: > > While I suspect the value is indeed Watts, I do not know > > why you're thinking 36A would indicate 400W or more. Modern > > CPUs typically run at relatively low voltages between 1.0V > > and 1.6V and proportionately high current. > > Unless acpiconf -i has changed between 7.0 and now, it reports Present > Rate in mW, at least when running on battery. My T23 right now reports > that as 13447mW, ie 13.447W. With a present battery voltage of 12.247V, > that'd be 1.097 Amps battery discharge. YMMV. Ah - my error. acpiconf -i reports on the battery, not the CPU. For some reason I was thinking that we were discussing CPU power consumption. My apologies. Dana From gdoe6545 at yahoo.it Sat Nov 22 12:29:06 2008 From: gdoe6545 at yahoo.it (Gianni Doe) Date: Sat Nov 22 12:29:13 2008 Subject: ACPI Errors on MSI Wind U100 Message-ID: Hi I've installed the latest 7.1-PRERELEASE on an MSI Wind U100 notebook and a number of APCI errors are reported at boot; the only noticeable consequence seems to be that the system won't resume from sleep, although there may be other issues that I haven't discovered yet. I've followed the suggstions in the handbook and posted a URL to the asl below and the dmesg and sysctl output. Any suggestions to help get the resume from sleep working would be much appreciated, also if there's any extra info I can provide to help diagnose the problem please let me know. Regards Gianni http://www.orpello.com/MSIWindU100.asl # sysctl hw.acpi hw.acpi.supported_sleep_state: S1 S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 1 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: 49.0C hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.passive_cooling: 0 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: -1 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 100.0C hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._TC1: -1 hw.acpi.thermal.tz0._TC2: -1 hw.acpi.thermal.tz0._TSP: -1 hw.acpi.acline: 0 hw.acpi.battery.life: 65 hw.acpi.battery.time: 67 hw.acpi.battery.state: 1 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 hw.acpi.cpu.cx_lowest: C1 #dmesg 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 (Nov 22 2008 06:55:15) npx0: INT 16 interface cryptosoft0: on motherboard crypto: assign cryptosoft0 driver id 0, flags 100663296 crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 2 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 3 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 4 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 5 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 16 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 6 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 7 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 18 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 19 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 20 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 8 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 15 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 9 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 10 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 13 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 14 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 11 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 21 flags 0 maxoplen 0 crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: wakeup code va 0xd906c000 pa 0x1000 ACPI Error (evregion-0427): No handler for Region [EC__] (0xc5228140) [EmbeddedControl] [20070320] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (uteval-0309): Method execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (evregion-0427): No handler for Region [EC__] (0xc5228140) [EmbeddedControl] [20070320] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (uteval-0309): Method execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (evregion-0427): No handler for Region [EC__] (0xc5228140) [EmbeddedControl] [20070320] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (uteval-0309): Method execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (evregion-0427): No handler for Region [EC__] (0xc5228140) [EmbeddedControl] [20070320] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (uteval-0309): Method execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (evregion-0427): No handler for Region [EC__] (0xc5228140) [EmbeddedControl] [20070320] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (uteval-0309): Method execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST pci_open(1): mode 1 addr port (0x0cf8) is 0x8000fa08 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=27ac8086) pcibios: No call entry point AcpiOsDerivePciId: \\_SB_.PCI0.SBRG.PIX0 -> bus 0 dev 31 func 0 ACPI Error (evregion-0427): No handler for Region [EC__] (0xc5228140) [EmbeddedControl] [20070320] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (uteval-0309): Method execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (evregion-0427): No handler for Region [EC__] (0xc5228140) [EmbeddedControl] [20070320] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI Error (uteval-0309): Method execution failed [\ \_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xc522b740), AE_NOT_EXIST ACPI timer: 1/0 0/3 1/1 1/2 0/3 0/4 0/3 1/2 0/4 0/3 -> 4 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 10 11 12 14 15 Validation 0 11 N 0 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 6 7 10 11 12 14 15 Validation 0 10 N 0 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 7 N 0 3 4 5 6 7 10 11 12 14 15 Validation 0 7 N 0 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 3 N 0 3 4 5 6 7 10 11 12 14 15 Validation 0 3 N 0 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 6 7 10 11 12 14 15 Validation 0 255 N 0 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 6 7 10 11 12 14 15 Validation 0 255 N 0 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 6 7 10 11 12 14 15 Validation 0 255 N 0 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 3 4 5 6 7 10 11 12 14 15 Validation 0 5 N 0 3 4 5 6 7 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 10 11 12 14 15 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x27ac, revid=0x03 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27ae, revid=0x03 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message map[10]: type Memory, range 32, base 0xdfe80000, size 19, enabled map[14]: type I/O Port, range 32, base 0xe0f0, size 3, enabled map[18]: type Prefetchable Memory, range 32, base 0xc0000000, size 28, enabled map[1c]: type Memory, range 32, base 0xdff00000, size 18, enabled pcib0: matched entry for 0.2.INTA pcib0: slot 2 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27a6, revid=0x03 domain=0, bus=0, slot=2, func=1 class=03-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xdfe00000, size 19, enabled found-> vendor=0x8086, dev=0x27d8, revid=0x02 domain=0, bus=0, slot=27, func=0 class=04-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xffe00000, size 14, enabled pcib0: matched entry for 0.27.INTA pcib0: slot 27 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27d0, revid=0x02 domain=0, bus=0, slot=28, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27d2, revid=0x02 domain=0, bus=0, slot=28, func=1 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTB pcib0: slot 28 INTB hardwired to IRQ 17 found-> vendor=0x8086, dev=0x27c8, revid=0x02 domain=0, bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[20]: type I/O Port, range 32, base 0xe080, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 23 found-> vendor=0x8086, dev=0x27c9, revid=0x02 domain=0, bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=3 map[20]: type I/O Port, range 32, base 0xe060, size 5, enabled pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 19 found-> vendor=0x8086, dev=0x27ca, revid=0x02 domain=0, bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=7 map[20]: type I/O Port, range 32, base 0xe040, size 5, enabled pcib0: matched entry for 0.29.INTC pcib0: slot 29 INTC hardwired to IRQ 18 found-> vendor=0x8086, dev=0x27cb, revid=0x02 domain=0, bus=0, slot=29, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 map[20]: type I/O Port, range 32, base 0xe020, size 5, enabled pcib0: matched entry for 0.29.INTD pcib0: slot 29 INTD hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27cc, revid=0x02 domain=0, bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xdff40000, size 10, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 23 found-> vendor=0x8086, dev=0x2448, revid=0xe2 domain=0, bus=0, slot=30, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27b9, revid=0x02 domain=0, bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27c4, revid=0x02 domain=0, bus=0, slot=31, func=2 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02b8, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=3 powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0xe0a0, size 4, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 19 found-> vendor=0x8086, dev=0x27da, revid=0x02 domain=0, bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=3 map[20]: type I/O Port, range 32, base 0xe000, size 5, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 19 vgapci0: port 0xe0f0-0xe0f7 mem 0xdfe80000-0xdfefffff,0xc0000000-0xcfffffff,0xdff00000-0xdff3ffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 vgapci0: Reserved 0x10000000 bytes for rid 0x18 type 3 at 0xc0000000 vgapci0: Reserved 0x80000 bytes for rid 0x10 type 3 at 0xdfe80000 vgapci0: Reserved 0x40000 bytes for rid 0x1c type 3 at 0xdff00000 agp0: detected 7932k stolen memory agp0: aperture size is 256M vgapci1: mem 0xdfe00000-0xdfe7ffff at device 2.1 on pci0 pcm0: mem 0xffe00000-0xffe03fff irq 16 at device 27.0 on pci0 pcm0: TCSEL: 0x00 -> 0x00 pcm0: DMA Coherency: Uncacheable / vendor=0x8086 pcm0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xffe00000 ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49 pcm0: [MPSAFE] pcm0: [ITHREAD] pcm0: hdac_dma_alloc: size=1024 -> roundsz=1024 pcm0: hdac_dma_alloc: size=2048 -> roundsz=2048 pcib1: irq 16 at device 28.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xd000-0xdfff pcib1: memory decode 0xdfd00000-0xdfdfffff pcib1: prefetched decode 0xffd00000-0xffdfffff pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x10ec, dev=0x8136, revid=0x02 domain=0, bus=1, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit MSI-X supports 2 messages in map 0x20 map[10]: type I/O Port, range 32, base 0xd000, size 8, enabled pcib1: requested I/O range 0xd000-0xd0ff: in range map[18]: type Prefetchable Memory, range 64, base 0xffd10000, size 12, enabled pcib1: requested memory range 0xffd10000-0xffd10fff: good map[20]: type Prefetchable Memory, range 64, base 0xffd00000, size 16, enabled pcib1: requested memory range 0xffd00000-0xffd0ffff: good pcib1: matched entry for 1.0.INTA pcib1: slot 0 INTA hardwired to IRQ 16 re0: port 0xd000-0xd0ff mem 0xffd10000-0xffd10fff,0xffd00000-0xffd0ffff irq 16 at device 0.0 on pci1 re0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0xffd10000 re0: MSI count : 1 re0: Chip rev. 0x34800000 re0: MAC rev. 0x00200000 miibus0: on re0 rlphy0: PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: bpf attached re0: Ethernet address: 00:21:85:dd:1f:77 re0: [MPSAFE] re0: [FILTER] pcib2: irq 17 at device 28.1 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xdfc00000-0xdfcfffff pcib2: no prefetched decode pci2: on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x1814, dev=0x0781, revid=0x00 domain=0, bus=2, slot=0, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 32 messages, 64 bit map[10]: type Memory, range 32, base 0xdfc00000, size 16, enabled pcib2: requested memory range 0xdfc00000-0xdfc0ffff: good pcib2: matched entry for 2.0.INTA pcib2: slot 0 INTA hardwired to IRQ 17 pci2: at device 0.0 (no driver attached) uhci0: port 0xe080-0xe09f irq 23 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe080 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 50 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 0xe060-0xe07f irq 19 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe060 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 51 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe040-0xe05f irq 18 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe040 ioapic0: routing intpin 18 (PCI IRQ 18) to vector 52 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xe020-0xe03f irq 16 at device 29.3 on pci0 uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe020 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xdff40000-0xdff403ff irq 23 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xdff40000 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered umass0: on uhub4 umass0:0:0:-1: Attached to scbus0 pcib3: at device 30.0 on pci0 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xf000-0xfff pcib3: no prefetched decode pcib3: Subtractively decoded bridge. pcib3: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P1 - AE_NOT_FOUND pci3: on pcib3 pci3: domain=0, physical bus=3 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe0a0-0xe0af irq 19 at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xe0a0 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=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 53 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=40 ostat1=40 ata1: stat0=0x0f err=0x0f lsb=0x0f msb=0x0f ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat0=0x0f err=0x0f lsb=0x0f msb=0x0f ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat0=0x0f err=0x0f lsb=0x0f msb=0x0f ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat0=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: stat1=0x07 err=0x07 lsb=0x07 msb=0x07 ata1: reset tp2 stat0=87 stat1=87 devices=0x0 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 54 ata1: [MPSAFE] ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_tz0: on acpi0 acpi_hpet0: iomem 0xfed03000-0xfed033ff on acpi0 acpi_hpet0: vend: 0x8086 rev: 0x1 num: 2 hz: 14318180 opts: legacy_route 64-bit Timecounter "HPET" frequency 14318180 Hz quality 900 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 55 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0065 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to vector 56 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 acpi_acad0: on acpi0 battery0: on acpi0 acpi_lid0: on acpi0 cpu0: on acpi0 ACPI: SSDT @ 0x0x7f5e8c90/0x0253 (v 2 PmRef Cpu0Ist 0x00003000 INTL 0x20051117) ACPI: SSDT @ 0x0x7f5e7690/0x0653 (v 2 PmRef Cpu0Cst 0x00003001 INTL 0x20051117) est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 ACPI: SSDT @ 0x0x7f5e8f10/0x00D0 (v 2 PmRef Cpu1Ist 0x00003000 INTL 0x20051117) ACPI: SSDT @ 0x0x7f611b10/0x0083 (v 2 PmRef Cpu1Cst 0x00003000 INTL 0x20051117) est1: on cpu1 p4tcc1: on cpu1 ex_isa_identify() ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 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 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 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xcf000-0xcffff 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) fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 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) sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0xea9 0xea9 0xea9 0xea9 sio0: probe failed test(s): 0 1 2 4 6 7 9 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0xea9 0xea9 0xea9 0xea9 sio0: probe failed test(s): 0 1 2 4 6 7 9 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding ioapic0: routing intpin 4 (ISA IRQ 4) to vector 57 sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0xea9 0xea9 0xea9 0xea9 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. Reducing kern.maxvnodes 133462 -> 100000 procfs registered lapic: Divisor 2, Frequency 66667060 hz Timecounter "TSC" frequency 1600009032 Hz quality -100 Timecounters tick every 1.000 msec lo0: bpf attached hptrr: no controller detected. acpi_acad0: acline initialization start battery0: battery initialization start ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ad0: 152627MB at ata0-master SATA150 ad0: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 system power profile changed to 'economy' acpi_acad0: Off Line acpi_acad0: acline initialization done, tried 1 times ad0: Intel check1 failed battery0: battery initialization done, tried 1 times ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed pcm0: HDA_DEBUG: HDA Config: on=0x00000000 off=0x00000000 pcm0: HDA_DEBUG: Starting CORB Engine... pcm0: HDA_DEBUG: Starting RIRB Engine... pcm0: HDA_DEBUG: Enabling controller interrupt... pcm0: HDA_DEBUG: Scanning HDA codecs [start index=0] ... pcm0: HDA_DEBUG: Probing codec: 0 pcm0: HDA_DEBUG: startnode=1 endnode=2 pcm0: HDA_DEBUG: Found AFG nid=1 [startnode=1 endnode=2] pcm0: HDA_DEBUG: Parsing AFG nid=1 cad=0 pcm0: Vendor: 0x000010ec pcm0: Device: 0x00000888 pcm0: Revision: 0x00000001 pcm0: Stepping: 0x00000001 pcm0: PCI Subvendor: 0x01101462 pcm0: Nodes: start=2 endnode=39 total=37 pcm0: CORB size: 256 pcm0: RIRB size: 256 pcm0: Streams: ISS=4 OSS=4 BSS=0 pcm0: GPIO: 0x40000002 pcm0: NumGPIO=2 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=8 entries=1 found=1 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=9 entries=1 found=1 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=10 entries=1 found=1 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=11 entries=10 found=10 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=12 entries=2 found=2 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=13 entries=2 found=2 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=14 entries=2 found=2 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=15 entries=2 found=2 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=17 entries=1 found=1 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=20 entries=5 found=5 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=21 entries=5 found=5 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=22 entries=5 found=5 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=23 entries=5 found=5 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=24 entries=5 found=5 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=25 entries=5 found=5 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=26 entries=5 found=5 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=27 entries=5 found=5 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=30 entries=1 found=1 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=34 entries=11 found=11 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=35 entries=11 found=11 pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=38 entries=2 found=2 pcm0: HDA_DEBUG: Parsing Ctls... pcm0: HDA_DEBUG: Parsing vendor patch... pcm0: HDA_DEBUG: Building AFG tree... pcm0: HDA_DEBUG: HWiP: HDA Widget Parser - Revision 1 pcm0: HDA_DEBUG: HWiP: Found 10 DAC path using HDA_PARSE_MIXER strategy. pcm0: HDA_DEBUG: AFG commit... pcm0: HDA_DEBUG: Ctls commit... pcm0: [ 5] Ctl nid=11 childnid=26 DISABLED pcm0: [ 6] Ctl nid=11 childnid=27 Bind to NONE pcm0: [ 7] Ctl nid=11 childnid=28 DISABLED pcm0: [ 8] Ctl nid=11 childnid=29 DISABLED pcm0: [ 9] Ctl nid=11 childnid=20 Bind to NONE pcm0: [10] Ctl nid=11 childnid=21 DISABLED pcm0: [11] Ctl nid=11 childnid=22 DISABLED pcm0: [12] Ctl nid=11 childnid=23 DISABLED pcm0: [13] Ctl nid=12 Bind to NONE pcm0: [15] Ctl nid=12 childnid=11 Bind to NONE pcm0: [16] Ctl nid=13 Bind to NONE pcm0: [18] Ctl nid=13 childnid=11 Bind to NONE pcm0: [19] Ctl nid=14 Bind to NONE pcm0: [21] Ctl nid=14 childnid=11 Bind to NONE pcm0: [22] Ctl nid=15 Bind to NONE pcm0: [24] Ctl nid=15 childnid=11 Bind to NONE pcm0: [25] Ctl nid=20 Bind to NONE pcm0: [26] Ctl nid=20 Bind to NONE pcm0: [27] Ctl nid=21 DISABLED pcm0: [28] Ctl nid=21 DISABLED pcm0: [29] Ctl nid=22 DISABLED pcm0: [30] Ctl nid=22 DISABLED pcm0: [31] Ctl nid=23 DISABLED pcm0: [32] Ctl nid=23 DISABLED pcm0: [33] Ctl nid=24 Bind to NONE pcm0: [34] Ctl nid=24 Bind to NONE pcm0: [35] Ctl nid=25 Bind to NONE pcm0: [36] Ctl nid=25 Bind to NONE pcm0: [37] Ctl nid=26 DISABLED pcm0: [38] Ctl nid=26 DISABLED pcm0: [39] Ctl nid=27 Bind to NONE pcm0: [40] Ctl nid=27 Bind to NONE pcm0: [41] Ctl nid=34 childnid=24 Bind to NONE pcm0: [42] Ctl nid=34 childnid=25 Bind to NONE pcm0: [43] Ctl nid=34 childnid=26 DISABLED pcm0: [44] Ctl nid=34 childnid=27 Bind to NONE pcm0: [45] Ctl nid=34 childnid=28 DISABLED pcm0: [46] Ctl nid=34 childnid=29 DISABLED pcm0: [47] Ctl nid=34 childnid=20 Bind to NONE pcm0: [48] Ctl nid=34 childnid=21 DISABLED pcm0: [49] Ctl nid=34 childnid=22 DISABLED pcm0: [50] Ctl nid=34 childnid=23 DISABLED pcm0: [51] Ctl nid=34 childnid=11 Bind to NONE pcm0: [52] Ctl nid=35 childnid=24 Bind to NONE pcm0: [53] Ctl nid=35 childnid=25 Bind to NONE pcm0: [54] Ctl nid=35 childnid=26 DISABLED pcm0: [55] Ctl nid=35 childnid=27 Bind to NONE pcm0: [56] Ctl nid=35 childnid=28 DISABLED pcm0: [57] Ctl nid=35 childnid=29 DISABLED pcm0: [58] Ctl nid=35 childnid=20 Bind to NONE pcm0: [59] Ctl nid=35 childnid=21 DISABLED pcm0: [60] Ctl nid=35 childnid=22 DISABLED pcm0: [61] Ctl nid=35 childnid=23 DISABLED pcm0: [62] Ctl nid=35 childnid=11 Bind to NONE pcm0: [63] Ctl nid=38 Bind to NONE pcm0: [65] Ctl nid=38 childnid=11 Bind to NONE pcm0: HDA_DEBUG: PCMDIR_PLAY setup... pcm0: HDA_DEBUG: PCMDIR_REC setup... pcm0: HDA_DEBUG: OSS mixer initialization... pcm0: HDA_DEBUG: Enabling Soft PCM volume pcm0: Mixer "vol": child=0x00000010 pcm0: Mixer "pcm": parent="vol" pcm0: Mixer "mic": pcm0: Mixer "rec": pcm0: Soft PCM mixer ENABLED pcm0: HDA_DEBUG: Registering PCM channels... pcm0: clone manager: deadline=750ms flags=0x8000001e pcm0: hdac_dma_alloc: size=4096 -> roundsz=4096 pcm0: sndbuf_setmap 17f0000, 4000; 0xe5967000 -> 17f0000 pcm0: hdac_dma_alloc: size=4096 -> roundsz=4096 pcm0: sndbuf_setmap 1800000, 4000; 0xe596b000 -> 1800000 pcm0: pcm0: pcm0: pcm0: pcm0: HDA config/quirks: forcestereo ivref50 ivref80 ivref100 ivref pcm0: pcm0: +-------------------+ pcm0: | DUMPING HDA NODES | pcm0: +-------------------+ pcm0: pcm0: Default Parameter pcm0: ----------------- pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x000e0560 pcm0: PCM size: 16 20 24 pcm0: PCM rate: 44 48 96 192 pcm0: IN amp: 0x00000000 pcm0: OUT amp: 0x00000000 pcm0: pcm0: nid: 2 [ANALOG] pcm0: name: audio output pcm0: widget_cap: 0x00000011 pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x000e0560 pcm0: PCM size: 16 20 24 pcm0: PCM rate: 44 48 96 192 pcm0: connections: 0 pcm0: pcm0: nid: 3 [ANALOG] pcm0: name: audio output pcm0: widget_cap: 0x00000011 pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x000e0560 pcm0: PCM size: 16 20 24 pcm0: PCM rate: 44 48 96 192 pcm0: connections: 0 pcm0: pcm0: nid: 4 [ANALOG] pcm0: name: audio output pcm0: widget_cap: 0x00000011 pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x000e0560 pcm0: PCM size: 16 20 24 pcm0: PCM rate: 44 48 96 192 pcm0: connections: 0 pcm0: pcm0: nid: 5 [ANALOG] pcm0: name: audio output pcm0: widget_cap: 0x00000011 pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x000e0560 pcm0: PCM size: 16 20 24 pcm0: PCM rate: 44 48 96 192 pcm0: connections: 0 pcm0: pcm0: nid: 6 [DIGITAL] [DISABLED] pcm0: name: audio output pcm0: widget_cap: 0x00000211 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x001e05e0 pcm0: PCM size: 16 20 24 32 pcm0: PCM rate: 44 48 88 96 192 pcm0: connections: 0 pcm0: pcm0: nid: 7 [ANALOG] pcm0: name: vendor widget pcm0: widget_cap: 0x00f00000 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: connections: 0 pcm0: pcm0: nid: 8 [ANALOG] pcm0: name: audio input pcm0: widget_cap: 0x0010011b pcm0: Parse flags: 0x00000002 pcm0: Ctl flags: 0x00000800 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x00060160 pcm0: PCM size: 16 20 pcm0: PCM rate: 44 48 96 pcm0: Input amp: 0x80051f0b pcm0: mute=1 step=31 size=5 offset=11 pcm0: connections: 1 pcm0: | pcm0: + <- nid=35 [audio mixer] pcm0: pcm0: nid: 9 [ANALOG] pcm0: name: audio input pcm0: widget_cap: 0x0010011b pcm0: Parse flags: 0x00000002 pcm0: Ctl flags: 0x00000800 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x00060160 pcm0: PCM size: 16 20 pcm0: PCM rate: 44 48 96 pcm0: Input amp: 0x80051f0b pcm0: mute=1 step=31 size=5 offset=11 pcm0: connections: 1 pcm0: | pcm0: + <- nid=34 [audio mixer] pcm0: pcm0: nid: 10 [DIGITAL] [DISABLED] pcm0: name: audio input pcm0: widget_cap: 0x00100391 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x001e0160 pcm0: PCM size: 16 20 24 32 pcm0: PCM rate: 44 48 96 pcm0: connections: 1 pcm0: | pcm0: + <- nid=31 [pin: speaker (none)] [DISABLED] pcm0: pcm0: nid: 11 [ANALOG] pcm0: name: audio mixer pcm0: widget_cap: 0x0020010b pcm0: Parse flags: 0x00000002 pcm0: Ctl flags: 0x00000081 pcm0: Input amp: 0x80051f17 pcm0: mute=1 step=31 size=5 offset=23 pcm0: connections: 10 pcm0: | pcm0: + <- nid=24 [pin: Mic in (jack)] pcm0: | pcm0: + <- nid=25 [pin: Mic in (fixed)] pcm0: | pcm0: + <- nid=26 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=27 [pin: speaker (fixed)] pcm0: | pcm0: + <- nid=28 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=29 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=20 [pin: headphones out (jack)] pcm0: | pcm0: + <- nid=21 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=22 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=23 [pin: speaker (none)] [DISABLED] pcm0: pcm0: nid: 12 [ANALOG] pcm0: name: audio mixer pcm0: widget_cap: 0x0020010f pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000091 pcm0: Output amp: 0x00051f1f pcm0: mute=0 step=31 size=5 offset=31 pcm0: Input amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: connections: 2 pcm0: | pcm0: + <- nid=2 [audio output] pcm0: | pcm0: + <- nid=11 [audio mixer] pcm0: pcm0: nid: 13 [ANALOG] pcm0: name: audio mixer pcm0: widget_cap: 0x0020010f pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Output amp: 0x00051f1f pcm0: mute=0 step=31 size=5 offset=31 pcm0: Input amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: connections: 2 pcm0: | pcm0: + <- nid=3 [audio output] pcm0: | pcm0: + <- nid=11 [audio mixer] pcm0: pcm0: nid: 14 [ANALOG] pcm0: name: audio mixer pcm0: widget_cap: 0x0020010f pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Output amp: 0x00051f1f pcm0: mute=0 step=31 size=5 offset=31 pcm0: Input amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: connections: 2 pcm0: | pcm0: + <- nid=4 [audio output] pcm0: | pcm0: + <- nid=11 [audio mixer] pcm0: pcm0: nid: 15 [ANALOG] pcm0: name: audio mixer pcm0: widget_cap: 0x0020010f pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Output amp: 0x00051f1f pcm0: mute=0 step=31 size=5 offset=31 pcm0: Input amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: connections: 2 pcm0: | pcm0: + <- nid=5 [audio output] pcm0: | pcm0: + <- nid=11 [audio mixer] pcm0: pcm0: nid: 16 [DIGITAL] [DISABLED] pcm0: name: audio output pcm0: widget_cap: 0x00000211 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x001e05e0 pcm0: PCM size: 16 20 24 32 pcm0: PCM rate: 44 48 88 96 192 pcm0: connections: 0 pcm0: pcm0: nid: 17 [DIGITAL] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x00400300 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x00000010 pcm0: OUT pcm0: Pin config: 0x411111f0 pcm0: Pin control: 0x00000040 OUT pcm0: connections: 1 pcm0: | pcm0: + <- nid=16 [audio output] [DISABLED] pcm0: pcm0: nid: 18 [ANALOG] pcm0: name: vendor widget pcm0: widget_cap: 0x00f00000 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: connections: 0 pcm0: pcm0: nid: 19 [ANALOG] pcm0: name: vendor widget pcm0: widget_cap: 0x00f00000 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: connections: 0 pcm0: pcm0: nid: 20 [ANALOG] pcm0: name: pin: headphones out (jack) pcm0: widget_cap: 0x0040018f pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x0000003e pcm0: TRQD HP OUT IN : UNSOL pcm0: Pin config: 0x0121401f pcm0: Pin control: 0x000000c0 HP OUT pcm0: Output amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: Input amp: 0x00270300 pcm0: mute=0 step=3 size=39 offset=0 pcm0: connections: 5 pcm0: | pcm0: + <- nid=12 [audio mixer] (selected) pcm0: | pcm0: + <- nid=13 [audio mixer] pcm0: | pcm0: + <- nid=14 [audio mixer] pcm0: | pcm0: + <- nid=15 [audio mixer] pcm0: | pcm0: + <- nid=38 [audio mixer] pcm0: pcm0: nid: 21 [ANALOG] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x0040018f pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x0000003e pcm0: TRQD HP OUT IN : UNSOL pcm0: Pin config: 0x411111f0 pcm0: Pin control: 0x000000e0 HP IN OUT pcm0: Output amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: Input amp: 0x00270300 pcm0: mute=0 step=3 size=39 offset=0 pcm0: connections: 5 pcm0: | pcm0: + <- nid=12 [audio mixer] pcm0: | pcm0: + <- nid=13 [audio mixer] pcm0: | pcm0: + <- nid=14 [audio mixer] pcm0: | pcm0: + <- nid=15 [audio mixer] pcm0: | pcm0: + <- nid=38 [audio mixer] pcm0: pcm0: nid: 22 [ANALOG] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x0040018f pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x00000036 pcm0: TRQD OUT IN : UNSOL pcm0: Pin config: 0x411111f0 pcm0: Pin control: 0x00000060 IN OUT pcm0: Output amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: Input amp: 0x00270300 pcm0: mute=0 step=3 size=39 offset=0 pcm0: connections: 5 pcm0: | pcm0: + <- nid=12 [audio mixer] pcm0: | pcm0: + <- nid=13 [audio mixer] pcm0: | pcm0: + <- nid=14 [audio mixer] pcm0: | pcm0: + <- nid=15 [audio mixer] pcm0: | pcm0: + <- nid=38 [audio mixer] pcm0: pcm0: nid: 23 [ANALOG] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x0040018f pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x00000036 pcm0: TRQD OUT IN : UNSOL pcm0: Pin config: 0x411111f0 pcm0: Pin control: 0x00000060 IN OUT pcm0: Output amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: Input amp: 0x00270300 pcm0: mute=0 step=3 size=39 offset=0 pcm0: connections: 5 pcm0: | pcm0: + <- nid=12 [audio mixer] pcm0: | pcm0: + <- nid=13 [audio mixer] pcm0: | pcm0: + <- nid=14 [audio mixer] pcm0: | pcm0: + <- nid=15 [audio mixer] pcm0: | pcm0: + <- nid=38 [audio mixer] pcm0: pcm0: nid: 24 [ANALOG] pcm0: name: pin: Mic in (jack) pcm0: widget_cap: 0x0040018f pcm0: Parse flags: 0x00000002 pcm0: Ctl flags: 0x00000081 pcm0: Pin cap: 0x0000373e pcm0: TRQD HP OUT IN VREF[ 50 80 100 GROUND HIZ ] : UNSOL pcm0: Pin config: 0x01a19820 pcm0: Pin control: 0x00000025 IN pcm0: Output amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: Input amp: 0x00270300 pcm0: mute=0 step=3 size=39 offset=0 pcm0: connections: 5 pcm0: | pcm0: + <- nid=12 [audio mixer] (selected) pcm0: | pcm0: + <- nid=13 [audio mixer] pcm0: | pcm0: + <- nid=14 [audio mixer] pcm0: | pcm0: + <- nid=15 [audio mixer] pcm0: | pcm0: + <- nid=38 [audio mixer] pcm0: pcm0: nid: 25 [ANALOG] pcm0: name: pin: Mic in (fixed) pcm0: widget_cap: 0x0040018f pcm0: Parse flags: 0x00000002 pcm0: Ctl flags: 0x00000081 pcm0: Pin cap: 0x0000373e pcm0: TRQD HP OUT IN VREF[ 50 80 100 GROUND HIZ ] : UNSOL pcm0: Pin config: 0x99a3092f pcm0: Pin control: 0x00000025 IN pcm0: Output amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: Input amp: 0x00270300 pcm0: mute=0 step=3 size=39 offset=0 pcm0: connections: 5 pcm0: | pcm0: + <- nid=12 [audio mixer] (selected) pcm0: | pcm0: + <- nid=13 [audio mixer] pcm0: | pcm0: + <- nid=14 [audio mixer] pcm0: | pcm0: + <- nid=15 [audio mixer] pcm0: | pcm0: + <- nid=38 [audio mixer] pcm0: pcm0: nid: 26 [ANALOG] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x0040018f pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x0000373e pcm0: TRQD HP OUT IN VREF[ 50 80 100 GROUND HIZ ] : UNSOL pcm0: Pin config: 0x411111f0 pcm0: Pin control: 0x000000e0 HP IN OUT pcm0: Output amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: Input amp: 0x00270300 pcm0: mute=0 step=3 size=39 offset=0 pcm0: connections: 5 pcm0: | pcm0: + <- nid=12 [audio mixer] pcm0: | pcm0: + <- nid=13 [audio mixer] pcm0: | pcm0: + <- nid=14 [audio mixer] pcm0: | pcm0: + <- nid=15 [audio mixer] pcm0: | pcm0: + <- nid=38 [audio mixer] pcm0: pcm0: nid: 27 [ANALOG] pcm0: name: pin: speaker (fixed) pcm0: widget_cap: 0x0040018f pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x0000373e pcm0: TRQD HP OUT IN VREF[ 50 80 100 GROUND HIZ ] : UNSOL pcm0: Pin config: 0x99130110 pcm0: Pin control: 0x00000040 OUT pcm0: Output amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: Input amp: 0x00270300 pcm0: mute=0 step=3 size=39 offset=0 pcm0: connections: 5 pcm0: | pcm0: + <- nid=12 [audio mixer] (selected) pcm0: | pcm0: + <- nid=13 [audio mixer] pcm0: | pcm0: + <- nid=14 [audio mixer] pcm0: | pcm0: + <- nid=15 [audio mixer] pcm0: | pcm0: + <- nid=38 [audio mixer] pcm0: pcm0: nid: 28 [ANALOG] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x00400001 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x00000020 pcm0: IN pcm0: Pin config: 0x411111f0 pcm0: Pin control: 0x00000020 IN pcm0: connections: 0 pcm0: pcm0: nid: 29 [ANALOG] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x00400000 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x00000020 pcm0: IN pcm0: Pin config: 0x4015920d pcm0: Pin control: 0x00000020 IN pcm0: connections: 0 pcm0: pcm0: nid: 30 [DIGITAL] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x00400300 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x00000010 pcm0: OUT pcm0: Pin config: 0x411111f0 pcm0: Pin control: 0x00000040 OUT pcm0: connections: 1 pcm0: | pcm0: + <- nid=6 [audio output] [DISABLED] pcm0: pcm0: nid: 31 [DIGITAL] [DISABLED] pcm0: name: pin: speaker (none) pcm0: widget_cap: 0x00400200 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: Pin cap: 0x00000020 pcm0: IN pcm0: Pin config: 0x411111f0 pcm0: Pin control: 0x00000020 IN pcm0: connections: 0 pcm0: pcm0: nid: 32 [ANALOG] pcm0: name: vendor widget pcm0: widget_cap: 0x00f00040 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: connections: 0 pcm0: pcm0: nid: 33 [ANALOG] pcm0: name: vendor widget pcm0: widget_cap: 0x00f00000 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: connections: 0 pcm0: pcm0: nid: 34 [ANALOG] pcm0: name: audio mixer pcm0: widget_cap: 0x0020010b pcm0: Parse flags: 0x00000006 pcm0: Ctl flags: 0x00000000 pcm0: Input amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: connections: 11 pcm0: | pcm0: + <- nid=24 [pin: Mic in (jack)] pcm0: | pcm0: + <- nid=25 [pin: Mic in (fixed)] pcm0: | pcm0: + <- nid=26 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=27 [pin: speaker (fixed)] pcm0: | pcm0: + <- nid=28 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=29 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=20 [pin: headphones out (jack)] pcm0: | pcm0: + <- nid=21 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=22 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=23 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=11 [audio mixer] pcm0: pcm0: nid: 35 [ANALOG] pcm0: name: audio mixer pcm0: widget_cap: 0x0020010b pcm0: Parse flags: 0x00000006 pcm0: Ctl flags: 0x00000000 pcm0: Input amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: connections: 11 pcm0: | pcm0: + <- nid=24 [pin: Mic in (jack)] pcm0: | pcm0: + <- nid=25 [pin: Mic in (fixed)] pcm0: | pcm0: + <- nid=26 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=27 [pin: speaker (fixed)] pcm0: | pcm0: + <- nid=28 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=29 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=20 [pin: headphones out (jack)] pcm0: | pcm0: + <- nid=21 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=22 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=23 [pin: speaker (none)] [DISABLED] pcm0: | pcm0: + <- nid=11 [audio mixer] pcm0: pcm0: nid: 36 [ANALOG] pcm0: name: vendor widget pcm0: widget_cap: 0x00f00000 pcm0: Parse flags: 0x00000000 pcm0: Ctl flags: 0x00000000 pcm0: connections: 0 pcm0: pcm0: nid: 37 [ANALOG] pcm0: name: audio output pcm0: widget_cap: 0x00000011 pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x000e0560 pcm0: PCM size: 16 20 24 pcm0: PCM rate: 44 48 96 192 pcm0: connections: 0 pcm0: pcm0: nid: 38 [ANALOG] pcm0: name: audio mixer pcm0: widget_cap: 0x0020010f pcm0: Parse flags: 0x00000001 pcm0: Ctl flags: 0x00000011 pcm0: Output amp: 0x00051f1f pcm0: mute=0 step=31 size=5 offset=31 pcm0: Input amp: 0x80000000 pcm0: mute=1 step=0 size=0 offset=0 pcm0: connections: 2 pcm0: | pcm0: + <- nid=37 [audio output] pcm0: | pcm0: + <- nid=11 [audio mixer] pcm0: pcm0: +------------------------+ pcm0: | DUMPING HDA AMPLIFIERS | pcm0: +------------------------+ pcm0: pcm0: 1: nid=8 dir=0x2 index=0 ossmask=0x00000800 ossdev=0 pcm0: 2: nid=9 dir=0x2 index=0 ossmask=0x00000800 ossdev=0 pcm0: 3: nid=11 cnid=24 dir=0x2 index=0 ossmask=0x00000081 ossdev=7 pcm0: 4: nid=11 cnid=25 dir=0x2 index=1 ossmask=0x00000081 ossdev=7 pcm0: 5: nid=11 cnid=26 dir=0x2 index=2 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 6: nid=11 cnid=27 dir=0x2 index=3 ossmask=0x00000000 ossdev=0 pcm0: 7: nid=11 cnid=28 dir=0x2 index=4 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 8: nid=11 cnid=29 dir=0x2 index=5 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 9: nid=11 cnid=20 dir=0x2 index=6 ossmask=0x00000000 ossdev=0 pcm0: 10: nid=11 cnid=21 dir=0x2 index=7 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 11: nid=11 cnid=22 dir=0x2 index=8 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 12: nid=11 cnid=23 dir=0x2 index=9 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 13: nid=12 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 14: nid=12 cnid=2 dir=0x2 index=0 ossmask=0x00000011 ossdev=4 pcm0: 15: nid=12 cnid=11 dir=0x2 index=1 ossmask=0x00000000 ossdev=0 pcm0: 16: nid=13 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 17: nid=13 cnid=3 dir=0x2 index=0 ossmask=0x00000011 ossdev=4 pcm0: 18: nid=13 cnid=11 dir=0x2 index=1 ossmask=0x00000000 ossdev=0 pcm0: 19: nid=14 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 20: nid=14 cnid=4 dir=0x2 index=0 ossmask=0x00000011 ossdev=4 pcm0: 21: nid=14 cnid=11 dir=0x2 index=1 ossmask=0x00000000 ossdev=0 pcm0: 22: nid=15 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 23: nid=15 cnid=5 dir=0x2 index=0 ossmask=0x00000011 ossdev=4 pcm0: 24: nid=15 cnid=11 dir=0x2 index=1 ossmask=0x00000000 ossdev=0 pcm0: 25: nid=20 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 26: nid=20 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 pcm0: 27: nid=21 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 28: nid=21 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 29: nid=22 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 30: nid=22 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 31: nid=23 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 32: nid=23 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 33: nid=24 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 34: nid=24 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 pcm0: 35: nid=25 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 36: nid=25 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 pcm0: 37: nid=26 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 38: nid=26 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 39: nid=27 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 40: nid=27 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 pcm0: 41: nid=34 cnid=24 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 pcm0: 42: nid=34 cnid=25 dir=0x2 index=1 ossmask=0x00000000 ossdev=0 pcm0: 43: nid=34 cnid=26 dir=0x2 index=2 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 44: nid=34 cnid=27 dir=0x2 index=3 ossmask=0x00000000 ossdev=0 pcm0: 45: nid=34 cnid=28 dir=0x2 index=4 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 46: nid=34 cnid=29 dir=0x2 index=5 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 47: nid=34 cnid=20 dir=0x2 index=6 ossmask=0x00000000 ossdev=0 pcm0: 48: nid=34 cnid=21 dir=0x2 index=7 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 49: nid=34 cnid=22 dir=0x2 index=8 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 50: nid=34 cnid=23 dir=0x2 index=9 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 51: nid=34 cnid=11 dir=0x2 index=10 ossmask=0x00000000 ossdev=0 pcm0: 52: nid=35 cnid=24 dir=0x2 index=0 ossmask=0x00000000 ossdev=0 pcm0: 53: nid=35 cnid=25 dir=0x2 index=1 ossmask=0x00000000 ossdev=0 pcm0: 54: nid=35 cnid=26 dir=0x2 index=2 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 55: nid=35 cnid=27 dir=0x2 index=3 ossmask=0x00000000 ossdev=0 pcm0: 56: nid=35 cnid=28 dir=0x2 index=4 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 57: nid=35 cnid=29 dir=0x2 index=5 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 58: nid=35 cnid=20 dir=0x2 index=6 ossmask=0x00000000 ossdev=0 pcm0: 59: nid=35 cnid=21 dir=0x2 index=7 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 60: nid=35 cnid=22 dir=0x2 index=8 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 61: nid=35 cnid=23 dir=0x2 index=9 ossmask=0x00000000 ossdev=0 [DISABLED] pcm0: 62: nid=35 cnid=11 dir=0x2 index=10 ossmask=0x00000000 ossdev=0 pcm0: 63: nid=38 dir=0x1 index=0 ossmask=0x00000000 ossdev=0 pcm0: 64: nid=38 cnid=37 dir=0x2 index=0 ossmask=0x00000011 ossdev=4 pcm0: 65: nid=38 cnid=11 dir=0x2 index=1 ossmask=0x00000000 ossdev=0 pcm0: pcm0: +-----------------------------------+ pcm0: | DUMPING HDA AUDIO/VOLUME CONTROLS | pcm0: +-----------------------------------+ pcm0: pcm0: Master Volume (OSS: vol) pcm0: | pcm0: +- nid: 11 index: 0 (nid: 24) mute: 1 step: 31 size: 5 off: 23 dir=0x2 ossmask=0x00000081 pcm0: | pcm0: +- nid: 11 index: 1 (nid: 25) mute: 1 step: 31 size: 5 off: 23 dir=0x2 ossmask=0x00000081 pcm0: | pcm0: +- nid: 12 index: 0 (nid: 2) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: | pcm0: +- nid: 13 index: 0 (nid: 3) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: | pcm0: +- nid: 14 index: 0 (nid: 4) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: | pcm0: +- nid: 15 index: 0 (nid: 5) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: | pcm0: +- nid: 38 index: 0 (nid: 37) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: pcm0: PCM Volume (OSS: pcm) pcm0: | pcm0: +- nid: 12 index: 0 (nid: 2) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: | pcm0: +- nid: 13 index: 0 (nid: 3) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: | pcm0: +- nid: 14 index: 0 (nid: 4) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: | pcm0: +- nid: 15 index: 0 (nid: 5) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: | pcm0: +- nid: 38 index: 0 (nid: 37) mute: 1 step: 0 size: 0 off: 0 dir=0x2 ossmask=0x00000011 pcm0: pcm0: Microphone Volume (OSS: mic) pcm0: | pcm0: +- nid: 11 index: 0 (nid: 24) mute: 1 step: 31 size: 5 off: 23 dir=0x2 ossmask=0x00000081 pcm0: | pcm0: +- nid: 11 index: 1 (nid: 25) mute: 1 step: 31 size: 5 off: 23 dir=0x2 ossmask=0x00000081 pcm0: pcm0: Recording Level (OSS: rec) pcm0: | pcm0: +- nid: 8 index: 0 mute: 1 step: 31 size: 5 off: 11 dir=0x2 ossmask=0x00000800 pcm0: | pcm0: +- nid: 9 index: 0 mute: 1 step: 31 size: 5 off: 11 dir=0x2 ossmask=0x00000800 pcm0: pcm0: Playback path: pcm0: pcm0: nid=20 [pin: headphones out (jack)] pcm0: ^ pcm0: | pcm0: +-----<------+ pcm0: ^ pcm0: | pcm0: nid=12 [audio mixer] pcm0: ^ pcm0: | pcm0: nid=2 [audio output] pcm0: pcm0: nid=27 [pin: speaker (fixed)] pcm0: ^ pcm0: | pcm0: +-----<------+ pcm0: ^ pcm0: | pcm0: nid=12 [audio mixer] pcm0: ^ pcm0: | pcm0: nid=2 [audio output] pcm0: pcm0: Recording sources: pcm0: pcm0: nid=34 [audio mixer] pcm0: | pcm0: + <- nid=24 [pin: Mic in (jack)] [recsrc: vol, mic] pcm0: | pcm0: + <- nid=25 [pin: Mic in (fixed)] [recsrc: vol, mic] pcm0: | pcm0: + <- nid=27 [pin: speaker (fixed)] pcm0: | pcm0: + <- nid=20 [pin: headphones out (jack)] pcm0: | pcm0: + <- nid=11 [audio mixer] [recsrc: vol, mic] pcm0: pcm0: nid=35 [audio mixer] pcm0: | pcm0: + <- nid=24 [pin: Mic in (jack)] [recsrc: vol, mic] pcm0: | pcm0: + <- nid=25 [pin: Mic in (fixed)] [recsrc: vol, mic] pcm0: | pcm0: + <- nid=27 [pin: speaker (fixed)] pcm0: | pcm0: + <- nid=20 [pin: headphones out (jack)] pcm0: | pcm0: + <- nid=11 [audio mixer] [recsrc: vol, mic] pcm0: pcm0: +--------------------------------------+ pcm0: | DUMPING PCM Playback/Record Channels | pcm0: +--------------------------------------+ pcm0: pcm0: PCM Playback: 1 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x000e0560 pcm0: PCM size: 16 20 24 pcm0: PCM rate: 44 48 96 192 pcm0: DAC: 2 3 4 5 37 pcm0: pcm0: PCM Record: 1 pcm0: Stream cap: 0x00000001 pcm0: Format: PCM pcm0: PCM cap: 0x00060160 pcm0: PCM size: 16 20 pcm0: PCM rate: 44 48 96 pcm0: ADC: 8 9 GEOM: new disk da0 pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Removable Direct Access SCSI-0 device pass0: 40.000MB/s transfers ATA PseudoRAID loaded SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 4 to local APIC 0 ioapic0: Assigning ISA IRQ 9 to local APIC 0 ioapic0: Assigning ISA IRQ 12 to local APIC 0 ioapic0: Assigning ISA IRQ 14 to local APIC 0 ioapic0: Assigning ISA IRQ 15 to local APIC 0 ioapic0: Assigning PCI IRQ 16 to local APIC 0 ioapic0: Assigning PCI IRQ 18 to local APIC 0 ioapic0: Assigning PCI IRQ 19 to local APIC 0 ioapic0: Assigning PCI IRQ 23 to local APIC 0 (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 Trying to mount root from ufs:/dev/ad0s1a start_init: trying /sbin/init GEOM_ELI: Device ad0s1b.eli created. GEOM_ELI: Encryption: Blowfish-CBC 128 GEOM_ELI: Crypto: software WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted Linux ELF exec handler installed (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 From bugmaster at FreeBSD.org Mon Nov 24 03:07:06 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 24 03:07:13 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200811241107.mAOB75BM019798@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 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 43 problems total. From onemda at gmail.com Mon Nov 24 08:20:07 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Nov 24 08:20:13 2008 Subject: Resume on hp nx7300 Message-ID: <3a142e750811240748o1923fdc4xca1ae55f44bf664d@mail.gmail.com> Hi, I managed somehow to succesfully resume laptop from suspend, setting hw.acpi.osname="Windows 2001" but lcd output is off and can not be turned on. sysctl hw.acpi.reset_video=1 does'nt work, instead to resume, machine remain in unknown state, keyboard input doesnt work. Also if powerd + cpufreq combination is used, some time after resume system will reboot itself: db:0:kdb.enter.unknown> show pcpu cpuid = 0 curthread = 0xc3ff0240: pid 667 "powerd" curpcb = 0xc3a72d90 fpcurthread = none idlethread = 0xc3d2fd80: pid 10 "idle: cpu0" APIC ID = 0 currentldt = 0x50 spin locks held: db:0:kdb.enter.unknown> bt Tracing pid 667 tid 100036 td 0xc3ff0240 mtrash_ctor(c3e21000,400,0,1,0,...) at mtrash_ctor+0x60 uma_zalloc_arg(c108ba20,0,1,0,c3e2c400,...) at uma_zalloc_arg+0x137 malloc(36c,c06d1bc0,1,210,c049b0c3,...) at malloc+0xcb cf_levels_method(c3e0ae80,c446f000,c3a72b4c,c3a72ba8,c446f3b4,...) at cf_levels_method+0x23d cpufreq_curr_sysctl(c3e414c0,c3e4f000,0,c3a72ba8,c3a72ba8,4,4,c3e414c0) at cpufreq_curr_sysctl+0x169 sysctl_root(c3a72ba8,0,c069a48a,587,c3ff0240,...) at sysctl_root+0x138 userland_sysctl(c3ff0240,c3a72c14,4,0,0,...) at userland_sysctl+0x115 __sysctl(c3ff0240,c3a72cf8,18,c06a0480,c06ce1b0,...) at __sysctl+0xb7 syscall(c3a72d38) at syscall+0x261 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x28172533, esp = 0xbfbfe84c, ebp = 0xbfbfe878 --- acpi_ec0: wait timed out (response), forcing polled mode <5>wakeup from sleeping state (slept 00:00:14) acpi_tz0: _CRT value is absurd, ignored (256.0C) agp0: on vgapci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M Memory modified after free 0xc3e21000(1020) val=0 @ 0xc3e21000 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xffff0020 fault code = supervisor read, page not present instruction pointer = 0x20:0xc062c350 stack pointer = 0x28:0xc3a72a04 frame pointer = 0x28:0xc3a72a24 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 667 (powerd) exclusive sx cpufreq lock (cpufreq lock) r = 0 (0xc3e4f000) locked @ /usr/src/sys/kern/kern_cpu.c:528 exclusive sx sysctl lock (sysctl lock) r = 0 (0xc070f404) locked @ /usr/src/sys/kern/kern_sysctl.c:1415 exclusive sleep mutex Giant (Giant) r = 0 (0xc070edf0) locked @ /usr/src/sys/kern/kern_sysctl.c:1353 exclusive sx cpufreq lock (cpufreq lock) r = 0 (0xc3e4f000) locked @ /usr/src/sys/kern/kern_cpu.c:528 exclusive sx sysctl lock (sysctl lock) r = 0 (0xc070f404) locked @ /usr/src/sys/kern/kern_sysctl.c:1415 exclusive sleep mutex Giant (Giant) r = 0 (0xc070edf0) locked @ /usr/src/sys/kern/kern_sysctl.c:1353 Do I need to build/install UP kernel, or I can use SMP one with smp disabled via loader.conf? -- Paul From onemda at gmail.com Mon Nov 24 16:58:12 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Nov 24 16:58:18 2008 Subject: Resume on hp nx7300 In-Reply-To: <3a142e750811240748o1923fdc4xca1ae55f44bf664d@mail.gmail.com> References: <3a142e750811240748o1923fdc4xca1ae55f44bf664d@mail.gmail.com> Message-ID: <3a142e750811241658i39097018x3c6f49aa62805fa7@mail.gmail.com> On 11/24/08, Paul B. Mahol wrote: > Hi, > > I managed somehow to succesfully resume laptop from suspend, > setting hw.acpi.osname="Windows 2001" It appears that it's not required at all. > but lcd output is off and can not be turned on. It will work if vesa is kldloaded _before_ suspend. Also kldload i915 (agp+drm+i915) _before_ suspend will do it. > sysctl hw.acpi.reset_video=1 does'nt work, instead to resume, machine > remain in unknown state, keyboard input doesnt work. > > Also if powerd + cpufreq combination is used, some time after resume > system will reboot itself: > > db:0:kdb.enter.unknown> show pcpu > cpuid = 0 > curthread = 0xc3ff0240: pid 667 "powerd" > curpcb = 0xc3a72d90 > fpcurthread = none > idlethread = 0xc3d2fd80: pid 10 "idle: cpu0" > APIC ID = 0 > currentldt = 0x50 > spin locks held: > db:0:kdb.enter.unknown> bt > Tracing pid 667 tid 100036 td 0xc3ff0240 > mtrash_ctor(c3e21000,400,0,1,0,...) at mtrash_ctor+0x60 > uma_zalloc_arg(c108ba20,0,1,0,c3e2c400,...) at uma_zalloc_arg+0x137 > malloc(36c,c06d1bc0,1,210,c049b0c3,...) at malloc+0xcb > cf_levels_method(c3e0ae80,c446f000,c3a72b4c,c3a72ba8,c446f3b4,...) at > cf_levels_method+0x23d > cpufreq_curr_sysctl(c3e414c0,c3e4f000,0,c3a72ba8,c3a72ba8,4,4,c3e414c0) > at cpufreq_curr_sysctl+0x169 > sysctl_root(c3a72ba8,0,c069a48a,587,c3ff0240,...) at sysctl_root+0x138 > userland_sysctl(c3ff0240,c3a72c14,4,0,0,...) at userland_sysctl+0x115 > __sysctl(c3ff0240,c3a72cf8,18,c06a0480,c06ce1b0,...) at __sysctl+0xb7 > syscall(c3a72d38) at syscall+0x261 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x28172533, esp = > 0xbfbfe84c, ebp = 0xbfbfe878 --- > > > acpi_ec0: wait timed out (response), forcing polled mode > <5>wakeup from sleeping state (slept 00:00:14) > acpi_tz0: _CRT value is absurd, ignored (256.0C) > agp0: on vgapci0 > agp0: detected 7932k stolen memory > agp0: aperture size is 256M > Memory modified after free 0xc3e21000(1020) val=0 @ 0xc3e21000 > powerd + cpufreq combination just works, above panic probably happened because agp is loaded _after_ resume. > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xffff0020 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc062c350 > stack pointer = 0x28:0xc3a72a04 > frame pointer = 0x28:0xc3a72a24 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 667 (powerd) > exclusive sx cpufreq lock (cpufreq lock) r = 0 (0xc3e4f000) locked @ > /usr/src/sys/kern/kern_cpu.c:528 > exclusive sx sysctl lock (sysctl lock) r = 0 (0xc070f404) locked @ > /usr/src/sys/kern/kern_sysctl.c:1415 > exclusive sleep mutex Giant (Giant) r = 0 (0xc070edf0) locked @ > /usr/src/sys/kern/kern_sysctl.c:1353 > exclusive sx cpufreq lock (cpufreq lock) r = 0 (0xc3e4f000) locked @ > /usr/src/sys/kern/kern_cpu.c:528 > exclusive sx sysctl lock (sysctl lock) r = 0 (0xc070f404) locked @ > /usr/src/sys/kern/kern_sysctl.c:1415 > exclusive sleep mutex Giant (Giant) r = 0 (0xc070edf0) locked @ > /usr/src/sys/kern/kern_sysctl.c:1353 > > > Do I need to build/install UP kernel, or I can use SMP one with smp > disabled via loader.conf? kern.smp.disabled="1" just works, and disabling dual core from bios is not required. Restarting moused after resume is must. pccard and ndis powered broadcom card do not work after resume, even if right driver was never loaded during/after boot - before suspend. Main problem is that shutdown button (S5) doesnt work after resume. Is there any know reason why that could happen? -- Paul From brinzer at mfrac.com Tue Nov 25 10:31:08 2008 From: brinzer at mfrac.com (Bill Brinzer) Date: Tue Nov 25 10:31:15 2008 Subject: Dell PowerEdge 840 ACPI panic early in boot Message-ID: <20081125181512.GA89700@fire.mfrac.vpn> Booting FreeBSD on my brand new Dell PowerEdge 840 causes a panic very early in the boot sequence. Disabling ACPI allows the boot to proceed normally. Here's what I've tried so far. Boot 7.0-RELEASE i386 via PXE -> early boot panic. Boot 7.0-PRERELEASE amd64 via PXE -> early boot panic. Boot 6.1 i386 via CD (GENERIC kernel) -> early boot panic. I set acpi.hw.osname (on 7.0-RELEASE i386) to "Windows 2001," "Windows 2006," "Windows 2006.1," "Linux," "Microsoft Windows NT" (all in the ASL, suspiciously enough) -> same panic. Here's a verbose boot log with the panic: /boot/kernel/acpi.ko text=0x521cc data=0x23a0+0x186c syms=[0x4+0x85d0+0x4+0xb062] KDB: debugger backends: ddb KDB: current backend: ddb SMAP type=01 base=0000000000000000 len=00000000000a0000 SMAP type=01 base=0000000000100000 len=000000007fec0000 SMAP type=03 base=000000007ffc0000 len=000000000000fc00 SMAP type=02 base=000000007ffcfc00 len=0000000000000400 SMAP type=02 base=000000007ffd0000 len=0000000000020000 SMAP type=02 base=000000007fff0000 len=000000000000f000 SMAP type=02 base=00000000f0000000 len=0000000004000000 SMAP type=02 base=00000000fec00000 len=0000000000100000 SMAP type=02 base=00000000fed00000 len=0000000000000400 SMAP type=02 base=00000000fed13000 len=000000000008d000 SMAP type=02 base=00000000fee00000 len=0000000000010000 SMAP type=02 base=00000000ffb00000 len=0000000000500000 Copyright (c) 1992-2008 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.0-RELEASE-p5 #2: Fri Nov 21 17:58:47 EST 2008 root@water.mfrac.vpn:/export/FreeBSD/7.x/obj/export/FreeBSD/7.x/src/sys/SMITHWICKS Preloaded elf kernel "/boot/kernel/kernel" at 0xc0e44000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0e441c4. Calibrating clock(s) ... i8254 clock: 1193165 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2000083510 Hz CPU: Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz (2000.08-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fd Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Instruction TLB: 4 KB Pages, 4-way set associative, 128 entries 2nd-level cache: 1 MB, 4-way set associative, 64-byte line size 1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 1024 kbytes, 4-way associative, 64 bytes/line real memory = 2147221504 (2047 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001028000 - 0x000000007db70fff, 2092208128 bytes (510793 pages) avail memory = 2091761664 (1994 MB) Table 'FACP' at 0xf9ff4 panic: vm_fault: fault on nofault entry, addr: c1423000 cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper(c0b7d055,c1020aa0,c07abbdf,c0ba132b,0,...) at 0xc04d49a6 = db_trace_self_wrapper+0x26 kdb_backtrace(c0ba132b,0,c0b974be,c1020aac,0,...) at 0xc07d2c89 = kdb_backtrace+0x29 panic(c0b974be,c1423000,1,c1020bb0,c1020ba0,...) at 0xc07abbdf = panic+0x10f vm_fault(c1471000,c1423000,1,0,0,...) at 0xc09fecd8 = vm_fault+0x178 trap_pfault(10,12,1000000,7476,c0c8b360,...) at 0xc0ae1a7e = trap_pfault+0x20e trap(c1020cf0) at 0xc0ae24da = trap+0x3fa calltrap() at 0xc0ac7b3b = calltrap+0x6 --- trap 0xc, eip = 0xc0e1f1ce, esp = 0xc1020d30, ebp = 0xc1020d50 --- madt_probe(c0ba06ab,0,0,c50e1748,fffffff,...) at 0xc0e1f1ce = madt_probe+0x10e apic_init(0,101ec00,101ec00,101e000,1028000,...) at 0xc0acfac3 = apic_init+0x53 mi_startup() at 0xc0771fc6 = mi_startup+0x96 begin() at 0xc0461a05 = begin+0x2c KDB: enter: panic [thread pid 0 tid 0 ] Stopped at 0xc07d2bd2 = kdb_enter+0x32: leave db> (gdb) l *madt_probe+0x10e 0x471ce is in madt_probe (/export/FreeBSD/7.x/src/sys/modules/acpi/acpi/../../../i386/acpica/madt.c:245). 240 return (ENXIO); 241 } 242 count = (xsdt->Header.Length - sizeof(ACPI_TABLE_HEADER)) / 243 sizeof(UINT64); 244 for (i = 0; i < count; i++) 245 if (madt_probe_table(xsdt->TableOffsetEntry[i])) 246 break; 247 madt_unmap_table(xsdt); 248 } else { 249 rsdt = madt_map_table(rsdp->RsdtPhysicalAddress, 1, I posted the dmesg(8) from boot -v with ACPI disabled at: And the ASL is here: Thanks in advance; let me know if I need to try anything else. Bill Brinzer From takawata at init-main.com Tue Nov 25 10:33:18 2008 From: takawata at init-main.com (Takanori Watanabe) Date: Tue Nov 25 10:33:25 2008 Subject: acpi_cpu: binding processor object to pcpu struct. Message-ID: <200811251835.mAPIZFIC002676@sana.init-main.com> In my box, processor does not binded properly to ACPI object, so I wrote the code as follows. comment? I'm afraid system pcpu unit number and cpu device instance number may inconsistent, but without this change, ACPI namespace and pcpu struct does not match. Index: acpi_cpu.c =================================================================== --- acpi_cpu.c (リビジョン 185289) +++ acpi_cpu.c (作業コピー) @@ -241,7 +241,9 @@ * in their Processor object as the ProcId values in the MADT. */ acpi_id = obj->Processor.ProcId; + AcpiOsFree(obj); + if (acpi_pcpu_get_id(device_get_unit(dev), &acpi_id, &cpu_id) != 0) return (ENXIO); @@ -427,25 +429,35 @@ KASSERT(acpi_id != NULL, ("Null acpi_id")); KASSERT(cpu_id != NULL, ("Null cpu_id")); + + /*Check for cpu that have duplicate acpi_id probed.*/ + for ( i = 0 ; i <= mp_maxid; i++){ + if (CPU_ABSENT(i)) + continue; + pcpu_data = pcpu_find(i); + if(cpu_softc[i]&& (pcpu_data->pc_acpi_id == *acpi_id)){ + return ESRCH; + } + } for (i = 0; i <= mp_maxid; i++) { if (CPU_ABSENT(i)) continue; pcpu_data = pcpu_find(i); KASSERT(pcpu_data != NULL, ("no pcpu data for %d", i)); - if (idx-- == 0) { - /* - * If pc_acpi_id was not initialized (e.g., a non-APIC UP box) - * override it with the value from the ASL. Otherwise, if the - * two don't match, prefer the MADT-derived value. Finally, - * return the pc_cpuid to reference this processor. - */ - if (pcpu_data->pc_acpi_id == 0xffffffff) + /* + * If pc_acpi_id was not initialized (e.g., a non-APIC UP box) + * override it with the value from the ASL. Otherwise, if the + * two don't match, prefer the MADT-derived value. Finally, + * return the pc_cpuid to reference this processor. + */ + if (pcpu_data->pc_acpi_id == 0xffffffff) pcpu_data->pc_acpi_id = *acpi_id; - else if (pcpu_data->pc_acpi_id != *acpi_id) - *acpi_id = pcpu_data->pc_acpi_id; - *cpu_id = pcpu_data->pc_cpuid; - return (0); + else if (pcpu_data->pc_acpi_id == *acpi_id){ + *cpu_id = pcpu_data->pc_cpuid; } + else + continue; + return 0; } return (ESRCH); From nate at root.org Tue Nov 25 10:40:07 2008 From: nate at root.org (Nate Lawson) Date: Tue Nov 25 10:40:13 2008 Subject: Dell PowerEdge 840 ACPI panic early in boot In-Reply-To: <20081125181512.GA89700@fire.mfrac.vpn> References: <20081125181512.GA89700@fire.mfrac.vpn> Message-ID: <492C4685.1030405@root.org> Bill Brinzer wrote: > Booting FreeBSD on my brand new Dell PowerEdge 840 causes a panic > very early in the boot sequence. Disabling ACPI allows the boot to > proceed normally. > avail memory = 2091761664 (1994 MB) > Table 'FACP' at 0xf9ff4 > panic: vm_fault: fault on nofault entry, addr: c1423000 > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper(c0b7d055,c1020aa0,c07abbdf,c0ba132b,0,...) at 0xc04d49a6 = db_trace_self_wrapper+0x26 > kdb_backtrace(c0ba132b,0,c0b974be,c1020aac,0,...) at 0xc07d2c89 = kdb_backtrace+0x29 > panic(c0b974be,c1423000,1,c1020bb0,c1020ba0,...) at 0xc07abbdf = panic+0x10f > vm_fault(c1471000,c1423000,1,0,0,...) at 0xc09fecd8 = vm_fault+0x178 > trap_pfault(10,12,1000000,7476,c0c8b360,...) at 0xc0ae1a7e = trap_pfault+0x20e > trap(c1020cf0) at 0xc0ae24da = trap+0x3fa > calltrap() at 0xc0ac7b3b = calltrap+0x6 > --- trap 0xc, eip = 0xc0e1f1ce, esp = 0xc1020d30, ebp = 0xc1020d50 --- > madt_probe(c0ba06ab,0,0,c50e1748,fffffff,...) at 0xc0e1f1ce = madt_probe+0x10e > apic_init(0,101ec00,101ec00,101e000,1028000,...) at 0xc0acfac3 = apic_init+0x53 > mi_startup() at 0xc0771fc6 = mi_startup+0x96 > begin() at 0xc0461a05 = begin+0x2c > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at 0xc07d2bd2 = kdb_enter+0x32: leave > db> > > (gdb) l *madt_probe+0x10e > 0x471ce is in madt_probe (/export/FreeBSD/7.x/src/sys/modules/acpi/acpi/../../../i386/acpica/madt.c:245). > 240 return (ENXIO); > 241 } > 242 count = (xsdt->Header.Length - sizeof(ACPI_TABLE_HEADER)) / > 243 sizeof(UINT64); > 244 for (i = 0; i < count; i++) > 245 if (madt_probe_table(xsdt->TableOffsetEntry[i])) > 246 break; > 247 madt_unmap_table(xsdt); > 248 } else { > 249 rsdt = madt_map_table(rsdp->RsdtPhysicalAddress, 1, > > I posted the dmesg(8) from boot -v with ACPI disabled at: > > > And the ASL is here: > > > Thanks in advance; let me know if I need to try anything else. The output of acpidump -t would help. That gives the fixed tables in addition to ASL. Perhaps the MADT is corrupt. Have you checked your vendor for a BIOS update? -- Nate From onemda at gmail.com Tue Nov 25 11:37:51 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Tue Nov 25 11:37:57 2008 Subject: Resume on hp nx7300 In-Reply-To: <3a142e750811241658i39097018x3c6f49aa62805fa7@mail.gmail.com> References: <3a142e750811240748o1923fdc4xca1ae55f44bf664d@mail.gmail.com> <3a142e750811241658i39097018x3c6f49aa62805fa7@mail.gmail.com> Message-ID: <3a142e750811251137se5091f8vc1ca13e5469413c3@mail.gmail.com> On 11/25/08, Paul B. Mahol wrote: > On 11/24/08, Paul B. Mahol wrote: >> Hi, >> >> I managed somehow to succesfully resume laptop from suspend, >> setting hw.acpi.osname="Windows 2001" > It appears that it's not required at all. > >> but lcd output is off and can not be turned on. > > It will work if vesa is kldloaded _before_ suspend. > Also kldload i915 (agp+drm+i915) _before_ suspend will do it. > >> sysctl hw.acpi.reset_video=1 does'nt work, instead to resume, machine >> remain in unknown state, keyboard input doesnt work. >> >> Also if powerd + cpufreq combination is used, some time after resume >> system will reboot itself: >> >> db:0:kdb.enter.unknown> show pcpu >> cpuid = 0 >> curthread = 0xc3ff0240: pid 667 "powerd" >> curpcb = 0xc3a72d90 >> fpcurthread = none >> idlethread = 0xc3d2fd80: pid 10 "idle: cpu0" >> APIC ID = 0 >> currentldt = 0x50 >> spin locks held: >> db:0:kdb.enter.unknown> bt >> Tracing pid 667 tid 100036 td 0xc3ff0240 >> mtrash_ctor(c3e21000,400,0,1,0,...) at mtrash_ctor+0x60 >> uma_zalloc_arg(c108ba20,0,1,0,c3e2c400,...) at uma_zalloc_arg+0x137 >> malloc(36c,c06d1bc0,1,210,c049b0c3,...) at malloc+0xcb >> cf_levels_method(c3e0ae80,c446f000,c3a72b4c,c3a72ba8,c446f3b4,...) at >> cf_levels_method+0x23d >> cpufreq_curr_sysctl(c3e414c0,c3e4f000,0,c3a72ba8,c3a72ba8,4,4,c3e414c0) >> at cpufreq_curr_sysctl+0x169 >> sysctl_root(c3a72ba8,0,c069a48a,587,c3ff0240,...) at sysctl_root+0x138 >> userland_sysctl(c3ff0240,c3a72c14,4,0,0,...) at userland_sysctl+0x115 >> __sysctl(c3ff0240,c3a72cf8,18,c06a0480,c06ce1b0,...) at __sysctl+0xb7 >> syscall(c3a72d38) at syscall+0x261 >> Xint0x80_syscall() at Xint0x80_syscall+0x20 >> --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x28172533, esp = >> 0xbfbfe84c, ebp = 0xbfbfe878 --- >> >> >> acpi_ec0: wait timed out (response), forcing polled mode >> <5>wakeup from sleeping state (slept 00:00:14) >> acpi_tz0: _CRT value is absurd, ignored (256.0C) >> agp0: on vgapci0 >> agp0: detected 7932k stolen memory >> agp0: aperture size is 256M >> Memory modified after free 0xc3e21000(1020) val=0 @ 0xc3e21000 >> > > powerd + cpufreq combination just works, above panic > probably happened because agp is loaded _after_ resume. > >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 0; apic id = 00 >> fault virtual address = 0xffff0020 >> fault code = supervisor read, page not present >> instruction pointer = 0x20:0xc062c350 >> stack pointer = 0x28:0xc3a72a04 >> frame pointer = 0x28:0xc3a72a24 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 667 (powerd) >> exclusive sx cpufreq lock (cpufreq lock) r = 0 (0xc3e4f000) locked @ >> /usr/src/sys/kern/kern_cpu.c:528 >> exclusive sx sysctl lock (sysctl lock) r = 0 (0xc070f404) locked @ >> /usr/src/sys/kern/kern_sysctl.c:1415 >> exclusive sleep mutex Giant (Giant) r = 0 (0xc070edf0) locked @ >> /usr/src/sys/kern/kern_sysctl.c:1353 >> exclusive sx cpufreq lock (cpufreq lock) r = 0 (0xc3e4f000) locked @ >> /usr/src/sys/kern/kern_cpu.c:528 >> exclusive sx sysctl lock (sysctl lock) r = 0 (0xc070f404) locked @ >> /usr/src/sys/kern/kern_sysctl.c:1415 >> exclusive sleep mutex Giant (Giant) r = 0 (0xc070edf0) locked @ >> /usr/src/sys/kern/kern_sysctl.c:1353 >> >> >> Do I need to build/install UP kernel, or I can use SMP one with smp >> disabled via loader.conf? > > kern.smp.disabled="1" just works, and disabling dual core from bios is > not required. > > Restarting moused after resume is must. > pccard and ndis powered broadcom card do not work after resume, > even if right driver was never loaded during/after boot - before suspend. > > Main problem is that shutdown button (S5) doesnt work after resume. > Is there any know reason why that could happen? Problem with cardbus controller appears to be that it never got into D3 state, because its hdr=0x02 I encountered also that setting hw.pci.do_power_nodriver=2 in /boot/loader.conf have same nasty effect when using it with suspend/resume. After resume all devices will be put back into D0 state, but if you kldunload one driver, for example snd_hda and kldload it again, all devices that do not have driver attached (and with hdr=0x00) will be put into D3 again. Same scenario happen when unloading driver, device will remain in D0 state until some other driver is loaded/attached to correct device. Current devices power state can be monitored with "pciconf -lvc". I think this is more general problem. -- Paul From matheus at eternamente.info Tue Nov 25 17:48:35 2008 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Tue Nov 25 17:48:42 2008 Subject: RFC: powerd algorithms enhancements In-Reply-To: <20081112142137.Q70117@sola.nimnet.asn.au> References: <491404BF.1090807@FreeBSD.org> <49186111.9020103@root.org> <20081111161549.U70117@sola.nimnet.asn.au> <7d13c992592d1976010179b40b26c057.squirrel@cygnus.homeunix.com> <1226449830.1244.30.camel@RabbitsDen> <20081112142137.Q70117@sola.nimnet.asn.au> Message-ID: <7781fee0f8d1ea36bc8899f48a946fb6.squirrel@10.1.1.10> answering two in a row ... On Wed, November 12, 2008 1:41 am, Ian Smith wrote: > On Tue, 11 Nov 2008, Alexandre "Sunny" Kovalenko wrote: > > On Tue, 2008-11-11 at 15:56 -0200, Nenhum_de_Nos wrote: > > > On Tue, November 11, 2008 3:20 am, Ian Smith wrote: > > > > On Mon, 10 Nov 2008, Nenhum_de_Nos wrote: > > > > > as all you are talking about the subject, and I read all > messages, is > > > > > there any module to load and make my AthlonXP 1700+ use less > power ? > > > > > > > > > > running 7-STABLE, just a file server. any acpi-stuff I could > enable > > > > would > > > > > be great, as I just use all its power when compiling ... > > > > > > > > What does 'sysctl hw.acpi dev.cpu' have to say? > > > > > [...] > > Reinjecting a bit .. > > > hw.acpi.thermal.user_override: 0 > > hw.acpi.thermal.tz0.temperature: 43.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: 66.0C > > hw.acpi.thermal.tz0._HOT: -1 > > hw.acpi.thermal.tz0._CRT: 70.0C > > hw.acpi.thermal.tz0._ACx: 66.0C -1 -1 -1 -1 -1 -1 -1 -1 -1 > > hw.acpi.thermal.tz0._TC1: 4 > > hw.acpi.thermal.tz0._TC2: 3 > > hw.acpi.thermal.tz0._TSP: 60 > > hw.acpi.cpu.cx_lowest: C1 > > Certainly no cpu frequency control. Surprisingly low _CRT temperature > but unless it ever actually gets too hot, it's not a problem. I don't > really follow why .passive-cooling=1 with no cpufreq driver/s attached? I have no idea also ... the cooling is indeed active ... > > > [root@xxx ~]# sysctl dev.cpu > > > dev.cpu.0.%desc: ACPI CPU > > > dev.cpu.0.%driver: cpu > > > dev.cpu.0.%location: handle=\_PR_.CPU0 > > > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > > > dev.cpu.0.%parent: acpi0 > > > dev.cpu.0.cx_supported: C1/0 C2/90 C3/900 > > > dev.cpu.0.cx_lowest: C1 > > > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% > > > [root@xxx ~]# > > > > > > if it rings any bells :) > > All I can suggest here is > > > > sysctl dev.cpu.0.cx_lowest="C3" got the system unresponsive to the point of a hard reset needed ... > > or, if it gets you totally unresponsive machine, > > > > sysctl dev.cpu.0.cx_lowest="C2" not much time in it, I must confess, bit didn't see any lowering in power consumption, will try again ... > > how much of the power saving you will see from this is the > > separate question. > > If that works to any extent you'll notice some drop in cpu temperature. > I do see a slight but noticeable idle temp. drop on my T23 in C2, though > nothing compared to the power reduction of lower frequency (about half). that was all I wanted, but as said that this cpu is older than yours, I really don't think I'll get all that ... > cheers, Ian thanks to all, matheus -- We will call you cygnus, The God of balance you shall be From brinzer at mfrac.com Wed Nov 26 06:27:26 2008 From: brinzer at mfrac.com (Bill Brinzer) Date: Wed Nov 26 06:27:32 2008 Subject: Dell PowerEdge 840 ACPI panic early in boot In-Reply-To: <492C4685.1030405@root.org> References: <20081125181512.GA89700@fire.mfrac.vpn> <492C4685.1030405@root.org> Message-ID: <20081126142723.GA2963@fire.mfrac.vpn> Nate, Thanks for the quick reply. On Tue, Nov 25, 2008 at 01:40:07PM -0500, Nate Lawson wrote: > The output of acpidump -t would help. That gives the fixed > tables in addition to ASL. /* RSD PTR: OEM=DELL, ACPI_Rev=2.0x (2) XSDT=0x000f9f04, length=36, cksum=42 */ /* XSDT: Length=84, Revision=1, Checksum=139, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=INTL, Creator Revision=0x1 Entries={ 0x000f9ff4, 0x000fa0e8, 0x000fa16c, 0x000fa1bc, 0x000fa1f4, 0x000fa230 } */ /* FACP: Length=244, Revision=3, Checksum=90, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=INTL, Creator Revision=0x1 FACS=0x7ffcfc00, DSDT=0x7ffc0000 INT_MODEL=PIC Preferred_PM_Profile=Enterprise Server (4) SCI_INT=9 SMI_CMD=0xb2, ACPI_ENABLE=0x69, ACPI_DISABLE=0x6a, S4BIOS_REQ=0x0 PSTATE_CNT=0x90 PM1a_EVT_BLK=0x800-0x803 PM1a_CNT_BLK=0x804-0x805 PM_TMR_BLK=0x808-0x80b GPE0_BLK=0x828-0x82f CST_CNT=0x90 P_LVL2_LAT=500 us, P_LVL3_LAT=5000 us FLUSH_SIZE=0, FLUSH_STRIDE=0 DUTY_OFFSET=0, DUTY_WIDTH=0 DAY_ALRM=0, MON_ALRM=0, CENTURY=50 IAPC_BOOT_ARCH={LEGACY_DEV,8042} Flags={WBINVD,PROC_C1,SLP_BUTTON,RTC_S4} X_FACS=0x7ffcfc00, X_DSDT=0x7ffc0000 X_PM1a_EVT_BLK=0x800:0[4] (IO) X_PM1a_CNT_BLK=0x804:0[2] (IO) X_PM_TMR_BLK=0x808:0[4] (IO) X_GPE0_BLK=0x828:0[8] (IO) */ /* FACS: Length=64, HwSig=0x00000000, Firm_Wake_Vec=0x00000000 Global_Lock= Flags= Version=1 */ /* DSDT: Length=8074, Revision=1, Checksum=53, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=INTL, Creator Revision=0x20050624 */ /* APIC: Length=132, Revision=1, Checksum=158, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=INTL, Creator Revision=0x1 Local APIC ADDR=0xfee00000 Flags={PC-AT} Type=Local APIC ACPI CPU=1 Flags={ENABLED} APIC ID=0 Type=Local APIC ACPI CPU=2 Flags={ENABLED} APIC ID=1 Type=Local APIC ACPI CPU=3 Flags={DISABLED} APIC ID=2 Type=Local APIC ACPI CPU=4 Flags={DISABLED} APIC ID=3 Type=Local NMI ACPI CPU=1 LINT Pin=1 Flags={Polarity=active-hi, Trigger=edge} Type=Local NMI ACPI CPU=2 LINT Pin=1 Flags={Polarity=active-hi, Trigger=edge} Type=INT Override BUS=0 IRQ=0 INTR=2 Flags={Polarity=conforming, Trigger=conforming} Type=INT Override BUS=0 IRQ=9 INTR=9 Flags={Polarity=active-hi, Trigger=level} Type=IO APIC APIC ID=2 INT BASE=0 ADDR=0x00000000fec00000 Type=IO APIC APIC ID=3 INT BASE=32 ADDR=0x00000000fec10000 */ /* SPCR: Length=80, Revision=1, Checksum=213, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=INTL, Creator Revision=0x1 */ /* HPET: Length=56, Revision=1, Checksum=74, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=INTL, Creator Revision=0x1 HPET Number=0 ADDR=0xfed00000:0[0] (Memory) HW Rev=0xff Comparitors=31 Counter Size=1 Legacy IRQ routing capable={TRUE} PCI Vendor ID=0xffff Minimal Tick=1000 */ /* MCFG: Length=60, Revision=1, Checksum=224, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=INTL, Creator Revision=0x1 Base Address= 0x00000000f0000000 Segment Group= 0x0000 Start Bus= 0 End Bus= 63 */ /* SLIC: Length=36, Revision=1, Checksum=25, OEMID=DELL, OEM Table ID=PE_SC3, OEM Revision=0x1, Creator ID=INTL, Creator Revision=0x1 */ > Perhaps the MADT is corrupt. Indeed, I don't see an MADT in the output above. Should there be one? > Have you checked your vendor for a BIOS update? Yes, I'm using their latest BIOS revision A06, dated October 8, 2008. Bill Brinzer From onemda at gmail.com Thu Nov 27 13:09:33 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Nov 27 13:09:39 2008 Subject: Resume on hp nx7300 In-Reply-To: <3a142e750811251137se5091f8vc1ca13e5469413c3@mail.gmail.com> References: <3a142e750811240748o1923fdc4xca1ae55f44bf664d@mail.gmail.com> <3a142e750811241658i39097018x3c6f49aa62805fa7@mail.gmail.com> <3a142e750811251137se5091f8vc1ca13e5469413c3@mail.gmail.com> Message-ID: <3a142e750811271309y714f5c5y38ca6fff577add5f@mail.gmail.com> On 11/25/08, Paul B. Mahol wrote: > On 11/25/08, Paul B. Mahol wrote: >> On 11/24/08, Paul B. Mahol wrote: >>> Hi, >>> >>> I managed somehow to succesfully resume laptop from suspend, >>> setting hw.acpi.osname="Windows 2001" >> It appears that it's not required at all. >> >>> but lcd output is off and can not be turned on. >> >> It will work if vesa is kldloaded _before_ suspend. >> Also kldload i915 (agp+drm+i915) _before_ suspend will do it. >> >>> sysctl hw.acpi.reset_video=1 does'nt work, instead to resume, machine >>> remain in unknown state, keyboard input doesnt work. >>> >>> Also if powerd + cpufreq combination is used, some time after resume >>> system will reboot itself: >>> >>> db:0:kdb.enter.unknown> show pcpu >>> cpuid = 0 >>> curthread = 0xc3ff0240: pid 667 "powerd" >>> curpcb = 0xc3a72d90 >>> fpcurthread = none >>> idlethread = 0xc3d2fd80: pid 10 "idle: cpu0" >>> APIC ID = 0 >>> currentldt = 0x50 >>> spin locks held: >>> db:0:kdb.enter.unknown> bt >>> Tracing pid 667 tid 100036 td 0xc3ff0240 >>> mtrash_ctor(c3e21000,400,0,1,0,...) at mtrash_ctor+0x60 >>> uma_zalloc_arg(c108ba20,0,1,0,c3e2c400,...) at uma_zalloc_arg+0x137 >>> malloc(36c,c06d1bc0,1,210,c049b0c3,...) at malloc+0xcb >>> cf_levels_method(c3e0ae80,c446f000,c3a72b4c,c3a72ba8,c446f3b4,...) at >>> cf_levels_method+0x23d >>> cpufreq_curr_sysctl(c3e414c0,c3e4f000,0,c3a72ba8,c3a72ba8,4,4,c3e414c0) >>> at cpufreq_curr_sysctl+0x169 >>> sysctl_root(c3a72ba8,0,c069a48a,587,c3ff0240,...) at sysctl_root+0x138 >>> userland_sysctl(c3ff0240,c3a72c14,4,0,0,...) at userland_sysctl+0x115 >>> __sysctl(c3ff0240,c3a72cf8,18,c06a0480,c06ce1b0,...) at __sysctl+0xb7 >>> syscall(c3a72d38) at syscall+0x261 >>> Xint0x80_syscall() at Xint0x80_syscall+0x20 >>> --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x28172533, esp = >>> 0xbfbfe84c, ebp = 0xbfbfe878 --- >>> >>> >>> acpi_ec0: wait timed out (response), forcing polled mode >>> <5>wakeup from sleeping state (slept 00:00:14) >>> acpi_tz0: _CRT value is absurd, ignored (256.0C) >>> agp0: on vgapci0 >>> agp0: detected 7932k stolen memory >>> agp0: aperture size is 256M >>> Memory modified after free 0xc3e21000(1020) val=0 @ 0xc3e21000 >>> >> >> powerd + cpufreq combination just works, above panic >> probably happened because agp is loaded _after_ resume. >> >>> >>> Fatal trap 12: page fault while in kernel mode >>> cpuid = 0; apic id = 00 >>> fault virtual address = 0xffff0020 >>> fault code = supervisor read, page not present >>> instruction pointer = 0x20:0xc062c350 >>> stack pointer = 0x28:0xc3a72a04 >>> frame pointer = 0x28:0xc3a72a24 >>> code segment = base 0x0, limit 0xfffff, type 0x1b >>> = DPL 0, pres 1, def32 1, gran 1 >>> processor eflags = interrupt enabled, resume, IOPL = 0 >>> current process = 667 (powerd) >>> exclusive sx cpufreq lock (cpufreq lock) r = 0 (0xc3e4f000) locked @ >>> /usr/src/sys/kern/kern_cpu.c:528 >>> exclusive sx sysctl lock (sysctl lock) r = 0 (0xc070f404) locked @ >>> /usr/src/sys/kern/kern_sysctl.c:1415 >>> exclusive sleep mutex Giant (Giant) r = 0 (0xc070edf0) locked @ >>> /usr/src/sys/kern/kern_sysctl.c:1353 >>> exclusive sx cpufreq lock (cpufreq lock) r = 0 (0xc3e4f000) locked @ >>> /usr/src/sys/kern/kern_cpu.c:528 >>> exclusive sx sysctl lock (sysctl lock) r = 0 (0xc070f404) locked @ >>> /usr/src/sys/kern/kern_sysctl.c:1415 >>> exclusive sleep mutex Giant (Giant) r = 0 (0xc070edf0) locked @ >>> /usr/src/sys/kern/kern_sysctl.c:1353 >>> >>> >>> Do I need to build/install UP kernel, or I can use SMP one with smp >>> disabled via loader.conf? >> >> kern.smp.disabled="1" just works, and disabling dual core from bios is >> not required. >> >> Restarting moused after resume is must. >> pccard and ndis powered broadcom card do not work after resume, >> even if right driver was never loaded during/after boot - before suspend. >> >> Main problem is that shutdown button (S5) doesnt work after resume. >> Is there any know reason why that could happen? > > Problem with cardbus controller appears to be that it never got into D3 > state, > because its hdr=0x02 > > I encountered also that setting hw.pci.do_power_nodriver=2 in > /boot/loader.conf > have same nasty effect when using it with suspend/resume. > > After resume all devices will be put back into D0 state, but if you > kldunload > one driver, for example snd_hda and kldload it again, all devices that > do not have > driver attached (and with hdr=0x00) will be put into D3 again. > > Same scenario happen when unloading driver, device will remain in D0 state > until some other driver is loaded/attached to correct device. > > Current devices power state can be monitored with "pciconf -lvc". > > I think this is more general problem. Here is status of cardbus before suspend: 02:06.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller Subsystem: Hewlett-Packard Company Unknown device 30a2 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt+ PostWrite- 16-bit legacy interface ports at 0001 00: 4c 10 39 80 07 00 10 02 00 00 07 06 10 40 82 00 10: 00 00 10 f4 a0 00 00 02 02 03 03 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 12 01 c4 03 40: 3c 10 a2 30 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 60 10 44 08 19 00 a3 01 00 00 17 00 22 1b 01 01 90: c0 02 64 40 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 02 7e 00 00 c0 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 22 52 d0 6f 05 98 01 04 00 00 00 00 00 00 00 00 and after resume: 02:06.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller Subsystem: Hewlett-Packard Company Unknown device 30a2 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset+ 16bInt- PostWrite- 16-bit legacy interface ports at 0001 00: 4c 10 39 80 00 00 10 02 00 00 07 06 00 00 82 00 10: 00 00 00 00 a0 00 00 02 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 01 40 03 40: 3c 10 a2 30 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 60 10 44 08 19 00 a3 01 00 00 17 00 22 1b 01 01 90: c0 02 64 40 00 00 00 00 00 00 00 00 00 00 00 00 a0: 01 00 02 7e 00 00 c0 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 22 52 d0 6f 05 98 01 04 00 00 00 00 00 00 00 00 -- Paul From onemda at gmail.com Thu Nov 27 15:58:18 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Nov 27 15:58:30 2008 Subject: Is the C3 possible with SMP? In-Reply-To: References: <20081121195714.CEE4B45010@ptavv.es.net> <20081122113015.B70117@sola.nimnet.asn.au> Message-ID: <3a142e750811271558r73727d81nb7dc7184627b54d3@mail.gmail.com> On 11/27/08, martinko wrote: > Ian Smith wrote: >> On Fri, 21 Nov 2008, Kevin Oberman wrote: >> > > From: martinko >> > > > [...] >> > > >> > > Hi, >> > > >> > > My laptop reports C1 state only: >> > > >> > > $ sysctl -a | grep cx_ >> > > hw.acpi.cpu.cx_lowest: C1 >> > > dev.cpu.0.cx_supported: C1/1 >> > > dev.cpu.0.cx_lowest: C1 >> > > dev.cpu.0.cx_usage: 100.00% >> > > >> > > But this is Pentium-M and I remember it could use C2 and C3 back with >> >> > > 5.x kernel and I'm sure I had USB as I have now. >> > > >> > > Do you have any idea why I don't have C2/C3 states available anymore >> ?? >> > >> > Under 7-Stable, my Pentium-M system (ThinkPad T43) shows C1, C2, and >> > C3. Of course, it's not an SMP. >> > dev.cpu.0.cx_supported: C1/1 C2/1 C3/85 >> > dev.cpu.0.cx_lowest: C1 >> > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% >> > >> > cx_supported has nothing to do with the value of cx_lowest. It should >> > simply be what the CPU reports back vi ACPI as to the C states >> supported >> > on the platform. >> >> Well, except that cx_supported shows the possible values for cx_lowest; >> ie you can only select a value for cx_lowest that's in cx_supported .. >> so it does seem odd that martinko's cx_supported has been limited to C1? >> >> Whether the system ever actually uses the cx_lowest value you select, >> other than C1, is another matter of course. My T23 (P3-M, 7.0-R) allows >> selection of C3, but only ever uses it if the machine was booted up on >> battery(!) but that might be a BIOS/EC bug that upgrading these may fix. >> >> cheers, Ian >> > > Well, booting with or without battery does make a difference, strangely: > > $ sysctl dev.cpu > 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.freq: 525 > dev.cpu.0.freq_levels: 2000/-1 1800/-1 1600/-1 1400/-1 1225/-1 1200/-1 > 1050/-1 1 > 000/-1 875/-1 800/-1 700/-1 600/-1 525/-1 450/-1 375/-1 300/-1 225/-1 > 150/-1 75/ > -1 > dev.cpu.0.cx_supported: C1/1 C2/1 C3/2 > dev.cpu.0.cx_lowest: C3 > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% > > This was suggested to me by Henry Hu: > > Henry Hu wrote: > > You may try to boot with battery. > > If I boot with AC, there are only C1 and C2. But if I boot with > > battery, there is C3. > > I found that the line to recheck cx states has been commented in the > > source code. So cx states keep the same since system startup. > > > > Cheers, > > > > Henry > > Cx states other than C1 are never used, unfortunately. Both C2 and C3 > were used back with 5.something (I started with 5.3). I guess USB might > be the culprit here. Anyway, it behaves strangely, at best. :( > > Cheers, > > Martin > > PS: Also, AFAIR C3 was not 2 but something like 100 back in times of 5.x > when it worked on this laptop correctly. It works for me: [ignoring fact that C3 appears only if laptop is disconneted from AC] Looks like I'm lucky ... CPU: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz (1662.51-MHz 686-class CPU dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 125 dev.cpu.0.freq_levels: 1667/31000 1458/27125 1333/22000 1166/19250 1000/13000 875/11375 750/9750 625/8125 500/6500 375/4875 250/3250 125/1625 dev.cpu.0.cx_supported: C1/1 C2/1 C3/57 dev.cpu.0.cx_lowest: C3 dev.cpu.0.cx_usage: 0.00% 4.59% 95.40% dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/1 C2/1 C3/57 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 0.00% 3.61% 96.38% Design capacity: 3365 mAh Last full capacity: 3365 mAh Technology: secondary (rechargeable) Design voltage: 10800 mV Capacity (warn): 169 mAh Capacity (low): 34 mAh Low/warn granularity: 100 mAh Warn/full granularity: 100 mAh Model number: Primary Serial number: 03400 2007/03/19 Type: LIon OEM info: Hewlett-Packard State: discharging Remaining capacity: 92% Remaining time: 2:12 Present rate: 15573 mA Voltage: 11708 mV It is interesting that when machine is almost completly idle typing inside syscons is very slooow - I need to move mouse all the time to speed up it (guess syscons is very slow). But just having mplayer playing music in background will improve interactivity a lot, note this doesnt happen inside X11. It doesnt happen if one of CPU have cx_lowest set to C2. This is very evident if I use powerd -b minimum. PS: I tested it with usb2_{core,controller_(ehci,uhci)} -- Paul From mav at FreeBSD.org Sun Nov 30 12:10:57 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Sun Nov 30 12:11:03 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <1224728582.00028075.1224715806@10.7.7.3> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> Message-ID: <4932F34C.1040804@FreeBSD.org> Hi. Alexander Motin wrote: > Jung-uk Kim wrote: >> I was working on suspend/resume support for amd64 and this is the >> result. It works with a modified QEMU (QEMU does not support S3) but >> real boxes that I have don't seem to like it (e.g., broken BIOSes). >> If there is someone interested in finishing it off or giving it a try, >> the patch is here: >> >> http://people.freebsd.org/~jkim/amd64_suspend.diff > > I have tried it on my Acer TM6292. S1/S2 are unsupported. On S3 system > successfully got down, but on wakeup button, two seconds after power up, > even without video initialization, it shut down, reset and then started > usual boot. I have tried both original and updated BIOS, without any > difference. > > Can I give you any other help? I have spent a day investigating the problem. I was inserting empty infinite loop into the different points of wakeup process trying to find the place where system reboots. I just haven't found any other feedback channel as video is not initialized and beeper is not working for some reason. As result, I have found, that if I am inserting: qqq: jmp qqq lines before line 98 of acpi_switch.S: movl $MSR_MTRRdefType, %ecx movl WAKEUP_CTX(mtrr), %eax wrmsr system hangs, but if I insert it just after them - system reboots. With just commenting this three lines I was able to get successful suspend/resume with UP amd64 kernel!!! Here is problems I still have now: - SMP kernel resume is not working, system reboots while doing acpi_wakeup_cpus(); - SATA controller does not resumes correctly, it dies for some reason, reporting timeouts on any request; - text mode video does not restores on resume, while Xorg graphic one does. hw.acpi.reset_video=1 does not help, it just hanging resume process. -- Alexander Motin From mav at FreeBSD.org Sun Nov 30 17:42:45 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Sun Nov 30 17:42:52 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <4932F34C.1040804@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> Message-ID: <49334110.4010308@FreeBSD.org> Alexander Motin wrote: > As result, I have found, that if I am inserting: > qqq: > jmp qqq > lines before line 98 of acpi_switch.S: > movl $MSR_MTRRdefType, %ecx > movl WAKEUP_CTX(mtrr), %eax > wrmsr > system hangs, but if I insert it just after them - system reboots. > > With just commenting this three lines I was able to get successful > suspend/resume with UP amd64 kernel!!! > > Here is problems I still have now: > - SMP kernel resume is not working, system reboots while doing > acpi_wakeup_cpus(); > - SATA controller does not resumes correctly, it dies for some reason, > reporting timeouts on any request; This one is not a problem anymore. Seems to be fixed. > - text mode video does not restores on resume, while Xorg graphic one > does. hw.acpi.reset_video=1 does not help, it just hanging resume process. -- Alexander Motin From smithi at nimnet.asn.au Sun Nov 30 20:16:27 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Sun Nov 30 20:16:34 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <49334110.4010308@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <49334110.4010308@FreeBSD.org> Message-ID: <20081201150743.V34249@sola.nimnet.asn.au> On Mon, 1 Dec 2008, Alexander Motin wrote: > Alexander Motin wrote: > > As result, I have found, that if I am inserting: > > qqq: > > jmp qqq > > lines before line 98 of acpi_switch.S: > > movl $MSR_MTRRdefType, %ecx > > movl WAKEUP_CTX(mtrr), %eax > > wrmsr > > system hangs, but if I insert it just after them - system reboots. > > > > With just commenting this three lines I was able to get successful > > suspend/resume with UP amd64 kernel!!! > > > > Here is problems I still have now: > > - SMP kernel resume is not working, system reboots while doing > > acpi_wakeup_cpus(); > > - SATA controller does not resumes correctly, it dies for some reason, > > reporting timeouts on any request; > > This one is not a problem anymore. Seems to be fixed. Progress! > > - text mode video does not restores on resume, while Xorg graphic one > > does. hw.acpi.reset_video=1 does not help, it just hanging resume process. Longshot: hw.syscons.sc_no_suspend_vtswitch=1 fixes similar symptoms on two (older, i386 and UP) laptops here. Some folks have reported needing to have VESA loaded to get text mode video back up. Maybe worth a try? cheers, Ian