From owner-freebsd-mobile@FreeBSD.ORG Wed Apr 21 04:17:11 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C90A16A4CE for ; Wed, 21 Apr 2004 04:17:11 -0700 (PDT) Received: from mx1.mail.ru (mx1.mail.ru [194.67.45.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BEF143D46 for ; Wed, 21 Apr 2004 04:17:11 -0700 (PDT) (envelope-from DYZ@mail.ru) Received: from [213.24.8.115] (port=4734 helo=localhost) by mx1.mail.ru with esmtp id 1BGFj4-00009l-00; Wed, 21 Apr 2004 15:17:10 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.31, engine: 4.31, virus records: 45256, updated: 2.02.2004] Date: Wed, 21 Apr 2004 17:17:09 +0600 From: DYZ@mail.ru X-Mailer: The Bat! (v2.00.6) Personal X-Priority: 3 (Normal) Message-ID: <166117603796.20040421171709@mail.ru> To: "M. Warner Losh" In-Reply-To: <20040421.042921.106823026.imp@bsdimp.com> References: <1588696859.20040421091522@mail.ru> <91114287000.20040421162152@mail.ru> <20040421.042921.106823026.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam: Not detected cc: freebsd-mobile@freebsd.org Subject: Re[2]: [freebsd] xl0: watchdog timeout X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: DYZ@mail.ru List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2004 11:17:11 -0000 Hello M., Wednesday, April 21, 2004, 4:29:21 PM, you wrote: MWL> In message: <91114287000.20040421162152@mail.ru> MWL> DYZ@mail.ru writes: MWL> : Hello M. Warner Losh, MWL> : MWL> : Wednesday, April 21, 2004, 3:59:03 PM, you wrote: MWL> : : MWL>> In message: <1588696859.20040421091522@mail.ru> : MWL>> DYZ@mail.ru writes: : MWL>> : Why the system assign the same IRQ 11 to 2 different devices? I : MWL>> : think that's the reason of timeouts. MWL> : : MWL>> unlikely. MWL> : : MWL>> : Is there any way to handle this matter and to assign resources manually. MWL> : : MWL>> because its a great big happy pci world. These resources are wired : MWL>> that way, so that's what you get. Especially since they are on the : MWL>> same card bus bridge, and there's only one interrupt pin to use. MWL> : : MWL>> My guess is that the memory ranges assigned to the card bus bridge : MWL>> aren't quite right, which is causing the heartache. MWL> : MWL> : so what do you think how can it be fixed? MWL> That's a small chance that booting -current will fix this problem. MWL> However, there are minor known issues with ata at the moment that are MWL> being hammered out. MWL> For the moment, you could try other addresses for the hw.cbb.start_mem MWL> resource you were setting. in what way? how can i check the current setting for hw.cbb.start_mem? # kenv hw.cbb.start_mem kenv: unable to get hw.cbb.start_mem MWL> Warner -- Best regards, DYZ mailto:DYZ@mail.ru