Date: Wed, 8 Mar 2006 21:25:35 +0300 (MSK) From: Oleg Sharoiko <os@rsu.ru> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-scsi@freebsd.org, Andrey Beresovsky <and@rsu.ru> Subject: Re: Boot hangs on ips0: resetting adapter, this may take up to 5 minutes Message-ID: <20060308203504.W717@wolf.os.rsu.ru> In-Reply-To: <200603071609.18149.jhb@freebsd.org> References: <20060215102749.D58480@brain.cc.rsu.ru> <200603071343.23672.jhb@freebsd.org> <20060307223407.M722@wolf.os.rsu.ru> <200603071609.18149.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Oleg Sharoiko. Software and Network Engineer Computer Center of Rostov State University.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060308203504.W717>