From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 14 06:27:00 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B317B16A41F for ; Wed, 14 Dec 2005 06:27:00 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 266B643D55 for ; Wed, 14 Dec 2005 06:27:00 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jBE6OgPM026693; Tue, 13 Dec 2005 23:24:48 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 13 Dec 2005 23:25:04 -0700 (MST) Message-Id: <20051213.232504.07010673.imp@bsdimp.com> To: jgrosch@MooseRiver.com From: "M. Warner Losh" In-Reply-To: <20051212051813.GA19499@mooseriver.com> References: <20051212051813.GA19499@mooseriver.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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 13 Dec 2005 23:24:48 -0700 (MST) Cc: freebsd-hackers@FreeBSD.org Subject: Re: Cardbus panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2005 06:27:00 -0000 In message: <20051212051813.GA19499@mooseriver.com> Josef Grosch writes: : : I have an IBM T22 thinkpad running FreeBSD 5.4-RELEASE-p8. I have the : CardBus devices in the current kernel. When I insert a CardBus device, A : Xircom RealPort CardBus Ethernet I get a kernel panic like so; : : Dec 9 18:42:32 paris kernel: cbb alloc res fail : Dec 9 18:42:32 paris kernel: cardbus1: Can't get memory for IO ports : Dec 9 18:42:32 paris kernel: dc0: port 0-0x7f mem \ : 0x88000000-0x880007ff,0x88000800-0x88000fff at device 0.0 on cardbus1 : Dec 9 18:42:32 paris kernel: cbb alloc res fail : Dec 9 18:42:32 paris kernel: dc0: couldn't map ports/memory : Dec 9 18:42:32 paris kernel: : Dec 9 18:42:32 paris kernel: : Dec 9 18:42:32 paris kernel: Fatal trap 12: page fault while in kernel mode : Dec 9 18:42:32 paris kernel: fault virtual address = 0x30 : Dec 9 18:42:32 paris kernel: fault code = supervisor write, pag\ : e not present : Dec 9 18:42:32 paris kernel: instruction pointer = 0x8:0xc07b01f2 : Dec 9 18:42:32 paris kernel: stack pointer = 0x10:0xd5428c10 : Dec 9 18:42:32 paris kernel: frame pointer = 0x10:0xd5428c14 : Dec 9 18:42:32 paris kernel: code segment = base 0x0, limit 0xfff\ : ff, type 0x1b : Dec 9 18:42:32 paris kernel: = DPL 0, pres 1, def32 1, gran 1 : Dec 9 18:42:32 paris kernel: processor eflags = interrupt enabled, resume, IO\ : PL = 0 : Dec 9 18:42:32 paris kernel: current process = 38 (cbb1) : Dec 9 18:42:32 paris kernel: trap number = 12 : Dec 9 18:42:32 paris kernel: panic: page fault : Dec 9 18:42:32 paris kernel: Uptime: 35s : Dec 9 18:42:32 paris kernel: Cannot dump. No dump device defined. : Dec 9 18:42:32 paris kernel: Automatic reboot in 15 seconds - press a key on t\ : he console to abort : : : Any ideas How I can fix this? The suggested sysctl, : hw.pci.allow_unsupported_io_range, does not seem to exist in the kernel. Try 6.0 or a recent 7.0 snapshot. A bug similar to this has been fixed. Warner