From owner-freebsd-questions Mon Apr 24 11:16:52 2000 Delivered-To: freebsd-questions@freebsd.org Received: from penguin.filetron.com (mail.filetron.com [206.171.92.89]) by hub.freebsd.org (Postfix) with SMTP id 0EF0837BBD1 for ; Mon, 24 Apr 2000 11:16:45 -0700 (PDT) (envelope-from drew@kmfms.com) Received: (qmail 13843 invoked from network); 24 Apr 2000 17:11:10 -0000 Received: from ns1.filetron.com (httpd@206.171.92.1) by mail.filetron.com with SMTP; 24 Apr 2000 17:11:10 -0000 Received: (from httpd@localhost) by ns1.filetron.com (8.8.7/8.8.7) id KAA30851; Mon, 24 Apr 2000 10:17:37 -0700 Date: Mon, 24 Apr 2000 10:17:37 -0700 Message-Id: <200004241717.KAA30851@ns1.filetron.com> Content-Type: text/plain Content-Disposition: inline Mime-Version: 1.0 X-Mailer: MIME-tools 4.103 (Entity 4.115) From: drew To: freebsd-questions@freebsd.org Subject: Re: usb -> kernel panic: fatal trap 12 during boot (FIXED) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Problem solved. My hunch about the IRQ issue proved to be correct. Synopsis: The Abit BP-6 mainboard is not very careful in automatic distribution of device IRQs. If the USB controller's IRQ is shared with another device, fatal trap 12 occurs when attempting to initialize the controller during bootstrap. This is not immediately obvious, even when looking at "dmesg | grep irq". With the BP-6, you can see the problem in the "PCI device list" printed just before bootstrap. The solution is to explicitly set the IRQ of the USB controller or the conflicting device in the BIOS to another, unused value. The original problem ocurred when attempting to add support for a USB Iomega ZIP 100 drive, in 4.0R GENERIC kernel with SMP and USB enabled. Dmitry Kavarov related a similar problem and confirmed my suspicion re: device IRQs in another forum. He saved me a day of kernel debugging. Thanks, Dmitry. Other users I talked to reported similar problems on notebook computers, so this default shared-IRQ problem is ny no means only related to the BP-6. I don't think it's very smart of mainboard manufacturers to have problemic default settings like that. Especially the Abit BP-6, which actually mentions FreeBSD as a supported OS in its manual. I'm not sure if Hibma and crew have an FAQ providing solutions to common USB problems. If so, this would probably be a good addition, as the BP-6 is a popular board, and I didn't find the problem to be self-evident (in my experience, it usually takes more than an IRQ fudge to panic a modern *BSD kernel). I'm just glad it was something "slap your forehead and say 'doh!'" instead of something "fix it in the next stable kernel". ;-) -------------->>> SIG: i don't use linux. please ignore the message below. i needed the web-based email, that's all. ---------------------- Do you do Linux? :) Get your FREE @linuxstart.com email address at: http://www.linuxstart.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message