Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Sep 2000 12:55:32 -0600
From:      joe.loughry@lmco.com
To:        Joe.Warner@smed.com
Cc:        freebsd-hackers@freebsd.org
Subject:   re: /dev/cuaa0 locks my system up..Help!
Message-ID:  <784F51866054D4118E8A00508BDF581A8DB998@emss02m02.ems.lmco.com>

next in thread | raw e-mail | index | archive | help
I had some weird serial port problems myself a few days ago.  I was having
an (unrelated) problem with a PCI video card, and I swapped it to a
different
PCI slot on the advice of the manufacturer, which fixed the problem, but
also
caused my VGA card to change *it's* interrupt, which grabbed the same
interrupt as one of my serial ports.

The symptoms were, sometimes FreeBSD would identify the serial port on
bootup, and sometimes it wouldn't see it at all.  I would get a login banner
on the terminal connected to that serial port when the system was booted,
but the terminal wouldn't respond to keystrokes at all.

Anyway, do this:

	dmesg | grep -i irq

and look for two devices using the same IRQ number.  Maybe that's it.

-Joe Loughry
loughry@uswest.net

> Regardless of what application I use to access my serial port
(/dev/cuaa0),
> when I do, it causes my system to freeze up.  CTRL + ALT + BACKSPACE
> doesn't work, CTRL + ALT + F2 doesn't work,..you get the picture.  When my
> system freezes like this, my only alternative is to do a cold reboot and I
> don't think this is too healthy a practice for any OS.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?784F51866054D4118E8A00508BDF581A8DB998>