From owner-freebsd-scsi@FreeBSD.ORG Wed Mar 8 20:11:22 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1EDD16A420 for ; Wed, 8 Mar 2006 20:11:22 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 185F243D46 for ; Wed, 8 Mar 2006 20:11:21 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k28KBIud037578; Wed, 8 Mar 2006 15:11:19 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Oleg Sharoiko Date: Wed, 8 Mar 2006 13:53:59 -0500 User-Agent: KMail/1.9.1 References: <20060215102749.D58480@brain.cc.rsu.ru> <200603071609.18149.jhb@freebsd.org> <20060308203504.W717@wolf.os.rsu.ru> In-Reply-To: <20060308203504.W717@wolf.os.rsu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603081354.02233.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1318/Tue Mar 7 15:55:18 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Mar 2006 20:11:22 -0000 On Wednesday 08 March 2006 13:25, Oleg Sharoiko wrote: > > On Tue, 7 Mar 2006, John Baldwin wrote: > > JB>Actually, the real issue is that GENERIC amd64 doesn't include device atpic > JB>in HEAD, but does on 6.x. And what is actually happening is that without > JB>APIC, there is no interrupt controller at all, and thus no interrupts. You > JB>will need to add 'device atpic' to your kernel config on HEAD for amd64 to > JB>test the non-APIC case. But really, the APIC case should be fixed. > > Yes, that was it. With atpic it works. > > JB>So amd64 is busted in both the UP and SMP cases with APIC enabled, yes? > > Yes, and UP kernel behaves even more weird than SMP does. Boot goes > further than "lo0: bpf attached" but starting from this line it gets very > slow and continues with huge timeouts. It passes "ips0: resetting adapter, > this may take up to 5 minutes" and gets to "start_init: trying /sbin/init" > where it stops forever. Well, probably not forever, but I didn't get > anything else from it during at least 30 minutes. > > Logs are available: > 1. i386 with UP kernel http://rsu.ru/~os/ips/boot.2006-03-08.i386.UP.txt > 2. amd64 with UP kernel http://rsu.ru/~os/ips/boot.2006-03-08.amd64.UP.txt > 3. output from mptable http://rsu.ru/~os/ips/mptable.txt > > I suppose in amd64/UP case ips gets its interrupts, but some other devices > don't. So, atpic works ok, but amd64 + APIC doesn't work in either UP or SMP, but i386 + APIC does work fine, and all the interrupts are routed identically, etc. What happens if you do 'hw.physmem=2g' and boot an amd64 kernel with APIC? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org