From owner-freebsd-bugs Sun Oct 21 0:30: 4 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7DF4237B403 for ; Sun, 21 Oct 2001 00:30:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f9L7U2130443; Sun, 21 Oct 2001 00:30:02 -0700 (PDT) (envelope-from gnats) Date: Sun, 21 Oct 2001 00:30:02 -0700 (PDT) Message-Id: <200110210730.f9L7U2130443@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: i386/30965: Cyclades Cyclom-Yep causes FreeBSD to hang during boot Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR i386/30965; it has been noted by GNATS. From: Bruce Evans To: Scott Klement Cc: Subject: Re: i386/30965: Cyclades Cyclom-Yep causes FreeBSD to hang during boot Date: Sun, 21 Oct 2001 17:19:24 +1000 (EST) On Fri, 19 Oct 2001, Scott Klement wrote: > The BIOS does not show any IRQ conflicts. The dmesg also does not show any > IRQ conflicts. (But perhaps something is responding on IRQs that it > shouldnt? I wish I knew more about how this works...) Do you mean it desn't show any shared IRQs? PCI IRQs can't really conflict. Shareing them is supposed to work. > I can certainly send you a dmesg if that will help. I could also send > the e-mail conversation that I had with the Tech Support person at > Cyclades about this.. would that help? Start with the complete dmesg for booting with -v, and "pciconf -lv" output. Did the Tech Support seem helpful? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message