Date: Fri, 19 Oct 2001 16:20:08 -0700 (PDT) From: Scott Klement <klemscot@klements.com> To: freebsd-bugs@FreeBSD.org Subject: Re: i386/30965: Cyclades Cyclom-Yep causes FreeBSD to hang during boot Message-ID: <200110192320.f9JNK8610463@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/30965; it has been noted by GNATS.
From: Scott Klement <klemscot@klements.com>
To: Bruce Evans <bde@zeta.org.au>
Cc: <FreeBSD-gnats-submit@FreeBSD.ORG>
Subject: Re: i386/30965: Cyclades Cyclom-Yep causes FreeBSD to hang during
boot
Date: Fri, 19 Oct 2001 18:16:27 -0500 (CDT)
On Thu, 18 Oct 2001, Bruce Evans wrote:
> On Thu, 27 Sep 2001, Scott Klement wrote:
>
> > The same problem occurs in 4.2-RELEASE and 4.3-RELEASE as well.
> > Problem has occurred on Dell OptiPlex GX100 and GX150.
> >
> > >Description:
> > System will stop responding ("hard-lock") while probing devices
> > as part of the booting process whenever a Cyclades Cyclom-Y/PCI
> > card is installed & configured in the kernel.
>
> -current has a small chance of working better (it has an updated pci
> probe for this driver), but I suspect the problem is with interrupt
> configuration and the driver doesn't have any significant changes
> related to that.
I'll have to try upgrading to -current, then. I'll let you know how
that turns out.
> I have seen hangs like this under Linux but not under FreeBSD. Linux
> hung on a BP6 motherboard when the YeP interrupt was shared with the
> second disk controller. This was presumably because the ide disk
> driver and/or the cy driver under Linux couldn't handle shared interrupts.
> I spent a lot of time shuffling pci cards to unshare the relevant
> interrupts (the BP6 BIOS strongly prefered to map the YeP interrupt
> to a bad place, perhaps because the YeP claims to be a "simple" serial
> card). Perhaps FreeBSD has the same problem but with a different driver
> (OTOH, a problem with interrupt sharing in the FreeBSD ata disk driver
> was fixed very recently).
I've set this computer up for dual-boot between RedHat 7.1 and FreeBSD.
The setup works, as-is, in RedHat. (I don't know if saying that helps you
troubleshoot the issue at all.)
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...)
> > The same symptom occurs both when "options CY_PCI_FASTINTR" is
> > enabled in the kernel and also when it is not enabled.
>
> This shouldn't matter much, but debug without it anyway.
>
> > I believe that this is a software issue because the problem
> > does NOT occur under RedHat Linux, on the same machines. I've
> > tried it with 3 different (known working) Cyclades units,
> > and with 3 different computers (2 Dell Optiplex GX100, 1 GX150)
> >
> > The same Cyclades units do work under FreeBSD with a different
> > (non-Dell) computer system.
>
> You will have to debug this further by finding the relevant differences.
> Apart from interrupt configuration, it's possible that the Dell BIOS
> maps something in a way that the driver doesn't understand, but this is
> less likely.
>
> Bruce
I'd be happy to search for the relevant differences -- but I've tried
everything that I can think of. Troubleshooting down at the driver level
is a bit over my head. :(
I've already tried removing or disabling all of the PCI devices on
the machine except for video and IDE, but it still hangs.
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?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110192320.f9JNK8610463>