From owner-freebsd-bugs Fri Aug 24 11:50: 9 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 13BD537B411 for ; Fri, 24 Aug 2001 11:50:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f7OIo1Y96045; Fri, 24 Aug 2001 11:50:01 -0700 (PDT) (envelope-from gnats) Received: from Daffy.timing.com (daffy.timing.com [206.168.13.218]) by hub.freebsd.org (Postfix) with ESMTP id 982B537B40D for ; Fri, 24 Aug 2001 11:40:45 -0700 (PDT) (envelope-from imp@timing.com) Received: from marvin.timing.com (root@marvin.timing.com [206.168.13.207]) by Daffy.timing.com (8.9.3/8.9.3) with ESMTP id MAA20614 for ; Fri, 24 Aug 2001 12:40:45 -0600 (MDT) (envelope-from imp@timing.com) Received: (from imp@localhost) by marvin.timing.com (8.11.6/8.9.3) id f7OIgfL09254; Fri, 24 Aug 2001 12:42:41 -0600 (MDT) (envelope-from imp) Message-Id: <200108241842.f7OIgfL09254@marvin.timing.com> Date: Fri, 24 Aug 2001 12:42:41 -0600 (MDT) From: "M. Warner Losh" Reply-To: "M. Warner Losh" To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: kern/30049: Bad iomem assigned in some cases. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 30049 >Category: kern >Synopsis: Bad iomem assigned in some cases. >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Aug 24 11:50:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: M. Warner Losh >Release: FreeBSD 4.4-RC >Organization: None >Environment: Laptop >Description: > : nsp0 at port 0x240-0x24f iomem 0xc8800-0xc97ff irq 5 slot 0 on pccard0 > : ^^^^^^^^^^^^^^^ > Nothing should have changed in the memory allocation scheme. The > above address looks wrong to me. Maybe it was with the addition of > the orm device and that 0xc8000 was taken. Maybe we're not aligning > things properly (since the memory needs to be 4k aligned, iirc, at the > bridge level). > > Do you have a orm device? If so, what does it say? Yes, jm3wud@cel% dmesg | grep orm orm0: