Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Nov 2004 14:46:14 -0500
From:      Adam K Kirchhoff <adamk@voicenet.com>
To:        Nate Lawson <nate@root.org>
Cc:        freebsd-acpi@freebsd.org
Subject:   Re: Laptop troubles...
Message-ID:  <41990786.2070604@voicenet.com>
In-Reply-To: <4198EDCD.8070306@root.org>
References:  <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> <41913F15.9060701@root.org> <419145A7.3000406@voicenet.com> <41914DCC.8000100@root.org> <20041112181038.GK31422@poupinou.org> <4198EDCD.8070306@root.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------050701000705000901090907
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Nate Lawson wrote:

> Bruno Ducrot wrote:
>
>> On Tue, Nov 09, 2004 at 03:07:56PM -0800, Nate Lawson wrote:
>>
>>> That's fine, try cx_lowest=C2.  If that works, a workaround is to 
>>> set cx_performance_state=C2 and cx_economy_state=C2 in /etc/rc.conf 
>>> (or something like that, see /etc/defaults/rc.conf for the right 
>>> variable names).  Please send me the output of acpidump -t -d > 
>>> adam.asl separately as an attachment.  I think I will have enough 
>>> with that to debug why C3 is hanging your system.  I'm pretty sure 
>>> the problem area of the commit is in enabling C3 for systems that 
>>> don't have bus master control.
>>>
>>
>> C3 support with a PIIX4 southbridge is buggy as hell and
>> should be disabled no matter what.
>
>
> Right, thanks for the reminder.  I actually have quirk code to do this 
> but it wasn't enabled since I wanted to find an actual test case 
> before turning it on.  Adam, please recompile with the attached 
> patch.  Also, send me pciconf -l.  The patch will disable C3 and you 
> should only get C1/C2 if your system is truly a PIIX4.
>
> Thanks,
> Nate


With that patch, I still have the option of setting C3.  And, if I do, I 
get the lockups.  I'm attaching the output of pciconf -l.

Adam


--------------050701000705000901090907
Content-Type: text/plain;
 name="pciconf.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="pciconf.txt"

agp0@pci0:0:0:	class=0x060000 card=0x00000000 chip=0x71908086 rev=0x03 hdr=0x00
pcib1@pci0:1:0:	class=0x060400 card=0x00000000 chip=0x71918086 rev=0x03 hdr=0x01
isab0@pci0:7:0:	class=0x068000 card=0x00000000 chip=0x71108086 rev=0x02 hdr=0x00
atapci0@pci0:7:1:	class=0x010180 card=0x00000000 chip=0x71118086 rev=0x01 hdr=0x00
uhci0@pci0:7:2:	class=0x0c0300 card=0x00000000 chip=0x71128086 rev=0x01 hdr=0x00
none0@pci0:7:3:	class=0x068000 card=0x00000000 chip=0x71138086 rev=0x03 hdr=0x00
cbb0@pci0:10:0:	class=0x060700 card=0x0010103c chip=0xac51104c rev=0x00 hdr=0x02
cbb1@pci0:10:1:	class=0x060700 card=0x0010103c chip=0xac51104c rev=0x00 hdr=0x02
none1@pci0:11:0:	class=0x020000 card=0x625610b7 chip=0x605510b7 rev=0x10 hdr=0x00
none2@pci0:11:1:	class=0x078000 card=0x615810b7 chip=0x100710b7 rev=0x10 hdr=0x00
pcm0@pci0:13:0:	class=0x040100 card=0x0010103c chip=0x1998125d rev=0x00 hdr=0x00
none3@pci1:0:0:	class=0x030000 card=0x0010103c chip=0x4c4d1002 rev=0x64 hdr=0x00

--------------050701000705000901090907--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41990786.2070604>