From bugmaster at FreeBSD.org Mon Dec 1 03:06:50 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 1 03:07:10 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200812011106.mB1B6o3D052446@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 mav at FreeBSD.org Mon Dec 1 09:19:36 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Dec 1 09:19:43 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <20081201150743.V34249@sola.nimnet.asn.au> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <49334110.4010308@FreeBSD.org> <20081201150743.V34249@sola.nimnet.asn.au> Message-ID: <49341CA4.8060801@FreeBSD.org> Ian Smith wrote: > 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? vtswitch does not help and vesa generally does not working under amd64. -- Alexander Motin From jhb at freebsd.org Mon Dec 1 11:32:20 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Dec 1 11:32:27 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: <200812011205.07767.jhb@freebsd.org> On Tuesday 25 November 2008 01:15:12 pm 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. > > 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. Try 6.4 or a 7.1 release candidate. There was a bug in the MADT stuff in earlier releases in that it didn't handle the MADT header spanning two pages. -- John Baldwin From jhb at freebsd.org Mon Dec 1 11:32:35 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Dec 1 11:32:52 2008 Subject: acpi_cpu: binding processor object to pcpu struct. In-Reply-To: <200811251835.mAPIZFIC002676@sana.init-main.com> References: <200811251835.mAPIZFIC002676@sana.init-main.com> Message-ID: <200812011212.45582.jhb@freebsd.org> On Tuesday 25 November 2008 01:35:15 pm Takanori Watanabe wrote: > 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. Hmm, so is the issue that the acpi_cpu driver expects processor objects to be listed in the same order in _PR_ as in the MADT? If so, then that is probably a false assumption. The MADT should always have ACPI IDs for non-UP systems. OTOH, the comment in the code in acpi_cpu_attach() indicates that some boxes do not use the same ProcID value in processor objects and MADT entries and your patch breaks that case. I will look at the spec to see how this is supposed to work. -- John Baldwin From nate at root.org Mon Dec 1 11:53:05 2008 From: nate at root.org (Nate Lawson) Date: Mon Dec 1 11:53:12 2008 Subject: acpi_cpu: binding processor object to pcpu struct. In-Reply-To: <200812011212.45582.jhb@freebsd.org> References: <200811251835.mAPIZFIC002676@sana.init-main.com> <200812011212.45582.jhb@freebsd.org> Message-ID: <493440A2.7070108@root.org> John Baldwin wrote: > On Tuesday 25 November 2008 01:35:15 pm Takanori Watanabe wrote: >> 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. > > Hmm, so is the issue that the acpi_cpu driver expects processor objects to be > listed in the same order in _PR_ as in the MADT? If so, then that is > probably a false assumption. The MADT should always have ACPI IDs for non-UP > systems. OTOH, the comment in the code in acpi_cpu_attach() indicates that > some boxes do not use the same ProcID value in processor objects and MADT > entries and your patch breaks that case. I will look at the spec to see how > this is supposed to work. It's good that you are concerned about not breaking the existing code. I had to rework it a lot to handle various different implementations when I first wrote it. There was always one BIOS that was slightly different, and I think some were even mutually incompatible with each other. My memory is fuzzy, but you are right that the MADT id does not always match the Processor object id. I believe some of them had duplicate IDs. I think I tried to do a fallback, where we would use the Processor id if they all matched, otherwise just do strict ordering. The cvs logs should have the details. I ended up thinking that Windows probably just used the order of Processor objects (or mptable enumeration) and ignored the id field completely. That would be the only way so many differently broken implementations would work. -- Nate From brinzer at mfrac.com Tue Dec 2 06:57:17 2008 From: brinzer at mfrac.com (Bill Brinzer) Date: Tue Dec 2 06:57:32 2008 Subject: Dell PowerEdge 840 ACPI panic early in boot In-Reply-To: <200812011205.07767.jhb@freebsd.org> References: <20081125181512.GA89700@fire.mfrac.vpn> <200812011205.07767.jhb@freebsd.org> Message-ID: <20081202145714.GA81256@fire.mfrac.vpn> On Mon, Dec 01, 2008 at 12:05:07PM -0500, John Baldwin wrote: > Try 6.4 or a 7.1 release candidate. There was a bug in the MADT > stuff in earlier releases in that it didn't handle the MADT > header spanning two pages. Just tried 7.1, and it boots perfectly with ACPI enabled, so that must've been it. Thank you! Bill Brinzer From krasznai.andras at haisystems.hu Tue Dec 2 07:48:20 2008 From: krasznai.andras at haisystems.hu (=?iso-8859-2?Q?Krasznai_Andr=E1s?=) Date: Tue Dec 2 07:48:26 2008 Subject: ACPI problems on Lenovo 3000 N100 Message-ID: Good afternoon! I have been using FreeBSD since 5.3. Nowadays I am using FreeBSD-7.1-PRERELEASE on my Lenovo 3000 N100 laptop. I tried to use the suspend function (I want itt o go to suspend when I close the display) and the laptop behaved strangely; closing the LCD-display it eventually switches off but never wakes up; the only thing I can do is to switch it off and on, and wait for fsck finishing... The laptop is installed as a multiboot machine and the suspend function works correctly in Windows VISTA so the hardware is able to perform suspend. After reading the FreeBSD handbook I tried various settings with acpiconf, but no success: acpiconf -s S3 and acpiconf -s S4 caused various crashes on the machine, and the computer did not accept acpiconf -s S5 : said that level 5 is unsupported ACPI mode. Has anybody any success with this type of laptop regarding suspend functionality? I get other messages from ACPI similar to the following, which - by the handbook - mean that the ACPI may be broken. (ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPC0.FIGD._STA] \\ (Node 0xc3f6d160), AE_NOT_FOUND) I attach some diagnostic information according to the Freebsd handbook; pls. I also attach my kernel configuration (GENERIC_K). Give some advice how te get this machine perform suspend. Best regards Andras Krasznai -------------- next part -------------- A non-text attachment was scrubbed... Name: sysctl_hw.acpi Type: application/octet-stream Size: 974 bytes Desc: sysctl_hw.acpi Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081202/0c88dc89/sysctl_hw.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: loader.conf Type: application/octet-stream Size: 435 bytes Desc: loader.conf Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081202/0c88dc89/loader.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: sysctl.conf Type: application/octet-stream Size: 768 bytes Desc: sysctl.conf Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081202/0c88dc89/sysctl.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: GENERIC_K Type: application/octet-stream Size: 6923 bytes Desc: GENERIC_K Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081202/0c88dc89/GENERIC_K.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesga Type: application/octet-stream Size: 64602 bytes Desc: dmesga Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081202/0c88dc89/dmesga.obj From jkim at FreeBSD.org Tue Dec 2 09:43:30 2008 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Tue Dec 2 09:43:37 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: <200812021243.08513.jkim@FreeBSD.org> On Sunday 30 November 2008 03:10 pm, Alexander Motin wrote: > 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!!! Good catch! I can confirm this is a correct bandaid. We cannot restore this MSR without restoring entire MTRR map. Actually, I should have written separate functions to save/restore all global MSRs. Only per-CPU MSRs should be embedded like that. > Here is problems I still have now: > - SMP kernel resume is not working, system reboots while doing > acpi_wakeup_cpus(); My dual-core CPU seems to resume okay but quite unstable. Can you try something like the following in amd64/mp_machdep.c and tell me if it helps? ------------ @@ -57,6 +57,7 @@ #include #include +#include #include #include #include @@ -1121,6 +1121,8 @@ int cpumask = PCPU_GET(cpumask); if (savectx2(&stopxpcbs[cpu])) { + /* Flush CPU cache. */ + wbinvd(); /* Indicate that we are suspended. */ atomic_set_int(&stopped_cpus, cpumask); } else { ------------ > - 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. It is very common problem for modern video cards. We cannot do much here without help of GPU-specific routines (e.g., ATI ATOM BIOS parser for RadeonHD) or in-kernel realmode emulation[1] (e.g., NetBSD). Thanks for the feedback! Jung-uk Kim [1] http://cvsweb.netbsd.org/bsdweb.cgi/src/common/lib/libx86emu/ http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/x86/x86/vga_post.c From mav at FreeBSD.org Tue Dec 2 11:03:51 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Tue Dec 2 11:04:03 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <200812021243.08513.jkim@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org> Message-ID: <49358684.7010508@FreeBSD.org> Hi. Jung-uk Kim wrote: >> Here is problems I still have now: >> - SMP kernel resume is not working, system reboots while doing >> acpi_wakeup_cpus(); > > My dual-core CPU seems to resume okay but quite unstable. Can you try > something like the following in amd64/mp_machdep.c and tell me if it > helps? > > ------------ > @@ -57,6 +57,7 @@ > #include > > #include > +#include > #include > #include > #include > @@ -1121,6 +1121,8 @@ > int cpumask = PCPU_GET(cpumask); > > if (savectx2(&stopxpcbs[cpu])) { > + /* Flush CPU cache. */ > + wbinvd(); > /* Indicate that we are suspended. */ > atomic_set_int(&stopped_cpus, cpumask); > } else { > ------------ Wow, it works! I am writing this letter just after suspending/resuming my dual-core C2D system 4 times straight. Music plays, USB, SATA, all other hardware works fine. What kind of instability do you have? The only strange effect I have noticed was incorrect CPU time some processes got: %ps ax PID TT STAT TIME COMMAND 12 ?? WL 280503:38,05 [intr] 1430 ?? Ss 280503:38,34 icewm But I think it is more timer driver related then resume itself. > Thanks for the feedback! Many thanks to you! I hope this long-waited feature will be finished! -- Alexander Motin From nate at root.org Tue Dec 2 11:19:27 2008 From: nate at root.org (Nate Lawson) Date: Tue Dec 2 11:19:33 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <49358684.7010508@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org> <49358684.7010508@FreeBSD.org> Message-ID: <49358A3F.7020701@root.org> Alexander Motin wrote: > Hi. > > Jung-uk Kim wrote: >>> Here is problems I still have now: >>> - SMP kernel resume is not working, system reboots while doing >>> acpi_wakeup_cpus(); >> >> My dual-core CPU seems to resume okay but quite unstable. Can you try >> something like the following in amd64/mp_machdep.c and tell me if it >> helps? >> >> ------------ >> @@ -57,6 +57,7 @@ >> #include >> >> #include >> +#include >> #include >> #include >> #include >> @@ -1121,6 +1121,8 @@ >> int cpumask = PCPU_GET(cpumask); >> >> if (savectx2(&stopxpcbs[cpu])) { >> + /* Flush CPU cache. */ >> + wbinvd(); >> /* Indicate that we are suspended. */ >> atomic_set_int(&stopped_cpus, cpumask); >> } else { >> ------------ > > Wow, it works! > > I am writing this letter just after suspending/resuming my dual-core C2D > system 4 times straight. Music plays, USB, SATA, all other hardware > works fine. What kind of instability do you have? Thank you both for debugging this. It's good to see progress on suspend/resume. > The only strange effect I have noticed was incorrect CPU time some > processes got: > %ps ax > PID TT STAT TIME COMMAND > 12 ?? WL 280503:38,05 [intr] > 1430 ?? Ss 280503:38,34 icewm > > But I think it is more timer driver related then resume itself. If you are using the LAPIC timer (default), it won't be running properly during resume. However, this wide discrepancy seems to indicate that the timer state is not being resumed properly. What if you use the ACPI timer (hw.timecounter.* I think are the sysctls)? -- Nate From mav at FreeBSD.org Tue Dec 2 11:26:56 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Tue Dec 2 11:27:08 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <49358A3F.7020701@root.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org> <49358684.7010508@FreeBSD.org> <49358A3F.7020701@root.org> Message-ID: <49358BED.3030903@FreeBSD.org> Nate Lawson wrote: >> The only strange effect I have noticed was incorrect CPU time some >> processes got: >> %ps ax >> PID TT STAT TIME COMMAND >> 12 ?? WL 280503:38,05 [intr] >> 1430 ?? Ss 280503:38,34 icewm >> >> But I think it is more timer driver related then resume itself. > > If you are using the LAPIC timer (default), it won't be running properly > during resume. However, this wide discrepancy seems to indicate that > the timer state is not being resumed properly. What if you use the ACPI > timer (hw.timecounter.* I think are the sysctls)? As I understand, I am now using LAPIC timer for HZ generation, ACPI-fast as time source and TSC as kernel DELAY() source. %sysctl -a | grep timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) ACPI-fast(1000) HPET(900) i8254(0) dummy(-1000000) kern.timecounter.hardware: ACPI-fast kern.timecounter.nsetclock: 3 kern.timecounter.ngetmicrotime: 353840 kern.timecounter.ngetnanotime: 481 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetmicrouptime: 2014472 kern.timecounter.ngetnanouptime: 8950060 kern.timecounter.ngetbinuptime: 419099 kern.timecounter.nmicrotime: 1460084 kern.timecounter.nnanotime: 40830 kern.timecounter.nbintime: 1500942 kern.timecounter.nmicrouptime: 2210 kern.timecounter.nnanouptime: 21 kern.timecounter.nbinuptime: 1988392 kern.timecounter.stepwarnings: 0 kern.timecounter.tc.i8254.mask: 65535 kern.timecounter.tc.i8254.counter: 46767 kern.timecounter.tc.i8254.frequency: 1193182 kern.timecounter.tc.i8254.quality: 0 kern.timecounter.tc.HPET.mask: 4294967295 kern.timecounter.tc.HPET.counter: 3274417396 kern.timecounter.tc.HPET.frequency: 14318180 kern.timecounter.tc.HPET.quality: 900 kern.timecounter.tc.ACPI-fast.mask: 16777215 kern.timecounter.tc.ACPI-fast.counter: 14616414 kern.timecounter.tc.ACPI-fast.frequency: 3579545 kern.timecounter.tc.ACPI-fast.quality: 1000 kern.timecounter.tc.TSC.mask: 4294967295 kern.timecounter.tc.TSC.counter: 3757339660 kern.timecounter.tc.TSC.frequency: 2394021468 kern.timecounter.tc.TSC.quality: -100 kern.timecounter.smp_tsc: 0 kern.timecounter.invariant_tsc: 1 There is sure some problem with LAPIC: %vmstat -i interrupt total rate ..... irq257: bge0 70774 29 cpu1: timer 17600 7 cpu1: timer 27617 11 cpu1: timer 15849 6 cpu1: timer 15413 6 cpu1: timer 877180 367 Total 2284801 957 -- Alexander Motin From jhb at freebsd.org Tue Dec 2 13:15:14 2008 From: jhb at freebsd.org (John Baldwin) Date: Tue Dec 2 13:15:44 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <49358BED.3030903@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <49358A3F.7020701@root.org> <49358BED.3030903@FreeBSD.org> Message-ID: <200812021559.05492.jhb@freebsd.org> On Tuesday 02 December 2008 02:26:37 pm Alexander Motin wrote: > Nate Lawson wrote: > >> The only strange effect I have noticed was incorrect CPU time some > >> processes got: > >> %ps ax > >> PID TT STAT TIME COMMAND > >> 12 ?? WL 280503:38,05 [intr] > >> 1430 ?? Ss 280503:38,34 icewm > >> > >> But I think it is more timer driver related then resume itself. > > > > If you are using the LAPIC timer (default), it won't be running properly > > during resume. However, this wide discrepancy seems to indicate that > > the timer state is not being resumed properly. What if you use the ACPI > > timer (hw.timecounter.* I think are the sysctls)? > > As I understand, I am now using LAPIC timer for HZ generation, ACPI-fast > as time source and TSC as kernel DELAY() source. > > %sysctl -a | grep timecounter > kern.timecounter.tick: 1 > kern.timecounter.choice: TSC(-100) ACPI-fast(1000) HPET(900) i8254(0) > dummy(-1000000) > kern.timecounter.hardware: ACPI-fast > kern.timecounter.nsetclock: 3 > kern.timecounter.ngetmicrotime: 353840 > kern.timecounter.ngetnanotime: 481 > kern.timecounter.ngetbintime: 0 > kern.timecounter.ngetmicrouptime: 2014472 > kern.timecounter.ngetnanouptime: 8950060 > kern.timecounter.ngetbinuptime: 419099 > kern.timecounter.nmicrotime: 1460084 > kern.timecounter.nnanotime: 40830 > kern.timecounter.nbintime: 1500942 > kern.timecounter.nmicrouptime: 2210 > kern.timecounter.nnanouptime: 21 > kern.timecounter.nbinuptime: 1988392 > kern.timecounter.stepwarnings: 0 > kern.timecounter.tc.i8254.mask: 65535 > kern.timecounter.tc.i8254.counter: 46767 > kern.timecounter.tc.i8254.frequency: 1193182 > kern.timecounter.tc.i8254.quality: 0 > kern.timecounter.tc.HPET.mask: 4294967295 > kern.timecounter.tc.HPET.counter: 3274417396 > kern.timecounter.tc.HPET.frequency: 14318180 > kern.timecounter.tc.HPET.quality: 900 > kern.timecounter.tc.ACPI-fast.mask: 16777215 > kern.timecounter.tc.ACPI-fast.counter: 14616414 > kern.timecounter.tc.ACPI-fast.frequency: 3579545 > kern.timecounter.tc.ACPI-fast.quality: 1000 > kern.timecounter.tc.TSC.mask: 4294967295 > kern.timecounter.tc.TSC.counter: 3757339660 > kern.timecounter.tc.TSC.frequency: 2394021468 > kern.timecounter.tc.TSC.quality: -100 > kern.timecounter.smp_tsc: 0 > kern.timecounter.invariant_tsc: 1 > > There is sure some problem with LAPIC: > %vmstat -i > interrupt total rate > ..... > irq257: bge0 70774 29 > cpu1: timer 17600 7 > cpu1: timer 27617 11 > cpu1: timer 15849 6 > cpu1: timer 15413 6 > cpu1: timer 877180 367 > Total 2284801 957 Oh, it's getting a new counter on each resume. That is a bug. Ah, I think the AP's are using lapic_setup(1) when they should be using lapic_setup(0) during a resume. -- John Baldwin From mav at FreeBSD.org Tue Dec 2 13:37:29 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Tue Dec 2 13:37:36 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <200812021559.05492.jhb@freebsd.org> References: <1224616985.00027652.1224606603@10.7.7.3> <49358A3F.7020701@root.org> <49358BED.3030903@FreeBSD.org> <200812021559.05492.jhb@freebsd.org> Message-ID: <4935AA86.7090405@FreeBSD.org> John Baldwin wrote: > Oh, it's getting a new counter on each resume. That is a bug. Ah, I think > the AP's are using lapic_setup(1) when they should be using lapic_setup(0) > during a resume. Thanks. With this LAPIC works better: --- mp_machdep.c.prev2 2008-12-02 23:33:10.000000000 +0200 +++ mp_machdep.c 2008-12-02 23:26:23.000000000 +0200 @@ -1127,7 +1127,7 @@ cpususpend_handler(void) atomic_set_int(&stopped_cpus, cpumask); } else { /* Set up local APIC again. */ - lapic_setup(1); + lapic_setup(0); } while (!(started_cpus & cpumask)) But statistic problem is still here: # ps ax PID TT STAT TIME COMMAND 1429 ?? Ss 282031:03,98 icewm -- Alexander Motin From niktychina at gmail.com Tue Dec 2 15:20:28 2008 From: niktychina at gmail.com (Nikolay Tychina) Date: Tue Dec 2 15:20:35 2008 Subject: ACPI problems on Lenovo 3000 N100 In-Reply-To: References: Message-ID: Hi, try to repair your dsdt, this information from gentoo-wiki will be useful: http://web.archive.org/web/20080125015702/http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems Could you send me your acpi dump? 2008/12/2 Krasznai Andr?s > Good afternoon! > > > I have been using FreeBSD since 5.3. Nowadays I am using > FreeBSD-7.1-PRERELEASE on my Lenovo 3000 N100 laptop. > > I tried to use the suspend function (I want itt o go to suspend when I > close the display) and the laptop behaved strangely; closing the LCD-display > it eventually switches off but never wakes up; the only thing I can do is to > switch it off and on, and wait for fsck finishing... > > > The laptop is installed as a multiboot machine and the suspend function > works correctly in Windows VISTA so the hardware is able to perform suspend. > > After reading the FreeBSD handbook I tried various settings with acpiconf, > but no success: > > acpiconf -s S3 and acpiconf -s S4 caused various crashes on the machine, > > and the computer did not accept acpiconf -s S5 : said that level 5 is > unsupported ACPI mode. > > Has anybody any success with this type of laptop regarding suspend > functionality? > > I get other messages from ACPI similar to the following, which - by the > handbook - mean that the ACPI may be broken. > > (ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPC0.FIGD._STA] > \\ > (Node 0xc3f6d160), AE_NOT_FOUND) > > > > I attach some diagnostic information according to the Freebsd handbook; > pls. I also attach my kernel configuration (GENERIC_K). > > Give some advice how te get this machine perform suspend. > > Best regards > > Andras Krasznai > > > > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > > From niktychina at gmail.com Wed Dec 3 09:31:52 2008 From: niktychina at gmail.com (Nikolay Tychina) Date: Wed Dec 3 09:31:59 2008 Subject: ACPI problems on Lenovo 3000 N100 In-Reply-To: References: Message-ID: >Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 167 Optimizations It seems, you needn't fix your acpi :) Maybe that console error mesagges appears cause freebsds' bug? Did you try linux (maybe ubuntu 8.10 - my acer suspends and wakes up very good when running it) ? 2008/12/3 Krasznai Andr?s > Hi, thank you for the answer > > > > Originally I attached the acpidump as well, but then the size of the mail > was over the 200KB limit. I attach the acpidump now. > > > > Thanks > > > > Andras Krasznai > > > > > ------------------------------ > > *From:* Nikolay Tychina [mailto:niktychina@gmail.com] > *Sent:* Wednesday, December 03, 2008 12:20 AM > *To:* Krasznai Andr?s; freebsd-acpi@freebsd.org > *Subject:* Re: ACPI problems on Lenovo 3000 N100 > > > > Hi, > > try to repair your dsdt, > this information from gentoo-wiki will be useful: > http://web.archive.org/web/20080125015702/http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems > > Could you send me your acpi dump? > > 2008/12/2 Krasznai Andr?s > > Good afternoon! > > > I have been using FreeBSD since 5.3. Nowadays I am using > FreeBSD-7.1-PRERELEASE on my Lenovo 3000 N100 laptop. > > I tried to use the suspend function (I want itt o go to suspend when I > close the display) and the laptop behaved strangely; closing the LCD-display > it eventually switches off but never wakes up; the only thing I can do is to > switch it off and on, and wait for fsck finishing... > > > The laptop is installed as a multiboot machine and the suspend function > works correctly in Windows VISTA so the hardware is able to perform suspend. > > After reading the FreeBSD handbook I tried various settings with acpiconf, > but no success: > > acpiconf -s S3 and acpiconf -s S4 caused various crashes on the machine, > > and the computer did not accept acpiconf -s S5 : said that level 5 is > unsupported ACPI mode. > > Has anybody any success with this type of laptop regarding suspend > functionality? > > I get other messages from ACPI similar to the following, which - by the > handbook - mean that the ACPI may be broken. > > (ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPC0.FIGD._STA] > \\ > (Node 0xc3f6d160), AE_NOT_FOUND) > > > > I attach some diagnostic information according to the Freebsd handbook; > pls. I also attach my kernel configuration (GENERIC_K). > > Give some advice how te get this machine perform suspend. > > Best regards > > Andras Krasznai > > > > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > > > From brde at optusnet.com.au Wed Dec 3 10:33:34 2008 From: brde at optusnet.com.au (Bruce Evans) Date: Wed Dec 3 10:33:41 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <49358BED.3030903@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org> <49358684.7010508@FreeBSD.org> <49358A3F.7020701@root.org> <49358BED.3030903@FreeBSD.org> Message-ID: <20081203210228.R1989@delplex.bde.org> On Tue, 2 Dec 2008, Alexander Motin wrote: > Nate Lawson wrote: >>> The only strange effect I have noticed was incorrect CPU time some >>> processes got: >>> %ps ax >>> PID TT STAT TIME COMMAND >>> 12 ?? WL 280503:38,05 [intr] >>> 1430 ?? Ss 280503:38,34 icewm >>> >>> But I think it is more timer driver related then resume itself. >> >> If you are using the LAPIC timer (default), it won't be running properly >> during resume. However, this wide discrepancy seems to indicate that >> the timer state is not being resumed properly. What if you use the ACPI >> timer (hw.timecounter.* I think are the sysctls)? > > As I understand, I am now using LAPIC timer for HZ generation, ACPI-fast as > time source and TSC as kernel DELAY() source. CPU times use mainly the cpu_ticker (TSC on i386), and the cpu_ticker code has always been broken if the frequency changes a lot. The main bugs that I know about are: (1) the cpu time is (total cpu_ticks) / cputick_frequency(now) but should be the integral over previous thread history of (delta cpu_ticks) / cputick_frequency(t) dt. The former gives a wrong value if cputick_frequency(t) is not constant over previous thread history, and the wrongness is very obvious for long-running threads like intr and idle ones if the TSC frequency changes significantly (e.g., by cpufreq). cpufreq has a callback to reinitialize the frequency calibration, but this doesn't help much. I can't find any resume method for the TSC. (2) frequency _re_calibration is broken. It never decreases the frequency. Thus if the frequency is transiently high, the transiently high calibration persists until the next reinitialization of the frequency calibration (or until a tranisiently higher frequency is seen). Small variations due to temperature changes thus make the frequency persistently slightly higher that it should be, and large variations due to stopping a timer or stopping or throttling the TSC can make the freqency persistently very wrong. This wrongness is very obvious using ddb. While in ddb, interrupt timers are stopped but the TSC advances. Recalibration then gives an enormously high frequency (nearly 1/0 = infinity) that is sticky due to the bug. Dividing by this then gives all cpu times of nearly 0, modulo monotonicity enforcement by calcru() (which helps here -- old nonzero times for intr and idle remain nonzero). The sanity checking in the recalibration detects remarkably few cases of insanity for some reason, perhaps because the timers are too in sync. You seem to have the opposite problem, that times are enormously high. This would be caused by the frequency being calibrated as nearly 0, but I can't see how this could happen -- the TSC is presumably stopped while the system is suspended, so the recalibration code would tend to give a frequency far too low if the resume method is indeed missing, but bug (2) prevents this low value being used; OTOH, the resume method should recalibrate only after restarting all clocks, so it shouldn't suffer from bug (2). There are possible races getting the calibration done by the resume method before the main timer interrupt handler does it based on bogus data, but the latter doesn't happen on every timer interrupt so you would be unlucky to lose these races. If the frequency is transiently miscalibrated as nearly 0 and you look at the cpu time using calcru() during this time, then bug (1) gives enormously high times like the above (nearly 1/0) for long running processes; then calcru()'s monotonicity enforcement preserves the enormously high times almost forever (recalibration should eventually fix the frequency, so bug (1) would give normal times again since nothing much has happened to the tick counts; however monotonicity enforcement results in the transiently high times being returned almost forever -- the returned times won't even increase until the normal times reach the enormous value or another transient miscalibration messes up the calculation of the raw times again). Bruce From franks at rudbek.com Wed Dec 3 13:55:43 2008 From: franks at rudbek.com (Steve Franks) Date: Wed Dec 3 13:56:05 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <200812021243.08513.jkim@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org> Message-ID: <539c60b90812031334kfe23981s35b965b12462a5b2@mail.gmail.com> On Tue, Dec 2, 2008 at 10:43 AM, Jung-uk Kim wrote: > On Sunday 30 November 2008 03:10 pm, Alexander Motin wrote: >> 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!!! > > Good catch! I can confirm this is a correct bandaid. We cannot > restore this MSR without restoring entire MTRR map. Actually, I > should have written separate functions to save/restore all global > MSRs. Only per-CPU MSRs should be embedded like that. > >> Here is problems I still have now: >> - SMP kernel resume is not working, system reboots while doing >> acpi_wakeup_cpus(); > > My dual-core CPU seems to resume okay but quite unstable. Can you try > something like the following in amd64/mp_machdep.c and tell me if it > helps? > > ------------ > @@ -57,6 +57,7 @@ > #include > > #include > +#include > #include > #include > #include > @@ -1121,6 +1121,8 @@ > int cpumask = PCPU_GET(cpumask); > > if (savectx2(&stopxpcbs[cpu])) { > + /* Flush CPU cache. */ > + wbinvd(); > /* Indicate that we are suspended. */ > atomic_set_int(&stopped_cpus, cpumask); > } else { > ------------ > >> - 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. > > It is very common problem for modern video cards. We cannot do much > here without help of GPU-specific routines (e.g., ATI ATOM BIOS > parser for RadeonHD) or in-kernel realmode emulation[1] (e.g., > NetBSD). > > Thanks for the feedback! > > Jung-uk Kim > > [1] http://cvsweb.netbsd.org/bsdweb.cgi/src/common/lib/libx86emu/ > http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/x86/x86/vga_post.c > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > Do you believe these patches should work against 6.4? I should like to try it out on my trusty 'ol desktop. Best, Steve From franks at rudbek.com Wed Dec 3 15:14:41 2008 From: franks at rudbek.com (Steve Franks) Date: Wed Dec 3 15:14:52 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <539c60b90812031334kfe23981s35b965b12462a5b2@mail.gmail.com> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org> <539c60b90812031334kfe23981s35b965b12462a5b2@mail.gmail.com> Message-ID: <539c60b90812031514x3246ca09ua2febc879f8a7fcf@mail.gmail.com> > On Tue, Dec 2, 2008 at 10:43 AM, Jung-uk Kim wrote: >> On Sunday 30 November 2008 03:10 pm, Alexander Motin wrote: >>> 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!!! >> >> Good catch! I can confirm this is a correct bandaid. We cannot >> restore this MSR without restoring entire MTRR map. Actually, I >> should have written separate functions to save/restore all global >> MSRs. Only per-CPU MSRs should be embedded like that. >> >>> Here is problems I still have now: >>> - SMP kernel resume is not working, system reboots while doing >>> acpi_wakeup_cpus(); >> >> My dual-core CPU seems to resume okay but quite unstable. Can you try >> something like the following in amd64/mp_machdep.c and tell me if it >> helps? >> >> ------------ >> @@ -57,6 +57,7 @@ >> #include >> >> #include >> +#include >> #include >> #include >> #include >> @@ -1121,6 +1121,8 @@ >> int cpumask = PCPU_GET(cpumask); >> >> if (savectx2(&stopxpcbs[cpu])) { >> + /* Flush CPU cache. */ >> + wbinvd(); >> /* Indicate that we are suspended. */ >> atomic_set_int(&stopped_cpus, cpumask); >> } else { >> ------------ >> >>> - 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. >> >> It is very common problem for modern video cards. We cannot do much >> here without help of GPU-specific routines (e.g., ATI ATOM BIOS >> parser for RadeonHD) or in-kernel realmode emulation[1] (e.g., >> NetBSD). >> >> Thanks for the feedback! >> >> Jung-uk Kim >> >> [1] http://cvsweb.netbsd.org/bsdweb.cgi/src/common/lib/libx86emu/ >> http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/x86/x86/vga_post.c >> _______________________________________________ >> freebsd-acpi@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" >> > Do you believe these patches should work against 6.4? I should like to try it out on my trusty 'ol desktop. Best, Steve From mav at FreeBSD.org Wed Dec 3 16:07:17 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Wed Dec 3 16:07:24 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <20081203210228.R1989@delplex.bde.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <200812021243.08513.jkim@FreeBSD.org> <49358684.7010508@FreeBSD.org> <49358A3F.7020701@root.org> <49358BED.3030903@FreeBSD.org> <20081203210228.R1989@delplex.bde.org> Message-ID: <4937181F.5000009@FreeBSD.org> Bruce Evans wrote: > On Tue, 2 Dec 2008, Alexander Motin wrote: >> Nate Lawson wrote: >>>> The only strange effect I have noticed was incorrect CPU time some >>>> processes got: >>>> %ps ax >>>> PID TT STAT TIME COMMAND >>>> 12 ?? WL 280503:38,05 [intr] >>>> 1430 ?? Ss 280503:38,34 icewm >>>> >>>> But I think it is more timer driver related then resume itself. >>> >>> If you are using the LAPIC timer (default), it won't be running properly >>> during resume. However, this wide discrepancy seems to indicate that >>> the timer state is not being resumed properly. What if you use the ACPI >>> timer (hw.timecounter.* I think are the sysctls)? >> >> As I understand, I am now using LAPIC timer for HZ generation, >> ACPI-fast as time source and TSC as kernel DELAY() source. > > CPU times use mainly the cpu_ticker (TSC on i386), and the cpu_ticker code > has always been broken if the frequency changes a lot. The main bugs that > I know about are: Latest CPUs, including mine, does not change TSC frequency with EST and Cx states. So I think it is not frequency problem. I haven't checked if it specially handled, but I think, that when system suspended, timers may not be just stopped, but could also be reseted. If CPU looses all it's context, why should it keep some timer state? If timer reseted - it's value probably will go back, that may be seen as negative overflow. Here is some more related error messages I have found on resume: kernel: calcru: runtime went backwards from 5095 usec to 12 usec for pid 1544 (sh) kernel: calcru: runtime went backwards from 4704 usec to 12 usec for pid 1544 (sh) kernel: calcru: runtime went backwards from 1279 usec to 2 usec for pid 1543 (sh) kernel: calcru: runtime went backwards from 4180 usec to 9 usec for pid 1511 (moused) kernel: calcru: runtime went backwards from 11869 usec to 26 usec for pid 1435 (csh) kernel: calcru: runtime went backwards from 46399 usec to 102 usec for pid 1435 (csh) kernel: calcru: runtime went backwards from 4377 usec to 9 usec for pid 1434 (su) kernel: calcru: runtime went backwards from 10097 usec to 22 usec for pid 1432 (csh) -- Alexander Motin From robert.moore at intel.com Thu Dec 4 09:54:19 2008 From: robert.moore at intel.com (Moore, Robert) Date: Thu Dec 4 10:21:11 2008 Subject: ACPICA version 20081204 released Message-ID: <4911F71203A09E4D9981D27F9D8308580DD53450@orsmsx503.amr.corp.intel.com> 04 December 2008. Summary of changes for version 20081204: This release is available at www.acpica.org/downloads. 1) ACPI CA Core Subsystem: The ACPICA Programmer Reference has been completely updated and revamped for this release. This includes updates to the external interfaces, OSL interfaces, the overview sections, and the debugger reference. Several new ACPICA interfaces have been implemented and documented in the programmer reference: AcpiReset - Writes the reset value to the FADT-defined reset register. AcpiDisableAllGpes - Disable all available GPEs. AcpiEnableAllRuntimeGpes - Enable all available runtime GPEs. AcpiGetGpeDevice - Get the GPE block device associated with a GPE. AcpiGbl_CurrentGpeCount - Tracks the current number of available GPEs. AcpiRead - Low-level read ACPI register (was HwLowLevelRead.) AcpiWrite - Low-level write ACPI register (was HwLowLevelWrite.) Most of the public ACPI hardware-related interfaces have been moved to a new file, components/hardware/hwxface.c Enhanced the FADT parsing and low-level ACPI register access: The ACPI register lengths within the FADT are now used, and the low level ACPI register access no longer hardcodes the ACPI register lengths. Given that there may be some risk in actually trusting the FADT register lengths, a run-time option was added to fall back to the default hardcoded lengths if the FADT proves to contain incorrect values - UseDefaultRegisterWidths. This option is set to true for now, and a warning is issued if a suspicious FADT register length is overridden with the default value. Fixed a reference count issue in NsRepairObject. This problem was introduced in version 20081031 as part of a fix to repair Buffer objects within Packages. Lin Ming. Added semaphore support to the Linux/Unix application OS-services layer (OSL). ACPICA BZ 448. Lin Ming. Added the ACPI_MUTEX_TYPE configuration option to select whether mutexes will be implemented in the OSL, or will binary semaphores be used instead. Example Code and Data Size: These are the sizes for the OS-independent acpica.lib produced by the Microsoft Visual C++ 6.0 32-bit compiler. The debug version of the code includes the debug output trace mechanism and has a much larger code and data size. Previous Release: Non-Debug Version: 81.7K Code, 17.3K Data, 99.0K Total Debug Version: 156.4K Code, 49.4K Data, 205.8K Total Current Release: Non-Debug Version: 82.3K Code, 17.4K Data, 99.7K Total Debug Version: 157.1K Code, 49.7K Data, 206.8K Total 2) iASL Compiler/Disassembler and Tools: iASL: Completed the '-e' option to include additional ACPI tables in order to aid with disassembly and External statement generation. ACPICA BZ 742. Lin Ming. iASL: Removed the "named object in while loop" error. The compiler cannot determine how many times a loop will execute. ACPICA BZ 730. Disassembler: Implemented support for FADT revision 2 (MS extension). ACPICA BZ 743. Disassembler: Updates for several ACPI data tables (HEST, EINJ, and MCFG). From ivakras1 at gmail.com Thu Dec 4 14:28:39 2008 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Thu Dec 4 14:28:45 2008 Subject: ACPICA version 20081204 released In-Reply-To: <4911F71203A09E4D9981D27F9D8308580DD53450@orsmsx503.amr.corp.intel.com> References: <4911F71203A09E4D9981D27F9D8308580DD53450@orsmsx503.amr.corp.intel.com> Message-ID: <200812050108.21644.ivakras1@gmail.com> On Thursday 04 December 2008 20:54:15 Moore, Robert wrote: > 04 December 2008. Summary of changes for version 20081204: > > This release is available at www.acpica.org/downloads. When it will be included in 7-PRE? Or how to integrate it in my /usr/src/ ? From niktychina at gmail.com Fri Dec 5 10:52:47 2008 From: niktychina at gmail.com (Nikolay Tychina) Date: Fri Dec 5 10:52:53 2008 Subject: ACPICA version 20081204 released In-Reply-To: <200812050108.21644.ivakras1@gmail.com> References: <4911F71203A09E4D9981D27F9D8308580DD53450@orsmsx503.amr.corp.intel.com> <200812050108.21644.ivakras1@gmail.com> Message-ID: We are really appreciate you for release, but we can't use it. How do i compile it for my FreeBSD 7.1-PRERELEASE ? (http://forums.freebsd.org/showthread.php?t=632, somebody needs it too :) ) 2008/12/5 Dmitry Kolosov > On Thursday 04 December 2008 20:54:15 Moore, Robert wrote: > > 04 December 2008. Summary of changes for version 20081204: > > > > This release is available at www.acpica.org/downloads. > > When it will be included in 7-PRE? Or how to integrate it in my /usr/src/ ? > > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > From oberman at es.net Fri Dec 5 10:59:35 2008 From: oberman at es.net (Kevin Oberman) Date: Fri Dec 5 10:59:41 2008 Subject: ACPICA version 20081204 released In-Reply-To: Your message of "Fri, 05 Dec 2008 21:48:39 +0300." Message-ID: <20081205185934.355784501A@ptavv.es.net> > Date: Fri, 5 Dec 2008 21:48:39 +0300 > From: "Nikolay Tychina" > Sender: owner-freebsd-acpi@freebsd.org > > We are really appreciate you for release, but we can't use it. > How do i compile it for my FreeBSD 7.1-PRERELEASE ? > > (http://forums.freebsd.org/showthread.php?t=632, somebody needs it too :) ) Unless you are a good FreeBSD hacker, you don't. In a bit of time, depending on just how busy some folks are, it will be integrated into the head and, after some testing, MFCed to RELENG_7. I expect it will be there for 7.2, but it's way too late to make it for 7.1. If you run RELENG_7, it may not be too long before it shows up. -- 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/20081205/43fa10de/attachment.pgp From nate at root.org Fri Dec 5 11:06:43 2008 From: nate at root.org (Nate Lawson) Date: Fri Dec 5 11:06:54 2008 Subject: ACPICA version 20081204 released In-Reply-To: <20081205185934.355784501A@ptavv.es.net> References: <20081205185934.355784501A@ptavv.es.net> Message-ID: <49397BC1.7050505@root.org> Kevin Oberman wrote: >> Date: Fri, 5 Dec 2008 21:48:39 +0300 >> From: "Nikolay Tychina" >> Sender: owner-freebsd-acpi@freebsd.org >> >> We are really appreciate you for release, but we can't use it. >> How do i compile it for my FreeBSD 7.1-PRERELEASE ? >> >> (http://forums.freebsd.org/showthread.php?t=632, somebody needs it too :) ) > > Unless you are a good FreeBSD hacker, you don't. In a bit of time, > depending on just how busy some folks are, it will be integrated into > the head and, after some testing, MFCed to RELENG_7. > > I expect it will be there for 7.2, but it's way too late to make it for > 7.1. If you run RELENG_7, it may not be too long before it shows up. Please do not harass Robert. He is an Intel developer only and is just making a courtesy announcement on the FreeBSD forums since we use his code. Some acpi-ca releases are not suitable for integration (think of them like FreeBSD-current). They need to be integrated, a patch built and tested, etc. before even being committed to HEAD. If a FreeBSD committer is interested in helping us do that process more regularly, see src/sys/contrib/dev/acpica/acpica_prep.sh for starters. But remember, you'll often have to implement new kernel APIs to support the different behavior of new acpi-ca versions. It's not just a matter of committing the code. -- Nate From jkim at FreeBSD.org Fri Dec 5 11:43:13 2008 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Fri Dec 5 11:43:20 2008 Subject: ACPICA version 20081204 released In-Reply-To: <49397BC1.7050505@root.org> References: <20081205185934.355784501A@ptavv.es.net> <49397BC1.7050505@root.org> Message-ID: <200812051443.03637.jkim@FreeBSD.org> On Friday 05 December 2008 02:06 pm, Nate Lawson wrote: > Kevin Oberman wrote: > >> Date: Fri, 5 Dec 2008 21:48:39 +0300 > >> From: "Nikolay Tychina" > >> Sender: owner-freebsd-acpi@freebsd.org > >> > >> We are really appreciate you for release, but we can't use it. > >> How do i compile it for my FreeBSD 7.1-PRERELEASE ? > >> > >> (http://forums.freebsd.org/showthread.php?t=632, somebody needs > >> it too :) ) > > > > Unless you are a good FreeBSD hacker, you don't. In a bit of > > time, depending on just how busy some folks are, it will be > > integrated into the head and, after some testing, MFCed to > > RELENG_7. > > > > I expect it will be there for 7.2, but it's way too late to make > > it for 7.1. If you run RELENG_7, it may not be too long before it > > shows up. > > Please do not harass Robert. He is an Intel developer only and is > just making a courtesy announcement on the FreeBSD forums since we > use his code. [Removed CC] > Some acpi-ca releases are not suitable for integration (think of > them like FreeBSD-current). They need to be integrated, a patch > built and tested, etc. before even being committed to HEAD. If a > FreeBSD committer is interested in helping us do that process more > regularly, see src/sys/contrib/dev/acpica/acpica_prep.sh for > starters. But remember, you'll often have to implement new kernel > APIs to support the different behavior of new acpi-ca versions. > It's not just a matter of committing the code. I have been updating ACPI-CA patchsets regualarly but it is becoming harder and harder because of API changes from both FreeBSD and ACPI-CA. http://people.freebsd.org/~jkim/acpica-import-.diff.gz Note these patches are generated from my desktop with "HEAD of the day" source + bunch of local patches. I always try to clean up unnecessary changes but they are not in committable forms nor properly reviewed. I briefly looked at the changes in this release, too. It seems I need some free time to digest and implement new OSL APIs for it. :-( Jung-uk Kim From jkim at FreeBSD.org Fri Dec 5 14:16:29 2008 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Fri Dec 5 14:16:35 2008 Subject: ACPICA version 20081204 released In-Reply-To: <200812051443.03637.jkim@FreeBSD.org> References: <20081205185934.355784501A@ptavv.es.net> <49397BC1.7050505@root.org> <200812051443.03637.jkim@FreeBSD.org> Message-ID: <200812051716.17441.jkim@FreeBSD.org> On Friday 05 December 2008 02:42 pm, Jung-uk Kim wrote: > On Friday 05 December 2008 02:06 pm, Nate Lawson wrote: > > Kevin Oberman wrote: > > >> Date: Fri, 5 Dec 2008 21:48:39 +0300 > > >> From: "Nikolay Tychina" > > >> Sender: owner-freebsd-acpi@freebsd.org > > >> > > >> We are really appreciate you for release, but we can't use it. > > >> How do i compile it for my FreeBSD 7.1-PRERELEASE ? > > >> > > >> (http://forums.freebsd.org/showthread.php?t=632, somebody > > >> needs it too :) ) > > > > > > Unless you are a good FreeBSD hacker, you don't. In a bit of > > > time, depending on just how busy some folks are, it will be > > > integrated into the head and, after some testing, MFCed to > > > RELENG_7. > > > > > > I expect it will be there for 7.2, but it's way too late to > > > make it for 7.1. If you run RELENG_7, it may not be too long > > > before it shows up. > > > > Please do not harass Robert. He is an Intel developer only and > > is just making a courtesy announcement on the FreeBSD forums > > since we use his code. > > [Removed CC] > > > Some acpi-ca releases are not suitable for integration (think of > > them like FreeBSD-current). They need to be integrated, a patch > > built and tested, etc. before even being committed to HEAD. If a > > FreeBSD committer is interested in helping us do that process > > more regularly, see src/sys/contrib/dev/acpica/acpica_prep.sh for > > starters. But remember, you'll often have to implement new > > kernel APIs to support the different behavior of new acpi-ca > > versions. It's not just a matter of committing the code. > > I have been updating ACPI-CA patchsets regualarly but it is > becoming harder and harder because of API changes from both FreeBSD > and ACPI-CA. > > http://people.freebsd.org/~jkim/acpica-import-.diff >.gz > > Note these patches are generated from my desktop with "HEAD of the > day" source + bunch of local patches. I always try to clean up > unnecessary changes but they are not in committable forms nor > properly reviewed. > > I briefly looked at the changes in this release, too. It seems I > need some free time to digest and implement new OSL APIs for it. > :-( Robert just let me know that there is no OSL change, actually. So, I just went ahead and updated it: http://people.freebsd.org/~jkim/acpica-import-20081204.diff.gz Thanks, Robert! Jung-uk Kim From ivakras1 at gmail.com Fri Dec 5 16:15:10 2008 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Fri Dec 5 16:15:16 2008 Subject: ACPICA version 20081204 released In-Reply-To: <200812051716.17441.jkim@FreeBSD.org> References: <20081205185934.355784501A@ptavv.es.net> <200812051443.03637.jkim@FreeBSD.org> <200812051716.17441.jkim@FreeBSD.org> Message-ID: <200812060315.05370.ivakras1@gmail.com> On Saturday 06 December 2008 01:16:03 Jung-uk Kim wrote: > > Robert just let me know that there is no OSL change, actually. So, I > just went ahead and updated it: > > http://people.freebsd.org/~jkim/acpica-import-20081204.diff.gz > > Thanks, Robert! > > Jung-uk Kim Is it for HEAD only? I'm running RELENG_7, could it be used for me? Thanks for answers, Kim! From unga888 at yahoo.com Sat Dec 6 21:53:25 2008 From: unga888 at yahoo.com (Unga) Date: Sat Dec 6 21:53:31 2008 Subject: shutdown does not power down Message-ID: <297791.94053.qm@web57005.mail.re3.yahoo.com> Hi I'm using RELENG_7 on i386. I noticed recently that "shutdown -p now" does not switch off the computer. I'm trying to understand how does the /sbin/shutdown performs a power down. I had a detailed look at the source code involved but find it difficult to see how. The program flow seems to be is as follows: shutdown => [/sbin/init or /sbin/halt] => reboot() => boot() => shutdown_final => shutdown_halt() => cpu_halt() Could you guys help me to identify how does shutdown request a power down. Many thanks in advance. Unga From peterjeremy at optushome.com.au Sun Dec 7 09:55:27 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sun Dec 7 09:55:34 2008 Subject: shutdown does not power down In-Reply-To: <297791.94053.qm@web57005.mail.re3.yahoo.com> References: <297791.94053.qm@web57005.mail.re3.yahoo.com> Message-ID: <20081207175523.GS58682@server.vk2pj.dyndns.org> On 2008-Dec-06 21:26:43 -0800, Unga wrote: >Could you guys help me to identify how does shutdown request a power down. It's done using ACPI. Look in acpi_shutdown_final(). -- 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/20081207/d6a473af/attachment.pgp From bugmaster at FreeBSD.org Mon Dec 8 03:06:51 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 8 03:07:07 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200812081106.mB8B6o80014159@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 nealhogan at gmail.com Mon Dec 8 13:53:42 2008 From: nealhogan at gmail.com (Neal Hogan) Date: Mon Dec 8 13:53:49 2008 Subject: boot hang with 7.1BETA2 (12/08) an no wifi Message-ID: Hi, I'm new to fBSD and recently installed 7.0 on my HP pavillion ze4400 (multiboot w/ XP). It appeared to work fine. I had it on there for several weeks and was just snooping around. Well, I attempted to upgrade to 7.1 prerelease. I used *freebsd-update upgrade -r 7.1-BETA2* and it seemed to work. However, when I reboot the system is hung after the the following line: pci1: on pcib1. I reboot with ACPI disabled and it boot fine. Below is my dmesg. Also, my wifi card doesn't work and I don't see it in the dmesg. The same was true of 7.0. This computer is older than my interest in *BSD. So, I don't know what card it has. Note that it works under XP. Thanks. 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.1-PRERELEASE-p1 #0: Mon Nov 24 11:49:24 UTC 2008 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: mobile AMD Athlon(tm) XP2400+ (1788.94-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383f9ff AMD Features=0xc0480800 real memory = 468647936 (446 MB) avail memory = 444547072 (423 MB) kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) pcib0: pcibus 0 on motherboard pir0: on motherboard $PIR: Using invalid BIOS IRQ 5 from 0.10.INTA for link 0x6 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x9000-0x90ff mem 0xe0000000-0xefffffff,0xd0100000-0xd010ffff irq 10 at device 5.0 on pci1 ohci0: mem 0xd0006000-0xd0006fff irq 9 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 4 ports with 4 removable, self powered pcm0: port 0x8400-0x84ff mem 0xd0007000-0xd0007fff irq 5 at device 6.0 on pci0 pcm0: pcm0: [GIANT-LOCKED] pcm0: [ITHREAD] isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 8.0 (no driver attached) pci0: at device 9.0 (no driver attached) cbb0: mem 0x80000000-0x80000fff irq 5 at device 10.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [ITHREAD] fwohci0: mem 0xd0009000-0xd00097ff,0xd0000000-0xd0003fff irq 10 at device 12.0 on pci0 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:0d:9d:71:9e:43:0c:6a fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:0d:9d:43:0c:6a fwe0: Ethernet address: 02:0d:9d:43:0c:6a fwip0: on firewire0 fwip0: Firewire address: 00:0d:9d:71:9e:43:0c:6a @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x12c0000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8080-0x808f at device 16.0 on pci0 atapci0: using PIO transfers above 137GB as workaround for 48bit DMA access bug, expect reduced performance ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 17.0 (no driver attached) sis0: port 0x8c00-0x8cff mem 0xd000a000-0xd000afff irq 11 at device 18.0 on pci0 sis0: Silicon Revision: DP83816A miibus0: on sis0 nsphyter0: PHY 0 on miibus0 nsphyter0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:0d:9d:43:2b:a7 sis0: [ITHREAD] cpu0 on motherboard powernow0: on cpu0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcefff,0xcf000-0xcf7ff,0xdb000-0xdbfff,0xdc000-0xdffff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FILTER] ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (memory) unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) ums0: on uhub0 ums0: 16 buttons and Z dir. umass0: on uhub0 Timecounter "TSC" frequency 1788940177 Hz quality 800 Timecounters tick every 1.000 msec firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ad0: 95396MB at ata0-master UDMA100 acd0: CDRW at ata1-master UDMA33 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 246MB (503808 512 byte sectors: 64H 32S/T 246C) Trying to mount root from ufs:/dev/ad0s2a WARNING: / was not properly dismounted WARNING: /usr was not properly dismounted /usr: mount pending error: blocks 56 files 2 WARNING: /var was not properly dismounted -- www.nealhogan.net From unga888 at yahoo.com Tue Dec 9 06:14:59 2008 From: unga888 at yahoo.com (Unga) Date: Tue Dec 9 06:15:05 2008 Subject: shutdown does not power down In-Reply-To: <297791.94053.qm@web57005.mail.re3.yahoo.com> Message-ID: <435143.84625.qm@web57005.mail.re3.yahoo.com> --- On Sun, 12/7/08, Unga wrote: > From: Unga > Subject: shutdown does not power down > To: freebsd-acpi@freebsd.org > Date: Sunday, December 7, 2008, 1:26 PM > Hi > > I'm using RELENG_7 on i386. > > I noticed recently that "shutdown -p now" does > not switch off the computer. > > I'm trying to understand how does the /sbin/shutdown > performs a power down. I had a detailed look at the source > code involved but find it difficult to see how. > After studying the ACPI, I realized that acpi_shutdown_final() doesn't get registered to "shutdown_final" event due to the fact /dev/acpi is missing. Therefore, the acpi_shutdown_final() doesn't executed when shutdown. I'm not sure why the /dev/acpi is not getting created by devfs. Appreciate if could give your ideas. Best regards Unga From nate at root.org Tue Dec 9 09:04:12 2008 From: nate at root.org (Nate Lawson) Date: Tue Dec 9 09:04:19 2008 Subject: shutdown does not power down In-Reply-To: <435143.84625.qm@web57005.mail.re3.yahoo.com> References: <435143.84625.qm@web57005.mail.re3.yahoo.com> Message-ID: <493EA50B.6000001@root.org> Unga wrote: > --- On Sun, 12/7/08, Unga wrote: > >> From: Unga >> Subject: shutdown does not power down >> To: freebsd-acpi@freebsd.org >> Date: Sunday, December 7, 2008, 1:26 PM >> Hi >> >> I'm using RELENG_7 on i386. >> >> I noticed recently that "shutdown -p now" does >> not switch off the computer. >> >> I'm trying to understand how does the /sbin/shutdown >> performs a power down. I had a detailed look at the source >> code involved but find it difficult to see how. >> > > After studying the ACPI, I realized that acpi_shutdown_final() doesn't get registered to "shutdown_final" event due to the fact /dev/acpi is missing. Therefore, the acpi_shutdown_final() doesn't executed when shutdown. > > I'm not sure why the /dev/acpi is not getting created by devfs. Appreciate if could give your ideas. Are you sure devfs is not just hiding it since it wasn't used yet? devfs unhide or touch /dev/acpi would probably reveal it. -- Nate From peterjeremy at optushome.com.au Tue Dec 9 10:02:41 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Tue Dec 9 10:02:47 2008 Subject: shutdown does not power down In-Reply-To: <435143.84625.qm@web57005.mail.re3.yahoo.com> References: <297791.94053.qm@web57005.mail.re3.yahoo.com> <435143.84625.qm@web57005.mail.re3.yahoo.com> Message-ID: <20081209180237.GA58682@server.vk2pj.dyndns.org> On 2008-Dec-09 06:14:58 -0800, Unga wrote: >After studying the ACPI, I realized that acpi_shutdown_final() >doesn't get registered to "shutdown_final" event due to the fact >/dev/acpi is missing. Therefore, the acpi_shutdown_final() doesn't >executed when shutdown. I'm not sure why the /dev/acpi is not >getting created by devfs. Are you sure ACPI is attaching? Does kldstat report 'acpi.ko'? Do you have an 'acpi0' device in your /var/run/dmesg.boot (and not have any ACPI-related errors in the probe messages)? Do you have a hw.acpi sysctl tree? -- 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/20081209/06a07add/attachment.pgp From unga888 at yahoo.com Tue Dec 9 22:51:22 2008 From: unga888 at yahoo.com (Unga) Date: Tue Dec 9 22:51:28 2008 Subject: shutdown does not power down In-Reply-To: <493EA50B.6000001@root.org> Message-ID: <11893.33156.qm@web57005.mail.re3.yahoo.com> --- On Wed, 12/10/08, Nate Lawson wrote: > Are you sure devfs is not just hiding it since it > wasn't used yet? > devfs unhide or touch /dev/acpi would probably reveal it. > 1) touch /dev/acpi Operation not supported 2) devfs unhide I did following but still /dev/acpi does not appear: /etc/devfs.rules [acpirules=10] add path acpi unhide /etc/rc.conf devfs_system_ruleset="acpirules" --- On Wed, 12/10/08, Peter Jeremy wrote: > Are you sure ACPI is attaching? Not sure. but sysctl -a | grep acpi shows lot of acpi info sysctl hw.acpi sysctl: unknown oid 'hw.acpi' > Does kldstat report 'acpi.ko'? Yes > Do you have an 'acpi0' device in your > /var/run/dmesg.boot (and > not have any ACPI-related errors in the probe messages)? No acpi0. No acpi word in the log. > Do you have a hw.acpi sysctl tree? > No. Best regards Unga From nate at root.org Wed Dec 10 08:21:25 2008 From: nate at root.org (Nate Lawson) Date: Wed Dec 10 08:21:47 2008 Subject: shutdown does not power down In-Reply-To: <11893.33156.qm@web57005.mail.re3.yahoo.com> References: <11893.33156.qm@web57005.mail.re3.yahoo.com> Message-ID: <493FEC84.10705@root.org> Unga wrote: > --- On Wed, 12/10/08, Nate Lawson wrote: >> Are you sure devfs is not just hiding it since it >> wasn't used yet? >> devfs unhide or touch /dev/acpi would probably reveal it. >> > >> Are you sure ACPI is attaching? > Not sure. but > sysctl -a | grep acpi > shows lot of acpi info > > sysctl hw.acpi > sysctl: unknown oid 'hw.acpi' Just post the output of dmesg after booting. -- Nate From jkim at FreeBSD.org Wed Dec 10 18:20:14 2008 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Wed Dec 10 18:20:21 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <49358684.7010508@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <200812021243.08513.jkim@FreeBSD.org> <49358684.7010508@FreeBSD.org> Message-ID: <200812102120.03788.jkim@FreeBSD.org> On Tuesday 02 December 2008 02:03 pm, Alexander Motin wrote: > Hi. > > Jung-uk Kim wrote: > >> Here is problems I still have now: > >> - SMP kernel resume is not working, system reboots while doing > >> acpi_wakeup_cpus(); > > > > My dual-core CPU seems to resume okay but quite unstable. Can > > you try something like the following in amd64/mp_machdep.c and > > tell me if it helps? > > > > ------------ > > @@ -57,6 +57,7 @@ > > #include > > > > #include > > +#include > > #include > > #include > > #include > > @@ -1121,6 +1121,8 @@ > > int cpumask = PCPU_GET(cpumask); > > > > if (savectx2(&stopxpcbs[cpu])) { > > + /* Flush CPU cache. */ > > + wbinvd(); > > /* Indicate that we are suspended. */ > > atomic_set_int(&stopped_cpus, cpumask); > > } else { > > ------------ > > Wow, it works! > > I am writing this letter just after suspending/resuming my > dual-core C2D system 4 times straight. Music plays, USB, SATA, all > other hardware works fine. What kind of instability do you have? > > The only strange effect I have noticed was incorrect CPU time some > processes got: > %ps ax > PID TT STAT TIME COMMAND > 12 ?? WL 280503:38,05 [intr] > 1430 ?? Ss 280503:38,34 icewm > > But I think it is more timer driver related then resume itself. > > > Thanks for the feedback! > > Many thanks to you! I hope this long-waited feature will be > finished! FYI, I uploaded a new patch with some fixes (against today's CURRENT): http://people.freebsd.org/~jkim/amd64_suspend.diff This patch should be feature complete but I'd say it is still considered experimental as it is not properly reviewed. Now, some useful tips of the day for starters: Tip #1: Try 'sysctl debug.acpi.suspend_bounce=1" first. If it hangs, this patch won't do any good for you. Tip #2: Suspend/resume several times in single user mode first to be safe. I am sure you don't want to lose your data. ;-) Tip #3: If keyboard LEDs blink (keyboard reset) but nothing is displayed on screen, try 'sysctl hw.acpi.reset_video=1' next time. Tip #4: If #3 does not work for you, try 'vbetool post' (available from ports/sysutils/vbetool) next. It works better in some cases. Tip #5: With Xorg, it is always safe to suspend in console unless you have a hook in suspend script to do some magic. When you switch to console by pressing Ctrl+Alt+F[1-8], Xorg driver will save GPU states. After resume is complete, you can return to Xorg screen by pressing Alt-F9 later. Then, Xorg driver should restore GPU states and screen. Tip #6: If your mouse pointer does not move any more, try restarting moused by '/etc/rc.d/moused restart'. Cheers, Jung-uk Kim From linimon at FreeBSD.org Wed Dec 10 20:50:00 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Dec 10 20:50:11 2008 Subject: amd64/129563: [ACPI] sleep broken on IBM/Lenovo T61 [amd64] Message-ID: <200812110449.mBB4nxYF060492@freefall.freebsd.org> Synopsis: [ACPI] sleep broken on IBM/Lenovo T61 [amd64] Responsible-Changed-From-To: freebsd-amd64->freebsd-acpi Responsible-Changed-By: linimon Responsible-Changed-When: Thu Dec 11 04:49:48 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=129563 From unga888 at yahoo.com Wed Dec 10 23:14:15 2008 From: unga888 at yahoo.com (Unga) Date: Wed Dec 10 23:14:22 2008 Subject: shutdown does not power down In-Reply-To: <493FEC84.10705@root.org> Message-ID: <861568.47553.qm@web57008.mail.re3.yahoo.com> --- On Thu, 12/11/08, Nate Lawson wrote: > >> Are you sure devfs is not just hiding it since it > >> wasn't used yet? > >> devfs unhide or touch /dev/acpi would probably > reveal it. > >> > > > >> Are you sure ACPI is attaching? > > Not sure. but > > sysctl -a | grep acpi > > shows lot of acpi info > > > > sysctl hw.acpi > > sysctl: unknown oid 'hw.acpi' > > Just post the output of dmesg after booting. > Below is the dmesg verbose output. I earlier wrote that "sysctl -a | grep acpi" shows lot of lines, that's because I manually created the /dev/acpi node before booting. Since it's get hidden after mount the devfs and cannot unhide, I removed it. Now "sysctl -a | grep acpi" is empty. Please let me know if you need further information. I really want to understand what causing that /dev/acpi does not created. Best regards Unga =========================== dmesg output - verbose (boot -v) =========================== 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-STABLE #0: Wed Dec 10 13:37:07 SGT 2008 root@grey.lan:/usr/obj/usr/src/sys/MYKERNEL Preloaded elf kernel "/boot/kernel/kernel" at 0xc0cf4000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0cf4194. Calibrating clock(s) ... i8254 clock: 1193205 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 3028309532 Hz CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3028.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400 Logical CPUs per core: 2 Instruction TLB: 4 KB, 2 MB or 4 MB pages, fully associative, 64 entries Data TLB: 4 KB or 4 MB pages, fully associative, 64 entries 1st-level data cache: 8 KB, 4-way set associative, sectored cache, 64 byte line size Trace cache: 12K-uops, 8-way set associative 2nd-level cache: 512 KB, 8-way set associative, sectored cache, 64 byte line size real memory = 1610547200 (1535 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001025000 - 0x000000005e4a3fff, 1564995584 bytes (382079 pages) avail memory = 1564483584 (1492 MB) MP Configuration Table version 1.4 found at 0xc00f5bc0 APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) MPTable: bios32: Found BIOS32 Service Directory header at 0xc00fdb50 bios32: Entry = 0xfdb60 (c00fdb60) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xdb81 pnpbios: Found PnP BIOS data at 0xc00f7020 pnpbios: Entry = f0000:5e0b Rev = 1.0 Other BIOS signatures found: ULE: setup cpu group 0 ULE: setup cpu 0 ULE: adding cpu 0 to group 0: cpus 1 mask 0x1 ioapic0: Assuming intbase of 0 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: Routing IRQ 0 -> intpin 2 lapic: Routing ExtINT -> LINT0 lapic: Routing NMI -> LINT1 ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x0001000f pcm: 0x00010000 wlan_amrr: wlan: <802.11 Link Layer> ath_rate: version 1.2 null: random: nfslock: pseudo-device io: kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support enabled ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Dec 10 2008 13:36:44) npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x80000090 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=25708086) pcibios: BIOS version 2.10 pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x2570, revid=0x02 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) map[10]: type Prefetchable Memory, range 32, base 0xf8000000, size 26, enabled found-> vendor=0x8086, dev=0x2571, revid=0x02 domain=0, bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x0d (3250 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x24d2, 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=11 map[20]: type I/O Port, range 32, base 0xe000, size 5, enabled pcib0: slot 29 INTA routed to irq 16 found-> vendor=0x8086, dev=0x24d4, 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=5 map[20]: type I/O Port, range 32, base 0xe400, size 5, enabled pcib0: slot 29 INTB routed to irq 19 found-> vendor=0x8086, dev=0x24d7, 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=5 map[20]: type I/O Port, range 32, base 0xe800, size 5, enabled pcib0: slot 29 INTC routed to irq 18 found-> vendor=0x8086, dev=0x24de, 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=a, irq=11 map[20]: type I/O Port, range 32, base 0xec00, size 5, enabled pcib0: slot 29 INTA routed to irq 16 found-> vendor=0x8086, dev=0x24dd, 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=d, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xfebff800, size 10, enabled pcib0: slot 29 INTD routed to irq 23 found-> vendor=0x8086, dev=0x244e, revid=0xc2 domain=0, bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x8080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x24d0, revid=0x02 domain=0, bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x24d1, revid=0x02 domain=0, bus=0, slot=31, func=2 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02a8, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type I/O Port, range 32, base 0xfc00, size 4, enabled found-> vendor=0x8086, dev=0x24d3, 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=11 map[20]: type I/O Port, range 32, base 0xc00, size 5, enabled pcib0: slot 31 INTB routed to irq 17 agp0: on hostb0 hostb0: Reserved 0x4000000 bytes for rid 0x10 type 3 at 0xf8000000 agp0: allocating GATT for aperture of size 64M pcib1: at device 1.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xfc900000-0xfe9fffff pcib1: prefetched decode 0xe7f00000-0xf7efffff pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x10de, dev=0x0322, revid=0xa1 domain=0, bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x05 (1250 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xfd000000, size 24, enabled pcib1: requested memory range 0xfd000000-0xfdffffff: good map[14]: type Prefetchable Memory, range 32, base 0xe8000000, size 27, enabled pcib1: requested memory range 0xe8000000-0xefffffff: good pcib1: slot 0 INTA routed to irq 16 vgapci0: mem 0xfd000000-0xfdffffff,0xe8000000-0xefffffff irq 16 at device 0.0 on pci1 uhci0: port 0xe000-0xe01f irq 16 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe000 ioapic0: routing intpin 16 (PCI IRQ 16) to vector 48 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 0xe400-0xe41f irq 19 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe400 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 49 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 0xe800-0xe81f irq 18 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xe800 ioapic0: routing intpin 18 (PCI IRQ 18) to vector 50 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 0xec00-0xec1f irq 16 at device 29.3 on pci0 uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0xec00 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 0xfebff800-0xfebffbff irq 23 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xfebff800 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 51 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 pcib2: at device 30.0 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xc000-0xcfff pcib2: memory decode 0xfea00000-0xfeafffff pcib2: no prefetched decode pcib2: Subtractively decoded bridge. pci2: on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x1412, dev=0x1724, revid=0x01 domain=0, bus=2, slot=2, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 1 supports D0 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xcc00, size 5, enabled pcib2: requested I/O range 0xcc00-0xcc1f: in range map[14]: type I/O Port, range 32, base 0xc800, size 7, enabled pcib2: requested I/O range 0xc800-0xc87f: in range pcib2: slot 2 INTA routed to irq 18 found-> vendor=0x1737, dev=0x1032, revid=0x10 domain=0, bus=2, slot=3, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x20 (8000 ns), maxlat=0x40 (16000 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type I/O Port, range 32, base 0xc400, size 8, enabled pcib2: requested I/O range 0xc400-0xc4ff: in range map[14]: type Memory, range 32, base 0xfeafff00, size 8, enabled pcib2: requested memory range 0xfeafff00-0xfeafffff: good pcib2: slot 3 INTA routed to irq 19 pci2: at device 2.0 (no driver attached) re0: port 0xc400-0xc4ff mem 0xfeafff00-0xfeafffff irq 19 at device 3.0 on pci2 re0: Reserved 0x100 bytes for rid 0x14 type 3 at 0xfeafff00 re0: Chip rev. 0x04000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: bpf attached re0: Ethernet address: 00:18:f8:0f:8e:ab re0: [MPSAFE] re0: [FILTER] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfc00 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 52 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 53 ata1: [MPSAFE] ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) cpu0 on motherboard p4tcc0: on cpu0 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 ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed ex_isa_identify() ata: ata0 already exists; skipping it ata: ata1 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 pnpbios: 15 devices, largest 126 bytes PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: adding io range 0x22-0x22, size=0x1, align=0x1 PNP0a03: adding io range 0x72-0x75, size=0x4, align=0x1 PNP0a03: adding io range 0x290-0x297, size=0x8, align=0x1 PNP0a03: adding io range 0x400-0x43f, size=0x40, align=0x1 PNP0a03: adding io range 0x800-0x87f, size=0x80, align=0x1 PNP0a03: adding io range 0x2e-0x2e, size=0x1, align=0x1 PNP0a03: adding io range 0x2f-0x2f, size=0x1, align=0x1 pnpbios: handle 0 device ID PNP0a03 (030ad041) PNP0c01: adding fixed memory32 range 0-0x9fbff, size=0x9fc00 PNP0c01: adding fixed memory32 range 0x9fc00-0x9ffff, size=0x400 PNP0c01: adding fixed memory32 range 0xf0000-0xfffff, size=0x10000 PNP0c01: adding fixed memory32 range 0x100000-0x5ffeffff, size=0x5fef0000 PNP0c01: adding fixed memory32 range 0x5fff0000-0x5fff7fff, size=0x8000 PNP0c01: adding fixed memory32 range 0x5fff8000-0x5fffffff, size=0x8000 PNP0c01: adding fixed memory32 range 0xfec00000-0xfec00fff, size=0x1000 PNP0c01: adding fixed memory32 range 0xfee00000-0xfee00fff, size=0x1000 PNP0c01: adding fixed memory32 range 0xfff00000-0xffffffff, size=0x100000 pnpbios: handle 1 device ID PNP0c01 (010cd041) PNP0200: adding dma mask 0x10 PNP0200: adding fixed io range 0-0xf, size=0x10, align=0x1 PNP0200: adding fixed io range 0x80-0x90, size=0x11, align=0x1 PNP0200: adding fixed io range 0x94-0x9f, size=0xc, align=0x1 PNP0200: adding fixed io range 0xc0-0xde, size=0x1f, align=0x1 pnpbios: handle 3 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding fixed io range 0x40-0x43, size=0x4, align=0x1 pnpbios: handle 4 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding fixed io range 0x70-0x71, size=0x2, align=0x1 pnpbios: handle 5 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding fixed io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding fixed io range 0x64-0x64, size=0x1, align=0x1 pnpbios: handle 6 device ID PNP0303 (0303d041) PNP0800: adding fixed io range 0x61-0x61, size=0x1, align=0x1 pnpbios: handle 7 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding fixed io range 0xf0-0xff, size=0x10, align=0x1 pnpbios: handle 8 device ID PNP0c04 (040cd041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x10 pnpbios: handle 9 device ID PNP0501 (0105d041) PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x8 pnpbios: handle 10 device ID PNP0501 (0105d041) PNP0400: adding io range 0x378-0x37f, size=0x8, align=0x4 PNP0400: adding irq mask 0x80 pnpbios: handle 11 device ID PNP0400 (0004d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x4 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 pnpbios: handle 12 device ID PNP0700 (0007d041) INT0800: adding fixed memory32 range 0xffb80000-0xffbfffff, size=0x80000 pnpbios: handle 13 device ID INT0800 (0008d425) PNP0f13: adding irq mask 0x1000 pnpbios: handle 14 device ID PNP0f13 (130fd041) sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcf7ff,0xe0000-0xe0fff pnpid ORM0000 on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) atkbdc0: at port 0x60,0x64 on isa0 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 54 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: current command byte:0065 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to vector 55 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 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 found at 0x378 ppc0: using extended I/O port range ppc0: SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ioapic0: routing intpin 7 (ISA IRQ 7) to vector 56 ppbus0: [MPSAFE] ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x4001 0x4011 0x4001 0x4001 sio0: irq maps: 0x4001 0x4011 0x4001 0x4001 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ioapic0: routing intpin 4 (ISA IRQ 4) to vector 57 sio0: [FILTER] sio1: irq maps: 0x4001 0x4009 0x4001 0x4001 sio1: irq maps: 0x4001 0x4009 0x4001 0x4001 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ioapic0: routing intpin 3 (ISA IRQ 3) to vector 58 sio1: [FILTER] 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 unknown: can't assign resources (memory) unknown: at iomem 0-0x9fbff pnpid PNP0c01 on isa0 unknown: can't assign resources (port) unknown: at port 0x60 pnpid PNP0303 on isa0 unknown: failed to probe at port 0x61 pnpid PNP0800 on isa0 unknown: can't assign resources (port) unknown: at port 0x3f8-0x3ff pnpid PNP0501 on isa0 unknown: can't assign resources (port) unknown: at port 0x2f8-0x2ff pnpid PNP0501 on isa0 unknown: can't assign resources (port) unknown: at port 0x378-0x37f pnpid PNP0400 on isa0 unknown: failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 pnpid PNP0700 on isa0 unknown: failed to probe at iomem 0xffb80000-0xffbfffff pnpid INT0800 on isa0 unknown: can't assign resources (irq) unknown: at irq 12 pnpid PNP0f13 on isa0 Device configuration finished. Reducing kern.maxvnodes 101915 -> 100000 procfs registered lapic: Divisor 2, Frequency 100943666 hz Timecounter "TSC" frequency 3028309532 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached hptrr: no controller detected. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire ad0: 78533MB at ata0-master UDMA100 ad0: 160836480 sectors [39420C/16H/255S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 ad0: Intel check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad2: 238475MB at ata1-master SATA150 ad2: 488397168 sectors [119705C/16H/255S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad2 ad2: Intel check1 failed ad2: Adaptec check1 failed ad2: LSI (v3) check1 failed ad2: LSI (v2) check1 failed ad2: FreeBSD check1 failed ATA PseudoRAID loaded Trying to mount root from ufs:/dev/ad2s1a start_init: trying /sbin/init =========================== End of dmesg output - verbose =========================== From yanefbsd at gmail.com Thu Dec 11 01:20:03 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 11 01:20:10 2008 Subject: amd64/129563: [ACPI] sleep broken on IBM/Lenovo T61 [amd64] Message-ID: <200812110920.mBB9K3Ve099619@freefall.freebsd.org> The following reply was made to PR kern/129563; it has been noted by GNATS. From: "Garrett Cooper" To: bug-followup@freebsd.org, gallasch@free.de Cc: Subject: Re: amd64/129563: [ACPI] sleep broken on IBM/Lenovo T61 [amd64] Date: Thu, 11 Dec 2008 01:14:54 -0800 This also occurs on i386 as well and is a documented issue. Please keep me in the correspondence mailings because I have a vested interest in this. Thanks! -Garrett From yanefbsd at gmail.com Thu Dec 11 01:34:23 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Thu Dec 11 01:34:30 2008 Subject: shutdown does not power down In-Reply-To: <861568.47553.qm@web57008.mail.re3.yahoo.com> References: <493FEC84.10705@root.org> <861568.47553.qm@web57008.mail.re3.yahoo.com> Message-ID: <7d6fde3d0812110107k71b19c94g2b80bba0b90cc47d@mail.gmail.com> On Wed, Dec 10, 2008 at 11:14 PM, Unga wrote: > --- On Thu, 12/11/08, Nate Lawson wrote: > >> >> Are you sure devfs is not just hiding it since it >> >> wasn't used yet? >> >> devfs unhide or touch /dev/acpi would probably >> reveal it. >> >> >> > >> >> Are you sure ACPI is attaching? >> > Not sure. but >> > sysctl -a | grep acpi >> > shows lot of acpi info >> > >> > sysctl hw.acpi >> > sysctl: unknown oid 'hw.acpi' >> >> Just post the output of dmesg after booting. >> > > Below is the dmesg verbose output. > > I earlier wrote that "sysctl -a | grep acpi" shows lot of lines, that's because I manually created the /dev/acpi node before booting. Since it's get hidden after mount the devfs and cannot unhide, I removed it. Now "sysctl -a | grep acpi" is empty. > > Please let me know if you need further information. I really want to understand what causing that /dev/acpi does not created. > > Best regards > Unga [ snip ] Have you tried compiling ACPI into the kernel? I do that at least and it works for me. I noticed that no one asked what kind of hardware you have. Also, here's my output (just as a working reference; I use 8-CURRENT): [gcooper@optimus /scratch]$ clear; dmesg | grep ^acpi acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cff00000 (3) failed acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 acpi_button0: on acpi0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cff00000 (3) failed acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 acpi_button0: on acpi0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cff00000 (3) failed acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 acpi_button0: on acpi0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cff00000 (3) failed acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 acpi_button0: on acpi0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, cff00000 (3) failed acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 acpi_button0: on acpi0 From unga888 at yahoo.com Thu Dec 11 02:35:17 2008 From: unga888 at yahoo.com (Unga) Date: Thu Dec 11 02:35:24 2008 Subject: shutdown does not power down In-Reply-To: <7d6fde3d0812110107k71b19c94g2b80bba0b90cc47d@mail.gmail.com> Message-ID: <361944.84545.qm@web57004.mail.re3.yahoo.com> --- On Thu, 12/11/08, Garrett Cooper wrote: > Have you tried compiling ACPI into the kernel? I do that at > least and it works for me. No. How could I do it? > > I noticed that no one asked what kind of hardware you have. This is Intel P4 3GHz desktop. I have two hard disks (SATA) fixed into this computer and on the first one, FreeBSD 7.0 and on the second, FreeBSD RELENG_7. When boot to first hard disk, the FreeBSD 7.0, the shutdown power off without any issue. My problem is with the second one, RELENG_7, which I do lot of experimentation. The RELENG_7 OS seems to run well. I do not see any other issue. I'm beginning to feel something required to get ACPI up is missing or accidentally got deleted from the RELENG_7 disk. I found /dev/acpi is missing. What should be there in minimum to get the ACPI up and get registered properly? Regards Unga From mav at FreeBSD.org Thu Dec 11 03:10:04 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Dec 11 03:10:12 2008 Subject: kern/129563: [ACPI] sleep broken on IBM/Lenovo T61 [amd64] Message-ID: <200812111110.mBBBA3PC081935@freefall.freebsd.org> The following reply was made to PR kern/129563; it has been noted by GNATS. From: Alexander Motin To: bug-followup@FreeBSD.org, gallasch@free.de Cc: Subject: Re: kern/129563: [ACPI] sleep broken on IBM/Lenovo T61 [amd64] Date: Thu, 11 Dec 2008 12:03:54 +0200 There is no suspend/resume support for amd64 platform available in FreeBSD 7.1. Amd64 suspend/resume support on both UP and SMP is now in active development by Jung-uk Kim. Working patches for 8-CURRENT and discussion can be found on freebsd-acpi@ mailing list. From smithi at nimnet.asn.au Thu Dec 11 03:33:09 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Thu Dec 11 03:33:16 2008 Subject: shutdown does not power down In-Reply-To: <7d6fde3d0812110107k71b19c94g2b80bba0b90cc47d@mail.gmail.com> References: <493FEC84.10705@root.org> <861568.47553.qm@web57008.mail.re3.yahoo.com> <7d6fde3d0812110107k71b19c94g2b80bba0b90cc47d@mail.gmail.com> Message-ID: <20081211213129.S84425@sola.nimnet.asn.au> On Thu, 11 Dec 2008, Garrett Cooper wrote: > On Wed, Dec 10, 2008 at 11:14 PM, Unga wrote: > > --- On Thu, 12/11/08, Nate Lawson wrote: [..] > >> Just post the output of dmesg after booting. > > Below is the dmesg verbose output. Apart from loading acpi.ko straight after kernel, there's not a whiff of detecting - or failing to detect - acpi at all that I could spot. > > I earlier wrote that "sysctl -a | grep acpi" shows lot of lines, > > that's because I manually created the /dev/acpi node before booting. I don't understand this at all. I thought it was created by acpi (via devd?) on detecting the ACPI BIOS and having a rewarding chat with it? > > Since it's get hidden after mount the devfs and cannot unhide, I > > removed it. Now "sysctl -a | grep acpi" is empty. > > > > Please let me know if you need further information. I really want > > to understand what causing that /dev/acpi does not created. Looks just like what you might expect to see choosing to boot without acpi, except that it shows loading the module. Unga, what's in your /boot/loader.conf ? > [ snip ] > > Have you tried compiling ACPI into the kernel? I do that at least and > it works for me. Me too, but isn't that supposed not to matter nowadays? Or does that apply only to some modules, and perhaps not acpi? (genuine question) > I noticed that no one asked what kind of hardware you have. Or whether its BIOS is right up to date .. cheers, Ian From unga888 at yahoo.com Thu Dec 11 03:51:55 2008 From: unga888 at yahoo.com (Unga) Date: Thu Dec 11 03:52:01 2008 Subject: shutdown does not power down In-Reply-To: <20081211213129.S84425@sola.nimnet.asn.au> Message-ID: <573262.33587.qm@web57003.mail.re3.yahoo.com> --- On Thu, 12/11/08, Ian Smith wrote: > From: Ian Smith > Subject: Re: shutdown does not power down > To: "Garrett Cooper" > Cc: unga888@yahoo.com, freebsd-acpi@freebsd.org > Date: Thursday, December 11, 2008, 7:33 PM > On Thu, 11 Dec 2008, Garrett Cooper wrote: > > On Wed, Dec 10, 2008 at 11:14 PM, Unga > wrote: > > > --- On Thu, 12/11/08, Nate Lawson > wrote: > [..] > > >> Just post the output of dmesg after booting. > > > > Below is the dmesg verbose output. > > Apart from loading acpi.ko straight after kernel, > there's not a whiff of > detecting - or failing to detect - acpi at all that I could > spot. > > > > I earlier wrote that "sysctl -a | grep > acpi" shows lot of lines, > > > that's because I manually created the > /dev/acpi node before booting. > > I don't understand this at all. I thought it was > created by acpi (via > devd?) on detecting the ACPI BIOS and having a rewarding > chat with it? > Since no /dev/acpi node, I mounted the root partition and created an acpi node /mnt/dev using mknod. Once boot, I get lot of lines in "sysctl -a | grep acpi". Since that /dev/acpi later disappear, I removed it the same way I created it by mounting the root partition. > > > Since it's get hidden after mount the devfs > and cannot unhide, I > > > removed it. Now "sysctl -a | grep > acpi" is empty. > > > > > > Please let me know if you need further > information. I really want > > > to understand what causing that /dev/acpi does > not created. > > Looks just like what you might expect to see choosing to > boot without > acpi, except that it shows loading the module. > > Unga, what's in your /boot/loader.conf ? > Empty > > [ snip ] > > > > Have you tried compiling ACPI into the kernel? I do > that at least and > > it works for me. > > Me too, but isn't that supposed not to matter nowadays? > Or does that > apply only to some modules, and perhaps not acpi? (genuine > question) > > > I noticed that no one asked what kind of hardware you > have. Its mentioned in my previous mail. Its Intel P4. > > Or whether its BIOS is right up to date .. BIOS seems old, but for FreeBSD 7 its not an issue, shutdown can power off. Its my second disk running FreeBSD RELENG_7 having a problem. Both versions are basically the same code, acpi code is identical, the problematic FreeBSD RELENG_7 is more evolved with various software updates. Regards Unga From dan at obluda.cz Thu Dec 11 03:54:06 2008 From: dan at obluda.cz (Dan Lukes) Date: Thu Dec 11 03:54:13 2008 Subject: shutdown does not power down In-Reply-To: <20081211213129.S84425@sola.nimnet.asn.au> References: <493FEC84.10705@root.org> <861568.47553.qm@web57008.mail.re3.yahoo.com> <7d6fde3d0812110107k71b19c94g2b80bba0b90cc47d@mail.gmail.com> <20081211213129.S84425@sola.nimnet.asn.au> Message-ID: <4940FF59.3090904@obluda.cz> Ian Smith napsal/wrote, On 12/11/08 12:33: > Looks just like what you might expect to see choosing to boot without > acpi, except that it shows loading the module. > > Unga, what's in your /boot/loader.conf ? Unga's ... >>>>> Output of 'kenv' command (acpi - related lines only, selected by me) >>> acpi_load="YES" >>> hint.acpi.0.oem="AMI " >>> hint.acpi.0.revision="1" >>> hint.acpi.0.rsdp="0xf9e20" >>> hint.acpi.0.rsdt="0x5fff0000" >>> smbios.bios.reldate="08/18/2003" >>> smbios.bios.vendor="American Megatrends Inc." >>> smbios.bios.version="V1.4 " >>> smbios.planar.product="MS-6728" It seems the ACPI is not disabled. > Or whether its BIOS is right up to date .. Very far from up to date (current version is about 2.5). But it works for on 7.0-R... Dan From mav at FreeBSD.org Thu Dec 11 15:01:30 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Thu Dec 11 15:01:37 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <200812102120.03788.jkim@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <200812021243.08513.jkim@FreeBSD.org> <49358684.7010508@FreeBSD.org> <200812102120.03788.jkim@FreeBSD.org> Message-ID: <49419BB9.8030408@FreeBSD.org> Jung-uk Kim wrote: > FYI, I uploaded a new patch with some fixes (against today's CURRENT): > > http://people.freebsd.org/~jkim/amd64_suspend.diff It is still working for me. > This patch should be feature complete but I'd say it is still > considered experimental as it is not properly reviewed. This comment looks stale: /* Restore PAT and MTRRdefType. */ :) -- Alexander Motin From jkim at FreeBSD.org Thu Dec 11 15:17:43 2008 From: jkim at FreeBSD.org (Jung-uk Kim) Date: Thu Dec 11 15:17:49 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <49419BB9.8030408@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <200812102120.03788.jkim@FreeBSD.org> <49419BB9.8030408@FreeBSD.org> Message-ID: <200812111817.32334.jkim@FreeBSD.org> On Thursday 11 December 2008 06:01 pm, Alexander Motin wrote: > Jung-uk Kim wrote: > > FYI, I uploaded a new patch with some fixes (against today's > > CURRENT): > > > > http://people.freebsd.org/~jkim/amd64_suspend.diff > > It is still working for me. Good. > > This patch should be feature complete but I'd say it is still > > considered experimental as it is not properly reviewed. > > This comment looks stale: > /* Restore PAT and MTRRdefType. */ Corrected. Thanks for the feedback! Jung-uk Kim From gallasch at free.de Thu Dec 11 16:54:43 2008 From: gallasch at free.de (Kai Gallasch) Date: Thu Dec 11 16:54:51 2008 Subject: amd64/129563: [ACPI] sleep broken on IBM/Lenovo T61 [amd64] In-Reply-To: <200812110449.mBB4nxYF060492@freefall.freebsd.org> References: <200812110449.mBB4nxYF060492@freefall.freebsd.org> Message-ID: <14E18200-CB04-4196-BE61-BD2AB24C22A6@free.de> Am 11.12.2008 um 05:49 schrieb linimon@FreeBSD.org: > Synopsis: [ACPI] sleep broken on IBM/Lenovo T61 [amd64] > > Responsible-Changed-From-To: freebsd-amd64->freebsd-acpi > Responsible-Changed-By: linimon > Responsible-Changed-When: Thu Dec 11 04:49:48 UTC 2008 > Responsible-Changed-Why: > Over to maintainer(s). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=129563 > _______________________________________________ After reading Alexander Motin's Reply in the Audit Trail of the PR it looks like this PR can be closed. Seems there never was support for ACPI suspend in freebsd7.1-amd64 and I was mistaken. Dang! So, no nothing to "fix" here. Kai Gallasch. From unga888 at yahoo.com Fri Dec 12 06:40:26 2008 From: unga888 at yahoo.com (Unga) Date: Fri Dec 12 06:40:32 2008 Subject: shutdown does not power down In-Reply-To: <4940FF59.3090904@obluda.cz> Message-ID: <269230.94089.qm@web57004.mail.re3.yahoo.com> I tried to enable debugging on ACPI and see what happens. I did following: 1. make WITH_KDB=YES WITH_DDB=YES WITH_GDB=YES \ buildkernel KERNCONF=MYKERNEL 2. make WITH_KDB=YES WITH_DDB=YES WITH_GDB=YES \ installkernel KERNCONF=MYKERNEL 3. cd /sys/modules/acpi/acpi make clean make ACPI_DEBUG=1 make install But I still get following messages when loading acpi.ko: Preloaded elf kernel "/boot/kernel/kernel" at 0xc0d2a000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0d2a188. link_elf: symbol db_readline undefined KLD file acpi.ko - could not finalize loading How could I enable ACPI debugging on FreeBSD 7.0? Best regards Unga From remko at FreeBSD.org Sat Dec 13 10:08:29 2008 From: remko at FreeBSD.org (remko@FreeBSD.org) Date: Sat Dec 13 10:08:35 2008 Subject: kern/129618: Problem with ACPI on laptop Message-ID: <200812131808.mBDI8T15081284@freefall.freebsd.org> Synopsis: Problem with ACPI on laptop Responsible-Changed-From-To: freebsd-i386->freebsd-acpi Responsible-Changed-By: remko Responsible-Changed-When: Sat Dec 13 18:07:52 UTC 2008 Responsible-Changed-Why: Not that much info but it's acpi, reassign to the acpi team. http://www.freebsd.org/cgi/query-pr.cgi?pr=129618 From mav at FreeBSD.org Sat Dec 13 12:06:52 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Sat Dec 13 12:06:58 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <4944115C.5020403@lissyara.su> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su> Message-ID: <494415D8.4090904@FreeBSD.org> Alex Keda wrote: > I trie it with my HP Compaq 6715s > sleep OK, but after press power button, for wake up, i see blue screen, > and nothing... After hard reset, I have im /var/log/messages: > > Dec 13 22:35:19 acer acpi: suspend at 20081213 22:35:19 > Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 0, > val 32768) > Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 0, val > 0xffffffff) > Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 24, > val 0xffffffff) > Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 16, > val 0xffffffff) > Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 16, > val 0) > Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 23, > val 18) > Dec 13 22:35:31 acer kernel: bge0: RX CPU self-diagnostics failed! > Dec 13 22:35:31 acer kernel: bge0: flow-through queue init failed > Dec 13 22:35:31 acer kernel: bge0: initialization failure Just interesting, how hostname "acer" related to "HP Compaq 6715s"? It's just a coincidence? :) I have Acer TM6292 notebook with bge LAN. And my bge works fine after resume. The only specific of my notebook is that it's BIOS does not allocate resources for PCIe bridges. FreeBSD also unable to do it, so now I have to use dirty hack to initialize them. I think I have seen alike bge messages (but without reboot) when that hack was working only on boot, but not restoring PCIe bridges state on resume. > Dec 13 22:40:52 acer savecore: reboot after panic: page fault > Dec 13 22:40:52 acer savecore: writing core to vmcore.9 Core is good. May be it can be debugged? -- Alexander Motin From admin at lissyara.su Sat Dec 13 12:22:36 2008 From: admin at lissyara.su (Alex Keda) Date: Sat Dec 13 12:22:49 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: <4944115C.5020403@lissyara.su> Alexander Motin ?????: > 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 trie it with my HP Compaq 6715s sleep OK, but after press power button, for wake up, i see blue screen, and nothing... After hard reset, I have im /var/log/messages: Dec 13 22:35:19 acer acpi: suspend at 20081213 22:35:19 Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 0, val 32768) Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 0, val 0xffffffff) Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 24, val 0xffffffff) Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 16, val 0xffffffff) Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 16, val 0) Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 23, val 18) Dec 13 22:35:31 acer kernel: bge0: RX CPU self-diagnostics failed! Dec 13 22:35:31 acer kernel: bge0: flow-through queue init failed Dec 13 22:35:31 acer kernel: bge0: initialization failure and Dec 13 22:40:52 acer savecore: reboot after panic: page fault Dec 13 22:40:52 acer savecore: writing core to vmcore.9 ============= acer$ uname -a FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sat Dec 13 22:29:48 MSK 2008 lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console amd64 From admin at lissyara.su Sat Dec 13 12:41:05 2008 From: admin at lissyara.su (Alex Keda) Date: Sat Dec 13 12:41:17 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <4944115C.5020403@lissyara.su> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su> Message-ID: <49441DDE.2010706@lissyara.su> Alex Keda ?????: > Alexander Motin ?????: > > 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 trie it with my HP Compaq 6715s > sleep OK, but after press power button, for wake up, i see blue screen, sorry, read as 'dark screen' - no video... From admin at lissyara.su Sat Dec 13 12:53:27 2008 From: admin at lissyara.su (Alex Keda) Date: Sat Dec 13 12:53:39 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <4944115C.5020403@lissyara.su> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su> Message-ID: <494420C4.80702@lissyara.su> Alex Keda ?????: > Alexander Motin ?????: > > 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 trie it with my HP Compaq 6715s > sleep OK, but after press power button, for wake up, i see blue screen, > and nothing... After hard reset, I have im /var/log/messages: > > > Dec 13 22:35:19 acer acpi: suspend at 20081213 22:35:19 > Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 0, > val 32768) > Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 0, val > 0xffffffff) > Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 24, > val 0xffffffff) > Dec 13 22:35:31 acer kernel: bge0: PHY read timed out (phy 1, reg 16, > val 0xffffffff) > Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 16, > val 0) > Dec 13 22:35:31 acer kernel: bge0: PHY write timed out (phy 1, reg 23, > val 18) > Dec 13 22:35:31 acer kernel: bge0: RX CPU self-diagnostics failed! > Dec 13 22:35:31 acer kernel: bge0: flow-through queue init failed > Dec 13 22:35:31 acer kernel: bge0: initialization failure > > and > > Dec 13 22:40:52 acer savecore: reboot after panic: page fault > Dec 13 22:40:52 acer savecore: writing core to vmcore.9 > ============= > acer$ uname -a > FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: > Sat Dec 13 22:29:48 MSK 2008 > lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console > amd64 may be it useful... acer# kgdb -q /boot/kernel/kernel vmcore.9 Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. ... skip .... Loaded symbols for /boot/kernel/radeon.ko Reading symbols from /boot/kernel/drm.ko...Reading symbols from /boot/kernel/drm.ko.symbols...done. done. Loaded symbols for /boot/kernel/drm.ko #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xffffffff80528008 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:759 #4 0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675 #5 0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at /usr/src/sys/amd64/amd64/trap.c:444 #6 0xffffffff807c80ae in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217 #7 0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at bus_if.h:46 #8 0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not available. ) at /usr/src/sys/kern/subr_bus.c:2953 #9 0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at /usr/src/sys/dev/ata/ata-all.c:713 #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" is not available. ) at /usr/src/sys/dev/ata/ata-sata.c:69 #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at /usr/src/sys/kern/subr_taskqueue.c:282 #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is not available. ) at /usr/src/sys/kern/subr_taskqueue.c:403 #13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 , arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90) at /usr/src/sys/kern/kern_fork.c:821 #14 0xffffffff807c84be in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:521 #15 0x0000000000000000 in ?? () #16 0x0000000000000000 in ?? () #17 0x0000000000000000 in ?? () #18 0x0000000000000000 in ?? () #19 0x0000000000000000 in ?? () #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000000 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000000000000000 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000000 in ?? () #33 0x0000000000000000 in ?? () #34 0x0000000000000000 in ?? () #35 0x0000000000000000 in ?? () #36 0x0000000000000000 in ?? () #37 0x0000000000000000 in ?? () #38 0x0000000000000000 in ?? () #39 0x0000000000e8a000 in ?? () #40 0x000000000000000b in ?? () ---Type to continue, or q to quit--- #41 0xffffffff80b4f880 in affinity () #42 0xffffffff80b4f880 in affinity () #43 0xffffff0001345720 in ?? () #44 0xfffffffe4005b240 in ?? () #45 0xfffffffe4005b1f8 in ?? () #46 0xffffff0001346720 in ?? () #47 0xffffffff8054abad in sched_switch (td=0xffffffff80561790, newtd=0xffffffff80b6b250, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1848 Previous frame inner to this frame (corrupt stack?) (kgdb) quit ================================================= acer# dmesg | grep ata atapci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports PM not supported ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: port not implemented ata3: [ITHREAD] ata4: on atapci0 ata4: port not implemented ata4: [ITHREAD] ata5: on atapci0 ata5: port not implemented ata5: [ITHREAD] atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] acd0: DVDR at ata0-master PIO4 ad4: 152627MB at ata2-master SATA300 cd0 at ata0 bus 0 target 0 lun 0 acer# From nate at root.org Sat Dec 13 13:04:55 2008 From: nate at root.org (Nate Lawson) Date: Sat Dec 13 13:05:06 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <494420C4.80702@lissyara.su> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su> <494420C4.80702@lissyara.su> Message-ID: <49442375.4010401@root.org> Alex Keda wrote: >> Dec 13 22:40:52 acer savecore: reboot after panic: page fault >> Dec 13 22:40:52 acer savecore: writing core to vmcore.9 >> ============= >> acer$ uname -a >> FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT >> #0: Sat Dec 13 22:29:48 MSK 2008 >> lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console >> amd64 > > may be it useful... > > acer# kgdb -q /boot/kernel/kernel vmcore.9 > Reading symbols from /boot/kernel/sound.ko...Reading symbols from > /boot/kernel/sound.ko.symbols...done. > done. > ... skip .... > Loaded symbols for /boot/kernel/radeon.ko > Reading symbols from /boot/kernel/drm.ko...Reading symbols from > /boot/kernel/drm.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/drm.ko > #0 doadump () at pcpu.h:196 > 196 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump () at pcpu.h:196 > #1 0xffffffff80528008 in boot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:420 > #2 0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at > /usr/src/sys/kern/kern_shutdown.c:576 > #3 0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, > eva=Variable "eva" is not available. > ) at /usr/src/sys/amd64/amd64/trap.c:759 > #4 0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, > usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675 > #5 0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at > /usr/src/sys/amd64/amd64/trap.c:444 > #6 0xffffffff807c80ae in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:217 > #7 0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at > bus_if.h:46 > #8 0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not > available. > ) at /usr/src/sys/kern/subr_bus.c:2953 > #9 0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at > /usr/src/sys/dev/ata/ata-all.c:713 > #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" > is not available. > ) at /usr/src/sys/dev/ata/ata-sata.c:69 > #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at > /usr/src/sys/kern/subr_taskqueue.c:282 > #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is > not available. > ) at /usr/src/sys/kern/subr_taskqueue.c:403 > #13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 > , arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90) > at /usr/src/sys/kern/kern_fork.c:821 > #14 0xffffffff807c84be in fork_trampoline () at > /usr/src/sys/amd64/amd64/exception.S:521 > #15 0x0000000000000000 in ?? () > acer# dmesg | grep ata > atapci0: port > 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f > mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 > atapci0: [ITHREAD] > atapci0: AHCI Version 01.10 controller with 4 ports PM not supported > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: port not implemented > ata3: [ITHREAD] > ata4: on atapci0 > ata4: port not implemented > ata4: [ITHREAD] > ata5: on atapci0 > ata5: port not implemented > ata5: [ITHREAD] > atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 > on pci0 > ata0: on atapci1 > ata0: [ITHREAD] > acd0: DVDR at ata0-master PIO4 > ad4: 152627MB at ata2-master SATA300 > cd0 at ata0 bus 0 target 0 lun 0 ATA should be disabling its SATA PHY task during suspend, then re-enabling it after resume. Looks like it doesn't do this. -- Nate From bu7cher at yandex.ru Sun Dec 14 21:51:39 2008 From: bu7cher at yandex.ru (Andrey V. Elsukov) Date: Sun Dec 14 21:51:46 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <49442375.4010401@root.org> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su> <494420C4.80702@lissyara.su> <49442375.4010401@root.org> Message-ID: <4945EB56.1060608@yandex.ru> Nate Lawson wrote: >> #7 0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at >> bus_if.h:46 >> #8 0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not >> available. >> ) at /usr/src/sys/kern/subr_bus.c:2953 >> #9 0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at >> /usr/src/sys/dev/ata/ata-all.c:713 >> #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" >> is not available. >> ) at /usr/src/sys/dev/ata/ata-sata.c:69 >> #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at >> /usr/src/sys/kern/subr_taskqueue.c:282 >> #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is >> not available. > > ATA should be disabling its SATA PHY task during suspend, then > re-enabling it after resume. Looks like it doesn't do this. It seems that resuming of ATA controller is already done. AHCI interrupts are enabled and PHY state was changed. And task are doing attach of hot-plugged device.. So, Alex, can you show output of a kgdb command: (kgdb) p "%s", msgbufp->msg_ptr -- WBR, Andrey V. Elsukov From bugmaster at FreeBSD.org Mon Dec 15 03:06:47 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 15 03:07:14 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200812151106.mBFB6kxA004228@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/129618 acpi Problem with ACPI on laptop o kern/129563 acpi [ACPI] sleep broken on IBM/Lenovo T61 [amd64] o kern/128639 acpi [PATCH] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/89411 acpi [acpi] acpiconf bug o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 f kern/67309 acpi zzz reboot computer (ACPI S3) o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 45 problems total. From invite+a2=690a6 at facebookmail.com Tue Dec 16 01:01:27 2008 From: invite+a2=690a6 at facebookmail.com (Maitri Karuna R) Date: Tue Dec 16 01:01:33 2008 Subject: Check out my Facebook profile Message-ID: <34ec45a2b1a60c68cee084d92db0ba79@localhost.localdomain> Hi freebsd-acpi, I set up a Facebook profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile. Thanks, Maitri To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=1005079607&k=XVBXYVS4VZ6M5BE1Q1VUTV&r From admin at lissyara.su Tue Dec 16 01:07:06 2008 From: admin at lissyara.su (Alex Keda) Date: Tue Dec 16 01:07:23 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <4945EB56.1060608@yandex.ru> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su> <494420C4.80702@lissyara.su> <49442375.4010401@root.org> <4945EB56.1060608@yandex.ru> Message-ID: <49476FB6.1020705@lissyara.su> Andrey V. Elsukov пишет: > Nate Lawson wrote: >>> #7 0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at >>> bus_if.h:46 >>> #8 0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not >>> available. >>> ) at /usr/src/sys/kern/subr_bus.c:2953 >>> #9 0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at >>> /usr/src/sys/dev/ata/ata-all.c:713 >>> #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable >>> "context" >>> is not available. >>> ) at /usr/src/sys/dev/ata/ata-sata.c:69 >>> #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at >>> /usr/src/sys/kern/subr_taskqueue.c:282 >>> #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is >>> not available. >> >> ATA should be disabling its SATA PHY task during suspend, then >> re-enabling it after resume. Looks like it doesn't do this. > > It seems that resuming of ATA controller is already done. > AHCI interrupts are enabled and PHY state was changed. > And task are doing attach of hot-plugged device.. > So, Alex, can you show output of a kgdb command: > (kgdb) p "%s", msgbufp->msg_ptr > big output. see attached file -------------- next part -------------- Script started on Tue Dec 16 12:03:21 2008 HP# kgdb -q /boot/kernel/kernel vmcore.9 Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_hda.ko Reading symbols from /boot/kernel/umodem.ko...Reading symbols from /boot/kernel/umodem.ko.symbols...done. done. Loaded symbols for /boot/kernel/umodem.ko Reading symbols from /boot/kernel/acpi_video.ko...Reading symbols from /boot/kernel/acpi_video.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_video.ko Reading symbols from /boot/kernel/atapicam.ko...Reading symbols from /boot/kernel/atapicam.ko.symbols...done. done. Loaded symbols for /boot/kernel/atapicam.ko Reading symbols from /boot/kernel/acpi_aiboost.ko...Reading symbols from /boot/kernel/acpi_aiboost.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_aiboost.ko Reading symbols from /boot/kernel/acpi_dock.ko...Reading symbols from /boot/kernel/acpi_dock.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_dock.ko Reading symbols from /boot/kernel/ng_bt3c.ko...Reading symbols from /boot/kernel/ng_bt3c.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_bt3c.ko Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from /boot/kernel/netgraph.ko.symbols...done. done. Loaded symbols for /boot/kernel/netgraph.ko Reading symbols from /boot/kernel/ng_btsocket.ko...Reading symbols from /boot/kernel/ng_btsocket.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_btsocket.ko Reading symbols from /boot/kernel/ng_bluetooth.ko...Reading symbols from /boot/kernel/ng_bluetooth.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_bluetooth.ko Reading symbols from /boot/kernel/ng_ubt.ko...Reading symbols from /boot/kernel/ng_ubt.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_ubt.ko Reading symbols from /boot/kernel/ubtbcmfw.ko...Reading symbols from /boot/kernel/ubtbcmfw.ko.symbols...done. done. Loaded symbols for /boot/kernel/ubtbcmfw.ko Reading symbols from /boot/kernel/ng_l2cap.ko...Reading symbols from /boot/kernel/ng_l2cap.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_l2cap.ko Reading symbols from /boot/kernel/iicbb.ko...Reading symbols from /boot/kernel/iicbb.ko.symbols...done. done. Loaded symbols for /boot/kernel/iicbb.ko Reading symbols from /boot/kernel/iicbus.ko...Reading symbols from /boot/kernel/iicbus.ko.symbols...done. done. Loaded symbols for /boot/kernel/iicbus.ko Reading symbols from /boot/kernel/tmpfs.ko...Reading symbols from /boot/kernel/tmpfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/tmpfs.ko Reading symbols from /boot/kernel/ng_hci.ko...Reading symbols from /boot/kernel/ng_hci.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_hci.ko Reading symbols from /boot/kernel/ng_socket.ko...Reading symbols from /boot/kernel/ng_socket.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_socket.ko Reading symbols from /boot/kernel/ipfw.ko...Reading symbols from /boot/kernel/ipfw.ko.symbols...done. done. Loaded symbols for /boot/kernel/ipfw.ko Reading symbols from /boot/kernel/vkbd.ko...Reading symbols from /boot/kernel/vkbd.ko.symbols...done. done. Loaded symbols for /boot/kernel/vkbd.ko Reading symbols from /usr/local/modules/fuse.ko...done. Loaded symbols for /usr/local/modules/fuse.ko Reading symbols from /usr/local/modules/rtc.ko...done. Loaded symbols for /usr/local/modules/rtc.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/radeon.ko...Reading symbols from /boot/kernel/radeon.ko.symbols...done. done. Loaded symbols for /boot/kernel/radeon.ko Reading symbols from /boot/kernel/drm.ko...Reading symbols from /boot/kernel/drm.ko.symbols...done. done. Loaded symbols for /boot/kernel/drm.ko #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xffffffff80528008 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:759 #4 0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675 #5 0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at /usr/src/sys/amd64/amd64/trap.c:444 #6 0xffffffff807c80ae in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217 #7 0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at bus_if.h:46 #8 0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not available. ) at /usr/src/sys/kern/subr_bus.c:2953 #9 0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at /usr/src/sys/dev/ata/ata-all.c:713 #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" is not available. ) at /usr/src/sys/dev/ata/ata-sata.c:69 #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at /usr/src/sys/kern/subr_taskqueue.c:282 #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is not available. ) at /usr/src/sys/kern/subr_taskqueue.c:403 #13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 , arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90) at /usr/src/sys/kern/kern_fork.c:821 #14 0xffffffff807c84be in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:521 #15 0x0000000000000000 in ?? () #16 0x0000000000000000 in ?? () #17 0x0000000000000000 in ?? () #18 0x0000000000000000 in ?? () #19 0x0000000000000000 in ?? () #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000000 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000000000000000 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000000 in ?? () #33 0x0000000000000000 in ?? () #34 0x0000000000000000 in ?? () #35 0x0000000000000000 in ?? () #36 0x0000000000000000 in ?? () #37 0x0000000000000000 in ?? () #38 0x0000000000000000 in ?? () #39 0x0000000000e8a000 in ?? () #40 0x000000000000000b in ?? () #41 0xffffffff80b4f880 in affinity () #42 0xffffffff80b4f880 in affinity () #43 0xffffff0001345720 in ?? () #44 0xfffffffe4005b240 in ?? () #45 0xfffffffe4005b1f8 in ?? () #46 0xffffff0001346720 in ?? () #47 0xffffffff8054abad in sched_switch (td=0xffffffff80561790, newtd=0xffffffff80b6b250, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1848 Previous frame inner to this frame (corrupt stack?) (kgdb) #0 doadump () at pcpu.h:196 #1 0xffffffff80528008 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:759 #4 0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675 #5 0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at /usr/src/sys/amd64/amd64/trap.c:444 #6 0xffffffff807c80ae in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217 #7 0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at bus_if.h:46 #8 0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not available. ) at /usr/src/sys/kern/subr_bus.c:2953 #9 0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at /usr/src/sys/dev/ata/ata-all.c:713 #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" is not available. ) at /usr/src/sys/dev/ata/ata-sata.c:69 #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at /usr/src/sys/kern/subr_taskqueue.c:282 #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is not available. ) at /usr/src/sys/kern/subr_taskqueue.c:403 #13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 , arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90) at /usr/src/sys/kern/kern_fork.c:821 #14 0xffffffff807c84be in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:521 #15 0x0000000000000000 in ?? () #16 0x0000000000000000 in ?? () #17 0x0000000000000000 in ?? () #18 0x0000000000000000 in ?? () #19 0x0000000000000000 in ?? () #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000000 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000000000000000 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000000 in ?? () #33 0x0000000000000000 in ?? () #34 0x0000000000000000 in ?? () #35 0x0000000000000000 in ?? () #36 0x0000000000000000 in ?? () #37 0x0000000000000000 in ?? () #38 0x0000000000000000 in ?? () #39 0x0000000000e8a000 in ?? () #40 0x000000000000000b in ?? () #41 0xffffffff80b4f880 in affinity () #42 0xffffffff80b4f880 in affinity () #43 0xffffff0001345720 in ?? () #44 0xfffffffe4005b240 in ?? () #45 0xfffffffe4005b1f8 in ?? () #46 0xffffff0001346720 in ?? () #47 0xffffffff8054abad in sched_switch (td=0xffffffff80561790, newtd=0xffffffff80b6b250, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1848 (kgdb) printf "%s", msgbufp->msg_ptr led, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 <118>. <118>Shutting down local packages:powernow0: set freq failed, err 6 <118> rtc00001 allow ip from any to any <118>[: =: unexpected operator <118>. <118>Stopping cron. <118>Stopping sshd. <118>Waiting for PIDS: 1281powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 <118>. <118>Stopping cupsd. <118>Waiting for PIDS: 1220powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 <118>. <118>Stopping exim. powernow0: set freq failed, err 6 <118>Stopping powerd. powernow1: set freq failed, err 6 powernow1: set freq failed, err 6 <118>sysctl: : Stopping fusefs. <118>Stopping bthidd. <118>Waiting for PIDS: 1079. <118>Stopping hcsecd. <118>Stopping named. <118>Waiting for PIDS: 930. <118>Stopping devd. <6>pid 1396 (hald), uid 560: exited on signal 11 <118>Writing entropy file:. <118>. <118>Dec 13 22:33:35 acer syslogd: exiting on signal 15 ---Type to continue, or q to quit--- Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiti nSgy n(cmianxg 6d0i sskesc,o nvdnso)d efso rr esmyasitneimn gp.r.o.ce5s s `syncer' to stop...2 1 1 0 0 done All buffers synced. 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 8.0-CURRENT #0: Sat Dec 13 22:29:48 MSK 2008 lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-60 (1995.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60f82 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f Cores per package: 2 usable memory = 1998295040 (1905 MB) avail memory = 1929797632 (1840 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Error (tbfadt-0516): 32/64X address mismatch in "Pm2ControlBlock": [ 8800] [ 0 8100], using 64X [20070320] ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) unknown: I/O range not supported acpi0: reservation of 0, 8000000 (3) failed acpi0: reservation of 100000, fff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x4000-0x40ff mem 0xc0000000-0xc7ffffff,0xd0200000-0xd020ffff,0xd0300000-0xd03fffff irq 19 at device 5.0 on pci1 acpi_video0: on vgapci0 pcib2: at device 4.0 on pci0 pci16: on pcib2 bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 miibus0: on bge0 brgphy0: PHY 1 on miibus0 ---Type to continue, or q to quit--- brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bge0: Ethernet address: 00:1f:29:89:38:f3 bge0: [ITHREAD] pcib3: at device 5.0 on pci0 pci32: on pcib3 pcib4: at device 6.0 on pci0 pci48: on pcib4 pci48: at device 0.0 (no driver attached) atapci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports PM not supported ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: port not implemented ata3: [ITHREAD] ata4: on atapci0 ata4: port not implemented ata4: [ITHREAD] ata5: on atapci0 ata5: port not implemented ata5: [ITHREAD] ohci0: mem 0xd0401000-0xd0401fff irq 23 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xd0402000-0xd0402fff irq 17 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xd0403000-0xd0403fff irq 17 at device 19.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ohci3: mem 0xd0404000-0xd0404fff irq 17 at device 19.3 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] ---Type to continue, or q to quit--- usb3: OHCI version 1.0, legacy support usb3: on ohci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ohci4: mem 0xd0405000-0xd0405fff irq 17 at device 19.4 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: on ohci4 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered ehci0: mem 0xd0406000-0xd04060ff irq 23 at device 19.5 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 usb5: on ehci0 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 10 ports with 10 removable, self powered pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] hdac0: irq 16 at device 20.2 on pci0 hdac0: HDA Driver Revision: 20081123_0118 hdac0: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib5: at device 20.4 on pci0 pci2: on pcib5 cbb0: mem 0xd0100000-0xd0100fff irq 20 at device 4.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [FILTER] battery0: on acpi0 battery1: on acpi0 acpi_acad0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 atrtc0: port 0x70-0x71,0x72-0x73 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ---Type to continue, or q to quit--- psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 cpu0: on acpi0 acpi_throttle0: on cpu0 powernow0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 powernow1: on cpu1 orm0: at iomem 0xd0000-0xd0fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range ubt0: on uhub0 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=10, buffer size=640 ums0: on uhub1 ums0: 3 buttons and Z dir. Timecounters tick every 1.000 msec acd0: DVDR at ata0-master PIO4 ad4: 152627MB at ata2-master SATA300 hdac0: HDA Codec #0: Analog Devices AD1981HD hdac0: HDA Codec #1: Lucent/Agere Systems (Unknown) pcm0: at cad 0 nid 1 on hdac0 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a <118>Entropy harvesting: interrupts ethernet point_to_point kickstart. <118>/dev/ad4s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS <118>/dev/ad4s1a: clean, 52516070 free (100286 frags, 6551973 blocks, 0.1% fragmentation) WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD. acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present <118>Starting Network: lo0 bge0. WARNING: attempt to net_add_domain(netgraph) after domainfinalize() ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled <118>Flushed all rules. <118>00100 allow ip from any to any via lo0 <118>00200 deny ip from any to 127.0.0.0/8 <118>00300 deny ip from 127.0.0.0/8 to any <118>Firewall rules loaded. <118>Waiting 30s for an interface to come up: (bge0) <118>Removing stale Samba tdb files: done ---Type to continue, or q to quit--- <118>Dec 13 22:34:45 acer bthidd[1083]: syntax error in line 1 <118>Starting fusefs. fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 <118>ATAidle: configuring device /dev/ad4 <118>Model: TOSHIBA MK1646GSX <118>Serial: 48AMC6DOT <118>Firmware Rev: LB114C <118>ATA revision: ATA-8 <118>LBA 48: yes <118>Geometry: 16383 cyls, 16 heads, 63 spt <118>Capacity: 149GB <118>SMART Supported: yes <118>SMART Enabled: yes <118>APM Supported: yes <118>APM Enabled: yes <118>AAM Supported: no <118>AAM Enabled: no <118>APM Value: 128 <118>lircd: WARNING: config file contains no valid remote control definition <118>Starting hald. <118>Starting avahi-daemon. <118>Starting avahi-dnsconfd. <118>Configuring syscons: keymap keyrate scrnmap font8x16 font8x14 font8x8 blanktime. <118>Local package initialization:[: =: unexpected operator <118>00001 allow ip from any to any <118> rtc. <118>/etc/rc.d/sysctl: WARNING: sysctl dev.pcm.0.vchans does not exist. <118> <118>Sat Dec 13 22:34:49 MSK 2008 <118>date: : Dec 13 22:34:50 acer hald[1400]: 22:34:50.461 [E] ck-tracker.c:367: Error doing GetSeats on ConsoleKit: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0 <118>Dec 13 22:34:50 acer hald[1400]: 22:34:50.462 [E] ck-tracker.c:792: Could not get seats and sessions <118>Dec 13 22:34:51 acer hald[1400]: 22:34:51.031 [E] hald_runner.c:671: Error running 'hald-addon-acpi': org.freedesktop.HalRunner.Failed: Start request failed <118>Dec 13 22:34:51 acer hald[1400]: 22:34:51.031 [E] hald.c:124: Cannot start addon hald-addon-acpi for udi /org/freedesktop/Hal/devices/computer drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] Initialized radeon 1.29.0 20080613 info: [drm] Setting GART location based on new memory map info: [drm] Loading RS690/RS740 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] info: [drm] Num pipes: 1 <118>Dec 13 22:35:08 acer login: ROOT LOGIN (root) ON ttyv1 bge0: PHY write timed out (phy 1, reg 0, val 32768) bge0: PHY read timed out (phy 1, reg 0, val 0xffffffff) bge0: PHY read timed out (phy 1, reg 24, val 0xffffffff) bge0: PHY read timed out (phy 1, reg 16, val 0xffffffff) bge0: PHY write timed out (phy 1, reg 16, val 0) ---Type to continue, or q to quit--- bge0: PHY write timed out (phy 1, reg 23, val 18) bge0: RX CPU self-diagnostics failed! bge0: flow-through queue init failed bge0: initialization failure ata3: port not implemented ata4: port not implemented ata5: port not implemented ubt_isoc_in_complete2: ubt0 - Isoc-in xfer failed, IOERROR (13). No new xfer will be submitted! ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer will be submitted! ums0: at uhub1 port 1 (addr 2) disconnected ubt0: at uhub0 port 2 (addr 2) disconnected Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x50 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff80551631 stack pointer = 0x10:0xfffffffe4005bad0 frame pointer = 0x10:0xfffffffe4005bb20 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq) trap number = 12 panic: page fault cpuid = 0 Uptime: 58s Physical memory: 1905 MB Dumping 206 MB: 191 175 159 143 127 111 95 79 63 47 31 15powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 info: [drm] Num pipes: 1 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 info: [drm] Loading RS690/RS740 Microcode info: [drm] Num pipes: 1 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow1: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- info: [drm] Num pipes: 1 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 info: [drm] Setting GART location based on new memory map info: [drm] Loading RS690/RS740 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs drm0: [ITHREAD] powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 info: [drm] Num pipes: 1 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 <118>Dec 13 22:33:18 acer shutdown: reboot by root: powernow0: set freq failed, err 6 ---Type to continue, or q to quit--- powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 <118>stty: powernow0: set freq failed, err 6 powernow0: set freq failed, err 6 <118>Stopping moused. <118>Waiting for PIDS: 1330powernow0: set freq failed, err 6 powernow0: set freq fai(kgdb) (kgdb) (kgdb) quit HP# ll sdocs/kgdb.txt -rw-r--r-- 1 root wheel 78K 16 ÄÅË 12:04 kgdb.txt HP# mail -s kgdb admin@lissyara.su < kgdb.txt HP# From admin at lissyara.su Tue Dec 16 08:55:23 2008 From: admin at lissyara.su (Alex Keda) Date: Tue Dec 16 08:55:32 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <4945EB56.1060608@yandex.ru> References: <1224616985.00027652.1224606603@10.7.7.3> <1224728582.00028075.1224715806@10.7.7.3> <4932F34C.1040804@FreeBSD.org> <4944115C.5020403@lissyara.su> <494420C4.80702@lissyara.su> <49442375.4010401@root.org> <4945EB56.1060608@yandex.ru> Message-ID: <4947DD70.9040800@lissyara.su> Andrey V. Elsukov ?????: > Nate Lawson wrote: >>> #7 0xffffffff80551631 in device_attach (dev=0xffffff000772fb00) at >>> bus_if.h:46 >>> #8 0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not >>> available. >>> ) at /usr/src/sys/kern/subr_bus.c:2953 >>> #9 0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at >>> /usr/src/sys/dev/ata/ata-all.c:713 >>> #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" >>> is not available. >>> ) at /usr/src/sys/dev/ata/ata-sata.c:69 >>> #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at >>> /usr/src/sys/kern/subr_taskqueue.c:282 >>> #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is >>> not available. >> >> ATA should be disabling its SATA PHY task during suspend, then >> re-enabling it after resume. Looks like it doesn't do this. > > It seems that resuming of ATA controller is already done. > AHCI interrupts are enabled and PHY state was changed. > And task are doing attach of hot-plugged device.. > So, Alex, can you show output of a kgdb command: > (kgdb) p "%s", msgbufp->msg_ptr > boot verbose, as requested -------------- next part -------------- Script started on Tue Dec 16 19:49:33 2008 HP# kgdb -q /boot/kernel/kernel vmcore.911 Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_hda.ko Reading symbols from /boot/kernel/umodem.ko...Reading symbols from /boot/kernel/umodem.ko.symbols...done. done. Loaded symbols for /boot/kernel/umodem.ko Reading symbols from /boot/kernel/acpi_video.ko...Reading symbols from /boot/kernel/acpi_video.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_video.ko Reading symbols from /boot/kernel/atapicam.ko...Reading symbols from /boot/kernel/atapicam.ko.symbols...done. done. Loaded symbols for /boot/kernel/atapicam.ko Reading symbols from /boot/kernel/acpi_aiboost.ko...Reading symbols from /boot/kernel/acpi_aiboost.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_aiboost.ko Reading symbols from /boot/kernel/acpi_dock.ko...Reading symbols from /boot/kernel/acpi_dock.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_dock.ko Reading symbols from /boot/kernel/ng_bt3c.ko...Reading symbols from /boot/kernel/ng_bt3c.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_bt3c.ko Reading symbols from /boot/kernel/netgraph.ko...Reading symbols from /boot/kernel/netgraph.ko.symbols...done. done. Loaded symbols for /boot/kernel/netgraph.ko Reading symbols from /boot/kernel/ng_btsocket.ko...Reading symbols from /boot/kernel/ng_btsocket.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_btsocket.ko Reading symbols from /boot/kernel/ng_bluetooth.ko...Reading symbols from /boot/kernel/ng_bluetooth.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_bluetooth.ko Reading symbols from /boot/kernel/ng_ubt.ko...Reading symbols from /boot/kernel/ng_ubt.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_ubt.ko Reading symbols from /boot/kernel/ubtbcmfw.ko...Reading symbols from /boot/kernel/ubtbcmfw.ko.symbols...done. done. Loaded symbols for /boot/kernel/ubtbcmfw.ko Reading symbols from /boot/kernel/ng_l2cap.ko...Reading symbols from /boot/kernel/ng_l2cap.ko.symbols...done. done. Loaded symbols for /boot/kernel/ng_l2cap.ko Reading symbols from /boot/kernel/iicbb.ko...Reading symbols from /boot/kernel/iicbb.ko.symbols...done. done. Loaded symbols for /boot/kernel/iicbb.ko Reading symbols from /boot/kernel/iicbus.ko...Reading symbols from /boot/kernel/iicbus.ko.symbols...done. done. Loaded symbols for /boot/kernel/iicbus.ko Reading symbols from /boot/kernel/tmpfs.ko...Reading symbols from /boot/kernel/tmpfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/tmpfs.ko Reading symbols from /usr/local/modules/rtc.ko...done. Loaded symbols for /usr/local/modules/rtc.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xffffffff80528008 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xffffffff8052844c in panic (fmt=0xffffffff808a4cbc "%s") at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xffffffff807e4ca8 in trap_fatal (frame=0xffffff0001345720, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:759 #4 0xffffffff807e5074 in trap_pfault (frame=0xfffffffe4005ba20, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:675 #5 0xffffffff807e5970 in trap (frame=0xfffffffe4005ba20) at /usr/src/sys/amd64/amd64/trap.c:444 #6 0xffffffff807c80ae in calltrap () at /usr/src/sys/amd64/amd64/exception.S:217 #7 0xffffffff80551631 in device_attach (dev=0xffffff0001afe900) at bus_if.h:46 #8 0xffffffff805529ea in bus_generic_attach (dev=Variable "dev" is not available. ) at /usr/src/sys/kern/subr_bus.c:2953 #9 0xffffffff8024c2f7 in ata_identify (dev=0xffffff0001559a00) at /usr/src/sys/dev/ata/ata-all.c:713 #10 0xffffffff80254d22 in ata_sata_phy_event (context=Variable "context" is not available. ) at /usr/src/sys/dev/ata/ata-sata.c:69 #11 0xffffffff8056155a in taskqueue_run (queue=0xffffff0001499780) at /usr/src/sys/kern/subr_taskqueue.c:282 #12 0xffffffff80561802 in taskqueue_thread_loop (arg=Variable "arg" is not available. ) at /usr/src/sys/kern/subr_taskqueue.c:403 #13 0xffffffff805069c8 in fork_exit (callout=0xffffffff80561790 , arg=0xffffffff80b6b250, frame=0xfffffffe4005bc90) at /usr/src/sys/kern/kern_fork.c:821 #14 0xffffffff807c84be in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:521 #15 0x0000000000000000 in ?? () #16 0x0000000000000000 in ?? () #17 0x0000000000000000 in ?? () #18 0x0000000000000000 in ?? () #19 0x0000000000000000 in ?? () #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000000 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000000000000000 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000000 in ?? () #33 0x0000000000000000 in ?? () #34 0x0000000000000000 in ?? () #35 0x0000000000000000 in ?? () #36 0x0000000000000000 in ?? () #37 0x0000000000000000 in ?? () #38 0x0000000000000000 in ?? () #39 0x0000000000e8a000 in ?? () #40 0xffffff0001345720 in ?? () ---Type to continue, or q to quit--- #41 0xffffffff80b50500 in tdq_cpu () #42 0xffffffff80b4f880 in affinity () #43 0xffffff0001345720 in ?? () #44 0xfffffffe4005b690 in ?? () #45 0xfffffffe4005b648 in ?? () #46 0xffffff0001891ab0 in ?? () #47 0xffffffff8054abad in sched_switch (td=0xffffffff80561790, newtd=0xffffffff80b6b250, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1848 Previous frame inner to this frame (corrupt stack?) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) printf "%s", msgbufp->msg_ptr 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 8.0-CURRENT #0: Sat Dec 13 22:29:48 MSK 2008 lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80e5f000. Preloaded elf obj module "/boot/kernel/sound.ko" at 0xffffffff80e5f1f8. Preloaded elf obj module "/boot/kernel/snd_hda.ko" at 0xffffffff80e5f860. Preloaded elf obj module "/boot/kernel/umodem.ko" at 0xffffffff80e5fe48. Preloaded elf obj module "/boot/kernel/acpi_video.ko" at 0xffffffff80e60370. Preloaded /boot/zfs/zpool.cache "/boot/zfs/zpool.cache" at 0xffffffff80e608e0. Preloaded elf obj module "/boot/kernel/atapicam.ko" at 0xffffffff80e60940. Preloaded elf obj module "/boot/kernel/acpi_aiboost.ko" at 0xffffffff80e60f30. Preloaded elf obj module "/boot/kernel/acpi_dock.ko" at 0xffffffff80e614a0. Preloaded elf obj module "/boot/kernel/ng_bt3c.ko" at 0xffffffff80e61a10. Preloaded elf obj module "/boot/kernel/netgraph.ko" at 0xffffffff80e61ff8. Preloaded elf obj module "/boot/kernel/ng_btsocket.ko" at 0xffffffff80e62668. Preloaded elf obj module "/boot/kernel/ng_bluetooth.ko" at 0xffffffff80e62cd8. Preloaded elf obj module "/boot/kernel/ng_ubt.ko" at 0xffffffff80e63248. Preloaded elf obj module "/boot/kernel/ubtbcmfw.ko" at 0xffffffff80e637b0. Preloaded elf obj module "/boot/kernel/ng_l2cap.ko" at 0xffffffff80e63ca0. Preloaded elf obj module "/boot/kernel/iicbb.ko" at 0xffffffff80e64290. Preloaded elf obj module "/boot/kernel/iicbus.ko" at 0xffffffff80e64738. Preloaded elf obj module "/boot/kernel/tmpfs.ko" at 0xffffffff80e64ba0. Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1994924370 Hz CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-60 (1994.92-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60f82 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f Cores per package: 2 L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative ---Type to continue, or q to quit--- L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative usable memory = 1998295040 (1905 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000e92000 - 0x0000000074ad3fff, 1942233088 bytes (474178 pages) avail memory = 1929797632 (1840 MB) ACPI APIC Table: INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 2 ULE: setup cpu 0 ULE: setup cpu 1 ACPI: RSDP @ 0x0xfe0b0/0x0024 (v 2 HP ) ACPI: XSDT @ 0x0x77fc81bc/0x0064 (v 1 HPQOEM SLIC-MPC 0x00000001 HP 0x00000001) ACPI: FACP @ 0x0x77fc8084/0x00F4 (v 4 HP 0944 0x00000003 HP 0x00000001) ACPI Error (tbfadt-0516): 32/64X address mismatch in "Pm2ControlBlock": [ 8800] [ 0 8100], using 64X [20070320] ACPI: DSDT @ 0x0x77fc84a4/0x1193C (v 1 HP SB400 0x00010000 MSFT 0x03000001) ACPI: FACS @ 0x0x77fe7d80/0x0040 ACPI: SLIC @ 0x0x77fc8220/0x0176 (v 1 HPQOEM SLIC-MPC 0x00000001 HP 0x00000001) ACPI: EPTH @ 0x0x77fc8398/0x0038 (v 1 HP 0944 0x00000001 HP 0x00000001) ACPI: APIC @ 0x0x77fc83d0/0x0062 (v 1 HP 0944 0x00000001 HP 0x00000001) ACPI: MCFG @ 0x0x77fc8434/0x003C (v 1 HP 0944 0x00000001 HP 0x00000001) ACPI: TCPA @ 0x0x77fc8470/0x0032 (v 2 HP 0944 0x00000001 HP 0x00000001) ACPI: SSDT @ 0x0x77fd9de0/0x0059 (v 1 HP HPQNLP 0x00000001 MSFT 0x03000001) ACPI: SSDT @ 0x0x77fd9e39/0x0206 (v 1 HP PSSTBLID 0x00000001 HP 0x00000001) MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 2 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: low lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ---Type to continue, or q to quit--- ID: 0x00000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00000400 ath_rate: version 1.9 wlan: <802.11 Link Layer> snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_buffersize=16384 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 null: random: nfslock: pseudo-device io: kbd: new array size 4 kbd1 at kbdmux0 mem: hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 (Dec 13 2008 22:26:24) acpi0: on motherboard PCIe: Memory Mapped configuration base @ 0xe0000000 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \_SB_.C08B.C08C.C08D.C154 -> bus 1 dev 5 func 0 ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] acpi0: [ITHREAD] acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \_SB_.C08B.C093 -> bus 0 dev 0 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \_SB_.C08B.C090 -> bus 0 dev 0 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \_SB_.C08B.C09F.C0B2 -> bus 0 dev 20 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \_SB_.C08B.C275.C278 -> bus 0 dev 18 func 0 acpi0: Power Button (fixed) acpi0: wakeup code va 0xfffffffe40004000 pa 0x4000 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \_SB_.C08B.C096 -> bus 0 dev 0 func 0 unknown: I/O range not supported acpi0: reservation of 0, 8000000 (3) failed acpi0: reservation of 100000, fff00000 (3) failed ACPI timer: 1/1 1/1 1/1 1/1 1/1 0/3 1/1 1/1 1/1 1/1 -> 9 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pci_link0: Index IRQ Rtd Ref IRQs ---Type to continue, or q to quit--- Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 9 Validation 0 255 N 0 9 After Disable 0 255 N 0 9 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x1002, dev=0x7910, revid=0x00 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2220, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x7912, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 ---Type to continue, or q to quit--- cmdreg=0x0007, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0c (3000 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x7914, revid=0x00 domain=0, bus=0, slot=4, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 3 supports D0 D3 current D0 MSI supports 1 message found-> vendor=0x1002, dev=0x7915, revid=0x00 domain=0, bus=0, slot=5, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 3 supports D0 D3 current D0 MSI supports 1 message found-> vendor=0x1002, dev=0x7916, revid=0x00 domain=0, bus=0, slot=6, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 3 supports D0 D3 current D0 MSI supports 1 message found-> vendor=0x1002, dev=0x4380, revid=0x00 domain=0, bus=0, slot=18, func=0 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x9000, size 3, enabled map[14]: type I/O Port, range 32, base 0x9008, size 2, enabled map[18]: type I/O Port, range 32, base 0x9010, size 3, enabled map[1c]: type I/O Port, range 32, base 0x5018, size 2, enabled map[20]: type I/O Port, range 32, base 0x5020, size 4, enabled map[24]: type Memory, range 32, base 0xd0409000, size 10, enabled pcib0: matched entry for 0.18.INTA pcib0: slot 18 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x4387, revid=0x00 domain=0, bus=0, slot=19, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) ---Type to continue, or q to quit--- lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[10]: type Memory, range 32, base 0xd0401000, size 12, enabled pcib0: matched entry for 0.19.INTA pcib0: slot 19 INTA hardwired to IRQ 23 found-> vendor=0x1002, dev=0x4388, revid=0x00 domain=0, bus=0, slot=19, func=1 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[10]: type Memory, range 32, base 0xd0402000, size 12, enabled pcib0: matched entry for 0.19.INTB pcib0: slot 19 INTB hardwired to IRQ 17 found-> vendor=0x1002, dev=0x4389, revid=0x00 domain=0, bus=0, slot=19, func=2 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 map[10]: type Memory, range 32, base 0xd0403000, size 12, enabled pcib0: matched entry for 0.19.INTC pcib0: slot 19 INTC hardwired to IRQ 17 found-> vendor=0x1002, dev=0x438a, revid=0x00 domain=0, bus=0, slot=19, func=3 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[10]: type Memory, range 32, base 0xd0404000, size 12, enabled pcib0: matched entry for 0.19.INTB pcib0: slot 19 INTB hardwired to IRQ 17 found-> vendor=0x1002, dev=0x438b, revid=0x00 domain=0, bus=0, slot=19, func=4 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 map[10]: type Memory, range 32, base 0xd0405000, size 12, enabled pcib0: matched entry for 0.19.INTC pcib0: slot 19 INTC hardwired to IRQ 17 found-> vendor=0x1002, dev=0x4386, revid=0x00 ---Type to continue, or q to quit--- domain=0, bus=0, slot=19, func=5 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd0406000, size 8, enabled pcib0: matched entry for 0.19.INTD pcib0: slot 19 INTD hardwired to IRQ 23 found-> vendor=0x1002, dev=0x4385, revid=0x14 domain=0, bus=0, slot=20, func=0 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0003, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type I/O Port, range 32, base 0x8200, size 4, enabled found-> vendor=0x1002, dev=0x438c, revid=0x00 domain=0, bus=0, slot=20, func=1 class=01-01-82, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0220, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 map[20]: type I/O Port, range 32, base 0x5040, size 4, enabled pcib0: matched entry for 0.20.INTA pcib0: slot 20 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x4383, revid=0x00 domain=0, bus=0, slot=20, func=2 class=04-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0410, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 64, base 0xd0408000, size 14, enabled pcib0: matched entry for 0.20.INTA pcib0: slot 20 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x438d, revid=0x00 domain=0, bus=0, slot=20, func=3 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x4384, revid=0x00 domain=0, bus=0, slot=20, func=4 class=06-04-01, hdrtype=0x01, mfdev=1 ---Type to continue, or q to quit--- cmdreg=0x0027, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 domain=0, bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 domain=0, bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 domain=0, bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 domain=0, bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib1: at device 1.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x4000-0x4fff pcib1: memory decode 0xd0200000-0xd03fffff pcib1: prefetched decode 0xc0000000-0xc7ffffff pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x1002, dev=0x791f, revid=0x00 domain=0, bus=1, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Prefetchable Memory, range 64, base 0xc0000000, size 27, enabled pcib1: requested memory range 0xc0000000-0xc7ffffff: good map[18]: type Memory, range 64, base 0xd0200000, size 16, enabled ---Type to continue, or q to quit--- pcib1: requested memory range 0xd0200000-0xd020ffff: good map[20]: type I/O Port, range 32, base 0x4000, size 8, enabled pcib1: requested I/O range 0x4000-0x40ff: in range map[24]: type Memory, range 32, base 0xd0300000, size 20, enabled pcib1: requested memory range 0xd0300000-0xd03fffff: good pcib1: matched entry for 1.5.INTB pcib1: slot 5 INTB hardwired to IRQ 19 vgapci0: port 0x4000-0x40ff mem 0xc0000000-0xc7ffffff,0xd0200000-0xd020ffff,0xd0300000-0xd03fffff irq 19 at device 5.0 on pci1 acpi_video0: on vgapci0 found Internal/Integrated Digital Flat Panel(110), idx#0, port#1, detectable by BIOS, head #0 found VGA CRT or VESA Compatible Analog Monitor(100), idx#0, port#0, detectable by BIOS, head #0 found TV/HDTV or Analog-Video Monitor(200), idx#0, port#0, detectable by BIOS, head #0 found TV/HDTV or Analog-Video Monitor(210), idx#0, port#1, detectable by BIOS, head #0 pcib2: at device 4.0 on pci0 pcib2: domain 0 pcib2: secondary bus 16 pcib2: subordinate bus 16 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xd0000000-0xd00fffff pcib2: no prefetched decode pcib2: could not get PCI interrupt routing table for \_SB_.C08B.C250 - AE_NOT_FOUND pci16: on pcib2 pci16: domain=0, physical bus=16 found-> vendor=0x14e4, dev=0x1713, revid=0x02 domain=0, bus=16, slot=0, func=0 class=02-00-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=10 powerspec 3 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xd0000000, size 16, enabled pcib2: requested memory range 0xd0000000-0xd000ffff: good pcib0: matched entry for 0.4.INTA pcib0: slot 4 INTA hardwired to IRQ 16 pcib2: slot 0 INTA is routed to irq 16 bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xd0000000 bge0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 256 to vector 49 bge0: using IRQ 256 for MSI miibus0: on bge0 ---Type to continue, or q to quit--- brgphy0: PHY 1 on miibus0 brgphy0: OUI 0x000af7, model 0x0004, rev. 0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bge0: bpf attached bge0: Ethernet address: 00:1f:29:89:38:f3 bge0: [MPSAFE] bge0: [ITHREAD] pcib3: at device 5.0 on pci0 pcib3: domain 0 pcib3: secondary bus 32 pcib3: subordinate bus 32 pcib3: I/O decode 0x2000-0x3fff pcib3: memory decode 0xcc000000-0xcfffffff pcib3: no prefetched decode pcib3: could not get PCI interrupt routing table for \_SB_.C08B.C255 - AE_NOT_FOUND pci32: on pcib3 pci32: domain=0, physical bus=32 pcib4: at device 6.0 on pci0 pcib4: domain 0 pcib4: secondary bus 48 pcib4: subordinate bus 48 pcib4: I/O decode 0xf000-0xfff pcib4: memory decode 0xc8000000-0xc80fffff pcib4: no prefetched decode pcib4: could not get PCI interrupt routing table for \_SB_.C08B.C25F - AE_NOT_FOUND pci48: on pcib4 pci48: domain=0, physical bus=48 found-> vendor=0x14e4, dev=0x4312, revid=0x02 domain=0, bus=48, slot=0, func=0 class=02-80-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=10 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xc8000000, size 14, enabled pcib4: requested memory range 0xc8000000-0xc8003fff: good pcib0: matched entry for 0.6.INTA pcib0: slot 6 INTA hardwired to IRQ 18 pcib4: slot 0 INTA is routed to irq 18 pci48: at device 0.0 (no driver attached) atapci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at devi---Type to continue, or q to quit--- ce 18.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x5020 atapci0: Reserved 0x400 bytes for rid 0x24 type 3 at 0xd0409000 ioapic0: routing intpin 16 (PCI IRQ 16) to vector 50 atapci0: [MPSAFE] atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports PM not supported ata2: on atapci0 ata2: SATA connect time=0ms ata2: BUSY wait time=1ms ata2: SIGNATURE: 00000101 ata2: ahci_reset devices=00000001 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci0 ata3: port not implemented ata3: [MPSAFE] ata3: [ITHREAD] ata4: on atapci0 ata4: port not implemented ata4: [MPSAFE] ata4: [ITHREAD] ata5: on atapci0 ata5: port not implemented ata5: [MPSAFE] ata5: [ITHREAD] ohci0: mem 0xd0401000-0xd0401fff irq 23 at device 19.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0401000 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 51 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xd0402000-0xd0402fff irq 17 at device 19.1 on pci0 ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0402000 ioapic0: routing intpin 17 (PCI IRQ 17) to vector 52 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support ---Type to continue, or q to quit--- usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xd0403000-0xd0403fff irq 17 at device 19.2 on pci0 ohci2: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0403000 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ohci3: mem 0xd0404000-0xd0404fff irq 17 at device 19.3 on pci0 ohci3: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0404000 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: on ohci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ohci4: mem 0xd0405000-0xd0405fff irq 17 at device 19.4 on pci0 ohci4: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0405000 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: on ohci4 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered ehci0: mem 0xd0406000-0xd04060ff irq 23 at device 19.5 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xd0406000 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] ehci0: Dropped interrupts workaround enabled usb5: EHCI version 1.0 usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 usb5: on ehci0 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 10 ports with 10 removable, self powered ---Type to continue, or q to quit--- pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0x5040 ata0: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x10000 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 53 ata0: [MPSAFE] ata0: [ITHREAD] hdac0: irq 16 at device 20.2 on pci0 hdac0: HDA Driver Revision: 20081123_0118 hdac0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0x80000000 hdac0: [MPSAFE] hdac0: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib5: at device 20.4 on pci0 pcib5: domain 0 pcib5: secondary bus 2 pcib5: subordinate bus 3 pcib5: I/O decode 0xf000-0xfff pcib5: memory decode 0xd0100000-0xd01fffff pcib5: no prefetched decode pcib5: Subtractively decoded bridge. pci2: on pcib5 pci2: domain=0, physical bus=2 found-> vendor=0x1180, dev=0x0476, revid=0xb6 domain=0, bus=2, slot=4, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd0100000, size 12, enabled pcib5: requested memory range 0xd0100000-0xd0100fff: good pcib5: matched entry for 2.4.INTA pcib5: slot 4 INTA hardwired to IRQ 20 cbb0: mem 0xd0100000-0xd0100fff irq 20 at device 4.0 on pci2 ---Type to continue, or q to quit--- cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xd0100000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 ioapic0: routing intpin 20 (PCI IRQ 20) to vector 54 cbb0: [MPSAFE] cbb0: [FILTER] cbb0: PCI Configuration space: 0x00: 0x04761180 0x02100007 0x060700b6 0x00824000 0x10: 0xd0100000 0x020000dc 0x20030302 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x07000114 0x40: 0x30c2103c 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x30a00001 0x00000000 0x04630463 0x00000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x00000008 0x00000000 0x00000000 0x00000000 0xb0: 0x00000000 0xbe000000 0x00003000 0x00000000 0xc0: 0x30c2103c 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 battery0: on acpi0 battery1: on acpi0 acpi_acad0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 atrtc0: port 0x70-0x71,0x72-0x73 irq 8 on acpi0 atrtc0: registered as a time-of-day clock (resolution 1000000us) 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 ---Type to continue, or q to quit--- 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, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 cpu0: on acpi0 cpu0: switching to generic Cx mode acpi_throttle0: on cpu0 acpi_throttle0: P_CNT from P_BLK 0x8010 powernow0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 powernow1: on cpu1 ahc_isa_probe 0: ioport 0xc00 alloc failed ex_isa_identify() isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: probing non-PnP devices orm0: at iomem 0xd0000-0xd0fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0: failed to probe at irq 7 on isa0 uart0: failed to probe at port 0x3f8-0x3ff irq 4 on isa0 uart1: failed to probe at port 0x2f8-0x2ff irq 3 on isa0 uart2: not probed (disabled) uart3: not probed (disabled) isa_probe_children: probing PnP devices ubt0: on uhub0 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=10, buffer size=640 ums0: on uhub1 ---Type to continue, or q to quit--- ums0: 3 buttons and Z dir. Device configuration finished. Reducing kern.maxvnodes 124747 -> 100000 procfs registered lapic: Divisor 2, Frequency 99746224 hz Timecounter "TSC" frequency 1994924370 Hz quality -100 Timecounters tick every 1.000 msec lo0: bpf attached hptrr: no controller detected. ata0: identify ch->devices=00010000 acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0 acpi_tz0: _AC1: temperature 66.0 >= setpoint 60.0 acpi_tz0: switched from NONE to _AC1: 66.0C ata0-master: pio=PIO4 wdma=WDMA2 udma=UNSUPPORTED cable=40 wire battery0: battery initialization start acd0: setting PIO4 on IXP600 chip battery1: battery initialization start acpi_acad0: acline initialization start acd0: DVDR drive at ata0 as master acd0: read 4134KB/s (4134KB/s) write 4134KB/s (4134KB/s), 2048KB buffer, PIO4 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata2: identify ch->devices=00000001 ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ad4: 152627MB at ata2-master SATA300 ad4: 312581808 sectors [310101C/16H/63S] 16 sectors/interrupt 1 depth queue acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0 acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0 battery0: battery initialization done, tried 1 times GEOM: new disk ad4 ad4: Silicon Image check3 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ---Type to continue, or q to quit--- ad4: FreeBSD check1 failed ata3: identify ch->devices=00000000 ata4: identify ch->devices=00000000 ata5: identify ch->devices=00000000 hdac0: Probing codec #0... hdac0: HDA Codec #0: Analog Devices AD1981HD hdac0: HDA Codec ID: 0x11d41981 hdac0: Vendor: 0x11d4 hdac0: Device: 0x1981 hdac0: Revision: 0x02 hdac0: Stepping: 0x00 hdac0: PCI Subvendor: 0x30c2103c hdac0: Found audio FG nid=1 startnode=2 endnode=32 total=30 hdac0: Probing codec #1... hdac0: HDA Codec #1: Lucent/Agere Systems (Unknown) hdac0: HDA Codec ID: 0x11c11040 hdac0: Vendor: 0x11c1 hdac0: Device: 0x1040 hdac0: Revision: 0x02 hdac0: Stepping: 0x00 hdac0: PCI Subvendor: 0x30c2103c hdac0: Found modem FG nid=1 startnode=2 endnode=127 total=125 hdac0: hdac0: Processing audio FG cad=0 nid=1... hdac0: GPIO: 0x40000004 NumGPIO=4 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 hdac0: GHOST: nid=2 j=0 entnum=4 index=0 res=0x00000401 hdac0: nid 5 0x92174110 as 1 seq 0 Speaker Fixed jack 7 loc 18 color Green misc 1 hdac0: nid 6 0x0421201f as 1 seq 15 Headphones Jack jack 1 loc 4 color Grey misc 0 hdac0: nid 7 0x410710f0 as 15 seq 0 Line-out None jack 7 loc 1 color Black misc 0 hdac0: nid 8 0x04a12020 as 2 seq 0 Mic Jack jack 1 loc 4 color Grey misc 0 hdac0: nid 9 0x0181302e as 2 seq 14 Line-in Jack jack 1 loc 1 color Blue misc 0 hdac0: nid 10 0x4145f0f0 as 15 seq 0 SPDIF-out None jack 5 loc 1 color Other misc 0 hdac0: nid 22 0x995711f0 as 15 seq 0 Digital-out Fixed jack 7 loc 25 color Black misc 1 hdac0: nid 23 0x5993e0f0 as 15 seq 0 AUX None jack 3 loc 25 color White misc 0 hdac0: nid 24 0xf0a79159 as 5 seq 9 Mic Both jack 7 loc 48 color Pink misc 1 hdac0: nid 25 0x593310f0 as 15 seq 0 CD None jack 3 loc 25 color Black misc 0 hdac0: Patched pins configuration: hdac0: nid 5 0x92174110 as 1 seq 0 Speaker Fixed jack 7 loc 18 color Green misc 1 hdac0: nid 6 0x0421201f as 1 seq 15 Headphones Jack jack 1 loc 4 color Grey misc 0 hdac0: nid 7 0x410710f0 as 15 seq 0 Line-out None jack 7 loc 1 color Black misc 0 [DISABLED] hdac0: nid 8 0x04a12020 as 2 seq 0 Mic Jack jack 1 loc 4 color Grey misc 0 hdac0: nid 9 0x0181302e as 2 seq 14 Line-in Jack jack 1 loc 1 color Blue misc 0 ---Type to continue, or q to quit--- hdac0: nid 10 0x4145f0f0 as 15 seq 0 SPDIF-out None jack 5 loc 1 color Other misc 0 [DISABLED] hdac0: nid 22 0x995711f0 as 15 seq 0 Digital-out Fixed jack 7 loc 25 color Black misc 1 hdac0: nid 23 0x5993e0f0 as 15 seq 0 AUX None jack 3 loc 25 color White misc 0 [DISABLED] hdac0: nid 24 0xf0a79159 as 5 seq 9 Mic Both jack 7 loc 48 color Pink misc 1 hdac0: nid 25 0x593310f0 as 15 seq 0 CD None jack 3 loc 25 color Black misc 0 [DISABLED] hdac0: 4 associations found: hdac0: Association 0 (1) out: hdac0: Pin nid=5 seq=0 hdac0: Pin nid=6 seq=15 hdac0: Association 1 (2) in: hdac0: Pin nid=8 seq=0 hdac0: Pin nid=9 seq=14 hdac0: Association 2 (5) in: hdac0: Pin nid=24 seq=9 hdac0: Association 3 (15) out: hdac0: Pin nid=22 seq=0 hdac0: Tracing association 0 (1) hdac0: Pin 5 traced to DAC 3 hdac0: Pin 6 traced to DAC 3 and hpredir 0 hdac0: Association 0 (1) trace succeded hdac0: Tracing association 1 (2) hdac0: Pin 8 traced to ADC 4 hdac0: Pin 9 traced to ADC 4 hdac0: Association 1 (2) trace succeded hdac0: Tracing association 2 (5) hdac0: Association 2 (5) trace failed hdac0: Tracing association 3 (15) hdac0: Unable to trace pin 22 seq 0 with min nid 0 hdac0: Association 3 (15) trace failed hdac0: Tracing input monitor hdac0: Tracing nid 12 to out hdac0: Tracing beeper hdac0: Enabling headphone/speaker audio routing switching: hdac0: as=0 sense nid=6 [UNSOL] hdac0: Pin sense: nid=6 res=0x0000f5df hdac0: FG config/quirks: forcestereo ivref50 ivref80 ivref100 ivref hdac0: hdac0: +-------------------+ hdac0: | DUMPING HDA NODES | hdac0: +-------------------+ hdac0: hdac0: Default Parameter ---Type to continue, or q to quit--- hdac0: ----------------- hdac0: Stream cap: 0x00000001 hdac0: PCM hdac0: PCM cap: 0x000e007f hdac0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz hdac0: IN amp: 0x00270300 hdac0: OUT amp: 0x80053f3d hdac0: hdac0: nid: 2 [DISABLED] hdac0: Name: audio output hdac0: Widget cap: 0x00030311 hdac0: DIGITAL STEREO hdac0: Stream cap: 0x00000005 hdac0: AC3 PCM hdac0: PCM cap: 0x00020060 hdac0: 16 bits, 44 48 KHz hdac0: connections: 2 hdac0: | hdac0: + [DISABLED] <- nid=1 [GHOST!] [UNKNOWN] (selected) hdac0: + <- nid=4 [audio input] hdac0: hdac0: nid: 3 hdac0: Name: audio output hdac0: Widget cap: 0x00000441 hdac0: PWR PROC STEREO hdac0: Association: 0 (0x00008001) hdac0: OSS: pcm (pcm) hdac0: Stream cap: 0x00000001 hdac0: PCM hdac0: PCM cap: 0x000e007f hdac0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz hdac0: hdac0: nid: 4 hdac0: Name: audio input hdac0: Widget cap: 0x00100511 hdac0: PWR STEREO hdac0: Association: 1 (0x00004001) hdac0: Stream cap: 0x00000001 hdac0: PCM hdac0: PCM cap: 0x0006007f hdac0: 16 20 bits, 8 11 16 22 32 44 48 KHz hdac0: connections: 1 ---Type to continue, or q to quit--- hdac0: | hdac0: + <- nid=21 [audio selector] hdac0: hdac0: nid: 5 hdac0: Name: pin: Speaker (Fixed) hdac0: Widget cap: 0x00400187 hdac0: UNSOL STEREO hdac0: Association: 0 (0x00000001) hdac0: Pin cap: 0x0001173f hdac0: ISC TRQD PDC HP OUT IN VREF[ 50 80 GROUND HIZ ] EAPD hdac0: Pin config: 0x92174110 hdac0: Pin control: 0x00000040 OUT hdac0: EAPD: 0x00000002 hdac0: Output amp: 0x80053f3d hdac0: mute=1 step=63 size=5 offset=61 hdac0: Input amp: 0x00270300 hdac0: mute=0 step=3 size=39 offset=0 hdac0: connections: 2 hdac0: | hdac0: + <- nid=3 [audio output] (selected) hdac0: + [DISABLED] <- nid=14 [audio mixer] [DISABLED] hdac0: hdac0: nid: 6 hdac0: Name: pin: Headphones (Jack) hdac0: Widget cap: 0x00400185 hdac0: UNSOL STEREO hdac0: Association: 0 (0x00008000) hdac0: Pin cap: 0x0000001f hdac0: ISC TRQD PDC HP OUT hdac0: Pin config: 0x0421201f hdac0: Pin control: 0x000000c0 HP OUT hdac0: Output amp: 0x80053f3d hdac0: mute=1 step=63 size=5 offset=61 hdac0: connections: 2 hdac0: | hdac0: + <- nid=3 [audio output] (selected) hdac0: + [DISABLED] <- nid=14 [audio mixer] [DISABLED] hdac0: hdac0: nid: 7 [DISABLED] hdac0: Name: pin: Line-out (None) hdac0: Widget cap: 0x00400104 hdac0: Pin cap: 0x00000010 ---Type to continue, or q to quit--- hdac0: OUT hdac0: Pin config: 0x410710f0 hdac0: Pin control: 0x00000000 hdac0: Output amp: 0x80053f3d hdac0: mute=1 step=63 size=5 offset=61 hdac0: connections: 1 hdac0: | hdac0: + [DISABLED] <- nid=15 [audio mixer] [DISABLED] hdac0: hdac0: nid: 8 hdac0: Name: pin: Mic (Jack) hdac0: Widget cap: 0x00400083 hdac0: UNSOL STEREO hdac0: Association: 1 (0x00000001) hdac0: OSS: mic (mic) hdac0: Pin cap: 0x00001727 hdac0: ISC TRQD PDC IN VREF[ 50 80 GROUND HIZ ] hdac0: Pin config: 0x04a12020 hdac0: Pin control: 0x00000024 IN VREFs hdac0: Input amp: 0x00270300 hdac0: mute=0 step=3 size=39 offset=0 hdac0: hdac0: nid: 9 hdac0: Name: pin: Line-in (Jack) hdac0: Widget cap: 0x00400187 hdac0: UNSOL STEREO hdac0: Association: 1 (0x00004000) hdac0: OSS: line (line) hdac0: Pin cap: 0x00001737 hdac0: ISC TRQD PDC OUT IN VREF[ 50 80 GROUND HIZ ] hdac0: Pin config: 0x0181302e hdac0: Pin control: 0x00000024 IN VREFs hdac0: Output amp: 0x80053f3d hdac0: mute=1 step=63 size=5 offset=61 hdac0: Input amp: 0x00270300 hdac0: mute=0 step=3 size=39 offset=0 hdac0: connections: 2 hdac0: | hdac0: + [DISABLED] <- nid=3 [audio output] (selected) hdac0: + [DISABLED] <- nid=14 [audio mixer] [DISABLED] hdac0: hdac0: nid: 10 [DISABLED] ---Type to continue, or q to quit--- hdac0: Name: pin: SPDIF-out (None) hdac0: Widget cap: 0x00400301 hdac0: DIGITAL STEREO hdac0: Pin cap: 0x00000010 hdac0: OUT hdac0: Pin config: 0x4145f0f0 hdac0: Pin control: 0x00000000 hdac0: connections: 1 hdac0: | hdac0: + <- nid=2 [audio output] [DISABLED] hdac0: hdac0: nid: 11 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x00300101 hdac0: STEREO hdac0: connections: 6 hdac0: | hdac0: + <- nid=3 [audio output] (selected) hdac0: + <- nid=12 [audio mixer] hdac0: + <- nid=9 [pin: Line-in (Jack)] hdac0: + [DISABLED] <- nid=14 [audio mixer] [DISABLED] hdac0: + <- nid=5 [pin: Speaker (Fixed)] hdac0: + <- nid=24 [pin: Mic (Both)] [DISABLED] hdac0: hdac0: nid: 12 hdac0: Name: audio mixer hdac0: Widget cap: 0x00200101 hdac0: STEREO hdac0: Association: 1 (0x00000001) hdac0: OSS: mic hdac0: connections: 2 hdac0: | hdac0: + <- nid=30 [audio selector] hdac0: + [DISABLED] <- nid=31 [audio selector] [DISABLED] hdac0: hdac0: nid: 13 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x0030010c hdac0: Output amp: 0x800b0f0f hdac0: mute=1 step=15 size=11 offset=15 hdac0: connections: 2 hdac0: | ---Type to continue, or q to quit--- hdac0: + <- nid=16 [beep widget] (selected) hdac0: + <- nid=22 [pin: Digital-out (Fixed)] [DISABLED] hdac0: hdac0: nid: 14 [DISABLED] hdac0: Name: audio mixer hdac0: Widget cap: 0x00200101 hdac0: STEREO hdac0: connections: 8 hdac0: | hdac0: + <- nid=13 [audio selector] [DISABLED] hdac0: + <- nid=17 [audio selector] [DISABLED] hdac0: + <- nid=18 [audio selector] [DISABLED] hdac0: + <- nid=19 [audio selector] [DISABLED] hdac0: + <- nid=26 [audio selector] [DISABLED] hdac0: + <- nid=27 [audio selector] [DISABLED] hdac0: + <- nid=28 [audio selector] [DISABLED] hdac0: + <- nid=29 [audio selector] [DISABLED] hdac0: hdac0: nid: 15 [DISABLED] hdac0: Name: audio mixer hdac0: Widget cap: 0x00200100 hdac0: connections: 1 hdac0: | hdac0: + <- nid=11 [audio selector] [DISABLED] hdac0: hdac0: nid: 16 hdac0: Name: beep widget hdac0: Widget cap: 0x00700000 hdac0: Association: -2 (0x00000000) hdac0: OSS: speaker (speaker) hdac0: hdac0: nid: 17 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Output amp: 0x80051f17 hdac0: mute=1 step=31 size=5 offset=23 hdac0: connections: 1 hdac0: | hdac0: + <- nid=3 [audio output] hdac0: hdac0: nid: 18 [DISABLED] ---Type to continue, or q to quit--- hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Output amp: 0x80051f17 hdac0: mute=1 step=31 size=5 offset=23 hdac0: connections: 1 hdac0: | hdac0: + <- nid=8 [pin: Mic (Jack)] hdac0: hdac0: nid: 19 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Output amp: 0x80051f17 hdac0: mute=1 step=31 size=5 offset=23 hdac0: connections: 1 hdac0: | hdac0: + <- nid=9 [pin: Line-in (Jack)] hdac0: hdac0: nid: 20 [DISABLED] hdac0: Name: power widget hdac0: Widget cap: 0x00500500 hdac0: PWR hdac0: connections: 13 hdac0: | hdac0: + <- nid=13 [audio selector] [DISABLED] (selected) hdac0: + <- nid=14 [audio mixer] [DISABLED] hdac0: + <- nid=15 [audio mixer] [DISABLED] hdac0: + <- nid=16 [beep widget] hdac0: + <- nid=19 [audio selector] [DISABLED] hdac0: + <- nid=20 [power widget] [DISABLED] hdac0: + <- nid=21 [audio selector] hdac0: + <- nid=22 [pin: Digital-out (Fixed)] [DISABLED] hdac0: + <- nid=23 [pin: AUX (None)] [DISABLED] hdac0: + <- nid=24 [pin: Mic (Both)] [DISABLED] hdac0: + <- nid=25 [pin: CD (None)] [DISABLED] hdac0: + <- nid=26 [audio selector] [DISABLED] hdac0: + <- nid=29 [audio selector] [DISABLED] hdac0: hdac0: nid: 21 hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d ---Type to continue, or q to quit--- hdac0: STEREO hdac0: Association: 1 (0x00004001) hdac0: OSS: line, mic hdac0: Output amp: 0x80050f00 hdac0: mute=1 step=15 size=5 offset=0 hdac0: connections: 8 hdac0: | hdac0: + <- nid=12 [audio mixer] (selected) hdac0: + <- nid=9 [pin: Line-in (Jack)] hdac0: + [DISABLED] <- nid=14 [audio mixer] [DISABLED] hdac0: + [DISABLED] <- nid=15 [audio mixer] [DISABLED] hdac0: + [DISABLED] <- nid=25 [pin: CD (None)] [DISABLED] hdac0: + [DISABLED] <- nid=5 [pin: Speaker (Fixed)] hdac0: + [DISABLED] <- nid=24 [pin: Mic (Both)] [DISABLED] hdac0: + [DISABLED] <- nid=23 [pin: AUX (None)] [DISABLED] hdac0: hdac0: nid: 22 [DISABLED] hdac0: Name: pin: Digital-out (Fixed) hdac0: Widget cap: 0x00400000 hdac0: Pin cap: 0x00000020 hdac0: IN hdac0: Pin config: 0x995711f0 hdac0: Pin control: 0x00000000 hdac0: hdac0: nid: 23 [DISABLED] hdac0: Name: pin: AUX (None) hdac0: Widget cap: 0x00400081 hdac0: UNSOL STEREO hdac0: Pin cap: 0x00000027 hdac0: ISC TRQD PDC IN hdac0: Pin config: 0x5993e0f0 hdac0: Pin control: 0x00000000 hdac0: hdac0: nid: 24 [DISABLED] hdac0: Name: pin: Mic (Both) hdac0: Widget cap: 0x00400187 hdac0: UNSOL STEREO hdac0: Pin cap: 0x00001737 hdac0: ISC TRQD PDC OUT IN VREF[ 50 80 GROUND HIZ ] hdac0: Pin config: 0xf0a79159 hdac0: Pin control: 0x00000000 hdac0: Output amp: 0x80053f3d ---Type to continue, or q to quit--- hdac0: mute=1 step=63 size=5 offset=61 hdac0: Input amp: 0x00270300 hdac0: mute=0 step=3 size=39 offset=0 hdac0: connections: 2 hdac0: | hdac0: + [DISABLED] <- nid=3 [audio output] (selected) hdac0: + [DISABLED] <- nid=14 [audio mixer] [DISABLED] hdac0: hdac0: nid: 25 [DISABLED] hdac0: Name: pin: CD (None) hdac0: Widget cap: 0x00400001 hdac0: STEREO hdac0: Pin cap: 0x00000020 hdac0: IN hdac0: Pin config: 0x593310f0 hdac0: Pin control: 0x00000000 hdac0: hdac0: nid: 26 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Output amp: 0x80051f17 hdac0: mute=1 step=31 size=5 offset=23 hdac0: connections: 1 hdac0: | hdac0: + <- nid=5 [pin: Speaker (Fixed)] hdac0: hdac0: nid: 27 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Output amp: 0x80051f17 hdac0: mute=1 step=31 size=5 offset=23 hdac0: connections: 1 hdac0: | hdac0: + [DISABLED] <- nid=23 [pin: AUX (None)] [DISABLED] hdac0: hdac0: nid: 28 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Output amp: 0x80051f17 ---Type to continue, or q to quit--- hdac0: mute=1 step=31 size=5 offset=23 hdac0: connections: 1 hdac0: | hdac0: + <- nid=24 [pin: Mic (Both)] [DISABLED] hdac0: hdac0: nid: 29 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Output amp: 0x80051f17 hdac0: mute=1 step=31 size=5 offset=23 hdac0: connections: 1 hdac0: | hdac0: + [DISABLED] <- nid=25 [pin: CD (None)] [DISABLED] hdac0: hdac0: nid: 30 hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Association: 1 (0x00000001) hdac0: OSS: mic hdac0: Output amp: 0x80000000 hdac0: mute=1 step=0 size=0 offset=0 hdac0: connections: 1 hdac0: | hdac0: + <- nid=8 [pin: Mic (Jack)] hdac0: hdac0: nid: 31 [DISABLED] hdac0: Name: audio selector hdac0: Widget cap: 0x0030010d hdac0: STEREO hdac0: Output amp: 0x80000000 hdac0: mute=1 step=0 size=0 offset=0 hdac0: connections: 1 hdac0: | hdac0: + <- nid=24 [pin: Mic (Both)] [DISABLED] hdac0: hdac0: Processing modem FG cad=1 nid=1... hdac0: pcm0: at cad 0 nid 1 on hdac0 pcm0: +--------------------------------------+ pcm0: | DUMPING PCM Playback/Record Channels | ---Type to continue, or q to quit--- pcm0: +--------------------------------------+ pcm0: pcm0: Playback: pcm0: pcm0: Stream cap: 0x00000001 pcm0: PCM pcm0: PCM cap: 0x000e007f pcm0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz pcm0: DAC: 3 pcm0: pcm0: Record: pcm0: pcm0: Stream cap: 0x00000001 pcm0: PCM pcm0: PCM cap: 0x0006007f pcm0: 16 20 bits, 8 11 16 22 32 44 48 KHz pcm0: ADC: 4 pcm0: pcm0: +--------------------------------+ pcm0: | DUMPING Playback/Record Pathes | pcm0: +--------------------------------+ pcm0: pcm0: Playback: pcm0: pcm0: nid=5 [pin: Speaker (Fixed)] pcm0: | pcm0: + <- nid=3 [audio output] [src: pcm] pcm0: pcm0: nid=6 [pin: Headphones (Jack)] pcm0: | pcm0: + <- nid=3 [audio output] [src: pcm] pcm0: pcm0: Record: pcm0: pcm0: nid=4 [audio input] pcm0: | pcm0: + <- nid=21 [audio selector] [src: line, mic] pcm0: | pcm0: + <- nid=12 [audio mixer] [src: mic] pcm0: | pcm0: + <- nid=30 [audio selector] [src: mic] pcm0: | ---Type to continue, or q to quit--- pcm0: + <- nid=8 [pin: Mic (Jack)] [src: mic] pcm0: + <- nid=9 [pin: Line-in (Jack)] [src: line] pcm0: pcm0: +-------------------------+ pcm0: | DUMPING Volume Controls | pcm0: +-------------------------+ pcm0: pcm0: Master Volume (OSS: vol) pcm0: | pcm0: +- ctl 1 (nid 5 in ): -91/3dB (64 steps) + mute pcm0: +- ctl 3 (nid 6 in ): -91/3dB (64 steps) + mute pcm0: pcm0: PCM Volume (OSS: pcm) pcm0: | pcm0: +- ctl 1 (nid 5 in ): -91/3dB (64 steps) + mute pcm0: +- ctl 3 (nid 6 in ): -91/3dB (64 steps) + mute pcm0: pcm0: Microphone Volume (OSS: mic) pcm0: | pcm0: +- ctl 5 (nid 8 out): 0/30dB (4 steps) pcm0: +- ctl 19 (nid 30 out): mute pcm0: pcm0: Line-in Volume (OSS: line) pcm0: | pcm0: +- ctl 7 (nid 9 out): 0/30dB (4 steps) pcm0: pcm0: Recording Level (OSS: rec) pcm0: | pcm0: +- ctl 12 (nid 21 out): 0/22dB (16 steps) + mute pcm0: +- ctl 19 (nid 30 out): mute pcm0: pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "rec": pcm0: Mixer "ogain": pcm0: clone manager: deadline=750ms flags=0x8000001e pcm0: sndbuf_setmap 1970000, 4000; 0xfffffffe78dc3000 -> 1970000 pcm0: sndbuf_setmap 1780000, 4000; 0xfffffffe78dd3000 -> 1780000 ATA PseudoRAID loaded SMP: AP CPU #1 Launched! ---Type to continue, or q to quit--- cpu1 AP: ID: 0x01000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00000400 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 9 to local APIC 1 ioapic0: Assigning ISA IRQ 12 to local APIC 0 ioapic0: Assigning ISA IRQ 14 to local APIC 1 ioapic0: Assigning PCI IRQ 16 to local APIC 0 ioapic0: Assigning PCI IRQ 17 to local APIC 1 ioapic0: Assigning PCI IRQ 20 to local APIC 0 ioapic0: Assigning PCI IRQ 23 to local APIC 1 msi: Assigning MSI IRQ 256 to local APIC 0 Trying to mount root from ufs:/dev/ad4s1a WARNING: / was not properly dismounted /: mount pending error: blocks 8 files 3 ct_to_ts([2008-12-16 19:33:55]) = 1229456035.000000000 start_init: trying /sbin/init <118>Entropy harvesting: kickstart. acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 (probe0:ata0:0:0:0): error 22 (probe0:ata0:0:0:0): Unretryable Error pass0 at ata0 bus 0 target 0 lun 0 pass0: Removable CD-ROM SCSI-0 device pass0: 16.000MB/s transfers GEOM: new disk cd0 (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error (cd0:ata0:0:0:0): error 6 (cd0:ata0:0:0:0): Unretryable Error acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 59.0 >= setpoint 50.0 ---Type to continue, or q to quit--- acpi_tz0: switched from _AC1 to _AC2: 59.0C acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 55.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 55.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0 battery1: battery initialization failed, giving up acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 52.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 55.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0 <118>/dev/ad4s1a: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) <118>/dev/ad4s1a: SUMMARY INFORMATION BAD (SALVAGED) <118>/dev/ad4s1a: BLK(S) MISSING IN BIT MAPS (SALVAGED) <118>/dev/ad4s1a: 453034 files, 20740782 used, 53902307 free (100531 frags, 6725222 blocks, 0.1% fragmentation) WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD. <118>/etc/rc: WARNING: $hostname is not set -- see rc.conf(5). <118>Starting Network: lo0. <118>hw.bus.devctl_disable: 0 -> 1 <118>Additional TCP/IP options: tcp extensions=NO TCP keepalive=NO. <118>savecore: reboot after panic: page fault <118>savecore: writing core to vmcore.10 acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0 <118>Removing stale Samba tdb files: done <118>Configuring syscons: blanktime. <118>Local package initialization:[: =: unexpected operator acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0 <118>ipfw: : (skipping /usr/local/etc/rc.d/kdm.sh, not executable) rtcLinux ELF exec handler installed <118>. <118>/etc/rc.d/sysctl: WARNING: sysctl dev.pcm.0.vchans does not exist. <118> <118>Tue Dec 16 19:36:18 MSK 2008 <118>date: : acpi_tz0: _AC3: temperature 52.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 52.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0 ---Type to continue, or q to quit--- acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 51.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 50.0 >= setpoint 40.0 hdac0: wake_prep disabled wake for \_SB_.C08B.C0FD (S3) pci0:1:5:0: Transition from D0 to D3 pci0:16:0:0: Transition from D0 to D3 vga0: saving 68 bytes of video state pci0:0:18:0: Transition from D0 to D3 pci0:0:19:5: Transition from D0 to D3 pci0:0:20:2: Transition from D0 to D3 acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0 acpi_tz0: switched from _AC2 to _AC3: 54.0C ata2: reiniting channel .. ata2: CONNECT requested ata2: SATA connect time=0ms ata2: BUSY wait time=1ms ata2: SIGNATURE: 00000101 ata2: ahci_reset devices=00000001 ata2: CONNECTED ata2: SATA connect time=0ms ata2: BUSY wait time=1ms ata2: SIGNATURE: 00000101 ata2: ahci_reset devices=00000001 ata2: identify ch->devices=00000001 ata2: reinit done .. ---Type to continue, or q to quit--- ata3: reiniting channel .. ata3: port not implemented ata3: reinit done .. ata4: reiniting channel .. ata4: port not implemented ata4: reinit done .. ata5: reiniting channel .. ata5: port not implemented ata5: reinit done .. acpi_tz0: _AC2: temperature 56.0 >= setpoint 55.0 acpi_tz0: switched from _AC3 to _AC2: 56.0C acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0 ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=00 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x10000 ubt0: at uhub0 port 2 (addr 2) disconnected ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=40 wire ad: ad4 already exists; skipping it ad: ad4 already exists; skipping it Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x50 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff80551631 stack pointer = 0x10:0xfffffffe4005bad0 frame pointer = 0x10:0xfffffffe4005bb20 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (thread taskq) trap number = 12 panic: page fault cpuid = 1 Uptime: 6m23s Physical memory: 1905 MB Dumping 217 MB: 202 186 170 154 138 122 106 90 74 58 42 26 10(kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) (kgdb) quit HP# exit exit Script done on Tue Dec 16 19:50:51 2008 From pluknet at gmail.com Tue Dec 16 17:02:35 2008 From: pluknet at gmail.com (pluknet) Date: Tue Dec 16 17:02:42 2008 Subject: [acpi] panic: knlist locked, but should not be Message-ID: Hi, Reproducible panic after entering into acpiconf -s 3 on -current SMP i386. [manually transcribed] panic: knlist locked, but should not be cpuid = 1 KDB: enter: panic [thread pid 1107 tid 100062 ] Stopped at kdb_enter db> bt Tracing pid 1107... kdb_enter panic knote acpi_ReqSleepState acpiioctl devfs_ioctl_f kern_ioctl ioctl syscall ... db> show locks exclusive sleep mutex ACPI global lock (ACPI global lock r = 0 (0xc086b040) loc ked @ /usr/src/sys/dev/acpica/acpi.c:2316 I'm still in ddb and can give further info if needed. -- wbr, pluknet From dynasore at bigfoot.com Fri Dec 19 14:58:23 2008 From: dynasore at bigfoot.com (David van Kuijk) Date: Fri Dec 19 14:58:30 2008 Subject: Problem on AMD64 Message-ID: <494C22EA.5010408@bigfoot.com> Hi I try to put my machine in sleep state but get the message that this is not supported. command and result: $ acpiconf -s 4 acpiconf: request sleep type (4) failed: Operation not supported I get the same message for other sleep states 1,2,3. My machine is a HP Proliant ML115 AMD64 running FreeBSD 7.0-RELEASE Result from sysctl hw.acpi is hw.acpi.supported_sleep_state: S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S4 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 $ dmesg | grep acpi acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi_timer0: <24-bit timer at 3.579545MHz> port 0x2008-0x200b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 acpi_button0: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Anyone suggestions to a solution or is this a bug? Best regards, David From yanefbsd at gmail.com Fri Dec 19 19:45:45 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 19 19:45:51 2008 Subject: Problem on AMD64 In-Reply-To: <494C22EA.5010408@bigfoot.com> References: <494C22EA.5010408@bigfoot.com> Message-ID: <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> On 12/19/08, David van Kuijk wrote: > Hi > > I try to put my machine in sleep state but get the message that this is > not supported. > > command and result: > $ acpiconf -s 4 > acpiconf: request sleep type (4) failed: Operation not supported > > I get the same message for other sleep states 1,2,3. > > My machine is a HP Proliant ML115 AMD64 running FreeBSD 7.0-RELEASE > > Result from sysctl hw.acpi is > hw.acpi.supported_sleep_state: S4 S5 > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S4 > 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 > > $ dmesg | grep acpi > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x2008-0x200b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on > acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > acpi_button0: on acpi0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > > > Anyone suggestions to a solution or is this a bug? > > Best regards, > David ACPI support doesn't work on mainline FreeBSD. There is a testing patch available via this thread though: http://www.mavetju.org/mail/view_message.php?list=freebsd-acpi&id=2850196 -Garrett From nate at root.org Sat Dec 20 12:19:30 2008 From: nate at root.org (Nate Lawson) Date: Sat Dec 20 12:19:37 2008 Subject: Problem on AMD64 In-Reply-To: <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> References: <494C22EA.5010408@bigfoot.com> <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> Message-ID: <494D50F6.70303@root.org> Garrett Cooper wrote: > On 12/19/08, David van Kuijk wrote: >> I try to put my machine in sleep state but get the message that this is >> not supported. >> >> command and result: >> $ acpiconf -s 4 >> acpiconf: request sleep type (4) failed: Operation not supported >> >> I get the same message for other sleep states 1,2,3. >> >> My machine is a HP Proliant ML115 AMD64 running FreeBSD 7.0-RELEASE >> >> Result from sysctl hw.acpi is >> hw.acpi.supported_sleep_state: S4 S5 Only S4 (suspend to disk) or S5 (power off) are supported by your BIOS. >> Anyone suggestions to a solution or is this a bug? > > ACPI support doesn't work on mainline FreeBSD. There is a testing > patch available via this thread though: > > http://www.mavetju.org/mail/view_message.php?list=freebsd-acpi&id=2850196 The patch won't help fix this. Someone needs to implement suspend-to-disk since we don't yet support it. It's a pretty big project. -- Nate From yanefbsd at gmail.com Sat Dec 20 17:22:51 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Dec 20 17:22:58 2008 Subject: Problem on AMD64 In-Reply-To: <494D50F6.70303@root.org> References: <494C22EA.5010408@bigfoot.com> <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> <494D50F6.70303@root.org> Message-ID: <7d6fde3d0812201722l8af8ec1uee7a4b7f5de604dc@mail.gmail.com> Err... yes, that indeed would be a problem ><. I didn't realize he was looking for S4 (I thought he was looking for S2, S3). -Garrett On 12/20/08, Nate Lawson wrote: > Garrett Cooper wrote: >> On 12/19/08, David van Kuijk wrote: >>> I try to put my machine in sleep state but get the message that this is >>> not supported. >>> >>> command and result: >>> $ acpiconf -s 4 >>> acpiconf: request sleep type (4) failed: Operation not supported >>> >>> I get the same message for other sleep states 1,2,3. >>> >>> My machine is a HP Proliant ML115 AMD64 running FreeBSD 7.0-RELEASE >>> >>> Result from sysctl hw.acpi is >>> hw.acpi.supported_sleep_state: S4 S5 > > Only S4 (suspend to disk) or S5 (power off) are supported by your BIOS. > >>> Anyone suggestions to a solution or is this a bug? >> >> ACPI support doesn't work on mainline FreeBSD. There is a testing >> patch available via this thread though: >> >> http://www.mavetju.org/mail/view_message.php?list=freebsd-acpi&id=2850196 > > The patch won't help fix this. Someone needs to implement > suspend-to-disk since we don't yet support it. It's a pretty big project. > > -- > Nate > From ganbold at micom.mng.net Sat Dec 20 20:36:39 2008 From: ganbold at micom.mng.net (Ganbold) Date: Sat Dec 20 20:36:46 2008 Subject: ACPI error, No pointer back to NS node in buffer obj Message-ID: <494DBF33.7040301@micom.mng.net> Hi, These messages are appearing on CURRENT. ... cpu0: on acpi0 ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj 0x854857c0 [20070320] ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\_PR_.CPU0._OSC] (Node 0x852c2620), AE_AML_INTERNAL est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj 0x85477c00 [20070320] ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\_PR_.CPU1._OSC] (Node 0x852c2540), AE_AML_INTERNAL est1: on cpu1 ... Are above messages harmful? Additional infos at: http://people.freebsd.org/~ganbold/acpi.txt thanks, Ganbold -- Being popular is important. Otherwise people might not like you. From dynasore at bigfoot.com Sun Dec 21 13:50:09 2008 From: dynasore at bigfoot.com (David van Kuijk) Date: Sun Dec 21 13:50:16 2008 Subject: Problem on AMD64 In-Reply-To: <7d6fde3d0812201722l8af8ec1uee7a4b7f5de604dc@mail.gmail.com> References: <494C22EA.5010408@bigfoot.com> <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> <494D50F6.70303@root.org> <7d6fde3d0812201722l8af8ec1uee7a4b7f5de604dc@mail.gmail.com> Message-ID: <494EB598.4020708@bigfoot.com> Thanks for the responses so far. I would be happy with S3. I am however a little confused about the abilities of my server as reported by sysctl hw.acpi. As commented below this line suggests that no other states than S4/S5 are supported: hw.acpi.supported_sleep_state: S4 S5 But this is also listed: hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 Are these last two overridden by the first, meaning that S3 is not available from my BIOS??? David Garrett Cooper wrote: > Err... yes, that indeed would be a problem ><. I didn't realize he was > looking for S4 (I thought he was looking for S2, S3). > -Garrett > > On 12/20/08, Nate Lawson wrote: >> Garrett Cooper wrote: >>> On 12/19/08, David van Kuijk wrote: >>>> I try to put my machine in sleep state but get the message that this is >>>> not supported. >>>> >>>> command and result: >>>> $ acpiconf -s 4 >>>> acpiconf: request sleep type (4) failed: Operation not supported >>>> >>>> I get the same message for other sleep states 1,2,3. >>>> >>>> My machine is a HP Proliant ML115 AMD64 running FreeBSD 7.0-RELEASE >>>> >>>> Result from sysctl hw.acpi is >>>> hw.acpi.supported_sleep_state: S4 S5 >> Only S4 (suspend to disk) or S5 (power off) are supported by your BIOS. >> >>>> Anyone suggestions to a solution or is this a bug? >>> ACPI support doesn't work on mainline FreeBSD. There is a testing >>> patch available via this thread though: >>> >>> http://www.mavetju.org/mail/view_message.php?list=freebsd-acpi&id=2850196 >> The patch won't help fix this. Someone needs to implement >> suspend-to-disk since we don't yet support it. It's a pretty big project. >> >> -- >> Nate >> > From oberman at es.net Sun Dec 21 15:49:15 2008 From: oberman at es.net (Kevin Oberman) Date: Sun Dec 21 15:49:21 2008 Subject: Problem on AMD64 In-Reply-To: Your message of "Sun, 21 Dec 2008 22:31:04 +0100." <494EB598.4020708@bigfoot.com> Message-ID: <20081221233822.7E92545020@ptavv.es.net> > Date: Sun, 21 Dec 2008 22:31:04 +0100 > From: David van Kuijk > Sender: owner-freebsd-acpi@freebsd.org > > Thanks for the responses so far. > > I would be happy with S3. I am however a little confused about the > abilities of my server as reported by sysctl hw.acpi. > > As commented below this line suggests that no other states than S4/S5 > are supported: > hw.acpi.supported_sleep_state: S4 S5 > > But this is also listed: > hw.acpi.standby_state: S1 > hw.acpi.suspend_state: S3 > > Are these last two overridden by the first, meaning that S3 is not > available from my BIOS??? Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 because almost all BIOSes support these states. Yours is the first BIOS I have seen that does not do S1. That is really odd. In any case, you have no available ways to cut power when your system is really idle other than powering off. Of course, you may be able to do some power saving with powerd and EST if your BIOS and CPU support those. -- 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/20081221/30ecc6c9/attachment.pgp From nate at root.org Sun Dec 21 15:52:40 2008 From: nate at root.org (Nate Lawson) Date: Sun Dec 21 15:52:47 2008 Subject: Problem on AMD64 In-Reply-To: <494EB598.4020708@bigfoot.com> References: <494C22EA.5010408@bigfoot.com> <7d6fde3d0812191923g3824a094p647809a0993574b6@mail.gmail.com> <494D50F6.70303@root.org> <7d6fde3d0812201722l8af8ec1uee7a4b7f5de604dc@mail.gmail.com> <494EB598.4020708@bigfoot.com> Message-ID: <494ED54B.2060508@root.org> David van Kuijk wrote: > Thanks for the responses so far. > > I would be happy with S3. I am however a little confused about the > abilities of my server as reported by sysctl hw.acpi. > > As commented below this line suggests that no other states than S4/S5 > are supported: > hw.acpi.supported_sleep_state: S4 S5 > > But this is also listed: > hw.acpi.standby_state: S1 > hw.acpi.suspend_state: S3 > > Are these last two overridden by the first, meaning that S3 is not > available from my BIOS??? Those are just the defaults for standby and suspend, respectively. Your BIOS only supports S4 (as is common for a lot of desktops). -Nate From bugmaster at FreeBSD.org Mon Dec 22 03:06:46 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 22 03:06:53 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200812221106.mBMB6k9R060469@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/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [ACPI] sleep broken on IBM/Lenovo T61 [amd64] o kern/128639 acpi [PATCH] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/89411 acpi [acpi] acpiconf bug o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 f kern/67309 acpi zzz reboot computer (ACPI S3) o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 45 problems total. From received at postcard.org Mon Dec 22 05:24:43 2008 From: received at postcard.org (received@postcard.org) Date: Mon Dec 22 05:24:56 2008 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20081222123704.503634507F@techno01.bek.jp> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http://www.loaps.com/postcard.gif.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://www.loaps.com/postcard.gif.exe From ivakras1 at gmail.com Mon Dec 22 08:27:08 2008 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Mon Dec 22 08:27:14 2008 Subject: Problem on AMD64 In-Reply-To: <20081221233822.7E92545020@ptavv.es.net> References: <20081221233822.7E92545020@ptavv.es.net> Message-ID: <200812221927.00568.ivakras1@gmail.com> On Monday 22 December 2008 02:38:22 Kevin Oberman wrote: > > Date: Sun, 21 Dec 2008 22:31:04 +0100 > > From: David van Kuijk > > Sender: owner-freebsd-acpi@freebsd.org > > > > Thanks for the responses so far. > > > > I would be happy with S3. I am however a little confused about the > > abilities of my server as reported by sysctl hw.acpi. > > > > As commented below this line suggests that no other states than S4/S5 > > are supported: > > hw.acpi.supported_sleep_state: S4 S5 > > > > But this is also listed: > > hw.acpi.standby_state: S1 > > hw.acpi.suspend_state: S3 > > > > Are these last two overridden by the first, meaning that S3 is not > > available from my BIOS??? > > Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 because > almost all BIOSes support these states. Yours is the first BIOS I have > seen that does not do S1. That is really odd. > > In any case, you have no available ways to cut power when your system is > really idle other than powering off. Of course, you may be able to do > some power saving with powerd and EST if your BIOS and CPU support those. Could you give to us some links about powersaving with EST? For now, i'm using powerd: powerd_enable="YES" powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me (125 MHz on battery and 2.16GHz on AC), BUT battery life time is equal in both cases and something about 50 minutes, so i think powerd is not so powerfull for me. From oberman at es.net Mon Dec 22 09:49:33 2008 From: oberman at es.net (Kevin Oberman) Date: Mon Dec 22 09:49:39 2008 Subject: Problem on AMD64 In-Reply-To: Your message of "Mon, 22 Dec 2008 19:27:00 +0300." <200812221927.00568.ivakras1@gmail.com> Message-ID: <20081222174932.93BC44500F@ptavv.es.net> > From: Dmitry Kolosov > Date: Mon, 22 Dec 2008 19:27:00 +0300 > Sender: owner-freebsd-acpi@freebsd.org > > On Monday 22 December 2008 02:38:22 Kevin Oberman wrote: > > > Date: Sun, 21 Dec 2008 22:31:04 +0100 > > > From: David van Kuijk > > > Sender: owner-freebsd-acpi@freebsd.org > > > > > > Thanks for the responses so far. > > > > > > I would be happy with S3. I am however a little confused about the > > > abilities of my server as reported by sysctl hw.acpi. > > > > > > As commented below this line suggests that no other states than S4/S5 > > > are supported: > > > hw.acpi.supported_sleep_state: S4 S5 > > > > > > But this is also listed: > > > hw.acpi.standby_state: S1 > > > hw.acpi.suspend_state: S3 > > > > > > Are these last two overridden by the first, meaning that S3 is not > > > available from my BIOS??? > > > > Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 because > > almost all BIOSes support these states. Yours is the first BIOS I have > > seen that does not do S1. That is really odd. > > > > In any case, you have no available ways to cut power when your system is > > really idle other than powering off. Of course, you may be able to do > > some power saving with powerd and EST if your BIOS and CPU support those. > > Could you give to us some links about powersaving with EST? For now, > i'm using > powerd: > powerd_enable="YES" > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me > (125 MHz on battery and 2.16GHz on AC), BUT battery life time is equal > in both cases and something about 50 minutes, so i think powerd is not > so powerfull for me. I thought that this was a desktop, so I assumed it was always on AC. Sorry. One things that can help is "deep sleep" using the Cx states in ACPI. Unfortunately, USB will prevent these from being effective. Work is underway to fix this in HEAD with the new USB stack, so this may take care of itself in time. Until then, I build my kernel without USB support and load it at boot time when I know I'll be needing it. (Interrupt the boot and drop to the loader prompt and "load umass" or whatever USB device(s) you might need. This can be a really big win for an idle or near idle system. I'd supply some added hints for power tuning, but I am running on my cell phone modem and I can only use it with Windows, so I can't look at my tuning parameters on FreeBSD right now. -- 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/20081222/13f23498/attachment.pgp From mav at FreeBSD.org Mon Dec 22 11:45:57 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Mon Dec 22 11:46:04 2008 Subject: Problem on AMD64 In-Reply-To: <1229973789.00051301.1229963402@10.7.7.3> References: <20081221233822.7E92545020@ptavv.es.net> <1229973789.00051301.1229963402@10.7.7.3> Message-ID: <494FEE73.906@FreeBSD.org> Dmitry Kolosov wrote: > Could you give to us some links about powersaving with EST? For now, i'm using > powerd: > powerd_enable="YES" > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me (125 MHz > on battery and 2.16GHz on AC), BUT battery life time is equal in both cases and > something about 50 minutes, so i think powerd is not so powerfull for me. powerd uses any frequency control features provided by kernel. On P4 and above kernel may provide both EST and P4TCC frequencies. You can see them by `sysctl -a | grep freq`. P4TCC usually gives very small power benefit on idle CPU. I have seen benefit only on old P4 without or later with disabled C1E mode support. For CPUs with C1E support P4TCC is not effective as CPU anyway completely disables it's frequency on C1 state (HALT instruction). EST instead is much more effective as it also controls CPU voltage. Check your boot messages and sysctls for EST support. -- Alexander Motin From dynasore at bigfoot.com Mon Dec 22 13:03:13 2008 From: dynasore at bigfoot.com (David van Kuijk) Date: Mon Dec 22 13:03:19 2008 Subject: Problem on AMD64 In-Reply-To: <20081221233822.7E92545020@ptavv.es.net> References: <20081221233822.7E92545020@ptavv.es.net> Message-ID: <49500088.2080609@bigfoot.com> OK, thanks again. I didn't know those tools. est is not supported om AMD64, but I will start experimenting with powerd. The main thing I want to accomplish is to lower my energy bill after I found out my server is costing me 50 cents a day of electricity. So any other ideas (besides powering off ;-) are welcome... Regards, David Kevin Oberman wrote: >> Date: Sun, 21 Dec 2008 22:31:04 +0100 >> From: David van Kuijk >> Sender: owner-freebsd-acpi@freebsd.org >> >> Thanks for the responses so far. >> >> I would be happy with S3. I am however a little confused about the >> abilities of my server as reported by sysctl hw.acpi. >> >> As commented below this line suggests that no other states than S4/S5 >> are supported: >> hw.acpi.supported_sleep_state: S4 S5 >> >> But this is also listed: >> hw.acpi.standby_state: S1 >> hw.acpi.suspend_state: S3 >> >> Are these last two overridden by the first, meaning that S3 is not >> available from my BIOS??? > > Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 because > almost all BIOSes support these states. Yours is the first BIOS I have > seen that does not do S1. That is really odd. > > In any case, you have no available ways to cut power when your system is > really idle other than powering off. Of course, you may be able to do > some power saving with powerd and EST if your BIOS and CPU support those. From yanefbsd at gmail.com Mon Dec 22 13:15:52 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Mon Dec 22 13:15:58 2008 Subject: Problem on AMD64 In-Reply-To: <49500088.2080609@bigfoot.com> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> Message-ID: <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> On 12/22/08, David van Kuijk wrote: > OK, thanks again. I didn't know those tools. est is not supported om > AMD64, but I will start experimenting with powerd. > > The main thing I want to accomplish is to lower my energy bill after I > found out my server is costing me 50 cents a day of electricity. So any > other ideas (besides powering off ;-) are welcome... > > Regards, > David > > Kevin Oberman wrote: >>> Date: Sun, 21 Dec 2008 22:31:04 +0100 >>> From: David van Kuijk >>> Sender: owner-freebsd-acpi@freebsd.org >>> >>> Thanks for the responses so far. >>> >>> I would be happy with S3. I am however a little confused about the >>> abilities of my server as reported by sysctl hw.acpi. >>> >>> As commented below this line suggests that no other states than S4/S5 >>> are supported: >>> hw.acpi.supported_sleep_state: S4 S5 >>> >>> But this is also listed: >>> hw.acpi.standby_state: S1 >>> hw.acpi.suspend_state: S3 >>> >>> Are these last two overridden by the first, meaning that S3 is not >>> available from my BIOS??? >> >> Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 because >> almost all BIOSes support these states. Yours is the first BIOS I have >> seen that does not do S1. That is really odd. >> >> In any case, you have no available ways to cut power when your system is >> really idle other than powering off. Of course, you may be able to do >> some power saving with powerd and EST if your BIOS and CPU support those. Look into the following sysctls: hw.acpi.cpu.cx_lowest hw.acpi.cpu.cx_highest Unfortunately [for you] est and PT4CC are completely Intel specific power regulation interfaces. AMD had something to offer on Linux, but I forget what that was... Cheers, -Garrett From smithi at nimnet.asn.au Mon Dec 22 19:40:53 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Mon Dec 22 19:41:03 2008 Subject: Problem on AMD64 In-Reply-To: <200812221927.00568.ivakras1@gmail.com> References: <20081221233822.7E92545020@ptavv.es.net> <200812221927.00568.ivakras1@gmail.com> Message-ID: <20081223140958.I29108@sola.nimnet.asn.au> On Mon, 22 Dec 2008, Dmitry Kolosov wrote: [..] > Could you give to us some links about powersaving with EST? For now, i'm using > powerd: > powerd_enable="YES" > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me (125 MHz > on battery and 2.16GHz on AC), BUT battery life time is equal in both cases and > something about 50 minutes, so i think powerd is not so powerfull for me. -i percent Specifies the CPU idle percent level when adaptive mode should begin to degrade performance to save power. The default is 90% or higher. -r percent Specifies the CPU idle percent level where adaptive mode should consider the CPU running and increase performance. The default is 65% or lower. I don't think your powerd running and idle percentages are likely to work too well; too close together, and too close to the 'busy' end. Try stopping powerd (/etc/rc.d/powerd stop) then running powerd manually in verbose mode in its own console (powerd -v [flags]) to watch how it behaves under varying loads. I suspect that you will find it 'flapping' between some frequencies too often at constant load, as there's insufficient hysteresis between the idle/running marks. Compare it with using the default -i and -r and if those aren't suitable, try rather smaller variations from the defaults. If it lacks responsiveness, try decreasing the polling interval. cheers, Ian From ivakras1 at gmail.com Tue Dec 23 08:43:02 2008 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Tue Dec 23 08:43:08 2008 Subject: Problem on AMD64 In-Reply-To: <20081223140958.I29108@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <200812221927.00568.ivakras1@gmail.com> <20081223140958.I29108@sola.nimnet.asn.au> Message-ID: <200812231941.11998.ivakras1@gmail.com> On Tuesday 23 December 2008 06:40:50 Ian Smith wrote: > On Mon, 22 Dec 2008, Dmitry Kolosov wrote: > [..] > > > Could you give to us some links about powersaving with EST? For now, i'm > > using powerd: > > powerd_enable="YES" > > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me > > (125 MHz on battery and 2.16GHz on AC), BUT battery life time is equal > > in both cases and something about 50 minutes, so i think powerd is not > > so powerfull for me. > > -i percent Specifies the CPU idle percent level when adaptive mode > should begin to degrade performance to save power. The > default is 90% or higher. > > -r percent Specifies the CPU idle percent level where adaptive mode > should consider the CPU running and increase performance. > The default is 65% or lower. > > I don't think your powerd running and idle percentages are likely to > work too well; too close together, and too close to the 'busy' end. > > Try stopping powerd (/etc/rc.d/powerd stop) then running powerd manually > in verbose mode in its own console (powerd -v [flags]) to watch how it > behaves under varying loads. > > I suspect that you will find it 'flapping' between some frequencies too > often at constant load, as there's insufficient hysteresis between the > idle/running marks. Compare it with using the default -i and -r and if > those aren't suitable, try rather smaller variations from the defaults. > > If it lacks responsiveness, try decreasing the polling interval. > > cheers, Ian Thanks Ian, -i and -r values was selected (3 month ago) by long playing with `powerd -v [flags]` in foreground, as you advice to me. The behavior of powerd is correct, and parameters was selected correctly to my environment. Also, debug.cpufreq.lowest was set to 500, and it starts to increase with 30% of CPU load, and decrease (to 500) with 35%. It's just good to me and it perfectly works. I'm realy think it's all about my hdd (WD), its toooooo hot, even when no file activity, even when lid is closed, on battery or on AC, no matter. It's about 60-65C. How to decrease the polling interval? Thanks again! From smithi at nimnet.asn.au Tue Dec 23 18:01:54 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Tue Dec 23 18:02:00 2008 Subject: Problem on AMD64 In-Reply-To: <200812231941.11998.ivakras1@gmail.com> References: <20081221233822.7E92545020@ptavv.es.net> <200812221927.00568.ivakras1@gmail.com> <20081223140958.I29108@sola.nimnet.asn.au> <200812231941.11998.ivakras1@gmail.com> Message-ID: <20081224122702.C29108@sola.nimnet.asn.au> On Tue, 23 Dec 2008, Dmitry Kolosov wrote: > On Tuesday 23 December 2008 06:40:50 Ian Smith wrote: > > On Mon, 22 Dec 2008, Dmitry Kolosov wrote: > > [..] > > > > > Could you give to us some links about powersaving with EST? For now, i'm > > > using powerd: > > > powerd_enable="YES" > > > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > > > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to me > > > (125 MHz on battery and 2.16GHz on AC), BUT battery life time is equal > > > in both cases and something about 50 minutes, so i think powerd is not > > > so powerfull for me. > > > > -i percent Specifies the CPU idle percent level when adaptive mode > > should begin to degrade performance to save power. The > > default is 90% or higher. > > > > -r percent Specifies the CPU idle percent level where adaptive mode > > should consider the CPU running and increase performance. > > The default is 65% or lower. > > > > I don't think your powerd running and idle percentages are likely to > > work too well; too close together, and too close to the 'busy' end. > > > > Try stopping powerd (/etc/rc.d/powerd stop) then running powerd manually > > in verbose mode in its own console (powerd -v [flags]) to watch how it > > behaves under varying loads. > > > > I suspect that you will find it 'flapping' between some frequencies too > > often at constant load, as there's insufficient hysteresis between the > > idle/running marks. Compare it with using the default -i and -r and if > > those aren't suitable, try rather smaller variations from the defaults. > > > > If it lacks responsiveness, try decreasing the polling interval. > > > > cheers, Ian > > Thanks Ian, > -i and -r values was selected (3 month ago) by long playing with `powerd -v > [flags]` in foreground, as you advice to me. The behavior of powerd is correct, > and parameters was selected correctly to my environment. Also, > debug.cpufreq.lowest was set to 500, and it starts to increase with 30% of CPU > load, and decrease (to 500) with 35%. It's just good to me and it perfectly > works. Fine if it works for you. However your settings are 30% idle (70% busy) and 35% idle (65% busy), not percent loaded as you've expressed it here. > I'm realy think it's all about my hdd (WD), its toooooo hot, even when no file > activity, even when lid is closed, on battery or on AC, no matter. It's about > 60-65C. I agree, 60C is too hot for a HDD. I'd get nervous over ~50C myself. Have you tried cleaning out the dust from the air passages and fan/s? > How to decrease the polling interval? -p ival Specifies a different polling interval (in milliseconds) for AC line state and system idle levels. The default is 500 ms. With a shorter interval, say 250ms, you may find that a lower value of debug.cpufreq.lowest will be responsive enough, which might save power. cheers, Ian From ganbold at micom.mng.net Wed Dec 24 00:15:07 2008 From: ganbold at micom.mng.net (Ganbold) Date: Wed Dec 24 00:15:14 2008 Subject: suspend/resume on T400 Message-ID: <4951EF85.9030406@micom.mng.net> Hi all, May I know the current status of suspend/resume state on i386 SMP system? I'm using CURRENT so if there are any patches I'm more than willing to try. Any links, tips and tricks are much appreciated. thanks in advance, Ganbold -- Q: What do little WASPs want to be when they grow up? A: The very best person they can possibly be. From takawata at init-main.com Wed Dec 24 00:23:55 2008 From: takawata at init-main.com (Takanori Watanabe) Date: Wed Dec 24 00:24:02 2008 Subject: suspend/resume on T400 In-Reply-To: Your message of "Wed, 24 Dec 2008 16:15:01 +0800." <4951EF85.9030406@micom.mng.net> Message-ID: <200812240819.mBO8Jxlt039089@sana.init-main.com> In message <4951EF85.9030406@micom.mng.net>, Ganbold wrote: >Hi all, > >May I know the current status of suspend/resume state on i386 SMP system? >I'm using CURRENT so if there are any patches I'm more than willing to try. >Any links, tips and tricks are much appreciated. > >thanks in advance, I wrote a patch for it ageinst current at MAY 2008 -CURRENT, but I don't update it then. http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html From ivakras1 at gmail.com Wed Dec 24 08:01:49 2008 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Wed Dec 24 08:01:56 2008 Subject: Problem on AMD64 In-Reply-To: <20081224122702.C29108@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <200812231941.11998.ivakras1@gmail.com> <20081224122702.C29108@sola.nimnet.asn.au> Message-ID: <200812241901.33857.ivakras1@gmail.com> On Wednesday 24 December 2008 05:01:50 Ian Smith wrote: > On Tue, 23 Dec 2008, Dmitry Kolosov wrote: > > On Tuesday 23 December 2008 06:40:50 Ian Smith wrote: > > > On Mon, 22 Dec 2008, Dmitry Kolosov wrote: > > > [..] > > > > > > > Could you give to us some links about powersaving with EST? For > > > > now, i'm using powerd: > > > > powerd_enable="YES" > > > > powerd_flags="-a maximum -b adaptive -n adaptive -r 30 -i 35" > > > > in my rc.conf. I'm not on AMD64, so i'm sorry, powerd works well to > > > > me (125 MHz on battery and 2.16GHz on AC), BUT battery life time is > > > > equal in both cases and something about 50 minutes, so i think > > > > powerd is not so powerfull for me. > > > > > > -i percent Specifies the CPU idle percent level when adaptive > > > mode should begin to degrade performance to save power. The default > > > is 90% or higher. > > > > > > -r percent Specifies the CPU idle percent level where adaptive > > > mode should consider the CPU running and increase performance. The > > > default is 65% or lower. > > > > > > I don't think your powerd running and idle percentages are likely to > > > work too well; too close together, and too close to the 'busy' end. > > > > > > Try stopping powerd (/etc/rc.d/powerd stop) then running powerd > > > manually in verbose mode in its own console (powerd -v [flags]) to > > > watch how it behaves under varying loads. > > > > > > I suspect that you will find it 'flapping' between some frequencies > > > too often at constant load, as there's insufficient hysteresis between > > > the idle/running marks. Compare it with using the default -i and -r > > > and if those aren't suitable, try rather smaller variations from the > > > defaults. > > > > > > If it lacks responsiveness, try decreasing the polling interval. > > > > > > cheers, Ian > > > > Thanks Ian, > > -i and -r values was selected (3 month ago) by long playing with > > `powerd -v [flags]` in foreground, as you advice to me. The behavior of > > powerd is correct, and parameters was selected correctly to my > > environment. Also, > > debug.cpufreq.lowest was set to 500, and it starts to increase with 30% > > of CPU load, and decrease (to 500) with 35%. It's just good to me and it > > perfectly works. > > Fine if it works for you. However your settings are 30% idle (70% busy) > and 35% idle (65% busy), not percent loaded as you've expressed it here. > > > I'm realy think it's all about my hdd (WD), its toooooo hot, even when > > no file activity, even when lid is closed, on battery or on AC, no > > matter. It's about 60-65C. > > I agree, 60C is too hot for a HDD. I'd get nervous over ~50C myself. > Have you tried cleaning out the dust from the air passages and fan/s? > > > How to decrease the polling interval? > > -p ival Specifies a different polling interval (in milliseconds) > for AC line state and system idle levels. The default is 500 ms. > > With a shorter interval, say 250ms, you may find that a lower value of > debug.cpufreq.lowest will be responsive enough, which might save power. > > cheers, Ian Oh,thanks Ian! I'll review my powerd settings. About the dust-its clean, laptop is 3 month old, and i'm checking fans and air ways for dust regulary. Thanks for advice! From ganbold at micom.mng.net Wed Dec 24 17:19:21 2008 From: ganbold at micom.mng.net (Ganbold) Date: Wed Dec 24 17:19:30 2008 Subject: suspend/resume on T400 In-Reply-To: <200812240819.mBO8Jxlt039089@sana.init-main.com> References: <200812240819.mBO8Jxlt039089@sana.init-main.com> Message-ID: <4952DF94.8000700@micom.mng.net> Takanori Watanabe wrote: > In message <4951EF85.9030406@micom.mng.net>, Ganbold wrote: > >> Hi all, >> >> May I know the current status of suspend/resume state on i386 SMP system? >> I'm using CURRENT so if there are any patches I'm more than willing to try. >> Any links, tips and tricks are much appreciated. >> >> thanks in advance, >> > > I wrote a patch for it ageinst current at MAY 2008 -CURRENT, > but I don't update it then. > > http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html > Do you have a list of drivers that are known to work with this patch or at least the drivers that you have no problem on your system? Please let me know. I will try experiment your patch on weekend. thanks a lot, Ganbold -- With reasonable men I will reason; with humane men I will plead; but to tyrants I will give no quarter. -- William Lloyd Garrison From dynasore at bigfoot.com Thu Dec 25 01:15:04 2008 From: dynasore at bigfoot.com (David van Kuijk) Date: Thu Dec 25 01:15:11 2008 Subject: Problem on AMD64 In-Reply-To: <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> Message-ID: <49534F10.7040305@bigfoot.com> >>>> >>>> Thanks for the responses so far. >>>> >>>> I would be happy with S3. I am however a little confused about the >>>> abilities of my server as reported by sysctl hw.acpi. >>>> >>>> As commented below this line suggests that no other states than S4/S5 >>>> are supported: >>>> hw.acpi.supported_sleep_state: S4 S5 >>>> >>>> But this is also listed: >>>> hw.acpi.standby_state: S1 >>>> hw.acpi.suspend_state: S3 >>>> >>>> Are these last two overridden by the first, meaning that S3 is not >>>> available from my BIOS??? >>> Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 because >>> almost all BIOSes support these states. Yours is the first BIOS I have >>> seen that does not do S1. That is really odd. >>> >>> In any case, you have no available ways to cut power when your system is >>> really idle other than powering off. Of course, you may be able to do >>> some power saving with powerd and EST if your BIOS and CPU support those. > > Look into the following sysctls: > > hw.acpi.cpu.cx_lowest > hw.acpi.cpu.cx_highest > I tried to find out what I can do with those sysctls. hw.acpi.cpu.cx_highest is not available on my system. hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I should set it to C2 or C3??? A second question; When I use powerd it switches between clock-frequencies of 1800 and 1000 correctly. Is it possible to set a sysctl so that even lower frequencies are supported, or are the supported frequencies simply dictated by the processors in my server (in my case Opteron 1.8 GHz)? Cheers, David From yanefbsd at gmail.com Fri Dec 26 19:12:27 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Fri Dec 26 19:12:32 2008 Subject: Problem on AMD64 In-Reply-To: <49534F10.7040305@bigfoot.com> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> Message-ID: <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: > > > >>>>> >>>>> Thanks for the responses so far. >>>>> >>>>> I would be happy with S3. I am however a little confused about the >>>>> abilities of my server as reported by sysctl hw.acpi. >>>>> >>>>> As commented below this line suggests that no other states than S4/S5 >>>>> are supported: >>>>> hw.acpi.supported_sleep_state: S4 S5 >>>>> >>>>> But this is also listed: >>>>> hw.acpi.standby_state: S1 >>>>> hw.acpi.suspend_state: S3 >>>>> >>>>> Are these last two overridden by the first, meaning that S3 is not >>>>> available from my BIOS??? >>>> >>>> Yes. FreeBSD, by default, sets up standby as S1 and suspend to S3 >>>> because >>>> almost all BIOSes support these states. Yours is the first BIOS I have >>>> seen that does not do S1. That is really odd. >>>> >>>> In any case, you have no available ways to cut power when your system is >>>> really idle other than powering off. Of course, you may be able to do >>>> some power saving with powerd and EST if your BIOS and CPU support >>>> those. >> >> Look into the following sysctls: >> >> hw.acpi.cpu.cx_lowest >> hw.acpi.cpu.cx_highest >> > > I tried to find out what I can do with those sysctls. > hw.acpi.cpu.cx_highest is not available on my system. > hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I > should set it to C2 or C3??? > > A second question; > When I use powerd it switches between clock-frequencies of 1800 and 1000 > correctly. Is it possible to set a sysctl so that even lower frequencies are > supported, or are the supported frequencies simply dictated by the > processors in my server (in my case Opteron 1.8 GHz)? > > Cheers, > David Dog gone it I've been typo'ing that for a long time (see http://lists.freebsd.org/pipermail/cvs-all/2003-November/036370.html). Try: hw.acpi.cpu.cx.lowest hw.acpi.cpu.cx.highest Note that the underscores were in fact periods. Cheers, -Garrett From smithi at nimnet.asn.au Fri Dec 26 22:39:28 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Fri Dec 26 22:39:35 2008 Subject: Problem on AMD64 In-Reply-To: <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> Message-ID: <20081227160941.I29108@sola.nimnet.asn.au> On Fri, 26 Dec 2008, Garrett Cooper wrote: > On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: [..] > >> Look into the following sysctls: > >> > >> hw.acpi.cpu.cx_lowest > >> hw.acpi.cpu.cx_highest > >> > > > > I tried to find out what I can do with those sysctls. > > hw.acpi.cpu.cx_highest is not available on my system. I don't think it exists; C1 state is always available AFAIK. > > hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I > > should set it to C2 or C3??? Give it a try. Setting it to C3 won't hurt, whether it's used or not. First check dev.cpu.%d.cx_supported which shows the supported states. There's also dev.cpu.%d.cx_lowest (showing the lowest state used) and dev.cpu.%d.cx_usage, showing percentage time spent in various states. If it winds up helping, set performance_cx_lowest=C3 (or C2 or just 'LOW') in /etc/rc.conf .. see /etc/rc.d/power_profile for how it's used. > > A second question; > > When I use powerd it switches between clock-frequencies of 1800 and 1000 > > correctly. Is it possible to set a sysctl so that even lower frequencies are > > supported, or are the supported frequencies simply dictated by the > > processors in my server (in my case Opteron 1.8 GHz)? Show us 'sysctl dev.cpu' .. and check dmesg for which if any of acpi cpufreq drivers are being used. Maybe it's powernow for the Opteron? 'sysctl dev | grep settings' may show something about the drivers used. > > Cheers, > > David > > Dog gone it I've been typo'ing that for a long time (see > http://lists.freebsd.org/pipermail/cvs-all/2003-November/036370.html). > > Try: > > hw.acpi.cpu.cx.lowest > hw.acpi.cpu.cx.highest > > Note that the underscores were in fact periods. I don't think that suggestion was ever implemented .. there have been quite some changes with all this, in fact I'm not sure the acpi(4) man is up to date (looking at 7-STABLE manuals online) .. it still talks about hw.acpi.cpu.{cx_supported,cx_lowest,cx_usage} where cx_supported and cx_usage have moved to dev.cpu.%d .. all a bit confusing. cheers, Ian From ganbold at micom.mng.net Sat Dec 27 04:57:05 2008 From: ganbold at micom.mng.net (Ganbold) Date: Sat Dec 27 04:57:12 2008 Subject: Semi-working patch for amd64 suspend/resume In-Reply-To: <200812111817.32334.jkim@FreeBSD.org> References: <1224616985.00027652.1224606603@10.7.7.3> <200812102120.03788.jkim@FreeBSD.org> <49419BB9.8030408@FreeBSD.org> <200812111817.32334.jkim@FreeBSD.org> Message-ID: <4956261D.9050305@micom.mng.net> Jung-uk Kim wrote: > On Thursday 11 December 2008 06:01 pm, Alexander Motin wrote: > >> Jung-uk Kim wrote: >> >>> FYI, I uploaded a new patch with some fixes (against today's >>> CURRENT): >>> >>> http://people.freebsd.org/~jkim/amd64_suspend.diff >>> Jung-uk, Do you have a patch for i386? What does require to make suspend/resume work on i386 (based on your patch)? I'm willing to test. I tried the patch (http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html) however system panics when I try to suspend. thanks, Ganbold >> It is still working for me. >> > > Good. > > >>> This patch should be feature complete but I'd say it is still >>> considered experimental as it is not properly reviewed. >>> >> This comment looks stale: >> /* Restore PAT and MTRRdefType. */ >> > > Corrected. > > Thanks for the feedback! > > Jung-uk Kim > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > > > > -- The one charm of marriage is that it makes a life of deception a necessity. -- Oscar Wilde From gaijin.k at gmail.com Sat Dec 27 07:04:18 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sat Dec 27 07:04:24 2008 Subject: Problem on AMD64 In-Reply-To: <20081227160941.I29108@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> <20081227160941.I29108@sola.nimnet.asn.au> Message-ID: <1230388519.1270.1.camel@RabbitsDen> On Sat, 2008-12-27 at 17:13 +1100, Ian Smith wrote: > On Fri, 26 Dec 2008, Garrett Cooper wrote: > > On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: > [..] > > >> Look into the following sysctls: > > >> > > >> hw.acpi.cpu.cx_lowest > > >> hw.acpi.cpu.cx_highest > > >> > > > > > > I tried to find out what I can do with those sysctls. > > > hw.acpi.cpu.cx_highest is not available on my system. > > I don't think it exists; C1 state is always available AFAIK. > > > > hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I > > > should set it to C2 or C3??? > > Give it a try. Setting it to C3 won't hurt, whether it's used or not. Actually it just might (hurt that is). See below for the discussion. http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+2482 +/usr/local/www/db/text/2008/freebsd-acpi/20081109.freebsd-acpi -- Alexandre "Sunny" Kovalenko (????????? ?????????) From smithi at nimnet.asn.au Sat Dec 27 18:20:29 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Sat Dec 27 18:20:35 2008 Subject: Problem on AMD64 In-Reply-To: <1230388519.1270.1.camel@RabbitsDen> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> <20081227160941.I29108@sola.nimnet.asn.au> <1230388519.1270.1.camel@RabbitsDen> Message-ID: <20081228124345.D51566@sola.nimnet.asn.au> On Sat, 27 Dec 2008, Alexandre "Sunny" Kovalenko wrote: > On Sat, 2008-12-27 at 17:13 +1100, Ian Smith wrote: > > On Fri, 26 Dec 2008, Garrett Cooper wrote: > > > On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: > > [..] > > > >> Look into the following sysctls: > > > >> > > > >> hw.acpi.cpu.cx_lowest > > > >> hw.acpi.cpu.cx_highest > > > >> > > > > > > > > I tried to find out what I can do with those sysctls. > > > > hw.acpi.cpu.cx_highest is not available on my system. > > > > I don't think it exists; C1 state is always available AFAIK. > > > > > > hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I > > > > should set it to C2 or C3??? > > > > Give it a try. Setting it to C3 won't hurt, whether it's used or not. > Actually it just might (hurt that is). See below for the discussion. > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+2482 > +/usr/local/www/db/text/2008/freebsd-acpi/20081109.freebsd-acpi Thanks. Yes that was indeed an interesting discussion. FWIW, I find that interface awkward, without threading. For me it's easier from: http://lists.freebsd.org/pipermail/freebsd-acpi/2008-November/005182.html Could I then safely say, setting it to C2 won't hurt? I'm glad there are folks working on power use with SMP, it still needs moving up the agenda. 'Global notebook sales finally beat desktops': http://www.theregister.co.uk/2008/12/24/notebooks_pass_desktops/ Soon it'll be hard to find uniprocessors even on subnotebooks; has anyone played with the new Intel Atom CPUs, which use HTT on one core? And to mix topics further, having USB enabled looks problematic with on-battery use of laptops .. does this new USB stack offer any relief? cheers, Ian From linimon at FreeBSD.org Sun Dec 28 18:27:28 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Dec 28 18:27:34 2008 Subject: i386/129953: [acpi] ACPI timeout (CDROM) with Shuttle X27D Message-ID: <200812290227.mBT2RSJ5071912@freefall.freebsd.org> Old Synopsis: ACPI timeout (CDROM) with Shuttle X27D New Synopsis: [acpi] ACPI timeout (CDROM) with Shuttle X27D Responsible-Changed-From-To: freebsd-i386->freebsd-acpi Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 29 02:27:06 UTC 2008 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=129953 From bugmaster at FreeBSD.org Mon Dec 29 03:06:50 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 29 03:07:10 2008 Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org Message-ID: <200812291106.mBTB6nvj024339@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D o kern/129618 acpi [acpi] Problem with ACPI on HP Pavilion DV2899 laptop o kern/129563 acpi [ACPI] sleep broken on IBM/Lenovo T61 [amd64] o kern/128639 acpi [PATCH] [acpi_asus] acpi for ASUS A6F,A3E,A3F,A3N not f kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/127581 acpi [patch] [acpi_sony] Add support for more Sony features o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/89411 acpi [acpi] acpiconf bug o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys s kern/73823 acpi [request] acpi / power-on by timer support o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/69750 acpi Boot without ACPI failed on ASUS L5 f kern/67309 acpi zzz reboot computer (ACPI S3) o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop 46 problems total. From cokane at FreeBSD.org Mon Dec 29 15:50:03 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Mon Dec 29 15:50:14 2008 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 Message-ID: <1230564886.2280.11.camel@localhost> Hi, I've been testing Jung-uk Kim's recent amd64 suspend patch on my HP notebook, and it seems to be very close to working well. The notebook goes into S3 state properly, but when it comes back out it seems that the hardware is left in a bad state. I cannot attach my if_bge and if_ndis network drivers after a resume. I've tried performing the suspend/resume with the appropriate kldunload lines in the /etc/rc.suspend, and I've also played around with the following sysctls to no avail: * debug.acpi.do_powerstate * hw.pci.do_power_resume * hw.pci.do_power_nodriver Additionally, when the system is resumed I needed hw.acpi.reset_video=1 to be set, otherwise the video doesn't get restored. I also need to execute a "vidcontrol 80x25" to refresh the syscons as well (or else I get no text on the screen). It seems that Xorg will resume properly if I've switched to a text console prior to the suspend (Alt-Ctrl-F1 through -F8), otherwise the video will come up hosed. I suspect there's probably a way that I can force the switch in a scripted manner in rc.suspend. Anyhow, it seems that some devices resume properly and some don't. The ones that don't seem to be my ndis0 (wireless card, BCM4321) and my bge0, which would be handy things to be able to use after a resume. Does anyone have similar issues in amd64 or i386 kernels when using S3? Any suggestions on where to go? -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081229/d14e198d/attachment.pgp From nate at root.org Mon Dec 29 16:19:21 2008 From: nate at root.org (Nate Lawson) Date: Mon Dec 29 16:19:28 2008 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <1230564886.2280.11.camel@localhost> References: <1230564886.2280.11.camel@localhost> Message-ID: <4958F887.2010203@root.org> Coleman Kane wrote: > I've been testing Jung-uk Kim's recent amd64 suspend patch on my HP > notebook, and it seems to be very close to working well. > > The notebook goes into S3 state properly, but when it comes back out it > seems that the hardware is left in a bad state. I cannot attach my > if_bge and if_ndis network drivers after a resume. Dump the pci config register states for those devices both before and after the resume. Where the bits differ is probably where you'll find the problem. Example to read 256 bytes: pciconf -r pci0:4:0 0:256 -- Nate From cokane at FreeBSD.org Mon Dec 29 19:41:57 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Mon Dec 29 19:42:03 2008 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <4958F887.2010203@root.org> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> Message-ID: <1230579699.2386.5.camel@localhost> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: > Coleman Kane wrote: > > I've been testing Jung-uk Kim's recent amd64 suspend patch on my HP > > notebook, and it seems to be very close to working well. > > > > The notebook goes into S3 state properly, but when it comes back out it > > seems that the hardware is left in a bad state. I cannot attach my > > if_bge and if_ndis network drivers after a resume. > > Dump the pci config register states for those devices both before and > after the resume. Where the bits differ is probably where you'll find > the problem. > > Example to read 256 bytes: > pciconf -r pci0:4:0 0:256 > Tried that, and I also tried to use pciconf -w to set the registers to the initial state of the hardware before if_bge is loaded. I still get the following messages when I attempt to reload the kld after the resume, followed by a failed attach: bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 bge0: firmware handshake timed out, found 0x4b657654 bge0: firmware handshake timed out, found 0x4b657654 bge0: RX CPU self-diagnostics failed! bge0: chip initialization failed device_attach: bge0 attach returned 6 Anyone have success with S3 on amd64 or i386 with if_bge cards? -- Coleman Kane -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081229/c5a30231/attachment.pgp From nate at root.org Mon Dec 29 20:16:55 2008 From: nate at root.org (Nate Lawson) Date: Mon Dec 29 20:17:02 2008 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <1230579699.2386.5.camel@localhost> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> Message-ID: <49593036.4030306@root.org> Coleman Kane wrote: > On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: >> Coleman Kane wrote: >>> I've been testing Jung-uk Kim's recent amd64 suspend patch on my HP >>> notebook, and it seems to be very close to working well. >>> >>> The notebook goes into S3 state properly, but when it comes back out it >>> seems that the hardware is left in a bad state. I cannot attach my >>> if_bge and if_ndis network drivers after a resume. >> Dump the pci config register states for those devices both before and >> after the resume. Where the bits differ is probably where you'll find >> the problem. >> >> Example to read 256 bytes: >> pciconf -r pci0:4:0 0:256 >> > > Tried that, and I also tried to use pciconf -w to set the registers to > the initial state of the hardware before if_bge is loaded. I still get > the following messages when I attempt to reload the kld after the > resume, followed by a failed attach: > > bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 > bge0: firmware handshake timed out, found 0x4b657654 > bge0: firmware handshake timed out, found 0x4b657654 > bge0: RX CPU self-diagnostics failed! > bge0: chip initialization failed > device_attach: bge0 attach returned 6 > > Anyone have success with S3 on amd64 or i386 with if_bge cards? Did you post the register states before and after? -- Nate From dleal at webvolution.net Mon Dec 29 22:22:14 2008 From: dleal at webvolution.net (Daniel Leal) Date: Mon Dec 29 22:22:21 2008 Subject: is acpi working well ? Message-ID: <49594754.8000607@webvolution.net> Hi. I have FreeBSD 7.1-BETA2 installed on my toshiba A200 laptop. Almost everything is working fine and I am really happy with it. I am not understanding well if acpi is working and needs some configuration, or if simply is not working. Lets see some symptoms that could give some information: - when I leave my laptop for a few minutes, the display goes down and as soon as I move the mouse it goes up0 again. - When I do "shutdown -p now" the computer does not switch off alone. I must press the power button for a few seconds. - I always use my laptop connected to electricity. One time I forgot and I run it disconnected, using the battery power. A few minutes after boot, the laptop simply went down by itself. Can someone give me some information about it please? Thanks! daniel #dmesg | grep ACPI Features=0xbfebfbff ACPI APIC Table: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 pcib2: irq 17 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 16 at device 28.1 on pci0 pci4: on pcib3 pcib4: irq 18 at device 28.2 on pci0 pci5: on pcib4 pcib5: at device 30.0 on pci0 pci6: on pcib5 battery0: on acpi0 cpu0: on acpi0 cpu1: on acpi0 #dmesg | grep acpi acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 acpi_acad0: on acpi0 battery0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 cpu0: on acpi0 cpu1: on acpi0 #sysctl hw.acpi 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.reset_video: 0 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.cpu.cx_lowest: C1 From prijavapodrska at gmail.com Tue Dec 30 15:36:25 2008 From: prijavapodrska at gmail.com (hepek) Date: Tue Dec 30 15:36:32 2008 Subject: VBScript does not work on XP (acpi)? Message-ID: <21218437.post@talk.nabble.com> This VBScript I run on xp but I get error "(null): 0x8004100C" on "For each" - line . Do I need enable some thing or what ??? ******************************** strServer = "." Set objWMI = GetObject("winmgmts://" & strServer & "/root\WMI") Set objInstances = objWMI.InstancesOf("MSAcpi",48) For Each objInstance in objInstances WScript.Echo objInstance.getObjectText_ Next ******************************** Thank you -- View this message in context: http://www.nabble.com/VBScript-does-not-work-on-XP-%28acpi%29--tp21218437p21218437.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From rpaulo at fnop.net Tue Dec 30 15:43:08 2008 From: rpaulo at fnop.net (Rui Paulo) Date: Tue Dec 30 15:43:14 2008 Subject: is acpi working well ? In-Reply-To: <49594754.8000607@webvolution.net> References: <49594754.8000607@webvolution.net> Message-ID: <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> On 29 Dec 2008, at 21:55, Daniel Leal wrote: > Hi. > > I have FreeBSD 7.1-BETA2 installed on my toshiba A200 laptop. > Almost everything is working fine and I am really happy with it. > I am not understanding well if acpi is working and needs some > configuration, > or if simply is not working. > Lets see some symptoms that could give some information: > - when I leave my laptop for a few minutes, the display goes down > and as soon > as I move the mouse it goes up0 again. You mean in Xorg ? That's normal. -- Rui Paulo From dleal at webvolution.net Tue Dec 30 16:34:47 2008 From: dleal at webvolution.net (Daniel Leal) Date: Tue Dec 30 16:34:54 2008 Subject: is acpi working well ? In-Reply-To: <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> Message-ID: <495A4DC3.3060709@webvolution.net> I just asked because I was not sure. But what about the other things? I already try to disable acpi in /boot/loader.conf with the line hint.acpi.0.disabled="1" but my laptop simply don't boot!! It crashes during freebsd boot with a few error that are to fast for my eyes. I must enable acpi during boot prompt to boot again. Maybe I could try other things besides acpi, but I not even able to switch off acpi ! Sorry of my lack of knowledge, but I really would like to know how is cpu temperature and so on... thanks, daniel Rui Paulo wrote: > > On 29 Dec 2008, at 21:55, Daniel Leal wrote: > >> Hi. >> >> I have FreeBSD 7.1-BETA2 installed on my toshiba A200 laptop. >> Almost everything is working fine and I am really happy with it. >> I am not understanding well if acpi is working and needs some >> configuration, >> or if simply is not working. >> Lets see some symptoms that could give some information: >> - when I leave my laptop for a few minutes, the display goes down and >> as soon >> as I move the mouse it goes up0 again. >> - When I do "shutdown -p now" the computer does not switch off alone. >> I must >> press the power button for a few seconds. >> - I always use my laptop connected to electricity. One time I forgot >> and I run it >> disconnected, using the battery power. A few minutes after boot, the >> laptop >> simply went down by itself. >> >> Can someone give me some information about it please? >> Thanks! >> >> daniel >> >> #dmesg | grep ACPI >> Features=0xbfebfbff >> >> ACPI APIC Table: >> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >> pcib0: port 0xcf8-0xcff on acpi0 >> pci0: on pcib0 >> pcib1: irq 16 at device 1.0 on pci0 >> pci1: on pcib1 >> pcib2: irq 17 at device 28.0 on pci0 >> pci2: on pcib2 >> pcib3: irq 16 at device 28.1 on pci0 >> pci4: on pcib3 >> pcib4: irq 18 at device 28.2 on pci0 >> pci5: on pcib4 >> pcib5: at device 30.0 on pci0 >> pci6: on pcib5 >> battery0: on acpi0 >> cpu0: on acpi0 >> cpu1: on acpi0 >> >> #dmesg | grep acpi >> acpi0: on motherboard >> acpi0: [ITHREAD] >> acpi0: Power Button (fixed) >> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 >> acpi_ec0: port 0x62,0x66 on acpi0 >> acpi_lid0: on acpi0 >> acpi_button0: on acpi0 >> pcib0: port 0xcf8-0xcff on acpi0 >> acpi_acad0: on acpi0 >> battery0: on acpi0 >> atkbdc0: port 0x60,0x64 irq 1 on acpi0 >> cpu0: on acpi0 >> cpu1: on acpi0 >> >> #sysctl hw.acpi >> 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.reset_video: 0 >> 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.cpu.cx_lowest: C1 > > You mean in Xorg ? That's normal. > > -- > Rui Paulo > From rpaulo at freebsd.org Tue Dec 30 17:53:41 2008 From: rpaulo at freebsd.org (Rui Paulo) Date: Tue Dec 30 17:54:20 2008 Subject: is acpi working well ? In-Reply-To: <495A4DC3.3060709@webvolution.net> References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> <495A4DC3.3060709@webvolution.net> Message-ID: On 30 Dec 2008, at 16:35, Daniel Leal wrote: > I just asked because I was not sure. > > But what about the other things? The other things are problems with your ACPI vendor implementation or FreeBSD's ACPI implementation problems. > I already try to disable acpi in /boot/loader.conf with the line > hint.acpi.0.disabled="1" > but my laptop simply don't boot!! It crashes during freebsd boot > with a few error that are to fast for my eyes. Several modern laptops don't work with ACPI disabled. > I must enable acpi during boot prompt to boot again. > > Maybe I could try other things besides acpi, but I not even able to > switch off acpi ! > > Sorry of my lack of knowledge, but I really would like to know how > is cpu temperature and so on... Not sure if that works; I haven't seen anything in your dmesg that shows that your laptop has a temperature sensor. Regards, -- Rui Paulo From dleal at webvolution.net Tue Dec 30 17:59:06 2008 From: dleal at webvolution.net (Daniel Leal) Date: Tue Dec 30 17:59:12 2008 Subject: is acpi working well ? In-Reply-To: References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> <495A4DC3.3060709@webvolution.net> Message-ID: <495A618D.8020702@webvolution.net> Thanks for your reply. So that means that simply my laptop is not able to deal with it, or maybe in a future FreeBSD release it could work? daniel Rui Paulo wrote: > > On 30 Dec 2008, at 16:35, Daniel Leal wrote: > >> I just asked because I was not sure. >> >> But what about the other things? > > The other things are problems with your ACPI vendor implementation or > FreeBSD's ACPI implementation problems. > >> I already try to disable acpi in /boot/loader.conf with the line >> hint.acpi.0.disabled="1" >> but my laptop simply don't boot!! It crashes during freebsd boot with >> a few error that are to fast for my eyes. > > Several modern laptops don't work with ACPI disabled. > >> I must enable acpi during boot prompt to boot again. >> >> Maybe I could try other things besides acpi, but I not even able to >> switch off acpi ! >> >> Sorry of my lack of knowledge, but I really would like to know how is >> cpu temperature and so on... > > > Not sure if that works; I haven't seen anything in your dmesg that > shows that your laptop has a temperature sensor. > > Regards, > -- > Rui Paulo > > From cokane at FreeBSD.org Tue Dec 30 18:36:19 2008 From: cokane at FreeBSD.org (Coleman Kane) Date: Tue Dec 30 18:36:25 2008 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <49593036.4030306@root.org> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> Message-ID: <1230662172.1702.2.camel@localhost> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-acpi/attachments/20081230/5368ce34/attachment.pgp From rpaulo at freebsd.org Tue Dec 30 18:43:35 2008 From: rpaulo at freebsd.org (Rui Paulo) Date: Tue Dec 30 18:43:41 2008 Subject: is acpi working well ? In-Reply-To: <495A618D.8020702@webvolution.net> References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> <495A4DC3.3060709@webvolution.net> <495A618D.8020702@webvolution.net> Message-ID: On 30 Dec 2008, at 17:59, Daniel Leal wrote: > Thanks for your reply. > > So that means that simply my laptop is not able to deal with it, or > maybe in a future FreeBSD release it could work? Yes, but, of course, you can try to find the problem and I'll try to help you with a fix if time permits :-) Regards, -- Rui Paulo From nate at root.org Tue Dec 30 19:14:18 2008 From: nate at root.org (Nate Lawson) Date: Tue Dec 30 19:14:25 2008 Subject: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 In-Reply-To: <1230662172.1702.2.camel@localhost> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> Message-ID: <495A7309.2060400@root.org> Coleman Kane wrote: > On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: >> Coleman Kane wrote: >>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: >>>> Coleman Kane wrote: >>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on my HP >>>>> notebook, and it seems to be very close to working well. >>>>> >>>>> The notebook goes into S3 state properly, but when it comes back out it >>>>> seems that the hardware is left in a bad state. I cannot attach my >>>>> if_bge and if_ndis network drivers after a resume. >>>> Dump the pci config register states for those devices both before and >>>> after the resume. Where the bits differ is probably where you'll find >>>> the problem. >>>> >>>> Example to read 256 bytes: >>>> pciconf -r pci0:4:0 0:256 >>>> >>> Tried that, and I also tried to use pciconf -w to set the registers to >>> the initial state of the hardware before if_bge is loaded. I still get >>> the following messages when I attempt to reload the kld after the >>> resume, followed by a failed attach: >>> >>> bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 >>> bge0: firmware handshake timed out, found 0x4b657654 >>> bge0: firmware handshake timed out, found 0x4b657654 >>> bge0: RX CPU self-diagnostics failed! >>> bge0: chip initialization failed >>> device_attach: bge0 attach returned 6 >>> >>> Anyone have success with S3 on amd64 or i386 with if_bge cards? >> Did you post the register states before and after? >> > Attached are the before and after snapshots of the device's PCI register > space. I need to track down a good table to mate these with. In this > case, I didn't unload the driver, as the if_bge driver is supposed to be > able to properly handle suspend/resume now. > > These are dumps of the whole 256-byte register space, using: > pciconf -r -b pci0:16:0:0 0:0x100 Great. So far in FreeBSD, anything after the first 64 bytes is the driver's responsibility. According to your dump, that is where all the differences are. -- Nate From dleal at webvolution.net Tue Dec 30 23:48:30 2008 From: dleal at webvolution.net (Daniel Leal) Date: Tue Dec 30 23:48:37 2008 Subject: is acpi working well ? In-Reply-To: References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> <495A4DC3.3060709@webvolution.net> <495A618D.8020702@webvolution.net> Message-ID: <495AB36D.1000804@webvolution.net> Well, the hw.acpi.thermal is not shown in the sysctl hw.acpi list. Maybe that means that my MB does not have that kind of sensor. But if not, is there a way to control the CPU fan speed according to CPU work? It seams to me that the CPU fan is always with the same velocity. And when I had windows installed in this laptop I remember that when some complicated apps were running the sound of the fan was different. Regarding the battery, do do you think that with the following list I can monitor the charge and be sure that I will not have an unexpected shutdown if I run my laptop just on battery? [dleal@Descomunal]$sysctl hw.acpi 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.reset_video: 0 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.cpu.cx_lowest: C1 Rui Paulo wrote: > > On 30 Dec 2008, at 17:59, Daniel Leal wrote: > >> Thanks for your reply. >> >> So that means that simply my laptop is not able to deal with it, or >> maybe in a future FreeBSD release it could work? > > Yes, but, of course, you can try to find the problem and I'll try to > help you with a fix if time permits :-) > > Regards, > -- > Rui Paulo > From rpaulo at freebsd.org Tue Dec 30 23:55:43 2008 From: rpaulo at freebsd.org (Rui Paulo) Date: Tue Dec 30 23:55:49 2008 Subject: is acpi working well ? In-Reply-To: <495AB36D.1000804@webvolution.net> References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> <495A4DC3.3060709@webvolution.net> <495A618D.8020702@webvolution.net> <495AB36D.1000804@webvolution.net> Message-ID: <378A9139-97D1-4E74-99C4-B2005A892F4D@freebsd.org> On 30 Dec 2008, at 23:49, Daniel Leal wrote: > Well, the hw.acpi.thermal is not shown in the sysctl hw.acpi list. > Maybe that means that my MB does not have that kind of sensor. But > if not, is there a way to control the CPU fan speed according to CPU > work? It seams to me that the CPU fan is always with the same > velocity. And when I had windows installed in this laptop I remember > that when some complicated apps were running the sound of the fan > was different. > Regarding the battery, do do you think that with the following list > I can monitor the charge and be sure that I will not have an > unexpected shutdown if I run my laptop just on battery? Try sysctl dev.cpu. Hopefully, you'll be able to set the cpu frequency you want. For a more dynamic change, try using powerd(1). Just enable it in /etc/ rc.conf and then run "/etc/rc.d/powerd start" -- Rui Paulo From fbsd at opal.com Wed Dec 31 00:27:38 2008 From: fbsd at opal.com (J.R. Oldroyd) Date: Wed Dec 31 00:27:48 2008 Subject: ACPI issues on Averatec 3250 Message-ID: <20081230185743.12fd1c3a@avera> I have just put 7-stable on an Averatec 3250HX laptop. Three things connected with ACPI do not work as they should. 1. Suspend/Resume The system suspends but does not resume. # acpiconf -s S3 system appears to suspend OK but then no keyboard action will wake it up need to power-off and reboot Relevant sysctls: 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 I tried the patch documented here: http://lists.freebsd.org/mailman/htdig/freebsd-acpi/2005-May/001557.html With this, the keyboard now does re-activate the system, but the system cold boots rather than restarting. 2. Thermal Zone The thermal zone reporting is not working. From the boot info: acpi_tz0: on acpi0 But sysctl info: hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: 0.0C hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.passive_cooling: 1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 90.0C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 110.0C hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._TC1: 2 hw.acpi.thermal.tz0._TC2: 4 hw.acpi.thermal.tz0._TSP: 30 3. Radio On/Off Button The WiFi Radio button does not do anything. The wifi card comes on with "ifconfig ral0 up" and goes off with "ifconfig ral0 down" and works OK in between. It would be nice to have the button do something. Any thoughts on these from you ACPI experts? The system's acpidump is here: http://opal.com/jr/averatec/20081230-acpidump.txt Thanks, -jr From smithi at nimnet.asn.au Wed Dec 31 03:37:18 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Wed Dec 31 03:37:26 2008 Subject: is acpi working well ? In-Reply-To: <495AB36D.1000804@webvolution.net> References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> <495A4DC3.3060709@webvolution.net> <495A618D.8020702@webvolution.net> <495AB36D.1000804@webvolution.net> Message-ID: <20081231135644.X51566@sola.nimnet.asn.au> On Tue, 30 Dec 2008, Daniel Leal wrote: > Well, the hw.acpi.thermal is not shown in the sysctl hw.acpi list. Maybe that > means that my MB does not have that kind of sensor. But if not, is there a > way to control the CPU fan speed according to CPU work? It seams to me that > the CPU fan is always with the same velocity. And when I had windows > installed in this laptop I remember that when some complicated apps were > running the sound of the fan was different. As Rui suggested, add 'powerd_enable=YES' to rc.conf for that. However it does seem a bit odd that hw.acpi.thermal sysctls aren't showing up. > Regarding the battery, do do you think that with the following list I can > monitor the charge and be sure that I will not have an unexpected shutdown if > I run my laptop just on battery? [..] > hw.acpi.verbose: 0 If you turn that on you may get some more clues in /var/log/messages. ie hw.acpi.verbose=1 in /boot/loader.conf > 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 I don't recall ever seeing a battery.state of 7? When fully charged my Thinkpad T23 shows state 0, battery.life 98 to 100 (%). If your battery is ok you should get at least 1 hour on battery, maybe 2 or 3 hours, so that does look like a problem .. whether hardware or ACPI I can't guess. Is this a new machine? Have you tried loading acpi_toshiba(4) ? Try kldload acpi_toshiba, if it's of any help, put acpi_toshiba_load="YES" in /boot/loader.conf cheers, Ian > Rui Paulo wrote: > > > > On 30 Dec 2008, at 17:59, Daniel Leal wrote: > > > > > Thanks for your reply. > > > > > > So that means that simply my laptop is not able to deal with it, or maybe > > > in a future FreeBSD release it could work? > > > > Yes, but, of course, you can try to find the problem and I'll try to help > > you with a fix if time permits :-) > > > > Regards, > > -- > > Rui Paulo From smithi at nimnet.asn.au Wed Dec 31 03:39:30 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Wed Dec 31 03:39:37 2008 Subject: is acpi working well ? In-Reply-To: References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> <495A4DC3.3060709@webvolution.net> Message-ID: <20081231143802.N51566@sola.nimnet.asn.au> On Tue, 30 Dec 2008, Rui Paulo wrote: > On 30 Dec 2008, at 16:35, Daniel Leal wrote: > > > I just asked because I was not sure. > > > > But what about the other things? > > The other things are problems with your ACPI vendor implementation or > FreeBSD's ACPI implementation problems. > > > I already try to disable acpi in /boot/loader.conf with the line > > hint.acpi.0.disabled="1" > > but my laptop simply don't boot!! It crashes during freebsd boot with a few > > error that are to fast for my eyes. > > Several modern laptops don't work with ACPI disabled. Do any multi-core laptops work (with >1 core) with ACPI disabled? cheers, Ian From giuseppe.bonfa at gmail.com Wed Dec 31 07:45:24 2008 From: giuseppe.bonfa at gmail.com (GiuseppeBonfa) Date: Wed Dec 31 07:45:30 2008 Subject: Implementation of AcpiOsDerivePciId Message-ID: <495B1C8A.7000808@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, My first post on ACPI-ML so I hope to be quite rigth, if not please excuse my OT. By visiting ACPI Project Page I've seen that AcpiOsDerivePciId has not a right implementation, my question is, can you please direct/point me to some coder? I'm working on a new version of AcpiOsDerivePciId so I need to know some Prj Person to submit my work. Have a nice Day and an Happy New Year! Giuseppe 'Evilcry' Bonfa' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJWxyJqkxgE33/urIRAnkjAJ9hNC1XKFBXkSqvog0Sv0ZN+w/regCeJnez MUTKLETrkNWrwj71NMpUo1A= =A2cI -----END PGP SIGNATURE----- From dleal at webvolution.net Wed Dec 31 09:21:53 2008 From: dleal at webvolution.net (Daniel Leal) Date: Wed Dec 31 09:22:00 2008 Subject: is acpi working well ? In-Reply-To: <20081231135644.X51566@sola.nimnet.asn.au> References: <49594754.8000607@webvolution.net> <9BD84977-D59F-47E2-97A9-B6338F7E3D48@fnop.net> <495A4DC3.3060709@webvolution.net> <495A618D.8020702@webvolution.net> <495AB36D.1000804@webvolution.net> <20081231135644.X51566@sola.nimnet.asn.au> Message-ID: <495B39D2.6080900@webvolution.net> This machine has almost 2 years old. Before I install FBSD the battery last like 2 hours. But now... I already load tochiba_acpi in loader.conf, but nothing new... I am going to turn on acpi verbosity to see what i can get from there. thanks, daniel Ian Smith wrote: > On Tue, 30 Dec 2008, Daniel Leal wrote: > > > Well, the hw.acpi.thermal is not shown in the sysctl hw.acpi list. Maybe that > > means that my MB does not have that kind of sensor. But if not, is there a > > way to control the CPU fan speed according to CPU work? It seams to me that > > the CPU fan is always with the same velocity. And when I had windows > > installed in this laptop I remember that when some complicated apps were > > running the sound of the fan was different. > > As Rui suggested, add 'powerd_enable=YES' to rc.conf for that. However > it does seem a bit odd that hw.acpi.thermal sysctls aren't showing up. > > > Regarding the battery, do do you think that with the following list I can > > monitor the charge and be sure that I will not have an unexpected shutdown if > > I run my laptop just on battery? > > [..] > > > hw.acpi.verbose: 0 > > If you turn that on you may get some more clues in /var/log/messages. > ie hw.acpi.verbose=1 in /boot/loader.conf > > > 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 > > I don't recall ever seeing a battery.state of 7? When fully charged my > Thinkpad T23 shows state 0, battery.life 98 to 100 (%). If your battery > is ok you should get at least 1 hour on battery, maybe 2 or 3 hours, so > that does look like a problem .. whether hardware or ACPI I can't guess. > > Is this a new machine? > > Have you tried loading acpi_toshiba(4) ? Try kldload acpi_toshiba, if > it's of any help, put acpi_toshiba_load="YES" in /boot/loader.conf > > cheers, Ian > > > Rui Paulo wrote: > > > > > > On 30 Dec 2008, at 17:59, Daniel Leal wrote: > > > > > > > Thanks for your reply. > > > > > > > > So that means that simply my laptop is not able to deal with it, or maybe > > > > in a future FreeBSD release it could work? > > > > > > Yes, but, of course, you can try to find the problem and I'll try to help > > > you with a fix if time permits :-) > > > > > > Regards, > > > -- > > > Rui Paulo > From volker at vwsoft.com Wed Dec 31 12:55:44 2008 From: volker at vwsoft.com (Volker) Date: Wed Dec 31 12:55:52 2008 Subject: Implementation of AcpiOsDerivePciId In-Reply-To: <495B1C8A.7000808@gmail.com> References: <495B1C8A.7000808@gmail.com> Message-ID: <495B6430.8060405@vwsoft.com> On 12/23/-58 20:59, GiuseppeBonfa wrote: > Hi there, > > My first post on ACPI-ML so I hope to be quite rigth, if not please > excuse my OT. > > By visiting ACPI Project Page I've seen that AcpiOsDerivePciId has not a > right implementation, my question is, can you please direct/point me to > some coder? I'm working on a new version of AcpiOsDerivePciId so I need > to know some Prj Person to submit my work. > > Have a nice Day and an Happy New Year! > Giuseppe 'Evilcry' Bonfa' Giuseppe, we do not make any deals in mystical dark rooms or at the backdoor. The official way for non-committers is to file a PR and attach patches. I suggest you to discuss your findings first in our fine mailing lists and have your proposed changes being validated first. This raises the chances for your PR not to die old in GNATS. Volker From nate at root.org Wed Dec 31 17:46:10 2008 From: nate at root.org (Nate Lawson) Date: Wed Dec 31 17:46:16 2008 Subject: Implementation of AcpiOsDerivePciId In-Reply-To: <495B6430.8060405@vwsoft.com> References: <495B1C8A.7000808@gmail.com> <495B6430.8060405@vwsoft.com> Message-ID: <495BAFE0.3070800@root.org> Volker wrote: > On 12/23/-58 20:59, GiuseppeBonfa wrote: >> Hi there, >> >> My first post on ACPI-ML so I hope to be quite rigth, if not please >> excuse my OT. >> >> By visiting ACPI Project Page I've seen that AcpiOsDerivePciId has not a >> right implementation, my question is, can you please direct/point me to >> some coder? I'm working on a new version of AcpiOsDerivePciId so I need >> to know some Prj Person to submit my work. >> >> Have a nice Day and an Happy New Year! >> Giuseppe 'Evilcry' Bonfa' > > Giuseppe, > > we do not make any deals in mystical dark rooms or at the backdoor. > > The official way for non-committers is to file a PR and attach patches. > I suggest you to discuss your findings first in our fine mailing lists > and have your proposed changes being validated first. This raises the > chances for your PR not to die old in GNATS. Correct. Post a link to the patches here and ask any questions. Then if it's ready to commit, throw it into the PR. -- Nate