From lowell@be-well.no-ip.com Tue May 18 17:13:47 2004 Return-Path: Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D30916A4CE; Tue, 18 May 2004 17:13:47 -0700 (PDT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2683C43D39; Tue, 18 May 2004 17:13:47 -0700 (PDT) (envelope-from lowell@be-well.no-ip.com) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (sccrmhc12) with ESMTP id <2004051900132701200k9vdge>; Wed, 19 May 2004 00:13:27 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 896CB55; Tue, 18 May 2004 20:13:23 -0400 (EDT) Message-Id: <20040519001323.896CB55@be-well.no-ip.com> Date: Tue, 18 May 2004 20:13:23 -0400 (EDT) From: Lowell Gilbert Reply-To: Lowell Gilbert To: FreeBSD-gnats-submit@freebsd.org Cc: imp@freebsd.org Subject: cardbus power support breaks cardbus support on HP Omnibook XE2 X-Send-Pr-Version: 3.113 X-GNATS-Notify: >Number: 66848 >Category: kern >Synopsis: [cardbus] cardbus power support breaks cardbus support on HP Omnibook XE2 >Confidential: no >Severity: serious >Priority: medium >Responsible: imp >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 18 17:20:19 PDT 2004 >Closed-Date: Fri Apr 17 11:20:10 MDT 2009 >Last-Modified: Fri Apr 17 11:20:10 MDT 2009 >Originator: Lowell Gilbert >Release: FreeBSD 5.2-CURRENT i386 >Organization: >Environment: System: FreeBSD laptop-unix.lan 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Sat Apr 3 16:26:42 EST 2004 root@lowell-laptop-unconfigured:/usr/src/sys/i386/compile/LAPTOP-5.x i386 [That's the working kernel; any updates from the middle of April or so on do not work.] This has been happening, apparently, since the PCI power support went into -CURRENT. >Description: This is on a HP Omnibook XE2; I posted about it before, but didn't get any responses. The problems showed up when the power support was added to -CURRENT. I've tried making the power manipulations in pccbb.c respect the hw.pci.do_powerstate flag, but all I could manage that way was to eliminate the error messages without actually getting the cardbus to bring up any cards. There's some other information on the system on my web site at http://be-well.ilk.org:8088/~lowell/systuff/laptop-problems.html from my previous battles with AGP support. Setting hw.cbb.debug and hw.pccard.debug didn't show anything that seemed useful to me. Someone who knows the register definitions for the bridge chip might well have better luck. . I'm attaching the dmesg. ================================================================ Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-CURRENT #13: Sun May 9 22:26:12 EDT 2004 root@laptop-unix.lan:/usr/obj/usr/src/sys/LAPTOP-5.x WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xc08f2000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (398.20-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66d Stepping = 13 Features=0x183f9ff real memory = 201261056 (191 MB) avail memory = 187265024 (178 MB) random: Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 pcib0: at pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 $PIR: 0:7 INTD routed to irq 10 $PIR: 0:10 INTA routed to irq 10 $PIR: 0:10 INTB routed to irq 10 $PIR: 0:13 INTA routed to irq 5 $PIR: 0:13 INTA routed to irq 5 pcib1: at device 1.0 on pci0 pci1: on pcib1 $PIR: 1:0 INTA routed to irq 10 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfcd0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: at 0x1f0 irq 14 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xfce0-0xfcff irq 10 at device 7.2 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xfce0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) cbb0: irq 10 at device 10.0 on pci0 cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0 cbb0: Found memory at 00000000 cbb0: Secondary bus is 0 cbb0: Secondary bus set to 1 subbus 2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: cbb_power: 0V cbb0: bad Vcc request. ctrl=0xf000ff00, status=0xf000e2c3 cbb_power: 0V cbb1: irq 10 at device 10.1 on pci0 cbb1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x1000 cbb1: Found memory at 00001000 cbb1: Secondary bus is 0 cbb1: Secondary bus set to 3 subbus 4 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 cbb1: cbb_power: 0V pci0: at device 13.0 (no driver attached) pci0: at device 13.1 (no driver attached) cpu0 on motherboard orm0: