From owner-freebsd-stable@FreeBSD.ORG Fri Dec 19 09:50:55 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F1516A4CE for ; Fri, 19 Dec 2003 09:50:55 -0800 (PST) Received: from pol.dyndns.org (pol.net1.nerim.net [80.65.225.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 026ED43D41 for ; Fri, 19 Dec 2003 09:50:52 -0800 (PST) (envelope-from guy@device.dyndns.org) Received: from pissenlit.device.local ([172.16.10.66]) by pol.dyndns.org (8.12.9/8.12.9) with ESMTP id hBJHoWdK013927 for ; Fri, 19 Dec 2003 18:50:33 +0100 (CET) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <004601c3c597$86fd0bd0$a2800551@ninja> Date: Fri, 19 Dec 2003 18:50:32 +0100 (CET) From: guy@device.dyndns.org To: freebsd-stable@freebsd.org X-Virus-Scanned: by amavis-milter (http://www.amavis.org/) Subject: RE: SMP forcing crash/reboot in 4.9-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2003 17:50:55 -0000 On 18-Dec-2003 Alasdair Lumsden wrote: >> This may be related to my problem, though the symptom is different. >> >> Since the same time (around the end of november) i tried many times to >> build a SMP-enabled 4.9-STABLE kernel for my bi-athlon machine. It > always >> hangs (no error msg, total iresponsiveness) at the end of the kernel > boot >> (just before mounting filesystems). >> >> I then reverted my cvs tree to use -RELEASE, and all is fine. >> >> I did not yet try a non-SMP kernel. I'll do that asap. > > Just a note - I believe SMP+APIC causes IRQ routing to be handled > differently compared with a non SMP kernel. We had a problem on one of > our boxes where after enabling SMP, the box would hang when trying to > mount the file systems. > > The cause was traced to the raid card we had installed, which was in a > riser card off of the motherboard (Rackmount server). Plugging the raid > card directly into the motherboard resolved the problem, as did moving > the card to the bottom slot of the riser card. > > I have no idea if this is related to your problem, but it did take us > hours of troubleshooting to work out this was what was wrong. This may prove a valuable information, as i have many PCI cards in that machine, amongst which lay a RAID card too. I may not have many choice to move it around as it is a PCI-64 (from memory, think only 2 of my PCI slots are 64 wide). Anyway, will try that (and the serial console heavy debuging session if the former is not enuf to fix the problem) as soon as i can spend a few hours on that machine. Thanks everybody for the help. -- Guy