From owner-freebsd-acpi@FreeBSD.ORG Sun Apr 25 09:41:14 2004 Return-Path: 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 4E7DE16A4CE for ; Sun, 25 Apr 2004 09:41:14 -0700 (PDT) Received: from snipers.mine.nu (YahooBB219008246026.bbtec.net [219.8.246.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2318043D1D for ; Sun, 25 Apr 2004 09:41:14 -0700 (PDT) (envelope-from kochi@netbsd.org) Received: from localhost (localhost [127.0.0.1]) by snipers.mine.nu (Postfix) with ESMTP id D968878724; Mon, 26 Apr 2004 01:41:12 +0900 (JST) Date: Mon, 26 Apr 2004 01:41:12 +0900 (JST) Message-Id: <20040426.014112.74748210.kochi@netbsd.org> To: nate@root.org From: Takayoshi Kochi In-Reply-To: <20040421194653.F40302@root.org> References: <20040421194653.F40302@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: kanaoka@netbsd.org Subject: Re: ACPI SCI flags X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Apr 2004 16:41:14 -0000 Hi, From: Nate Lawson Subject: Re: ACPI SCI flags Date: Wed, 21 Apr 2004 19:48:52 -0700 (PDT) > On Fri, 9 Apr 2004, Brown, Len wrote: > > Nate, > > > > I think we finally got the vague part of the ACPI spec > > regarding SCI polarity/trigger cleared up. In Linux > > as of 2.4.26 and 2.6.5 we now do this: > > > > PIC mode: > > force level/low via ELCR always. > > Did you find that made a difference on some systems? If so, which ones? > The opinion here was that ELCR is probably EISA-only. Kanaoka-san reported that if SCI is not set level-trigger, the SCI doesn't work properly on his laptop. It (Libretto L3) has ALi chipsets (1543 south bridge). When I tested on my laptop (ThinkPad X31, Intel ICH4), it seemed that the setting of ELCR didn't make any difference, though. --- Takayoshi Kochi From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 26 04:40:01 2004 Return-Path: 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 962EC16A4CE for ; Mon, 26 Apr 2004 04:40:01 -0700 (PDT) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8C2F43D53 for ; Mon, 26 Apr 2004 04:40:00 -0700 (PDT) (envelope-from bsword@mail.ru) Received: from [82.140.65.90] (port=49190 helo=fort) by mx2.mail.ru with esmtp id 1BI4Sr-000Ahj-00 for freebsd-acpi@FreeBSD.org; Mon, 26 Apr 2004 15:39:57 +0400 From: Ed Korotkov To: freebsd-acpi@FreeBSD.org Date: Mon, 26 Apr 2004 15:40:02 +0400 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200404261540.02871.bsword@mail.ru> X-Spam: Not detected Subject: ACPI & FDD X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 11:40:01 -0000 OK. No attachments. #boot -v Preloaded elf module "/boot/kernel/acpi.ko" at 0xc08561cc. Calibrating clock(s) ... i8254 clock: 1193192 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1999780952 Hz CPU: Intel(R) Celeron(R) CPU 2.00GHz (1999.78-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbffreal memory = 259260416 (247 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c26000 - 0x000000000f2c0fff, 241807360 bytes (59035 pages) avail memory = 242184192 (230 MB) bios32: Found BIOS32 Service Directory header at 0xc00f0000 bios32: Entry = 0xf0010 (c00f0010) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0x31 pnpbios: Found PnP BIOS data at 0xc00f53e0 pnpbios: Entry = f0000:5a1a Rev = 1.0 Other BIOS signatures found: null: random: mem: Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x80000094 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=25608086) pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00f52d0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 29 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 B 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 D 0x6b 3 4 5 6 7 9 10 11 12 14 15 embedded 0 31 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 31 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 1 8 A 0x68 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 2 A 0x60 3 4 5 6 7 9 10 11 12 14 15 slot 1 1 0 A 0x69 3 4 5 6 7 9 10 11 12 14 15 slot 1 1 0 B 0x6a 3 4 5 6 7 9 10 11 12 14 15 slot 1 1 0 C 0x6b 3 4 5 6 7 9 10 11 12 14 15 slot 1 1 0 D 0x68 3 4 5 6 7 9 10 11 12 14 15 slot 2 1 1 A 0x6a 3 4 5 6 7 9 10 11 12 14 15 slot 2 1 1 B 0x69 3 4 5 6 7 9 10 11 12 14 15 slot 2 1 1 C 0x68 3 4 5 6 7 9 10 11 12 14 15 slot 2 1 1 D 0x6b 3 4 5 6 7 9 10 11 12 14 15 slot 3 1 2 A 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 3 1 2 B 0x63 3 4 5 6 7 9 10 11 12 14 15 slot 3 1 2 C 0x61 3 4 5 6 7 9 10 11 12 14 15 slot 3 1 2 D 0x60 3 4 5 6 7 9 10 11 12 14 15 slot 4 1 3 A 0x63 3 4 5 6 7 9 10 11 12 14 15 slot 4 1 3 B 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 4 1 3 C 0x69 3 4 5 6 7 9 10 11 12 14 15 slot 4 1 3 D 0x6a 3 4 5 6 7 9 10 11 12 14 15 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: Power Button (fixed) ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks GOOD min = 3, max = 5, width = 2 ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks GOOD min = 3, max = 5, width = 2 ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks GOOD min = 3, max = 4, width = 1 ACPI timer looks GOOD min = 3, max = 4, width = 1 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_cpu0: port 0x530-0x537 on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_cpu1: port 0x530-0x537 on acpi0 device_probe_and_attach: acpi_cpu1 attach returned 6 pcib0: port 0xcf8-0xcff on acpi0 ---- initial configuration ------------------------ \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.0 \\_SB_.LNKD irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.1 \\_SB_.LNKC irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.2 \\_SB_.LNKH irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.3 \\_SB_.LNKC irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.31.0 \\_SB_.LNKB irq 3: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.31.1 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.1.0 \\_SB_.LNKB irq 3: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.1.1 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.2.0 ---- before setting priority for links ------------ ---- before fixup boot-disabled links ------------- ---- after fixup boot-disabled links -------------- ---- arbitrated configuration --------------------- \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.0 \\_SB_.LNKD irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.1 \\_SB_.LNKC irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.2 \\_SB_.LNKH irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.29.3 \\_SB_.LNKC irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.31.0 \\_SB_.LNKB irq 3: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.31.1 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.1.0 \\_SB_.LNKB irq 3: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.1.1 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.2.0 pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base f8000000, size 26, enabled found-> vendor=0x8086, dev=0x2560, revid=0x01 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 3, range 32, base f0000000, size 27, enabled map[14]: type 1, range 32, base ffa80000, size 19, enabled pcib0: matched entry for 0.2.INTA (source \\_SB_.LNKA) pcib0: slot 2 INTA is routed to irq 11 found-> vendor=0x8086, dev=0x2562, revid=0x01 bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 1 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000e800, size 5, enabled pcib0: matched entry for 0.29.INTA (source \\_SB_.LNKA) pcib0: slot 29 INTA is routed to irq 11 found-> vendor=0x8086, dev=0x24c2, revid=0x01 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 4, range 32, base 0000e880, size 5, enabled pcib0: matched entry for 0.29.INTB (source \\_SB_.LNKD) pcib0: slot 29 INTB is routed to irq 5 found-> vendor=0x8086, dev=0x24c4, revid=0x01 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 4, range 32, base 0000ec00, size 5, enabled pcib0: matched entry for 0.29.INTC (source \\_SB_.LNKC) pcib0: slot 29 INTC is routed to irq 9 found-> vendor=0x8086, dev=0x24c7, revid=0x01 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=9 map[10]: type 1, range 32, base ffa7fc00, size 10, enabled pcib0: matched entry for 0.29.INTD (source \\_SB_.LNKH) pcib0: slot 29 INTD is routed to irq 10 found-> vendor=0x8086, dev=0x24cd, revid=0x01 bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, 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 found-> vendor=0x8086, dev=0x244e, revid=0x81 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=0x02 (500 ns) found-> vendor=0x8086, dev=0x24c0, revid=0x01 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x010f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 4, range 32, base 00000000, size 3, enabled map[14]: type 4, range 32, base 00000000, size 2, enabled map[18]: type 4, range 32, base 00000000, size 3, enabled map[1c]: type 4, range 32, base 00000000, size 2, enabled map[20]: type 4, range 32, base 0000ffa0, size 4, enabled found-> vendor=0x8086, dev=0x24cb, revid=0x01 bus=0, slot=31, func=1 class=01-01-8a, 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=255 map[20]: type 4, range 32, base 0000e000, size 5, enabled pcib0: matched entry for 0.31.INTB (source \\_SB_.LNKB) pcib0: slot 31 INTB is routed to irq 3 found-> vendor=0x8086, dev=0x24c3, revid=0x01 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=3 map[10]: type 4, range 32, base 0000e400, size 8, enabled map[14]: type 4, range 32, base 0000e080, size 6, enabled map[18]: type 1, range 32, base ffa7f800, size 9, enabled map[1c]: type 1, range 32, base ffa7f400, size 8, enabled pcib0: matched entry for 0.31.INTB (source \\_SB_.LNKB) pcib0: slot 31 INTB is routed to irq 3 found-> vendor=0x8086, dev=0x24c5, revid=0x01 bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=3 powerspec 2 supports D0 D3 current D0 agp0: mem 0xffa80000-0xffafffff,0xf0000000-0xf7ffffff irq 11 at device 2.0 on pci0 agp0: detected 8060k stolen memory agp0: aperture size is 128M uhci0: port 0xe800-0xe81f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe880-0xe89f irq 5 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xec00-0xec1f irq 9 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib1: at device 30.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xd000-0xdfff pcib1: memory decode 0xff800000-0xff8fffff pcib1: prefetched decode 0xe6a00000-0xe6afffff ---- initial configuration ------------------------ \\_SB_.LNKE irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.8.0 \\_SB_.LNKF irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.0.0 \\_SB_.LNKG irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.0.1 \\_SB_.LNKH irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.0.2 \\_SB_.LNKE irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.0.3 \\_SB_.LNKG irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.1.0 \\_SB_.LNKF irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.1.1 \\_SB_.LNKE irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.1.2 \\_SB_.LNKH irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.1.3 \\_SB_.LNKC irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.2.0 \\_SB_.LNKD irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.2.1 \\_SB_.LNKB irq 3: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.2.2 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.2.3 \\_SB_.LNKD irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.3.0 \\_SB_.LNKC irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.3.1 \\_SB_.LNKF irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.3.2 \\_SB_.LNKG irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.3.3 ---- before setting priority for links ------------ \\_SB_.LNKF: interrupts: 3 4 5 6 7 9 10 11 12 14 15 penalty: 1960 1660 960 1660 1660 1060 960 1360 1660 10660 10660 references: 3 priority: 0 \\_SB_.LNKG: interrupts: 3 4 5 6 7 9 10 11 12 14 15 penalty: 1960 1660 960 1660 1660 1060 960 1360 1660 10660 10660 references: 3 priority: 0 ---- before fixup boot-disabled links ------------- \\_SB_.LNKF: interrupts: 3 4 5 6 7 9 10 11 12 14 15 penalty: 1960 1660 960 1660 1660 1060 960 1360 1660 10660 10660 references: 3 priority: 9343 \\_SB_.LNKG: interrupts: 3 4 5 6 7 9 10 11 12 14 15 penalty: 1960 1660 960 1660 1660 1060 960 1360 1660 10660 10660 references: 3 priority: 9343 ---- after fixup boot-disabled links -------------- ---- arbitrated configuration --------------------- \\_SB_.LNKE irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.8.0 \\_SB_.LNKF irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.0.0 \\_SB_.LNKG irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.0.1 \\_SB_.LNKH irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.0.2 \\_SB_.LNKE irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.0.3 \\_SB_.LNKG irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.1.0 \\_SB_.LNKF irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.1.1 \\_SB_.LNKE irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.1.2 \\_SB_.LNKH irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.1.3 \\_SB_.LNKC irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.2.0 \\_SB_.LNKD irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.2.1 \\_SB_.LNKB irq 3: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.2.2 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.2.3 \\_SB_.LNKD irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.3.0 \\_SB_.LNKC irq 9: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.3.1 \\_SB_.LNKF irq 10: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.3.2 \\_SB_.LNKG irq 5: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 1.3.3 pci1: on pcib1 pci1: physical bus=1 map[10]: type 1, range 32, base ff8ff000, size 12, enabled map[14]: type 4, range 32, base 0000dc00, size 6, enabled pcib1: matched entry for 1.8.INTA (source \\_SB_.LNKE) pcib1: slot 8 INTA is routed to irq 11 found-> vendor=0x8086, dev=0x1039, revid=0x81 bus=1, slot=8, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 fxp0: port 0xdc00-0xdc3f mem 0xff8ff000-0xff8fffff irq 11 at device 8.0 on pci1 pcib1: device fxp0 requested decoded memory range 0xff8ff000-0xff8fffff fxp0: using memory space register mapping fxp0: Ethernet address 00:0c:f1:7e:cd:ae fxp0: PCI IDs: 8086 1039 8086 3048 0081 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x90 err=0x90 lsb=0x90 msb=0x90 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 mask=03 stat0=50 stat1=00 devices=0x1 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: reset tp1 mask=03 ostat0=7f ostat1=50 ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-master: stat=0x7f err=0x7f lsb=0x7f msb=0x7f ata1-slave: stat=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 mask=02 stat0=ff stat1=00 devices=0x8 ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 31.3 (no driver attached) pcm0: port 0xe080-0xe0bf,0xe400-0xe4ff mem 0xffa7f400-0xffa7f4ff,0xffa7f800-0xffa7f9ff irq 3 at device 31.5 on pci0 pcm0: pcm0: Codec features headphone, 20 bit DAC, 18 bit ADC, 6 bit master volume, Realtek 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, double rate PCM, reserved 1, AMAP, reserved 4 pcm0: sndbuf_setmap 286000, 4000; 0xd6541000 -> 286000 pcm0: sndbuf_setmap 29a000, 4000; 0xd6545000 -> 29a000 acpi_button0: on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: irq maps: 0 0 0 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A unknown: not probed (disabled) ppc0: using extended I/O port range ppc0: ECP SPP SPP ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 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:0x1, flags:0x3d0000 psm0: unable to allocate IRQ psmcpnp0 irq 12 on acpi0 psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:4 psm0: syncmask:08, syncbits:08 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) acpi_cpu1: port 0x530-0x537 on acpi0 device_probe_and_attach: acpi_cpu1 attach returned 6 mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) unknown: not probed (disabled) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sio: sio0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 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 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fe0: not probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) lnc0: not probed (disabled) pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0 0 0 0 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. procfs registered linprocfs registered Timecounter "TSC" frequency 1999780952 Hz quality 800 Timecounters tick every 10.000 msec ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to deny, logging limited to 100 packets/entry by default IPv6 packet filtering initialized, logging limited to 100 packets/entry Linux ELF exec handler installed lo0: bpf attached ata1: spurious interrupt - status=0x00 error=0x01 acpi_cpu0: set speed to 100.0% acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ata0-master: setting PIO4 on Intel ICH4 chip ata0-master: setting UDMA100 on Intel ICH4 chip GEOM: create disk ad0 dp=0xc2e5c660 ad0: ATA-6 disk at ata0-master ad0: 38166MB (78165360 sectors), 77545 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 ata1-slave: pio=0x0c wdma=0x22 udma=0xffffffff cable=40pin ata1-slave: setting PIO4 on Intel ICH4 chip [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:78156162 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 40015954944 end 40015987199 GEOM: Configure ad0s1a, start 0 length 536870912 end 536870911 GEOM: Configure ad0s1b, start 536870912 length 536870912 end 1073741823 GEOM: Configure ad0s1c, start 0 length 40015954944 end 40015954943 GEOM: Configure ad0s1d, start 1073741824 length 536870912 end 1610612735 GEOM: Configure ad0s1e, start 1610612736 length 536870912 end 2147483647 GEOM: Configure ad0s1f, start 2147483648 length 37868471296 end 40015954943 acd0: CDROM drive at ata1 as slave acd0: read 8268KB/s (8268KB/s), 120KB buffer, PIO4 acd0: Reads: CDR, CDRW, CDDA stream, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc pcm0: measured ac97 link rate at 48005 Hz, will use 48000 Hz Mounting root from ufs:/dev/ad0s1a start_init: trying /sbin/init splash: image decoder found: blank_saver From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 26 05:05:40 2004 Return-Path: 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 1843D16A4CE; Mon, 26 Apr 2004 05:05:40 -0700 (PDT) Received: from gvr.gvr.org (gvr-gw.gvr.org [80.126.103.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8477243D2F; Mon, 26 Apr 2004 05:05:39 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id D9A516D; Mon, 26 Apr 2004 14:05:38 +0200 (CEST) Date: Mon, 26 Apr 2004 14:05:38 +0200 From: Guido van Rooij To: Mark Santcroos Message-ID: <20040426120538.GA78787@gvr.gvr.org> References: <20040414051207.GK58667@pcwin002.win.tue.nl> <20040413222717.O80191@root.org> <20040414.001039.116586661.imp@bsdimp.com> <20040414092553.F83452@root.org> <20040415135755.GA925@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040415135755.GA925@laptop.6bone.nl> cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: Experiences with new PCI code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 12:05:40 -0000 On Thu, Apr 15, 2004 at 03:57:55PM +0200, Mark Santcroos wrote: > On Wed, Apr 14, 2004 at 09:29:35AM -0700, Nate Lawson wrote: > > For instance, snd_ich works pretty well for me but will stop generating > > interrupts if shared with if_an on resume. But for others its sample rate > > is off after resume. Now this problem may have been fixed by Warner's > > power code so it would be a good time to test those drivers because if the > > problem is still there, it's a driver problem and there's not much more > > to be done outside the driver. > > My laptop was one of those with the snd_ich problems after S4_BIOS resume. > It was caused by bad BAR restores as the problem could be fixed by simply > setting the PCI registers as they were before suspend. SInce you earlier reported you have a Dell, could you tell me the brand of your laptop and the tool you used to create the suspend partition? I am still trying to gte info from Dell on such a tool for my Latitude D600. -Guido From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 26 05:07:06 2004 Return-Path: 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 4180E16A4CE; Mon, 26 Apr 2004 05:07:06 -0700 (PDT) Received: from xraided.net (xraided.net [66.88.26.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D31943D5C; Mon, 26 Apr 2004 05:07:06 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: by xraided.net (CommuniGate Pro PIPE 4.1.8) with PIPE id 1710975; Mon, 26 Apr 2004 05:07:06 -0700 X-PolluStop-Diagnostic: ########## X-PolluStop-Score: 1.00 X-PolluStop: Scanned with Niversoft PolluStop 2.0 public beta 7, http://www.niversoft.com/pollustop Received: from mx2.freebsd.org ([216.136.204.119] verified) by xraided.net (CommuniGate Pro SMTP 4.1.8) with SMTP id 1710974 for kyle@xraided.net; Mon, 26 Apr 2004 05:07:00 -0700 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 53B1856361; Mon, 26 Apr 2004 05:06:20 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 82D2116A4DA; Mon, 26 Apr 2004 05:06:18 -0700 (PDT) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1843D16A4CE; Mon, 26 Apr 2004 05:05:40 -0700 (PDT) Received: from gvr.gvr.org (gvr-gw.gvr.org [80.126.103.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8477243D2F; Mon, 26 Apr 2004 05:05:39 -0700 (PDT) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id D9A516D; Mon, 26 Apr 2004 14:05:38 +0200 (CEST) Date: Mon, 26 Apr 2004 14:05:38 +0200 From: Guido van Rooij To: Mark Santcroos Message-ID: <20040426120538.GA78787@gvr.gvr.org> References: <20040414051207.GK58667@pcwin002.win.tue.nl> <20040414.001039.116586661.imp@bsdimp.com> <20040415135755.GA925@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040415135755.GA925@laptop.6bone.nl> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org cc: acpi@freebsd.org cc: current@freebsd.org Subject: [SPAM] Re: Experiences with new PCI code X-BeenThere: freebsd-acpi@freebsd.org List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 12:07:06 -0000 On Thu, Apr 15, 2004 at 03:57:55PM +0200, Mark Santcroos wrote: > On Wed, Apr 14, 2004 at 09:29:35AM -0700, Nate Lawson wrote: > > For instance, snd_ich works pretty well for me but will stop generating > > interrupts if shared with if_an on resume. But for others its sample rate > > is off after resume. Now this problem may have been fixed by Warner's > > power code so it would be a good time to test those drivers because if the > > problem is still there, it's a driver problem and there's not much more > > to be done outside the driver. > > My laptop was one of those with the snd_ich problems after S4_BIOS resume. > It was caused by bad BAR restores as the problem could be fixed by simply > setting the PCI registers as they were before suspend. SInce you earlier reported you have a Dell, could you tell me the brand of your laptop and the tool you used to create the suspend partition? I am still trying to gte info from Dell on such a tool for my Latitude D600. -Guido _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 26 05:08:11 2004 Return-Path: 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 247DC16A4CE; Mon, 26 Apr 2004 05:08:11 -0700 (PDT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D8F943D48; Mon, 26 Apr 2004 05:08:10 -0700 (PDT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id 860434EF4E; Mon, 26 Apr 2004 14:08:09 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 457EE55D94; Mon, 26 Apr 2004 14:08:09 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i3QC89c4008051; Mon, 26 Apr 2004 14:08:09 +0200 Received: (nullmailer pid 1238 invoked by uid 1001); Mon, 26 Apr 2004 12:08:08 -0000 Date: Mon, 26 Apr 2004 14:08:08 +0200 From: Mark Santcroos To: Guido van Rooij Message-ID: <20040426120808.GA801@laptop.6bone.nl> References: <20040414051207.GK58667@pcwin002.win.tue.nl> <20040413222717.O80191@root.org> <20040414.001039.116586661.imp@bsdimp.com> <20040414092553.F83452@root.org> <20040415135755.GA925@laptop.6bone.nl> <20040426120538.GA78787@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040426120538.GA78787@gvr.gvr.org> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.000007 / 0.0 / 0.0 / disabled X-RIPE-Signature: 61faa2c79b025d7183d4fcf6205e7a95 cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: Experiences with new PCI code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 12:08:11 -0000 On Mon, Apr 26, 2004 at 02:05:38PM +0200, Guido van Rooij wrote: > SInce you earlier reported you have a Dell, could you tell me > the brand of your laptop and the tool you used to create the suspend > partition? > > I am still trying to gte info from Dell on such a tool for my Latitude D600. I have a Latitude C640. Dell has a tool, mks2d.exe, but I don't know if your laptop supports it. Should be easy to find out on their site though. Mark From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 26 05:08:51 2004 Return-Path: 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 48CE716A4CE; Mon, 26 Apr 2004 05:08:51 -0700 (PDT) Received: from xraided.net (xraided.net [66.88.26.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DF0E43D3F; Mon, 26 Apr 2004 05:08:51 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: by xraided.net (CommuniGate Pro PIPE 4.1.8) with PIPE id 1710980; Mon, 26 Apr 2004 05:08:51 -0700 X-PolluStop-Diagnostic: ########## X-PolluStop-Score: 1.00 X-PolluStop: Scanned with Niversoft PolluStop 2.0 public beta 7, http://www.niversoft.com/pollustop Received: from mx2.freebsd.org ([216.136.204.119] verified) by xraided.net (CommuniGate Pro SMTP 4.1.8) with SMTP id 1710978 for kyle@xraided.net; Mon, 26 Apr 2004 05:08:40 -0700 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 12D1755E7E; Mon, 26 Apr 2004 05:08:38 -0700 (PDT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C157316A4E1; Mon, 26 Apr 2004 05:08:36 -0700 (PDT) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 247DC16A4CE; Mon, 26 Apr 2004 05:08:11 -0700 (PDT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D8F943D48; Mon, 26 Apr 2004 05:08:10 -0700 (PDT) (envelope-from marks@dell-laptop.6bone.nl) Received: by postman.ripe.net (Postfix, from userid 8) id 860434EF4E; Mon, 26 Apr 2004 14:08:09 +0200 (CEST) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 457EE55D94; Mon, 26 Apr 2004 14:08:09 +0200 (CEST) Received: from dell-laptop.6bone.nl (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i3QC89c4008051; Mon, 26 Apr 2004 14:08:09 +0200 Received: (nullmailer pid 1238 invoked by uid 1001); Mon, 26 Apr 2004 12:08:08 -0000 Date: Mon, 26 Apr 2004 14:08:08 +0200 From: Mark Santcroos To: Guido van Rooij Message-ID: <20040426120808.GA801@laptop.6bone.nl> References: <20040414051207.GK58667@pcwin002.win.tue.nl> <20040414.001039.116586661.imp@bsdimp.com> <20040415135755.GA925@laptop.6bone.nl> <20040426120538.GA78787@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040426120538.GA78787@gvr.gvr.org> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.000007 / 0.0 / 0.0 / disabled X-RIPE-Signature: 61faa2c79b025d7183d4fcf6205e7a95 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org cc: acpi@freebsd.org cc: current@freebsd.org Subject: [SPAM] Re: Experiences with new PCI code X-BeenThere: freebsd-acpi@freebsd.org List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 12:08:51 -0000 On Mon, Apr 26, 2004 at 02:05:38PM +0200, Guido van Rooij wrote: > SInce you earlier reported you have a Dell, could you tell me > the brand of your laptop and the tool you used to create the suspend > partition? > > I am still trying to gte info from Dell on such a tool for my Latitude D600. I have a Latitude C640. Dell has a tool, mks2d.exe, but I don't know if your laptop supports it. Should be easy to find out on their site though. Mark _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 26 08:22:30 2004 Return-Path: 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 B707B16A4CE for ; Mon, 26 Apr 2004 08:22:30 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 7BC2B43D5A for ; Mon, 26 Apr 2004 08:22:30 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 73113 invoked by uid 1000); 26 Apr 2004 15:22:30 -0000 Date: Mon, 26 Apr 2004 08:22:30 -0700 (PDT) From: Nate Lawson To: Ed Korotkov In-Reply-To: <200404261540.02871.bsword@mail.ru> Message-ID: <20040426082052.O73109@root.org> References: <200404261540.02871.bsword@mail.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@FreeBSD.org Subject: Re: ACPI & FDD X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 15:22:30 -0000 On Mon, 26 Apr 2004, Ed Korotkov wrote: > OK. No attachments. > #boot -v > > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc08561cc. > Calibrating clock(s) ... i8254 clock: 1193192 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz quality 0 > Calibrating TSC clock ... TSC clock: 1999780952 Hz > CPU: Intel(R) Celeron(R) CPU 2.00GHz (1999.78-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > Features=0xbfebfbffreal > memory = 259260416 (247 MB) > > fdc0: port > 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 I don't see any error here. Please send the dmesg from AFTER you try to mount the floppy and get an error. Or are there no kernel messages while trying that? Also, what date was your kernel cvsupped to -current? -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 26 09:22:02 2004 Return-Path: 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 0E4AA16A613 for ; Mon, 26 Apr 2004 09:22:02 -0700 (PDT) Received: from snipers.mine.nu (YahooBB219008246026.bbtec.net [219.8.246.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96B5C43D54 for ; Mon, 26 Apr 2004 09:22:01 -0700 (PDT) (envelope-from kochi@netbsd.org) Received: from localhost (localhost [127.0.0.1]) by snipers.mine.nu (Postfix) with ESMTP id 33FEB7871C; Tue, 27 Apr 2004 01:22:00 +0900 (JST) Date: Tue, 27 Apr 2004 01:21:59 +0900 (JST) Message-Id: <20040427.012159.74740435.kochi@netbsd.org> To: len.brown@intel.com From: Takayoshi Kochi In-Reply-To: <29AC424F54821A4FB5D7CBE081922E402FE8C6@hdsmsx403.hd.intel.com> References: <29AC424F54821A4FB5D7CBE081922E402FE8C6@hdsmsx403.hd.intel.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: kanaoka@netbsd.org Subject: Re: ACPI SCI flags X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 16:22:02 -0000 Hi, From: "Brown, Len" Subject: RE: ACPI SCI flags Date: Sun, 25 Apr 2004 21:44:56 -0400 > >> > PIC mode: > >> > force level/low via ELCR always. > >> > >> Did you find that made a difference on some systems? If so, > >which ones? > >> The opinion here was that ELCR is probably EISA-only. > > > >Kanaoka-san reported that if SCI is not set level-trigger, > >the SCI doesn't work properly on his laptop. > >It (Libretto L3) has ALi chipsets (1543 south bridge). > > > >When I tested on my laptop (ThinkPad X31, Intel ICH4), > >it seemed that the setting of ELCR didn't make any difference, though. > > You mean it doesn't work in either case? > Testing it via power button? It DID work in both cases. > Months ago when Linux did the PIC-mode level/low thing, I had > A bunch of users test it, and for many the hardware worked > correctly no matter if ELCR was set to level or edge. > > However, there were others which did care, and only worked > if level triggered. Most of these had a BIOS that had already > set the ELCR to level, but some required the OS to do it. Thanks for the long explanation. I agree that setting ELCR makes sense. --- Takayoshi Kochi From owner-freebsd-acpi@FreeBSD.ORG Tue Apr 27 07:54:33 2004 Return-Path: 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 0F9FF16A4CE for ; Tue, 27 Apr 2004 07:54:33 -0700 (PDT) Received: from hotmail.com (bay2-dav29.bay2.hotmail.com [65.54.246.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB28043D53 for ; Tue, 27 Apr 2004 07:54:32 -0700 (PDT) (envelope-from dsnofe@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 27 Apr 2004 07:54:32 -0700 Received: from 218.109.182.51 by bay2-dav29.bay2.hotmail.com with DAV; Tue, 27 Apr 2004 14:54:32 +0000 X-Originating-IP: [218.109.182.51] X-Originating-Email: [dsnofe@hotmail.com] X-Sender: dsnofe@hotmail.com Date: Tue, 27 Apr 2004 22:54:34 +0800 From: Deng XueFeng To: freebsd-acpi@freebsd.org Message-Id: <20040427225114.965C.DSNOFE@hotmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.09.01 [CN] X-OriginalArrivalTime: 27 Apr 2004 14:54:32.0472 (UTC) FILETIME=[8C900980:01C42C67] Subject: need help X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2004 14:54:33 -0000 My laptop is HP NX7000. when I enable acpi, panic will get when booting. how can i save the panic info or how to debug it that use ddb? thanks! Sincerely, Deng XueFeng From owner-freebsd-acpi@FreeBSD.ORG Tue Apr 27 08:52:23 2004 Return-Path: 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 14C3416A4D9 for ; Tue, 27 Apr 2004 08:52:23 -0700 (PDT) Received: from web41114.mail.yahoo.com (web41114.mail.yahoo.com [66.218.93.30]) by mx1.FreeBSD.org (Postfix) with SMTP id CAF0D43D68 for ; Tue, 27 Apr 2004 08:52:20 -0700 (PDT) (envelope-from jmkatcher@yahoo.com) Message-ID: <20040427155220.45753.qmail@web41114.mail.yahoo.com> Received: from [24.18.54.216] by web41114.mail.yahoo.com via HTTP; Tue, 27 Apr 2004 08:52:20 PDT Date: Tue, 27 Apr 2004 08:52:20 -0700 (PDT) From: Jeffrey Katcher To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Fan Control Success on IBM T40? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2004 15:52:23 -0000 I've been playing with adaptive power management for my Thinkpad T40, running an up-to-date current with ACPI. While I can cycle the clock on demand, I'm noticing that once the fan comes on, it stays on. Judging from the visible variables, there's not a lot of control there. I even notice the lack of battery time, though I get a coherent number from apm. Can I do anything to remedy this? I'm running BIOS 2.03 and have tried a slightly patched DSDT with little visible difference. There is a later BIOS, but as I don't have Windows or even a floppy, it's a pain to try (also I've really been burned by IBM BIOS upgrades before on an older A20p). Jeff Katcher ---- sysctl hw.acpi dump ---- hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 5 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.disable_on_poweroff: 1 hw.acpi.reset_video: 1 hw.acpi.cpu.throttle_max: 8 hw.acpi.cpu.throttle_state: 8 hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 hw.acpi.cpu.cx_lowest: 0 hw.acpi.cpu.cx_history: 10808/0 0/0 0/0 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.tz0.temperature: 3002 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3617 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3662 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover From owner-freebsd-acpi@FreeBSD.ORG Tue Apr 27 12:32:23 2004 Return-Path: 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 24DEA16A4CE for ; Tue, 27 Apr 2004 12:32:23 -0700 (PDT) Received: from mailbox.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61D1943D5E for ; Tue, 27 Apr 2004 12:32:22 -0700 (PDT) (envelope-from le@FreeBSD.org) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) i3RJVnEW930024; Tue, 27 Apr 2004 21:31:50 +0200 Date: Tue, 27 Apr 2004 21:31:48 +0200 (CEST) From: Lukas Ertl To: Jeffrey Katcher In-Reply-To: <20040427155220.45753.qmail@web41114.mail.yahoo.com> Message-ID: <20040427212944.O652@korben> References: <20040427155220.45753.qmail@web41114.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: imap 4243; Body=0 Fuz1=0 Fuz2=0 cc: freebsd-acpi@FreeBSD.org Subject: Re: Fan Control Success on IBM T40? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2004 19:32:23 -0000 On Tue, 27 Apr 2004, Jeffrey Katcher wrote: > I've been playing with adaptive power management for my Thinkpad T40, running > an up-to-date current with ACPI. While I can cycle the clock on demand, I'm > noticing that once the fan comes on, it stays on. You probably can't do anything against that, I'm seeing it too on my T40. There are many discussions about the "T40 fan problem" in newsgroups, seems like IBM botched this model. I've heard from inofficial sources that it's a problem with the on-board temperature sensor, so maybe you can solve this by replacing the system board. cheers, le -- Lukas Ertl http://mailbox.univie.ac.at/~le/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-acpi@FreeBSD.ORG Tue Apr 27 16:56:41 2004 Return-Path: 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 267D616A4CE for ; Tue, 27 Apr 2004 16:56:41 -0700 (PDT) Received: from out007.verizon.net (out007pub.verizon.net [206.46.170.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99E7F43D46 for ; Tue, 27 Apr 2004 16:56:40 -0700 (PDT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([141.153.210.237]) by out007.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040427235638.IMUX28276.out007.verizon.net@RabbitsDen> for ; Tue, 27 Apr 2004 18:56:38 -0500 Date: Tue, 27 Apr 2004 19:56:07 -0400 From: Alexandre "Sunny" Kovalenko To: freebsd-acpi@freebsd.org Message-Id: <20040427195607.7f434912.Alex.Kovalenko@verizon.net> In-Reply-To: <20040427155220.45753.qmail@web41114.mail.yahoo.com> References: <20040427155220.45753.qmail@web41114.mail.yahoo.com> Organization: Home X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out007.verizon.net from [141.153.210.237] at Tue, 27 Apr 2004 18:56:37 -0500 Subject: Re: Fan Control Success on IBM T40? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2004 23:56:41 -0000 On Tue, 27 Apr 2004 08:52:20 -0700 (PDT) Jeffrey Katcher wrote: > I've been playing with adaptive power management for my Thinkpad T40, running > an up-to-date current with ACPI. While I can cycle the clock on demand, I'm > noticing that once the fan comes on, it stays on. Judging from the visible > variables, there's not a lot of control there. I even notice the lack of > battery time, though I get a coherent number from apm. Can I do anything to > remedy this? I'm running BIOS 2.03 and have tried a slightly patched DSDT > with little visible difference. There is a later BIOS, but as I don't have > Windows or even a floppy, it's a pain to try (also I've really been > burned by IBM BIOS upgrades before on an older A20p). > > Jeff Katcher > > ---- sysctl hw.acpi dump ---- > hw.acpi.supported_sleep_state: S3 S4 S5 > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S1 > hw.acpi.lid_switch_state: S1 > hw.acpi.standby_state: S1 > hw.acpi.suspend_state: S3 > hw.acpi.sleep_delay: 5 > hw.acpi.s4bios: 0 > hw.acpi.verbose: 0 > hw.acpi.disable_on_poweroff: 1 > hw.acpi.reset_video: 1 > hw.acpi.cpu.throttle_max: 8 > hw.acpi.cpu.throttle_state: 8 > hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 > hw.acpi.cpu.cx_lowest: 0 > hw.acpi.cpu.cx_history: 10808/0 0/0 0/0 > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.tz0.temperature: 3002 > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 3617 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 3662 > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.battery.life: 100 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 0 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > hw.acpi.acline: 1 > > > > > > __________________________________ > Do you Yahoo!? > Win a $20,000 Career Makeover at Yahoo! HotJobs > http://hotjobs.sweepstakes.yahoo.com/careermakeover > _______________________________________________ > 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" What I have done to my machine (Averatec 3140H) is ripping apart RTEP method in ASL which was doing fan control and creating _ACx/_ALx pairs with the proper power devices out of it. I was lucky, since machine: -- actually had fan management -- it was somewhat readable in the sense that I was able to recognize pieces that are turning on fans at the different speed -- it has hardware emergency shut-off on overheating (this is the most important thing, since chances of laptop meltdown are fairly high with this kind of work). My ASL also had _TMP method which was returning value, stored in some location during startup and never updated afterwards. I was lucky again to find method, which actually does return current temperature and then calling it from _TMP. If you are interested, please let me know and I will send you original ASL and the end result. -- Alexandre "Sunny" Kovalenko. From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 00:04:05 2004 Return-Path: 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 F38C016A4CE for ; Wed, 28 Apr 2004 00:04:04 -0700 (PDT) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8E4A43D5E for ; Wed, 28 Apr 2004 00:04:04 -0700 (PDT) (envelope-from bsword@mail.ru) Received: from [82.140.65.90] (port=49207 helo=fort) by mx2.mail.ru with esmtp id 1BIj6x-000P8H-00 for freebsd-acpi@freebsd.org; Wed, 28 Apr 2004 11:04:03 +0400 From: Ed Korotkov To: freebsd-acpi@freebsd.org Date: Wed, 28 Apr 2004 11:04:09 +0400 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200404281104.09090.bsword@mail.ru> X-Spam: Not detected Subject: ACPI & FDD X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 07:04:05 -0000 There are no kernel messages while I trying to mount the floppy. The kernel is recompiled by me from GENERIC 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 09:05:05 2004 Return-Path: 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 565DA16A4CE for ; Wed, 28 Apr 2004 09:05:05 -0700 (PDT) Received: from web41114.mail.yahoo.com (web41114.mail.yahoo.com [66.218.93.30]) by mx1.FreeBSD.org (Postfix) with SMTP id 3081843D2D for ; Wed, 28 Apr 2004 09:05:05 -0700 (PDT) (envelope-from jmkatcher@yahoo.com) Message-ID: <20040428160504.36451.qmail@web41114.mail.yahoo.com> Received: from [24.18.54.216] by web41114.mail.yahoo.com via HTTP; Wed, 28 Apr 2004 09:05:04 PDT Date: Wed, 28 Apr 2004 09:05:04 -0700 (PDT) From: Jeffrey Katcher To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Fan Control Success on IBM T40? (another quick Q) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 16:05:05 -0000 >From everything I've seen (on the linux-acpi lists), the T40 doesn't have _any_ fan control in the DSDT. Apparently it's explicitly controlled via SMBIOS. There's a SMAPI interface available from FreeBSD, but I don't have enough info yet to exploit it. Second question, still on power/clock issues, but diverging a little from ACPI: What's the interaction between SpeedStep clock and ACPI clock percentage? If I start on batteries, apparently the clock is at 600Mhz (even though dmesg reports it as 1600Mhz no matter what). ACPI CPU then can reduce this base by eighths? So if I start on AC, it's eighths of 1600 and DC, it's eighths of 600? Thanks again, Jeff Katcher __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 11:40:26 2004 Return-Path: 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 3B2B616A4CE for ; Wed, 28 Apr 2004 11:40:26 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 29AAB43D31 for ; Wed, 28 Apr 2004 11:40:26 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 88230 invoked by uid 1000); 28 Apr 2004 18:40:27 -0000 Date: Wed, 28 Apr 2004 11:40:27 -0700 (PDT) From: Nate Lawson To: Ed Korotkov In-Reply-To: <200404281104.09090.bsword@mail.ru> Message-ID: <20040428114001.O88145@root.org> References: <200404281104.09090.bsword@mail.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: ACPI & FDD X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 18:40:26 -0000 On Wed, 28 Apr 2004, Ed Korotkov wrote: > There are no kernel messages while I trying to mount the floppy. > The kernel is recompiled by me from > GENERIC 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004 Try 5-current. I believe this problem was fixed. You can test with an ISO from snapshots.jp.freebsd.org. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 11:45:42 2004 Return-Path: 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 BCFE616A4CE for ; Wed, 28 Apr 2004 11:45:42 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id BC95743D2F for ; Wed, 28 Apr 2004 11:45:41 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 88278 invoked by uid 1000); 28 Apr 2004 18:45:42 -0000 Date: Wed, 28 Apr 2004 11:45:42 -0700 (PDT) From: Nate Lawson To: Jeffrey Katcher In-Reply-To: <20040428160504.36451.qmail@web41114.mail.yahoo.com> Message-ID: <20040428114036.R88145@root.org> References: <20040428160504.36451.qmail@web41114.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: Fan Control Success on IBM T40? (another quick Q) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 18:45:42 -0000 On Wed, 28 Apr 2004, Jeffrey Katcher wrote: > >From everything I've seen (on the linux-acpi lists), the T40 doesn't have _any_ > fan control in the DSDT. Apparently it's explicitly controlled via SMBIOS. > There's a SMAPI interface available from FreeBSD, but I don't have enough info > yet to exploit it. That's similar to my T23. It actually handles fans automatically with SMM code and does not export the info through ACPI. > Second question, still on power/clock issues, but diverging a little from ACPI: > What's the interaction between SpeedStep clock and ACPI clock percentage? > If I start on batteries, apparently the clock is at 600Mhz (even though dmesg > reports it as 1600Mhz no matter what). ACPI CPU then can reduce this base by > eighths? So if I start on AC, it's eighths of 1600 and DC, it's eighths of > 600? SpeedStep and ACPI performance states are clock/voltage. Throttling is a % of the current clock. So they are additive. I'm working on a cpufreq driver for the former and acpi_cpu supports the latter currently. Thinkpads automatically switch SpeedStep based on AC line at boot time so if I boot with the AC line unplugged, I get the lowest clock/voltage combo. Throttling, if activated, would be in addition to that. So if your chipset, like mine, offers 1 Ghz and 733 Mhz clock/voltage settings, and 100% and 50% throttling settings, you have four actual settings: 1000 mhz 733 mhz 500 mhz (1 ghz + 50% throttle) 366 mhz (733 mhz + 50% throttle) You won't be able to adjust SpeedStep-like settings until the cpufreq driver is finished. It will automatically combine the two additive settings and export a unified interface that just allows you to select the clock rate. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 13:15:15 2004 Return-Path: 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 4CCEC16A4D1 for ; Wed, 28 Apr 2004 13:15:14 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id AC45343D46 for ; Wed, 28 Apr 2004 13:15:12 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 88870 invoked by uid 1000); 28 Apr 2004 20:15:13 -0000 Date: Wed, 28 Apr 2004 13:15:13 -0700 (PDT) From: Nate Lawson To: Jeffrey Katcher In-Reply-To: <20040428114036.R88145@root.org> Message-ID: <20040428131247.K88558@root.org> References: <20040428160504.36451.qmail@web41114.mail.yahoo.com> <20040428114036.R88145@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: Fan Control Success on IBM T40? (another quick Q) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 20:15:15 -0000 On Wed, 28 Apr 2004, Nate Lawson wrote: > On Wed, 28 Apr 2004, Jeffrey Katcher wrote: > > >From everything I've seen (on the linux-acpi lists), the T40 doesn't have _any_ > > fan control in the DSDT. Apparently it's explicitly controlled via SMBIOS. > > There's a SMAPI interface available from FreeBSD, but I don't have enough info > > yet to exploit it. > > > Second question, still on power/clock issues, but diverging a little from ACPI: > > What's the interaction between SpeedStep clock and ACPI clock percentage? > > If I start on batteries, apparently the clock is at 600Mhz (even though dmesg > > reports it as 1600Mhz no matter what). ACPI CPU then can reduce this base by > > eighths? So if I start on AC, it's eighths of 1600 and DC, it's eighths of > > 600? > I forgot to add -- the reason the clock rate announced at boot time is different is because the test for CPU TSC is done before acpi is enabled. At some point when the SMI is disabled and acpi enabled, the clock rate is switched by your BIOS to the lower rate. You can see this because the clock rate announced by the TSC timecounter will be ~600 mhz while the initial boot clock rate will list ~1600 mhz. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 14:18:27 2004 Return-Path: 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 8CCCB16A4CE for ; Wed, 28 Apr 2004 14:18:27 -0700 (PDT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D90B43D1F for ; Wed, 28 Apr 2004 14:18:27 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Wed, 28 Apr 2004 14:18:26 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id A02195D07; Wed, 28 Apr 2004 14:18:26 -0700 (PDT) To: Nate Lawson In-reply-to: Your message of "Wed, 28 Apr 2004 13:15:13 PDT." <20040428131247.K88558@root.org> Date: Wed, 28 Apr 2004 14:18:26 -0700 From: "Kevin Oberman" Message-Id: <20040428211826.A02195D07@ptavv.es.net> cc: freebsd-acpi@freebsd.org cc: Jeffrey Katcher Subject: Re: Fan Control Success on IBM T40? (another quick Q) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 21:18:27 -0000 > Date: Wed, 28 Apr 2004 13:15:13 -0700 (PDT) > From: Nate Lawson > Sender: owner-freebsd-acpi@freebsd.org > > I forgot to add -- the reason the clock rate announced at boot time is > different is because the test for CPU TSC is done before acpi is enabled. > At some point when the SMI is disabled and acpi enabled, the clock rate is > switched by your BIOS to the lower rate. You can see this because the > clock rate announced by the TSC timecounter will be ~600 mhz while the > initial boot clock rate will list ~1600 mhz. This all makes sense, but it conflicts a bit with my observations. (Probably implies something bad about my powers of observation.) I boot and the system (T30) is running at 1.8 GHz. I throttle the CPU. Testing clearly shows that the throttling is working. I use the test you suggested of calculating an MD5 hash of a big string of zeros. But, when I "count cycles" to test the CPU speed (code appended), I still see 1.8 GHz. Why don't I see the speed reduced when throttling? I suspect my lack of fundamental understanding of the interactions of throttling and the ACPI clock. -- 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 /* * $Id: MHz.c,v 1.4 2001/05/21 18:58:01 davej Exp $ * This file is part of x86info. * (C) 2001 Dave Jones. * * Licensed under the terms of the GNU GPL License version 2. * * Estimate CPU MHz routine by Andrea Arcangeli * Small changes by David Sterba * */ #include #include #include #include __inline__ unsigned long long int rdtsc() { unsigned long long int x; __asm__ volatile (".byte 0x0f, 0x31" : "=A" (x)); return x; } char *estimate_MHz() { char *buffer; struct timezone tz; struct timeval tvstart, tvstop; unsigned long long int cycles[2]; /* gotta be 64 bit */ unsigned int microseconds; /* total time taken */ memset(&tz, 0, sizeof(tz)); /* get this function in cached memory */ gettimeofday(&tvstart, &tz); cycles[0] = rdtsc(); gettimeofday(&tvstart, &tz); /* we don't trust that this is any specific length of time */ usleep(100); cycles[1] = rdtsc(); gettimeofday(&tvstop, &tz); microseconds = ((tvstop.tv_sec-tvstart.tv_sec)*1000000) + (tvstop.tv_usec-tvstart.tv_usec); buffer = malloc(sizeof(char)*512); sprintf(buffer, "%lldMHz", (cycles[1]-cycles[0])/microseconds); return buffer; } From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 14:24:13 2004 Return-Path: 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 46E0C16A4CE for ; Wed, 28 Apr 2004 14:24:13 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 1788643D1F for ; Wed, 28 Apr 2004 14:24:13 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 89279 invoked by uid 1000); 28 Apr 2004 21:24:14 -0000 Date: Wed, 28 Apr 2004 14:24:14 -0700 (PDT) From: Nate Lawson To: Kevin Oberman In-Reply-To: <20040428211826.A02195D07@ptavv.es.net> Message-ID: <20040428142302.T89203@root.org> References: <20040428211826.A02195D07@ptavv.es.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org cc: Jeffrey Katcher Subject: Re: Fan Control Success on IBM T40? (another quick Q) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 21:24:13 -0000 On Wed, 28 Apr 2004, Kevin Oberman wrote: > > Date: Wed, 28 Apr 2004 13:15:13 -0700 (PDT) > > From: Nate Lawson > > Sender: owner-freebsd-acpi@freebsd.org > > > > I forgot to add -- the reason the clock rate announced at boot time is > > different is because the test for CPU TSC is done before acpi is enabled. > > At some point when the SMI is disabled and acpi enabled, the clock rate is > > switched by your BIOS to the lower rate. You can see this because the > > clock rate announced by the TSC timecounter will be ~600 mhz while the > > initial boot clock rate will list ~1600 mhz. > > This all makes sense, but it conflicts a bit with my > observations. (Probably implies something bad about my powers of > observation.) > > I boot and the system (T30) is running at 1.8 GHz. I throttle the CPU. > Testing clearly shows that the throttling is working. I use the test you > suggested of calculating an MD5 hash of a big string of zeros. > > But, when I "count cycles" to test the CPU speed (code appended), I > still see 1.8 GHz. > > Why don't I see the speed reduced when throttling? I suspect my lack of > fundamental understanding of the interactions of throttling and the ACPI > clock. This is totally different. You aren't using SpeedStep/performance states, only throttling. Throttling works by changing the duty cycle but with the SAME base clock rate. Since the TSC comes from the base rate, your test reading the TSC will never change. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 14:34:39 2004 Return-Path: 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 2EB3A16A4CE for ; Wed, 28 Apr 2004 14:34:39 -0700 (PDT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1A8543D3F for ; Wed, 28 Apr 2004 14:34:38 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 17934 invoked from network); 28 Apr 2004 21:34:38 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 28 Apr 2004 21:34:38 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i3SLYYvM016922; Wed, 28 Apr 2004 17:34:35 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Wed, 28 Apr 2004 17:34:46 -0400 User-Agent: KMail/1.6 References: <20040428211826.A02195D07@ptavv.es.net> <20040428142302.T89203@root.org> In-Reply-To: <20040428142302.T89203@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404281734.46945.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Jeffrey Katcher Subject: Re: Fan Control Success on IBM T40? (another quick Q) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 21:34:39 -0000 On Wednesday 28 April 2004 05:24 pm, Nate Lawson wrote: > On Wed, 28 Apr 2004, Kevin Oberman wrote: > > > Date: Wed, 28 Apr 2004 13:15:13 -0700 (PDT) > > > From: Nate Lawson > > > Sender: owner-freebsd-acpi@freebsd.org > > > > > > I forgot to add -- the reason the clock rate announced at boot time is > > > different is because the test for CPU TSC is done before acpi is > > > enabled. At some point when the SMI is disabled and acpi enabled, the > > > clock rate is switched by your BIOS to the lower rate. You can see > > > this because the clock rate announced by the TSC timecounter will be > > > ~600 mhz while the initial boot clock rate will list ~1600 mhz. > > > > This all makes sense, but it conflicts a bit with my > > observations. (Probably implies something bad about my powers of > > observation.) > > > > I boot and the system (T30) is running at 1.8 GHz. I throttle the CPU. > > Testing clearly shows that the throttling is working. I use the test you > > suggested of calculating an MD5 hash of a big string of zeros. > > > > But, when I "count cycles" to test the CPU speed (code appended), I > > still see 1.8 GHz. > > > > Why don't I see the speed reduced when throttling? I suspect my lack of > > fundamental understanding of the interactions of throttling and the ACPI > > clock. > > This is totally different. You aren't using SpeedStep/performance states, > only throttling. Throttling works by changing the duty cycle but with the > SAME base clock rate. Since the TSC comes from the base rate, your test > reading the TSC will never change. Also, even with SpeedStep, the CPU will "fake" the TSC so that it stays at a constant rate even when the CPU is throttled down to a slower speed. I think that's what the 'ACPI' bit in the cpu_features indicates. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 15:44:45 2004 Return-Path: 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 1B00C16A4CE for ; Wed, 28 Apr 2004 15:44:45 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1F1043D41 for ; Wed, 28 Apr 2004 15:44:44 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i3SMihgr069208 for ; Wed, 28 Apr 2004 16:44:44 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 28 Apr 2004 16:45:04 -0600 (MDT) Message-Id: <20040428.164504.01407523.imp@bsdimp.com> To: acpi@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Latest acpi on my FIVA X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 22:44:45 -0000 >From the latest sources on my FIVA MPC-205: ACPI-0440: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0.ISA_.EC0_.SMRD] (Node 0xc44d5440), AE_NO_HARDWARE_RESPONSE ACPI-1303: *** Error: Method execution failed [\\_SB_.BAT1.UPBI] (Node 0xc44d8540), AE_NO_HARDWARE_RESPONSE ACPI-1303: *** Error: Method execution failed [\\_SB_.BAT1._BIF] (Node 0xc44d8580), AE_NO_HARDWARE_RESPONSE Repeated 4 or 5 times on boot. Warner From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 16:46:59 2004 Return-Path: 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 51F0B16A4CF for ; Wed, 28 Apr 2004 16:46:59 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 03A7743D2D for ; Wed, 28 Apr 2004 16:46:59 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 90088 invoked by uid 1000); 28 Apr 2004 23:47:00 -0000 Date: Wed, 28 Apr 2004 16:47:00 -0700 (PDT) From: Nate Lawson To: "M. Warner Losh" In-Reply-To: <20040428.164504.01407523.imp@bsdimp.com> Message-ID: <20040428164403.G90064@root.org> References: <20040428.164504.01407523.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: Latest acpi on my FIVA X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 23:46:59 -0000 On Wed, 28 Apr 2004, M. Warner Losh wrote: > >From the latest sources on my FIVA MPC-205: > > ACPI-0440: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE > ACPI-1303: *** Error: Method execution failed [\\_SB_.PCI0.ISA_.EC0_.SMRD] (Node 0xc44d5440), AE_NO_HARDWARE_RESPONSE > ACPI-1303: *** Error: Method execution failed [\\_SB_.BAT1.UPBI] (Node 0xc44d8540), AE_NO_HARDWARE_RESPONSE > ACPI-1303: *** Error: Method execution failed [\\_SB_.BAT1._BIF] (Node 0xc44d8580), AE_NO_HARDWARE_RESPONSE > > Repeated 4 or 5 times on boot. For some reason, reads from the EC time out on some systems. There's no discernable common cause but some possible causes include heavy load (Giant being held too long? ithread taking too long to run?), boot time setup of the EC GPE, or buggy EC that fails at various times. Try updating your BIOS and or EC flash. The new acpi import I'm working on may help (modifies GPE initialization). If it doesn't happen at runtime, don't worry about it. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Apr 28 22:01:02 2004 Return-Path: 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 8042916A4CE for ; Wed, 28 Apr 2004 22:01:02 -0700 (PDT) Received: from web41106.mail.yahoo.com (web41106.mail.yahoo.com [66.218.93.22]) by mx1.FreeBSD.org (Postfix) with SMTP id 477EF43D62 for ; Wed, 28 Apr 2004 22:01:02 -0700 (PDT) (envelope-from jmkatcher@yahoo.com) Message-ID: <20040429050101.63950.qmail@web41106.mail.yahoo.com> Received: from [24.18.54.216] by web41106.mail.yahoo.com via HTTP; Wed, 28 Apr 2004 22:01:01 PDT Date: Wed, 28 Apr 2004 22:01:01 -0700 (PDT) From: Jeffrey Katcher To: freebsd-acpi@freebsd.org In-Reply-To: <20040428142302.T89203@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Fan Control Success on IBM T40? (another quick Q) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2004 05:01:02 -0000 FYI, if anyone needs to update their Thinkpad BIOS/system controller and doesn't have a floppy or run Windows, I have a working procedure involving Bochs, FreeDOS, and bootable CDs. Bochs/FreeDOS is used to generate floppy boot images from IBM's DOS only BIOS/system controller updaters which are then burned as standalone boot CDs to remove the necessity of having a floppy drive. The current T40 system controller (3.0a)/BIOS (3.04) seems quite a bit better about powering down the fan. Hope this is helpful, Jeff Katcher __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 29 11:16:24 2004 Return-Path: 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 DAE3716A4CE for ; Thu, 29 Apr 2004 11:16:24 -0700 (PDT) Received: from mailbox.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B82443D45 for ; Thu, 29 Apr 2004 11:16:24 -0700 (PDT) (envelope-from l.ertl@univie.ac.at) Received: from leelou (adslle.cc.univie.ac.at [131.130.102.11]) i3TIGIJW1258020 for ; Thu, 29 Apr 2004 20:16:20 +0200 Date: Thu, 29 Apr 2004 20:16:18 +0200 (CEST) From: Lukas Ertl To: acpi@freebsd.org Message-ID: <20040429201041.W751@leelou.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: imap 4241; Body=1 Fuz1=1 Fuz2=1 Subject: Suspend/resume regression with latest ACPI code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2004 18:16:25 -0000 Hi, I'm seeing a suspend/resume regression with the latest ACPI code. Last known good kernel was from April 12th, so that was before the import of ACPI CA 20040402. The box in question is a ThinkPad T40, and with the old kernel, I could perfectly suspend/resume my laptop. Now, only the first suspend/resume cycle works; if I try afterwards, it immediately wakes up again after suspending. No errors or otherwise suspiscous output. I'm not sure if this could be related to the PCI changes from Warner. cheers, le -- Lukas Ertl eMail: l.ertl@univie.ac.at UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 29 12:21:50 2004 Return-Path: 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 1458116A4CE for ; Thu, 29 Apr 2004 12:21:50 -0700 (PDT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0079043D48 for ; Thu, 29 Apr 2004 12:21:50 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Thu, 29 Apr 2004 12:21:49 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4B3F75D0B; Thu, 29 Apr 2004 12:21:49 -0700 (PDT) To: Lukas Ertl In-reply-to: Your message of "Thu, 29 Apr 2004 20:16:18 +0200." <20040429201041.W751@leelou.in.tern> Date: Thu, 29 Apr 2004 12:21:49 -0700 From: "Kevin Oberman" Message-Id: <20040429192149.4B3F75D0B@ptavv.es.net> cc: acpi@freebsd.org Subject: Re: Suspend/resume regression with latest ACPI code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2004 19:21:50 -0000 > Date: Thu, 29 Apr 2004 20:16:18 +0200 (CEST) > From: Lukas Ertl > Sender: owner-freebsd-acpi@freebsd.org > > Hi, > > I'm seeing a suspend/resume regression with the latest ACPI code. Last > known good kernel was from April 12th, so that was before the import of > ACPI CA 20040402. > > The box in question is a ThinkPad T40, and with the old kernel, I could > perfectly suspend/resume my laptop. Now, only the first suspend/resume > cycle works; if I try afterwards, it immediately wakes up again after > suspending. No errors or otherwise suspiscous output. > > I'm not sure if this could be related to the PCI changes from Warner. This is a me-too (tm-AOL). In my case it's an IBM T30. Looks like the problem may be common to multiple IBM systems. I've seen some other reports of this on IBMs, but I'm not sure if I've seen reports on other platforms. I'm seriously suspicious that this is really a PCI issue in the power stuff. I suspect that something is not being properly reset on resume and that the next attempt to suspend fails because something is not in the right state. It gets all the way to the end of the suspend, though, before it decides that it really can't. I have a couple of other problems that I think are really PCI issues (sound and the loss of IRQ11 after a while) and I think that this should also go on the list. -- 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 From owner-freebsd-acpi@FreeBSD.ORG Thu Apr 29 12:53:02 2004 Return-Path: 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 782FF16A4CE for ; Thu, 29 Apr 2004 12:53:02 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 41C5C43D49 for ; Thu, 29 Apr 2004 12:53:02 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 95591 invoked by uid 1000); 29 Apr 2004 19:53:03 -0000 Date: Thu, 29 Apr 2004 12:53:03 -0700 (PDT) From: Nate Lawson To: Lukas Ertl In-Reply-To: <20040429201041.W751@leelou.in.tern> Message-ID: <20040429125159.F95574@root.org> References: <20040429201041.W751@leelou.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: Suspend/resume regression with latest ACPI code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2004 19:53:02 -0000 On Thu, 29 Apr 2004, Lukas Ertl wrote: > I'm seeing a suspend/resume regression with the latest ACPI code. Last > known good kernel was from April 12th, so that was before the import of > ACPI CA 20040402. > > The box in question is a ThinkPad T40, and with the old kernel, I could > perfectly suspend/resume my laptop. Now, only the first suspend/resume > cycle works; if I try afterwards, it immediately wakes up again after > suspending. No errors or otherwise suspiscous output. > > I'm not sure if this could be related to the PCI changes from Warner. Yep, I've got the same issue. If someone has time, it would be very helpful to cvsup a kernel from before the PCI changes but an acpi.ko from after the import. This would help isolate the issue. Thanks, Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Apr 30 09:57:07 2004 Return-Path: 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 97D7E16A4CE for ; Fri, 30 Apr 2004 09:57:07 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 5A9F143D49 for ; Fri, 30 Apr 2004 09:57:07 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 1540 invoked by uid 1000); 30 Apr 2004 16:57:08 -0000 Date: Fri, 30 Apr 2004 09:57:07 -0700 (PDT) From: Nate Lawson To: Lukas Ertl In-Reply-To: <20040429201041.W751@leelou.in.tern> Message-ID: <20040430095545.K1475@root.org> References: <20040429201041.W751@leelou.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: Suspend/resume regression with latest ACPI code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Apr 2004 16:57:07 -0000 On Thu, 29 Apr 2004, Lukas Ertl wrote: > I'm seeing a suspend/resume regression with the latest ACPI code. Last > known good kernel was from April 12th, so that was before the import of > ACPI CA 20040402. > > The box in question is a ThinkPad T40, and with the old kernel, I could > perfectly suspend/resume my laptop. Now, only the first suspend/resume > cycle works; if I try afterwards, it immediately wakes up again after > suspending. No errors or otherwise suspiscous output. > > I'm not sure if this could be related to the PCI changes from Warner. Just a quick status report. A hacked version of a new ACPI import does fix things and I can suspend/resume multiple times just fine. The issue is with wake GPE handling. I don't think it is the power code at all. In fact, the BAR restoration allows my console video to work after resume now whereas before only X worked. -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Apr 30 10:24:52 2004 Return-Path: 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 441DD16A4CE for ; Fri, 30 Apr 2004 10:24:52 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id F30EC43D53 for ; Fri, 30 Apr 2004 10:24:51 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 1694 invoked by uid 1000); 30 Apr 2004 17:24:52 -0000 Date: Fri, 30 Apr 2004 10:24:52 -0700 (PDT) From: Nate Lawson To: Jeffrey Katcher In-Reply-To: <20040429050101.63950.qmail@web41106.mail.yahoo.com> Message-ID: <20040430095720.R1475@root.org> References: <20040429050101.63950.qmail@web41106.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: Fan Control Success on IBM T40? (another quick Q) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Apr 2004 17:24:52 -0000 On Wed, 28 Apr 2004, Jeffrey Katcher wrote: > FYI, if anyone needs to update their Thinkpad BIOS/system controller and > doesn't > have a floppy or run Windows, I have a working procedure involving Bochs, > FreeDOS, > and bootable CDs. Bochs/FreeDOS is used to generate floppy boot images from > IBM's > DOS only BIOS/system controller updaters which are then burned as standalone > boot > CDs to remove the necessity of having a floppy drive. > > The current T40 system controller (3.0a)/BIOS (3.04) seems quite a bit better > about powering down the fan. I don't know if anyone is reading/using the ACPI section of the handbook but this should be one of the first suggestions in it. UPDATE YOUR BIOS AND/OR EC BEFORE COMPLAINING. :) http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html -Nate