From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 4 03:05:59 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 704B016A41F for ; Sun, 4 Dec 2005 03:05:59 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC57943D5C for ; Sun, 4 Dec 2005 03:05:58 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by zproxy.gmail.com with SMTP id i11so800870nzh for ; Sat, 03 Dec 2005 19:05:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=j5WGgYzy0PQzGXgCmG8EWidFMyKloEmGn6S2G/TOgTa22jBnLWahAATWbDRmMwAUlMNj+qQSstFqGeid4lp6hUY/esembz/9qQgtS/3QAeCfJo4n8aD11rfil/ABFZm/0cDr/F/qtuBLJeHfFHRXlHzmDa1TXyzfcqjr8VvOU8g= Received: by 10.65.188.8 with SMTP id q8mr2156695qbp; Sat, 03 Dec 2005 19:05:58 -0800 (PST) Received: by 10.65.22.9 with HTTP; Sat, 3 Dec 2005 19:05:58 -0800 (PST) Message-ID: Date: Sun, 4 Dec 2005 12:05:58 +0900 From: Eric Kjeldergaard To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: cpufreq and schedulers instead of powerd X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 03:05:59 -0000 Hello all. I hope this is the right place for such an item. I've been pondering processor dynamic clocking for a while and recently have been wondering if it is optimal to have the processor rate chosen by a daemon as it is now, or rather integrate the downclocking into the scheduler. My reasoning largely is based on the thought of overhead for switching processor speeds. With modernish processors (especially the Pentium-m) it seems that the time to change operating frequencies is very low which would lead me to think that something like a scheduler could take advantage of that and clock them down faster and more often. Also, schedulers (I've been looking mainly at ULE) have more knowledge about processor usage than just the current load which appears to be all that powerd looks at. Does anyone have any additional information on dynamic clock handling in OS schedulers or information on why freebsd chose powerd over an implementation in scheduler(s)? Eric Kjeldergaard -- If I write a signature, my emails will appear more personalised. From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 4 09:55:51 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D5D516A41F; Sun, 4 Dec 2005 09:55:51 +0000 (GMT) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B4CD43D46; Sun, 4 Dec 2005 09:55:49 +0000 (GMT) (envelope-from eugen@kuzbass.ru) Received: from kuzbass.ru (kost [213.184.65.82]) by www.svzserv.kemerovo.su (8.13.3/8.13.3) with ESMTP id jB49tfCW012712; Sun, 4 Dec 2005 16:55:42 +0700 (KRAT) (envelope-from eugen@kuzbass.ru) Message-ID: <4392BCF7.E4248A35@kuzbass.ru> Date: Sun, 04 Dec 2005 16:55:03 +0700 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: John Baldwin References: <20050513140240.GA25774@svzserv.kemerovo.su> <200512021732.15866.jhb@freebsd.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: 5.4: pci_link problem on 440BX X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 09:55:51 -0000 John Baldwin wrote: > > > We shouldn't print that message unless pci_link is enabled. When > > > pci_link is disabled we shouldn't even be looking at PRT entries. Can > > > you try booting a 6.0-snapshot CD and seeing if it works ok? > > > > Now 6.0 boots to multiuser mode with ACPI fully enabled or fully disabled. > > make buildworld cannot be completed with ACPI - still silent hang > > of userland and no console switching (keyboard leds do switch and > > KDB works). > > > > 6.0's GENERIC does not boot to single user with > > debug.acpi.disabled="pci_link", fatal trap 12 occures: page fault while in > > kernel mode, > > fault virtual address 0x0, supervisor read, page not present > > in acpi_pci_link_lookup+0x26. > > I think I know what this is and this patch probably fixes the panic in the > case that you use 'debug.acpi.disabled="pci_link"' > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_pci_link.c 2005/11/23 16:40:40 > +++ //depot/user/jhb/acpipci/dev/acpica/acpi_pci_link.c 2005/12/02 22:28:08 > @@ -1011,6 +1011,9 @@ > { > struct link *link; > > + if (acpi_disabled("pci_link")) > + return (PCI_INVALID_IRQ); > + > ACPI_SERIAL_BEGIN(pci_link); > link = acpi_pci_link_lookup(dev, index); > if (link == NULL) > > How does the 6.0 install CD do on your machine both with ACPI enabled and disabled? Two problems, my IBM HDD with 6.0 died and I'll need reinstall 6.0 to perform tests. I still run 4.11-STABLE with that motherboard. Second, I'll have no Internet access for a day or two. So I'll answer some days later this week. Thank you for patch. Eugene Grosbein. From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 4 12:01:06 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16F0116A41F for ; Sun, 4 Dec 2005 12:01:06 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A34D243D55 for ; Sun, 4 Dec 2005 12:01:05 +0000 (GMT) (envelope-from nate@root.org) Received: from [172.16.0.224] (fi01-84CBdd.tokyo.flets.isao.net [211.132.203.221] (may be forged)) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jB4C10du019044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 4 Dec 2005 04:01:04 -0800 Message-ID: <4392DA43.1060205@root.org> Date: Sun, 04 Dec 2005 04:00:03 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Kjeldergaard References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: cpufreq and schedulers instead of powerd X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 12:01:06 -0000 Eric Kjeldergaard wrote: > Hello all. I hope this is the right place for such an item. > > I've been pondering processor dynamic clocking for a while and > recently have been wondering if it is optimal to have the processor > rate chosen by a daemon as it is now, or rather integrate the > downclocking into the scheduler. My reasoning largely is based on the > thought of overhead for switching processor speeds. With modernish > processors (especially the Pentium-m) it seems that the time to change > operating frequencies is very low which would lead me to think that > something like a scheduler could take advantage of that and clock them > down faster and more often. Also, schedulers (I've been looking > mainly at ULE) have more knowledge about processor usage than just the > current load which appears to be all that powerd looks at. Does > anyone have any additional information on dynamic clock handling in OS > schedulers or information on why freebsd chose powerd over an > implementation in scheduler(s)? I don't want to single you out, and I do hope you'll be the one who follows through with actual code. However, I wish people would stop talking about this and just implement it already. This is like the 10th email asking the same thing. Here is a link with references to the appropriate papers: http://wikitest.freebsd.org/moin.cgi/powerd To answer your specific question, more transitions != better power saving. If you were idle and now have moderate CPU load, it's best to go to 100% to complete the work faster. If you were busy and are now idle, it's best to start decreasing to the lowest level as soon as possible. Total power used is the integral of instantaneous power over the workload. Running a CPU bound process at the lowest frequency is worse than running it at 100% and then going to the lowest frequency once idle. Our issue currently is not lack of quality of measurements. It's lack of a good algorithm that could do better with the same measurements. I don't know if you've looked at the code, but it only takes 1 measurement and makes all decisions based on that. Better to have a running history and implement several of the algorithms and benchmark them. Once we have that working, THEN it makes sense to investigate getting quality measurements to the algorithm. Again, please read the history/research if you're interested in helping out. http://wikitest.freebsd.org/moin.cgi/powerd -- Nate From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 4 17:43:01 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DC8216A41F for ; Sun, 4 Dec 2005 17:43:01 +0000 (GMT) (envelope-from glup@momu.dk) Received: from mx01.stofanet.dk (mx01.stofanet.dk [212.10.10.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E59943D60 for ; Sun, 4 Dec 2005 17:43:00 +0000 (GMT) (envelope-from glup@momu.dk) Received: from d40ad98f.rev.stofanet.dk ([212.10.217.143] helo=[192.168.0.47]) by mx01.stofanet.dk (envelope-from ) with esmtp id 1Eixt4-0004IV-1s for freebsd-acpi@freebsd.org; Sun, 04 Dec 2005 18:42:59 +0100 Message-ID: <43932AD4.7070100@momu.dk> Date: Sun, 04 Dec 2005 18:43:48 +0100 From: Gregers Petersen User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: IBM R51 & 6.0 Release + Suspend/Resume? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 17:43:01 -0000 Dear All I have recently acquired an IBM R51, with a 1400x1050 screen and 1 GB RAM, with the intent of using it for daily work and activities (I not a coder or anything in that direction, I just like the FreeBSD OS). I started out with installing 6.0 Release running generic kernel - all my hardware is supported and the various IBM buttons are working 'out of the box' - and everything was doing very well until I began looking at some of the common tasks of a laptop. Suspend and Resume is somewhat of a problem (I have below listed the additions I have made to the different .conf files): ---------------------------- sysctl.conf : hw.acpi.reset_video=0 hw.syscons.sc_no_suspend_vtswitch=1 hw.acpi.lid_switch_state=S3 ---------------------------- I have enable Speedstep via: rc.conf : est_enable="YES" estctl_enable="YES" estctl_speed_ac="adaptive" estctl_speed_battery=adaptive" --------------- loader.conf acpi_video_load="YES" snd_ich_load="YES" --------------------- I have added the following line to rc.resume : /etc/rc.d/moused restart --------------------------- When I run the command (as su): acpiconf -s S3 the system goes into suspend - and when I press the Fn button it again comes out of suspend (resumes) - at first I had problem with a "dead" mouse, but that problem was resolved with the above mentioned addition to rc.resume. BUT I still have problems with my network connection, which is "dead" - and I'm not really able to bring it back to life again (without a reboot). During most of my attempt at revieving the network the system ends up in a compelte freeze ... ? On the other hand - If I close the lid the system goes into suspend (S3) - but when I again opens the lid the mouse + network stays "dead" (and I can not find a solution to this problem) ? ---------------- I have tryed to add the following to devd.conf : notify 10 { match "system" "ACPI"; match "subsystem" "Lid"; match "notify" "0"; action "/usr/sbin/acpiconf -s 3"; }; ------------------ Which did'nt help either (actually it did absolutely nothing to the suspend and resume function)? Apart from this I have some questions regarding the functions around: hw.acpi.cpu.cx_lowest hw.acpi.cpu.cx_supported hw.acpi.cpu.cx_usage which I just don't really can figure out in regard to tuning of power consumption. cpu speed etc ? The problem is that it seems that my cpu is running quite fast (the the fan kicks in quite offen, dispite the R51 basicly doing nothing) ? I just hope that I have been specificly enough, with the discription and attempts at solving the problem.. sincerely Gregers (the anthropologist) From owner-freebsd-acpi@FreeBSD.ORG Sun Dec 4 21:06:04 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6368816A41F; Sun, 4 Dec 2005 21:06:04 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07CE043D62; Sun, 4 Dec 2005 21:06:02 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 491E65647E; Sun, 4 Dec 2005 22:06:01 +0100 (CET) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00636-02-2; Sun, 4 Dec 2005 22:05:59 +0100 (CET) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id C43945647C; Sun, 4 Dec 2005 22:05:59 +0100 (CET) Received: from 192.168.1.20 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Sun, 4 Dec 2005 22:05:59 +0100 (CET) Message-ID: <56639.192.168.1.20.1133730359.squirrel@webmail.thilelli.net> In-Reply-To: <200512031626.59048.jhb@freebsd.org> References: <49704.192.168.1.18.1113475314.squirrel@webmail.thilelli.net> <200512020811.33720.jhb@freebsd.org> <62227.192.168.1.20.1133563026.squirrel@webmail.thilelli.net> <200512031626.59048.jhb@freebsd.org> Date: Sun, 4 Dec 2005 22:05:59 +0100 (CET) From: "Julien Gabel" To: "John Baldwin" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Cc: freebsd-acpi@freebsd.org, freebsd-usb@freebsd.org, bug-followup@freebsd.org Subject: Re: usb/74989: (regression) Lost USB support between 5.2.1-RELEASE and 5.3-RELEASE on K7T266 Pro2. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpeg@thilelli.net List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 21:06:04 -0000 >> Ok. I think you finally got it this time. Applied this patch against >> RELENG_6 and it seems to work fine now. I build and installed the >> kernel, set the loader.conf directives >> hint.acpi.0.disabled to 0 >> hint.apic.0.disabled to 0 >> and reboot on the system... it works well now, thank you ;) > Ok, fix committed. It will be in 6.1 as well. Good news, thanks! >>>> (*) The boot disk seems not be able to be used for the root mount, >>>> i.e. ufs:/dev/ad0s1a in my case. >>> If you could get a verbose dmesg for this case using a serial console >>> I'd be interested in looking at that too. >> Certainly! The output can be found at: >> http://www.thilelli.net/~jgabel/store/pub/PR/74989/serial.dmesg.boot-v >> >> Note: the kernel used for this boot was the just-previously-patched one. > Ok, what happens here is that the $PIR code ends up using IRQ 14 for a > virgin-routed link. You can just use a tunable to override this like so: > > hw.pci.link.0x1.irq=12 Yes, this setting solved the problem with both ACPI and APIC support disabled. > That should make the vga adapter use irq 12 rather than irq 14. If you > have a BIOS setting that says 'enable VGA irq' you could also try > turning that on. However, you'd probably much rather be running with > ACPI + APIC enabled anyway. Sure... ;) Just a little question though: what can i "expect", from now on, to have ACPI and APIC enabled in the same time, rather than ACPI support alone (without APIC)? -- -jpeg. From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 05:11:39 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADC9E16A41F; Mon, 5 Dec 2005 05:11:39 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BDBE43D4C; Mon, 5 Dec 2005 05:11:38 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3161818 for multiple; Mon, 05 Dec 2005 00:09:44 -0500 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB55BYfV035201; Mon, 5 Dec 2005 00:11:34 -0500 (EST) (envelope-from jhb@freebsd.org) In-Reply-To: <56639.192.168.1.20.1133730359.squirrel@webmail.thilelli.net> References: <49704.192.168.1.18.1113475314.squirrel@webmail.thilelli.net> <200512020811.33720.jhb@freebsd.org> <62227.192.168.1.20.1133563026.squirrel@webmail.thilelli.net> <200512031626.59048.jhb@freebsd.org> <56639.192.168.1.20.1133730359.squirrel@webmail.thilelli.net> Mime-Version: 1.0 (Apple Message framework v746.2) X-Priority: 3 (Normal) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7D56D5E2-3905-4C68-812D-004C2F65EBA4@freebsd.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Mon, 5 Dec 2005 00:11:27 -0500 To: jpeg@thilelli.net X-Mailer: Apple Mail (2.746.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-acpi@freebsd.org, freebsd-usb@freebsd.org, bug-followup@freebsd.org Subject: Re: usb/74989: (regression) Lost USB support between 5.2.1-RELEASE and 5.3-RELEASE on K7T266 Pro2. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 05:11:39 -0000 On Dec 4, 2005, at 4:05 PM, Julien Gabel wrote: >> Ok, what happens here is that the $PIR code ends up using IRQ 14 >> for a >> virgin-routed link. You can just use a tunable to override this >> like so: >> >> hw.pci.link.0x1.irq=12 > > Yes, this setting solved the problem with both ACPI and APIC support > disabled. Ok. >> That should make the vga adapter use irq 12 rather than irq 14. >> If you >> have a BIOS setting that says 'enable VGA irq' you could also try >> turning that on. However, you'd probably much rather be running with >> ACPI + APIC enabled anyway. > > Sure... ;) > > Just a little question though: what can i "expect", from now on, to > have > ACPI and APIC enabled in the same time, rather than ACPI support alone > (without APIC)? Well, out of the box we default to ACPI + APIC, so I'd just stick to using that with the patch I just committed. 6.1 and later should just work out of the box on your system now. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 11:01:47 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE78E16A41F for ; Mon, 5 Dec 2005 11:01:47 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA41C43D53 for ; Mon, 5 Dec 2005 11:01:41 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB5B1fwY023760 for ; Mon, 5 Dec 2005 11:01:41 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB5B1dCG023752 for freebsd-acpi@freebsd.org; Mon, 5 Dec 2005 11:01:39 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 5 Dec 2005 11:01:39 GMT Message-Id: <200512051101.jB5B1dCG023752@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 11:01:48 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/22] i386/54756 acpi ACPI suspend/resume problem on CF-W2 lapt o [2003/08/17] i386/55661 acpi ACPI suspend/resume problem on ARMADA M70 o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel o [2003/08/27] kern/56024 acpi ACPI suspend drains battery while in S3 o [2003/09/03] i386/56372 acpi acpi don't work on TYAN tiger100 M/B o [2004/03/09] i386/64002 acpi acpi problem o [2004/05/27] i386/67273 acpi [hang] system hangs with acpi and Xfree o [2004/10/12] i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Arma o [2005/03/21] i386/79080 acpi acpi thermal changes freezes HP nx6110 o [2005/03/21] i386/79081 acpi ACPI suspend/resume not working on HP nx6 o [2005/11/11] kern/88859 acpi ACPI broken on Compaq DL360 11 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/03/17] kern/64365 acpi ACPI problems o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5 o [2004/11/11] i386/73822 acpi [request] add thermal support to ACPI o [2004/11/11] kern/73823 acpi [feature request] acpi / power-on by time o [2004/11/17] kern/74030 acpi Unplugging AC causes battery % to stay lo o [2004/11/21] kern/74215 acpi [request] add ACPI headers to /usr/includ o [2005/05/09] kern/80815 acpi ACPI(pci_link) problem in 5.4-STABLE: TIM o [2005/11/21] i386/89376 acpi cmbat related ACPI change between 6.0-rel o [2005/12/03] kern/89879 acpi [acpi] ACPI-0438: *** Error: Looking up [ 10 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 17:18:31 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2B1616A41F for ; Mon, 5 Dec 2005 17:18:31 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DCEE43D46 for ; Mon, 5 Dec 2005 17:18:27 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jB5HKQPx062151 for ; Mon, 5 Dec 2005 17:20:26 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jB5HKQx5062150 for freebsd-acpi@freebsd.org; Mon, 5 Dec 2005 17:20:26 GMT (envelope-from dunstan) Date: Mon, 5 Dec 2005 17:20:25 +0000 From: "Wojciech A. Koszek" To: freebsd-acpi@freebsd.org Message-ID: <20051205172025.GA62040@freebsd.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: [ASUS A4D] Patch for DSDT which corrects 'acpi_perf0..' problem X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 17:18:31 -0000 Hello, While booting default kernel (-CURRENT) on my ASUS A4D I get: [..] acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package ..the same line dozen of times.. acpi_perf0: invalid _PSS package acpi_perf0: invalid _PSS package [..] acpidump -dt > dunstan-ASUS_A4D.asl This file is available at [1]. This is what I get while trying to compile dumped ASL with iasl: # iasl ./dunstan-ASUS_A4D.asl Intel ACPI Component Architecture ASL Optimizing Compiler version 20051021 [Dec 4 2005] Copyright (C) 2000 - 2005 Intel Corporation Supports ACPI Specification Revision 3.0 ./dunstan-ASUS_A4D.asl 5973: Package (0x06) Error 1045 - Initializer list too long ^ ASL Input: ./dunstan-ASUS_A4D.asl - 7196 lines, 248468 bytes, 3059 keywords Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 664 Optimizations After removing bogus lines [2] problem disappeared. I've written a patch [3] for ASL, and it seems to work. acpi(4) no longer complains about "_PSS" [1] http://freebsd.czest.pl/dunstan/FreeBSD/acpi/dunstan-ASUS_A4D.asl [2] http://freebsd.czest.pl/dunstan/FreeBSD/acpi/dunstan-ASUS_A4D.asl.new [3] http://freebsd.czest.pl/dunstan/FreeBSD/acpi/dunstan-ASUS_A4D.diff Additional information: [4] http://freebsd.czest.pl/dunstan/FreeBSD/acpi/dunstan-ASUS_A4D.sysctl-acpi (after patching) [5] http://freebsd.czest.pl/dunstan/FreeBSD/acpi/dunstan-ASUS_A4D.dmesg Comments are welcome. -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 18:18:46 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71CB716A420; Mon, 5 Dec 2005 18:18:46 +0000 (GMT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09B0343D5A; Mon, 5 Dec 2005 18:18:42 +0000 (GMT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (smmsp@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.3/8.13.3) with ESMTP id jB5IIdxK076451; Tue, 6 Dec 2005 01:18:39 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from root@localhost) by www.svzserv.kemerovo.su (8.13.3/8.13.3/Submit) id jB5IIdwo076450; Tue, 6 Dec 2005 01:18:39 +0700 (KRAT) (envelope-from eugen) Date: Tue, 6 Dec 2005 01:18:39 +0700 From: Eugene Grosbein To: John Baldwin Message-ID: <20051205181839.GA75425@svzserv.kemerovo.su> References: <20050513140240.GA25774@svzserv.kemerovo.su> <200512021732.15866.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512021732.15866.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-acpi@freebsd.org Subject: Re: 5.4: pci_link problem on 440BX X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 18:18:46 -0000 On Fri, Dec 02, 2005 at 05:32:14PM -0500, John Baldwin wrote: > > > We shouldn't print that message unless pci_link is enabled. When > > > pci_link is disabled we shouldn't even be looking at PRT entries. Can > > > you try booting a 6.0-snapshot CD and seeing if it works ok? > > > > Now 6.0 boots to multiuser mode with ACPI fully enabled or fully disabled. > > make buildworld cannot be completed with ACPI - still silent hang > > of userland and no console switching (keyboard leds do switch and > > KDB works). > > > > 6.0's GENERIC does not boot to single user with > > debug.acpi.disabled="pci_link", fatal trap 12 occures: page fault while in > > kernel mode, > > fault virtual address 0x0, supervisor read, page not present > > in acpi_pci_link_lookup+0x26. > > I think I know what this is and this patch probably fixes the panic in the > case that you use 'debug.acpi.disabled="pci_link"' > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_pci_link.c 2005/11/23 16:40:40 > +++ //depot/user/jhb/acpipci/dev/acpica/acpi_pci_link.c 2005/12/02 22:28:08 > @@ -1011,6 +1011,9 @@ > { > struct link *link; > > + if (acpi_disabled("pci_link")) > + return (PCI_INVALID_IRQ); > + > ACPI_SERIAL_BEGIN(pci_link); > link = acpi_pci_link_lookup(dev, index); > if (link == NULL) I'll try this patch a bit later. > > How does the 6.0 install CD do on your machine both with ACPI enabled and disabled? I've just installed 6.0-RELEASE again. I booted it using [default] option (e.g. with ACPI enabled) and installation ran smoothly. However, I could not extract /usr/ports/distfiles/gettext-0.14.5.tar.gz, /usr/ports is mounted from 4.11 installation. All disk activity stopped and kernel repeatedly wrote something about "DANGER Will Robinson !!", I think it was from /usr/src/sys/dev/ata/ata-queue.c I rebooted with ACPI disabled and the problem disappeared. Now I'm going to test 'debug.acpi.disabled="pci_link"' case. Eugene Grosbein From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 18:54:18 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE30916A420 for ; Mon, 5 Dec 2005 18:54:18 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A978243D68 for ; Mon, 5 Dec 2005 18:54:16 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3200107 for multiple; Mon, 05 Dec 2005 13:52:22 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB5Is6L3040561; Mon, 5 Dec 2005 13:54:08 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Robert Faulds" Date: Mon, 5 Dec 2005 13:28:12 -0500 User-Agent: KMail/1.8.2 References: <331CA3AB8A236A488C92DEC289C7D04D01642079@Deliverance.voxify.com> In-Reply-To: <331CA3AB8A236A488C92DEC289C7D04D01642079@Deliverance.voxify.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512051328.12923.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-acpi@freebsd.org Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 18:54:18 -0000 On Friday 02 December 2005 06:20 pm, Robert Faulds wrote: > No love from SMP either. It still only boots with apic disabled. > I put up the mptable, and a few other files at > http://xocolatl.com/rfaulds/freebsd-acpi/ > I've been stepping through the BIOS but there is no options for forcing > the mp spec. > Interestingly, I have disabled HyperThreading in the BIOS and yet the > SMP kernel still detects it. The BIOS toggle just changes the HT CPUs to be listed as disabled in the MADT table ACPI uses. The 'Hyperthreading' printf in the dmesg is based on reading the registers from the CPU and is output even in a UP kernel. Your MP table looks ok as well, so I'm not sure why a dmesg with no ACPI is not finding your CPUs. How did you disable ACPI, did you boot using safe mode? If so, try breaking into the loader and just disable ACPI via set hint.acpi.0.disabled=1 Safe mode disables SMP support as well as ACPI. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 18:54:52 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5042416A420; Mon, 5 Dec 2005 18:54:52 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from orsfmr003.jf.intel.com (fmr18.intel.com [134.134.136.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 929C143D78; Mon, 5 Dec 2005 18:54:40 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from orsfmr101.jf.intel.com (orsfmr101.jf.intel.com [10.7.209.17]) by orsfmr003.jf.intel.com (8.12.10/8.12.10/d: major-outer.mc,v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id jB5IsdsL009796; Mon, 5 Dec 2005 18:54:39 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by orsfmr101.jf.intel.com (8.12.10/8.12.10/d: major-inner.mc,v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id jB5IqTmN003001; Mon, 5 Dec 2005 18:54:37 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs041.jf.intel.com (SAVSMTP 3.1.7.47) with SMTP id M2005120510425605515 ; Mon, 05 Dec 2005 10:42:59 -0800 Received: from orsmsx403.amr.corp.intel.com ([192.168.65.209]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 5 Dec 2005 10:42:52 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Dec 2005 10:42:51 -0800 Message-ID: <971FCB6690CD0E4898387DBF7552B90E03A00AAF@orsmsx403.amr.corp.intel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: kern/89879: [acpi] ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND thread-index: AcX4Omm4OcJklGNpSlG+WPPJoi203ABkQWXw From: "Moore, Robert" To: "Ariff Abdullah" , X-OriginalArrivalTime: 05 Dec 2005 18:42:52.0382 (UTC) FILETIME=[B2D3A7E0:01C5F9CB] X-Scanned-By: MIMEDefang 2.52 on 10.7.209.17 Cc: Subject: RE: kern/89879: [acpi] ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 18:54:52 -0000 I'm still looking at a fix for this, to allow references within packages to be passed around with no validation. It's a bit difficult given that such references are currently validated against the namespace at the moment they are parsed in the AML byte stream, with no regard to the context of the reference. Bob > -----Original Message----- > From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- > acpi@freebsd.org] On Behalf Of Ariff Abdullah > Sent: Saturday, December 03, 2005 10:50 AM > To: freebsd-acpi@freebsd.org > Subject: Re: kern/89879: [acpi] ACPI-0438: *** Error: Looking up [Z00C] in > namespace, AE_NOT_FOUND >=20 > The following reply was made to PR kern/89879; it has been noted by GNATS. >=20 > From: Ariff Abdullah > To: bug-followup@FreeBSD.org, dana.myers@gmail.com, dwerner1974@yahoo.com > Cc: > Subject: Re: kern/89879: [acpi] ACPI-0438: *** Error: Looking up [Z00C] in > namespace, AE_NOT_FOUND > Date: Sun, 4 Dec 2005 02:43:06 +0800 >=20 > On Sat, 3 Dec 2005 18:00:21 GMT > "Dana H. Myers" wrote: > > The following reply was made to PR kern/89879; it has been noted by > > GNATS. > > > > From: "Dana H. Myers" > > To: bug-followup@FreeBSD.org, dwerner1974@yahoo.com > > Cc: > > Subject: Re: kern/89879: [acpi] ACPI-0438: *** Error: Looking up > > [Z00C] in > > namespace, AE_NOT_FOUND > > Date: Sat, 03 Dec 2005 09:55:19 -0800 > > > > I see the same problem on the Acer Ferrari 4005, where Z00C isn't > > defined and thus the battery status method fails. > > > This is actually easy to fix, provided that you know how to dump, edit > and recompile your acpi dsdt using acpidump(8) and iasl(8). Take a > look at http://people.freebsd.org/~ariff/acer_ferrari/ for an example > on how to tweak and recover the functionality of battery status > method. >=20 > -- > Ariff Abdullah > FreeBSD > _______________________________________________ > 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 owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 19:23:01 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C43F16A41F; Mon, 5 Dec 2005 19:23:01 +0000 (GMT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CABC43D5A; Mon, 5 Dec 2005 19:23:00 +0000 (GMT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (smmsp@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.3/8.13.3) with ESMTP id jB5JMvHU082269; Tue, 6 Dec 2005 02:22:57 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from root@localhost) by www.svzserv.kemerovo.su (8.13.3/8.13.3/Submit) id jB5JMvGw082268; Tue, 6 Dec 2005 02:22:57 +0700 (KRAT) (envelope-from eugen) Date: Tue, 6 Dec 2005 02:22:57 +0700 From: Eugene Grosbein To: John Baldwin Message-ID: <20051205192257.GC75425@svzserv.kemerovo.su> References: <20050513140240.GA25774@svzserv.kemerovo.su> <200512021732.15866.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512021732.15866.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-acpi@freebsd.org Subject: Re: 5.4: pci_link problem on 440BX X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 19:23:01 -0000 > > 6.0's GENERIC does not boot to single user with > > debug.acpi.disabled="pci_link", fatal trap 12 occures: page fault while in > > kernel mode, > > fault virtual address 0x0, supervisor read, page not present > > in acpi_pci_link_lookup+0x26. > > I think I know what this is and this patch probably fixes the panic in the > case that you use 'debug.acpi.disabled="pci_link"' > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_pci_link.c 2005/11/23 16:40:40 > +++ //depot/user/jhb/acpipci/dev/acpica/acpi_pci_link.c 2005/12/02 22:28:08 > @@ -1011,6 +1011,9 @@ > { > struct link *link; > > + if (acpi_disabled("pci_link")) > + return (PCI_INVALID_IRQ); > + > ACPI_SERIAL_BEGIN(pci_link); > link = acpi_pci_link_lookup(dev, index); > if (link == NULL) > 6.0-RELEASE boots with this patch, ACPI enabled and debug.acpi.disabled="pci_link", make buildworld started but several minutes later kernel started to write to console: ad4: req=0xc223d7d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! ad4: req=0xc223d7d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! ad4: req=0xc223d7d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! Every 4 seconds another line is appears. Ctrl-T now shows: load: 0.07 cmd: sh 16681 [ufs] 0.00u 0.00s 0% 284k I cannot login using another vty, getty hangs too: login: root load: 0.08 cmd: getty 549 [ufs] 0.00u 0.00s 0% 928k 6.0-RELEASE is installed on ad6, and ad4 holds /usr/obj mounted from 4.11 installation. ad4 is partitioned to hold 4.11-STABLE, Windows 98SE and Windows XP, all three OSes boot and run from ad4 without a problem. 6.0-RELEASE with GENERIC kernel behaves not so well. However, previously established outgoing ssh session works and I'm writting this letter using this session and pasting messages with mouse :-) Eugene Grosbein From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 19:31:42 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77AE316A41F for ; Mon, 5 Dec 2005 19:31:42 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id C14B543D53 for ; Mon, 5 Dec 2005 19:31:41 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3202527 for multiple; Mon, 05 Dec 2005 14:29:33 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB5JVLHC040885; Mon, 5 Dec 2005 14:31:21 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Eugene Grosbein Date: Mon, 5 Dec 2005 14:00:02 -0500 User-Agent: KMail/1.8.2 References: <20050513140240.GA25774@svzserv.kemerovo.su> <200512021732.15866.jhb@freebsd.org> <20051205181839.GA75425@svzserv.kemerovo.su> In-Reply-To: <20051205181839.GA75425@svzserv.kemerovo.su> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512051400.03509.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-acpi@freebsd.org Subject: Re: 5.4: pci_link problem on 440BX X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 19:31:42 -0000 On Monday 05 December 2005 01:18 pm, Eugene Grosbein wrote: > On Fri, Dec 02, 2005 at 05:32:14PM -0500, John Baldwin wrote: > > > > We shouldn't print that message unless pci_link is enabled. When > > > > pci_link is disabled we shouldn't even be looking at PRT entries. > > > > Can you try booting a 6.0-snapshot CD and seeing if it works ok? > > > > > > Now 6.0 boots to multiuser mode with ACPI fully enabled or fully > > > disabled. make buildworld cannot be completed with ACPI - still silent > > > hang of userland and no console switching (keyboard leds do switch and > > > KDB works). > > > > > > 6.0's GENERIC does not boot to single user with > > > debug.acpi.disabled="pci_link", fatal trap 12 occures: page fault while > > > in kernel mode, > > > fault virtual address 0x0, supervisor read, page not present > > > in acpi_pci_link_lookup+0x26. > > > > I think I know what this is and this patch probably fixes the panic in > > the case that you use 'debug.acpi.disabled="pci_link"' > > > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_pci_link.c > > 2005/11/23 16:40:40 +++ > > //depot/user/jhb/acpipci/dev/acpica/acpi_pci_link.c 2005/12/02 22:28:08 > > @@ -1011,6 +1011,9 @@ > > { > > struct link *link; > > > > + if (acpi_disabled("pci_link")) > > + return (PCI_INVALID_IRQ); > > + > > ACPI_SERIAL_BEGIN(pci_link); > > link = acpi_pci_link_lookup(dev, index); > > if (link == NULL) > > I'll try this patch a bit later. > > > How does the 6.0 install CD do on your machine both with ACPI enabled and > > disabled? > > I've just installed 6.0-RELEASE again. > I booted it using [default] option (e.g. with ACPI enabled) > and installation ran smoothly. However, I could not extract > /usr/ports/distfiles/gettext-0.14.5.tar.gz, /usr/ports is mounted > from 4.11 installation. All disk activity stopped and kernel > repeatedly wrote something about "DANGER Will Robinson !!", > I think it was from /usr/src/sys/dev/ata/ata-queue.c > > I rebooted with ACPI disabled and the problem disappeared. > Now I'm going to test 'debug.acpi.disabled="pci_link"' case. Well, ACPI is probably not going to be all that happy with pci_link disabled as your machine will no longer be able to route interrupts. Are any IRQs different in the non-ACPI vs ACPI dmesgs? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Mon Dec 5 21:23:59 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66B9F16A420 for ; Mon, 5 Dec 2005 21:23:59 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66A7043D62 for ; Mon, 5 Dec 2005 21:23:58 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3208975 for multiple; Mon, 05 Dec 2005 16:21:56 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB5LNZPw041669; Mon, 5 Dec 2005 16:23:45 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Eugene Grosbein Date: Mon, 5 Dec 2005 15:25:09 -0500 User-Agent: KMail/1.8.2 References: <20050513140240.GA25774@svzserv.kemerovo.su> <200512021732.15866.jhb@freebsd.org> <20051205192257.GC75425@svzserv.kemerovo.su> In-Reply-To: <20051205192257.GC75425@svzserv.kemerovo.su> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512051525.10549.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-acpi@freebsd.org Subject: Re: 5.4: pci_link problem on 440BX X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 21:23:59 -0000 On Monday 05 December 2005 02:22 pm, Eugene Grosbein wrote: > > > 6.0's GENERIC does not boot to single user with > > > debug.acpi.disabled="pci_link", fatal trap 12 occures: page fault while > > > in kernel mode, > > > fault virtual address 0x0, supervisor read, page not present > > > in acpi_pci_link_lookup+0x26. > > > > I think I know what this is and this patch probably fixes the panic in > > the case that you use 'debug.acpi.disabled="pci_link"' > > > > --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_pci_link.c > > 2005/11/23 16:40:40 +++ > > //depot/user/jhb/acpipci/dev/acpica/acpi_pci_link.c 2005/12/02 22:28:08 > > @@ -1011,6 +1011,9 @@ > > { > > struct link *link; > > > > + if (acpi_disabled("pci_link")) > > + return (PCI_INVALID_IRQ); > > + > > ACPI_SERIAL_BEGIN(pci_link); > > link = acpi_pci_link_lookup(dev, index); > > if (link == NULL) > > 6.0-RELEASE boots with this patch, ACPI enabled > and debug.acpi.disabled="pci_link", make buildworld started > but several minutes later kernel started to write to console: So it's not pci_link that's your problem, but something else ACPI triggers in ata(4). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 6 04:00:34 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91C5E16A41F; Tue, 6 Dec 2005 04:00:34 +0000 (GMT) (envelope-from Robert.Faulds@voxify.com) Received: from mail.voxify.com (65-123-2-7.dia.cust.qwest.net [65.123.2.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C79B143D7D; Tue, 6 Dec 2005 04:00:22 +0000 (GMT) (envelope-from Robert.Faulds@voxify.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Dec 2005 20:00:21 -0800 Message-ID: <331CA3AB8A236A488C92DEC289C7D04D016423FF@Deliverance.voxify.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) Thread-Index: AcX5zUn0Be1vtP4KQqmW5PWm22xO/gAOiQoQ From: "Robert Faulds" To: "John Baldwin" Cc: freebsd-acpi@freebsd.org Subject: RE: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 04:00:34 -0000 What I did for these tests:=20 installed 6.0-RELEASE/i386 (booted with with apic disabled) cd /usr/src; make kernel KERNCONF=3DSMP connect a serial console reboot at the boot menu I hit 6 OK set console=3Dcomconsole Then disable apic: The dmesg is in http://xocolatl.com/rfaulds/freebsd-acpi/test2-SMP-dmesg-apic-disabled This boots ok. I repeat the same procedure but this time I disable acpi: http://xocolatl.com/rfaulds/freebsd-acpi/test2-SMP-dmesg-acpi-disabled=20 This won't boot, but I left it for about 20 minutes and it printed the message that it had attached pass0 and da0. After an hour or so, it was still sitting complaining that "mpt1: Timedout requests already complete. Interrupts may not be functioning." I repeated these steps with an Adaptec 2130SLP controller and I get the same behavior. I also discovered the error I made originally WRT disabling APIC along with ACPI. Choosing option 2 from the boot menu (or setting hint.acpi.0.disabled=3D1 at the loader prompt) of amd64 6.0-REL also disables APIC. I do not know why but it turned out to be a feature in my case. Suggestions? TIA, Robert -----Original Message----- From: John Baldwin [mailto:jhb@freebsd.org]=20 Sent: Monday, December 05, 2005 10:28 AM To: Robert Faulds Cc: freebsd-acpi@freebsd.org Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) On Friday 02 December 2005 06:20 pm, Robert Faulds wrote: > No love from SMP either. It still only boots with apic disabled. > I put up the mptable, and a few other files at > http://xocolatl.com/rfaulds/freebsd-acpi/ > I've been stepping through the BIOS but there is no options for forcing > the mp spec. > Interestingly, I have disabled HyperThreading in the BIOS and yet the > SMP kernel still detects it. The BIOS toggle just changes the HT CPUs to be listed as disabled in the MADT=20 table ACPI uses. The 'Hyperthreading' printf in the dmesg is based on=20 reading the registers from the CPU and is output even in a UP kernel. Your=20 MP table looks ok as well, so I'm not sure why a dmesg with no ACPI is not=20 finding your CPUs. How did you disable ACPI, did you boot using safe mode? =20 If so, try breaking into the loader and just disable ACPI via set hint.acpi.0.disabled=3D1 Safe mode disables SMP support as well as ACPI. --=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 6 09:08:17 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E62F216A449; Tue, 6 Dec 2005 09:08:17 +0000 (GMT) (envelope-from njl@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B95E43D5C; Tue, 6 Dec 2005 09:08:17 +0000 (GMT) (envelope-from njl@FreeBSD.org) Received: from freefall.freebsd.org (njl@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB698H1k030453; Tue, 6 Dec 2005 09:08:17 GMT (envelope-from njl@freefall.freebsd.org) Received: (from njl@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB698F1T030449; Tue, 6 Dec 2005 09:08:15 GMT (envelope-from njl) Date: Tue, 6 Dec 2005 09:08:15 GMT From: Nate Lawson Message-Id: <200512060908.jB698F1T030449@freefall.freebsd.org> To: pldrouin@pldrouin.net, njl@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: i386/89376: cmbat related ACPI change between 6.0-release and Nov 10th -stable sources is making Dell laptops to hang X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 09:08:18 -0000 Synopsis: cmbat related ACPI change between 6.0-release and Nov 10th -stable sources is making Dell laptops to hang State-Changed-From-To: open->closed State-Changed-By: njl State-Changed-When: Tue Dec 6 09:07:28 GMT 2005 State-Changed-Why: Committed a fix to current and MFCd right around the time this bug was submitted. The _BIF method was too heavyweight on some systems so I switched it to only run from the Notify handler. http://www.freebsd.org/cgi/query-pr.cgi?pr=89376 From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 6 09:10:26 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C9C216A41F; Tue, 6 Dec 2005 09:10:26 +0000 (GMT) (envelope-from njl@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1787543D70; Tue, 6 Dec 2005 09:10:24 +0000 (GMT) (envelope-from njl@FreeBSD.org) Received: from freefall.freebsd.org (njl@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB69ANS1030670; Tue, 6 Dec 2005 09:10:23 GMT (envelope-from njl@freefall.freebsd.org) Received: (from njl@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB69ANi3030666; Tue, 6 Dec 2005 09:10:23 GMT (envelope-from njl) Date: Tue, 6 Dec 2005 09:10:23 GMT From: Nate Lawson Message-Id: <200512060910.jB69ANi3030666@freefall.freebsd.org> To: marcus@freebsd.org, njl@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: kern/74215: [request] add ACPI headers to /usr/include X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 09:10:26 -0000 Synopsis: [request] add ACPI headers to /usr/include State-Changed-From-To: open->closed State-Changed-By: njl State-Changed-When: Tue Dec 6 09:10:08 GMT 2005 State-Changed-Why: This was done a while ago. We install just acpiio.h http://www.freebsd.org/cgi/query-pr.cgi?pr=74215 From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 6 09:12:55 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AF6C16A422; Tue, 6 Dec 2005 09:12:55 +0000 (GMT) (envelope-from njl@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E25D43D66; Tue, 6 Dec 2005 09:12:47 +0000 (GMT) (envelope-from njl@FreeBSD.org) Received: from freefall.freebsd.org (njl@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB69Cloe030845; Tue, 6 Dec 2005 09:12:47 GMT (envelope-from njl@freefall.freebsd.org) Received: (from njl@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB69Clx3030841; Tue, 6 Dec 2005 09:12:47 GMT (envelope-from njl) Date: Tue, 6 Dec 2005 09:12:47 GMT From: Nate Lawson Message-Id: <200512060912.jB69Clx3030841@freefall.freebsd.org> To: aurelien.nephtali@wanadoo.fr, njl@FreeBSD.org, freebsd-acpi@FreeBSD.org Cc: Subject: Re: kern/74030: Unplugging AC causes battery % to stay locked at 98% X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 09:12:55 -0000 Synopsis: Unplugging AC causes battery % to stay locked at 98% State-Changed-From-To: open->feedback State-Changed-By: njl State-Changed-When: Tue Dec 6 09:11:08 GMT 2005 State-Changed-Why: Can you report any error messages that occur around the time the battery status gets stuck? Also, please send a full dmesg and a URL to your ASL file (acpidump -t -d | gzip -c > Presario_2157EA.asl.gz) http://www.freebsd.org/cgi/query-pr.cgi?pr=74030 From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 6 21:49:23 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DABD16A422 for ; Tue, 6 Dec 2005 21:49:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 860C443D46 for ; Tue, 6 Dec 2005 21:49:07 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3275220 for multiple; Tue, 06 Dec 2005 16:49:15 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB6Ln0Ut051148; Tue, 6 Dec 2005 16:49:01 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Robert Faulds" Date: Tue, 6 Dec 2005 15:19:36 -0500 User-Agent: KMail/1.8.2 References: <331CA3AB8A236A488C92DEC289C7D04D016423FF@Deliverance.voxify.com> In-Reply-To: <331CA3AB8A236A488C92DEC289C7D04D016423FF@Deliverance.voxify.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512061519.36848.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-acpi@freebsd.org Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 21:49:23 -0000 On Monday 05 December 2005 11:00 pm, Robert Faulds wrote: > What I did for these tests: > > installed 6.0-RELEASE/i386 (booted with with apic disabled) > cd /usr/src; make kernel KERNCONF=SMP > connect a serial console > reboot > at the boot menu I hit 6 > OK set console=comconsole > > Then disable apic: > The dmesg is in > http://xocolatl.com/rfaulds/freebsd-acpi/test2-SMP-dmesg-apic-disabled > This boots ok. > > I repeat the same procedure but this time I disable acpi: > http://xocolatl.com/rfaulds/freebsd-acpi/test2-SMP-dmesg-acpi-disabled > > This won't boot, but I left it for about 20 minutes and it printed the > message that it had attached pass0 and da0. After an hour or so, it was > still sitting complaining that "mpt1: Timedout requests already > complete. Interrupts may not be functioning." > > I repeated these steps with an Adaptec 2130SLP controller and I get the > same behavior. > > I also discovered the error I made originally WRT disabling APIC along > with ACPI. Choosing option 2 from the boot menu (or setting > hint.acpi.0.disabled=1 at the loader prompt) of amd64 6.0-REL also > disables APIC. I do not know why but it turned out to be a feature in my > case. Well, option 2 does disable APIC. The acpi hint alone does not. So, it seems that you have problems if you use APIC, and don't have problems if you disable APIC, and ACPI has no real bearing. It sounds like perhaps your BIOS is not giving us the right information about how the interrupts are connected. Have you tried plugging the devices into mpt0 rather than mpt1 btw? As it is, you can try to override your BIOS to set the IRQ for mpt1 manually to try to figure out what IRQ it is really routed to. (If there is a BIOS update that might also fix this problem.) I'd try IRQs 24-47 (on your second ioapic) first. You can try an IRQ by setting this in the loader before boot (this would use IRQ 24 for mpt1): hw.pci3.3.INTB.irq=24 -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 6 22:39:23 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1634416A41F; Tue, 6 Dec 2005 22:39:23 +0000 (GMT) (envelope-from Robert.Faulds@voxify.com) Received: from mail.voxify.com (65-123-2-7.dia.cust.qwest.net [65.123.2.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 046D843D7B; Tue, 6 Dec 2005 22:38:39 +0000 (GMT) (envelope-from Robert.Faulds@voxify.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Tue, 6 Dec 2005 14:38:31 -0800 Message-ID: <331CA3AB8A236A488C92DEC289C7D04D016425A0@Deliverance.voxify.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) Thread-Index: AcX6ruBRHFhQ1MR7Qiaghmjp8+hyHAABRdIw From: "Robert Faulds" To: "John Baldwin" Cc: freebsd-acpi@freebsd.org Subject: RE: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 22:39:23 -0000 > From: John Baldwin [mailto:jhb@freebsd.org] > Sent: Tuesday, December 06, 2005 12:20 PM > To: Robert Faulds > Cc: freebsd-acpi@freebsd.org > Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) > > > Well, option 2 does disable APIC. The acpi hint alone does not. So, it seems =20 > that you have problems if you use APIC, and don't have problems if you > disable APIC, and ACPI has no real bearing. It sounds like perhaps your BIOS > is not giving us the right information about how the interrupts are=20 > connected. Have you tried plugging the devices into mpt0 rather than mpt1 > btw? As it is, you can try to override your BIOS to set the IRQ for mpt1=20 > manually to try to figure out what IRQ it is really routed to. (If there is > a BIOS update that might also fix this problem.) I'd try IRQs 24-47 (on your > second ioapic) first. You can try an IRQ by setting this in the loader > before boot (this would use IRQ 24 for mpt1): >=20 > hw.pci3.3.INTB.irq=3D24 > Thanks. I had started doing that with no luck. Unfortunately, I'm at the latest BIOS Tyan offers and it has no provision for forcing interrupts. I had moved the disks to channel 2 because I had an older CDROM on the first (external connector) and thought it might be a conflict (SCSI3 vs SCSI1). No luck there either. At this point I believe the most efficient use of my time will be to ship these all back and get them replaced with something a bit more compliant. Thanks for all the help and advice, Robert =20 From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 6 23:10:08 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D039316A41F; Tue, 6 Dec 2005 23:10:08 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 561FF43D49; Tue, 6 Dec 2005 23:10:08 +0000 (GMT) (envelope-from nate@root.org) Received: from [172.16.0.224] (fi01-84CBdd.tokyo.flets.isao.net [211.132.203.221]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jB6NA9du003591 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Dec 2005 15:10:11 -0800 Message-ID: <43961A47.6020007@root.org> Date: Wed, 07 Dec 2005 08:09:59 +0900 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Faulds References: <331CA3AB8A236A488C92DEC289C7D04D016425A0@Deliverance.voxify.com> In-Reply-To: <331CA3AB8A236A488C92DEC289C7D04D016425A0@Deliverance.voxify.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 23:10:08 -0000 Robert Faulds wrote: >>From: John Baldwin [mailto:jhb@freebsd.org] >>Sent: Tuesday, December 06, 2005 12:20 PM >>To: Robert Faulds >>Cc: freebsd-acpi@freebsd.org >>Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) >> >> >>Well, option 2 does disable APIC. The acpi hint alone does not. So, > > it seems > > >>that you have problems if you use APIC, and don't have problems if you > > >>disable APIC, and ACPI has no real bearing. It sounds like perhaps > > your BIOS > >>is not giving us the right information about how the interrupts are >>connected. Have you tried plugging the devices into mpt0 rather than > > mpt1 > >>btw? As it is, you can try to override your BIOS to set the IRQ for > > mpt1 > >>manually to try to figure out what IRQ it is really routed to. (If > > there is > >>a BIOS update that might also fix this problem.) I'd try IRQs 24-47 > > (on your > >>second ioapic) first. You can try an IRQ by setting this in the > > loader > >>before boot (this would use IRQ 24 for mpt1): >> >>hw.pci3.3.INTB.irq=24 >> > > > > Thanks. I had started doing that with no luck. Unfortunately, I'm at the > latest BIOS Tyan offers and it has no provision for forcing interrupts. > I had moved the disks to channel 2 because I had an older CDROM on the > first (external connector) and thought it might be a conflict (SCSI3 vs > SCSI1). No luck there either. > > At this point I believe the most efficient use of my time will be to > ship these all back and get them replaced with something a bit more > compliant. Wait, before you do that, try setting the hint John suggested or moving the drives to mpt0. We need to work around this at least for other users. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 7 00:16:13 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3290F16A41F; Wed, 7 Dec 2005 00:16:13 +0000 (GMT) (envelope-from Robert.Faulds@voxify.com) Received: from mail.voxify.com (65-123-2-7.dia.cust.qwest.net [65.123.2.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAE6743D64; Wed, 7 Dec 2005 00:16:11 +0000 (GMT) (envelope-from Robert.Faulds@voxify.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Tue, 6 Dec 2005 16:16:10 -0800 Message-ID: <331CA3AB8A236A488C92DEC289C7D04D016425D7@Deliverance.voxify.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) Thread-Index: AcX6ujRtmlDIgQmWTXKfMUjds+tVHwAB0ykg From: "Robert Faulds" To: "Nate Lawson" Cc: freebsd-acpi@freebsd.org Subject: RE: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 00:16:13 -0000 -----Original Message----- From: Nate Lawson [mailto:nate@root.org]=20 Sent: Tuesday, December 06, 2005 3:10 PM To: Robert Faulds Cc: John Baldwin; freebsd-acpi@freebsd.org Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) Robert Faulds wrote: >>From: John Baldwin [mailto:jhb@freebsd.org] >>Sent: Tuesday, December 06, 2005 12:20 PM >>To: Robert Faulds >>Cc: freebsd-acpi@freebsd.org >>Subject: Re: Tyan Tiget S5351-i7322 hangs with ACPI (AMD64 or i386) >> >> >>Well, option 2 does disable APIC. The acpi hint alone does not. So, >=20 > it seems > =20 >=20 >>that you have problems if you use APIC, and don't have problems if you >=20 >=20 >>disable APIC, and ACPI has no real bearing. It sounds like perhaps >=20 > your BIOS >=20 >>is not giving us the right information about how the interrupts are=20 >>connected. Have you tried plugging the devices into mpt0 rather than >=20 > mpt1 >=20 >>btw? As it is, you can try to override your BIOS to set the IRQ for >=20 > mpt1=20 >=20 >>manually to try to figure out what IRQ it is really routed to. (If >=20 > there is >=20 >>a BIOS update that might also fix this problem.) I'd try IRQs 24-47 >=20 > (on your >=20 >>second ioapic) first. You can try an IRQ by setting this in the >=20 > loader >=20 >>before boot (this would use IRQ 24 for mpt1): >> >>hw.pci3.3.INTB.irq=3D24 >> >=20 >=20 >=20 > Thanks. I had started doing that with no luck. Unfortunately, I'm at the > latest BIOS Tyan offers and it has no provision for forcing interrupts. > I had moved the disks to channel 2 because I had an older CDROM on the > first (external connector) and thought it might be a conflict (SCSI3 vs > SCSI1). No luck there either. >=20 > At this point I believe the most efficient use of my time will be to > ship these all back and get them replaced with something a bit more > compliant. > Wait, before you do that, try setting the hint John suggested or moving=20 > the drives to mpt0. We need to work around this at least for other users. Sure... I did try that although not for the entire range. I got too bored. This thing takes several minutes to POST and boot and I'm crunched with other work. I tried stepping through IRQ's from 24-30, and from 9-15, with drives on both channels and with no drives connected, with no luck. I tried setting INTA and INTB to different values in that range based off the earlier probes and successes, and even a few of the failures, as reported at the logs I posted earlier. http://xocolatl.com/rfaulds/freebsd-acpi/ I'm willing to try anything you want to test. I'll hang on to one or two of these boxes to use them to debug this. The other 6 need to go back to be replaced so I can put something into service doing real work soon. Let me know how I can help, Robert From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 7 14:00:17 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35A8716A427 for ; Wed, 7 Dec 2005 14:00:05 +0000 (GMT) (envelope-from skripachov@mail.ru) Received: from mx6.mail.ru (mx6.mail.ru [194.67.23.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9349043D46 for ; Wed, 7 Dec 2005 14:00:04 +0000 (GMT) (envelope-from skripachov@mail.ru) Received: from [213.183.242.226] (port=18407 helo=satellite.osatec-msk.ru) by mx6.mail.ru with esmtp id 1Ejzpx-0005Hl-00 for freebsd-acpi@freebsd.org; Wed, 07 Dec 2005 17:00:01 +0300 From: Yuri Skripachov To: freebsd-acpi@freebsd.org Date: Wed, 7 Dec 2005 16:59:57 +0300 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512071659.58560.skripachov@mail.ru> Subject: Toshiba Satellite P10 + wrong battery state reported by ACPIIO_BATT_GET_BATTINFO. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 14:00:17 -0000 Hi All, Checking _BST results in the acpi_battery_bst_valid() (acpi_battery.c) always brings about 'not present' state if I have plugged AC adapter as result of comparing battery state with ACPI_BATT_STAT_MAX (because 1.90 and 1.50 bioses use bit7 as a 'AC plugged' sign). Is this behaviour a ACPI BIOS bug? Could ACPI BIOS conforming to the specification report battery state more than ACPI_BATT_STAT_MAX (==0x7 now)? Currently I've wrapped _BST method by masking returned state with 0x7f. The same is possible for the acpi_battery_bst_valid() function in dev/acpica/acpi_battery.c Which way is right? -- Best regards, Yuri Skripachov "The faster I go, the behinder I get." -- Lewis Carroll -- From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 8 07:02:31 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A482216A41F for ; Thu, 8 Dec 2005 07:02:31 +0000 (GMT) (envelope-from skripachov@mail.ru) Received: from mx4.mail.ru (fallback.mail.ru [194.67.57.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 448F643D83 for ; Thu, 8 Dec 2005 07:02:22 +0000 (GMT) (envelope-from skripachov@mail.ru) Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.149]) by mx4.mail.ru (mPOP.Fallback_MX) with ESMTP id 087F047B9B2 for ; Thu, 8 Dec 2005 10:02:18 +0300 (MSK) Received: from [213.183.242.226] (port=53892 helo=satellite.osatec-msk.ru) by mx3.mail.ru with esmtp id 1EkFf5-000O6R-00 for freebsd-acpi@freebsd.org; Thu, 08 Dec 2005 09:53:51 +0300 From: Yuri Skripachov To: freebsd-acpi@freebsd.org Date: Thu, 8 Dec 2005 09:53:49 +0300 User-Agent: KMail/1.8.3 References: <200512071659.58560.skripachov@mail.ru> In-Reply-To: <200512071659.58560.skripachov@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512080953.50224.skripachov@mail.ru> Subject: Re: Toshiba Satellite P10 + wrong battery state reported by ACPIIO_BATT_GET_BATTINFO. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 07:02:31 -0000 > Currently I've wrapped _BST method by masking returned state with > 0x7f. The same is possible for the acpi_battery_bst_valid() > function in dev/acpica/acpi_battery.c > Which way is right? ACPI spec v3.0 mentions of just bits 0, 1 and 2 in _BST battery state field so I think the best way is to mask the rest bits in the acpi_battery.c before comparing with ACPI_BATT_STAT_MAX. PS: Besides bit7 toshiba uses bit3 in battery state as a sign of 'warning' battery level :) Is special acpi_toshiba_battery need? -- Best regards, Yuri Skripachov mailto:skripachov@mail.ru "The faster I go, the behinder I get." -- Lewis Carroll -- From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 8 07:37:28 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB19D16A42B for ; Thu, 8 Dec 2005 07:37:28 +0000 (GMT) (envelope-from skripachov@mail.ru) Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40F2F43D9C for ; Thu, 8 Dec 2005 07:37:10 +0000 (GMT) (envelope-from skripachov@mail.ru) Received: from [213.183.242.226] (port=39876 helo=satellite.osatec-msk.ru) by mx3.mail.ru with esmtp id 1EkGKs-000O11-00 for freebsd-acpi@freebsd.org; Thu, 08 Dec 2005 10:37:02 +0300 From: Yuri Skripachov To: freebsd-acpi@freebsd.org Date: Thu, 8 Dec 2005 10:37:02 +0300 User-Agent: KMail/1.8.3 References: <200512071659.58560.skripachov@mail.ru> <200512080953.50224.skripachov@mail.ru> In-Reply-To: <200512080953.50224.skripachov@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512081037.02878.skripachov@mail.ru> Subject: Re: Toshiba Satellite P10 + wrong battery state reported by ACPIIO_BATT_GET_BATTINFO. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 07:37:29 -0000 > acpi_battery.c before comparing with ACPI_BATT_STAT_MAX. Or even better remove this comparing at all? -- Best regards, Yuri Skripachov mailto:skripachov@mail.ru "The faster I go, the behinder I get." -- Lewis Carroll -- From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 8 11:37:41 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1FDC16A41F for ; Thu, 8 Dec 2005 11:37:41 +0000 (GMT) (envelope-from skripachov@mail.ru) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE6A143D88 for ; Thu, 8 Dec 2005 11:37:40 +0000 (GMT) (envelope-from skripachov@mail.ru) Received: from [213.183.242.226] (port=49972 helo=satellite.osatec-msk.ru) by mx2.mail.ru with esmtp id 1EkK5i-0009r2-00 for freebsd-acpi@freebsd.org; Thu, 08 Dec 2005 14:37:38 +0300 From: Yuri Skripachov To: freebsd-acpi@freebsd.org Date: Thu, 8 Dec 2005 14:37:35 +0300 User-Agent: KMail/1.8.3 References: <200512071659.58560.skripachov@mail.ru> In-Reply-To: <200512071659.58560.skripachov@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512081437.36332.skripachov@mail.ru> Subject: Re: Toshiba Satellite P10 + wrong battery state reported by ACPIIO_BATT_GET_BATTINFO. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 11:37:41 -0000 > Which way is right? It seems to me that right way is to define ACPI_BATT_STAT_NOT_PRESENT as (ACPI_BATT_STAT_CHARGING | ACPI_BATT_STAT_DISCHARG) because these bits are mutually exclusive and must not both be set at the same time. Even in critical state. And then change the acpi_battery_bst_valid() in dev/acpica/acpi_battery.c. -- cut /* Check _BST results for validity. */ int acpi_battery_bst_valid(struct acpi_bst *bst) { if ((bst->state & ACPI_BATT_STAT_NOT_PRESENT) == ACPI_BATT_STAT_NOT_PRESENT || bst->cap == 0xffffffff || bst->volt == 0xffffffff) return (FALSE); else return (TRUE); } -- cut -- Best regards, Yuri Skripachov mailto:skripachov@mail.ru "The faster I go, the behinder I get." -- Lewis Carroll -- From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 9 12:38:04 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D29E416A424 for ; Fri, 9 Dec 2005 12:38:04 +0000 (GMT) (envelope-from huge@nm.ru) Received: from flock1.newmail.ru (flock1.newmail.ru [212.48.140.157]) by mx1.FreeBSD.org (Postfix) with SMTP id EF89143DBB for ; Fri, 9 Dec 2005 12:37:23 +0000 (GMT) (envelope-from huge@nm.ru) Received: (qmail 14272 invoked from network); 9 Dec 2005 12:19:23 -0000 Received: from unknown (HELO ?192.168.0.100?) (huge@nm.ru@212.45.14.9) by smtpd.newmail.ru with SMTP; 9 Dec 2005 12:19:23 -0000 Date: Fri, 9 Dec 2005 15:38:53 +0300 From: huge@nm.ru X-Mailer: The Bat! (v2.10.03) Personal X-Priority: 3 (Normal) Message-ID: <1287807936.20051209153853@nm.ru> To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: toshiba portege r100 doesn't resume from S3 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: huge@nm.ru List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 12:38:05 -0000 Hi! I have a problem. Would you help me? My Toshiba Portege R100 doesn't resume from S3. There is a problem with disk access after resume. It looks the same if I did "atacontrol detach ata0". And that's interesting: ad0 is detached but error messages are successfully logged. [from dmesg] .......... acpi_button0: run_prep cleaned up for \\_SB_.PWRB acpi_lid0: run_prep cleaned up for \\_SB_.LID_ acpi: suspend request ignored (not ready yet) cbb0: [MPSAFE] ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=80 ostat1=80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 ata0: stat0=0x50 err=0x00 lsb=0xfe msb=0x3f ata0: stat1=0x00 err=0x00 lsb=0xfe msb=0x3f ata0: reset tp2 stat0=50 stat1=00 devices=0x0 --> ad0: detached ata0: reinit done .. ata1: reiniting channel .. ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: reinit done .. atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) battery0: battery initialization start battery0: battery initialization done, tried 1 times battery1: battery initialization start --> g_vfs_done():ad0s1a[READ(offset=277413888, length=2560)]error = 6 vnode_pager_getpages: I/O read error --> g_vfs_done():ad0s1a[READ(offset=268517376, length=12800)]error = 6 vnode_pager_getpages: I/O read error --> g_vfs_done():ad0s1e[WRITE(offset=6144000, length=2048)]error = 6 --> g_vfs_done():ad0s1e[WRITE(offset=65536, length=2048)]error = 6 panic: vinvalbuf: dirty bufs Uptime: 33m47s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. Rebooting... ......... And there is another problem. Video doesn't work after resume. With hw.acpi.reset_video=1 display is just off, with 0 it shows multicolored vertical lines. The DSDT seems to be ok since it's recompiled without errors and the same machine successfully resumes from S3 under linux. # dmesg http://media-trest.ru/r100/dmesg-v # sysctl hw.acpi http://media-trest.ru/r100/sysctl ASL http://media-trest.ru/r100/toshiba-portege-r100.asl Thanks! Alexandre Scherbanov