Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Nov 2009 08:00:13 -0600
From:      Karl Denninger <karl@denninger.net>
To:        Mike Tancsa <mike@sentex.net>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: V8.x-PRE2 Serious PUC problem - Heads Up!
Message-ID:  <4B054F6D.70300@denninger.net>
In-Reply-To: <200911191357.nAJDvd3X095748@lava.sentex.ca>
References:  <4B054DCC.6020701@denninger.net> <200911191357.nAJDvd3X095748@lava.sentex.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------080409010609040000060607
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Mike Tancsa wrote:
> At 08:53 AM 11/19/2009, Karl Denninger wrote:
>
>> I will update as I have more information - this is a serious issue for
>> anyone who needs working serial ports on multiport cards under FreeBSD
>> for things like a fax server..... this is not the sort of "surprise" one
>> wants to see!
>
> Its not the puc per se as the transition from sio to uart
>
> from /usr/src/UPDATING
>
> 20080713:
>         The sio(4) driver has been removed from the i386 and amd64
>         kernel configuration files. This means uart(4) is now the
>         default serial port driver on those platforms as well.
>
>         To prevent collisions with the sio(4) driver, the uart(4) driver
>         uses different names for its device nodes. This means the
>         onboard serial port will now most likely be called "ttyu0"
>         instead of "ttyd0". You may need to reconfigure applications to
>         use the new device names.
>
>         When using the serial port as a boot console, be sure to update
>         /boot/device.hints and /etc/ttys before booting the new kernel.
>         If you forget to do so, you can still manually specify the hints
>         at the loader prompt:
>
>                 set hint.uart.0.at="isa"
>                 set hint.uart.0.port="0x3F8"
>                 set hint.uart.0.flags="0x10"
>                 set hint.uart.0.irq="4"
>                 boot -s
Well ok then the uart driver is BROKEN.

It simply locks up on the port after some period of time, returning
nothing.  I have found no way to reset the port other than a reboot
either.  That's a "surprise" that people running fax servers and other
similar things are going to be very unhappy about.

-- Karl

--------------080409010609040000060607--





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