From owner-freebsd-bugs Sat Mar 20 22:30:48 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 65F5F15302 for ; Sat, 20 Mar 1999 22:30:43 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id WAA09905; Sat, 20 Mar 1999 22:30:25 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sat, 20 Mar 1999 22:30:25 -0800 (PST) Message-Id: <199903210630.WAA09905@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Subject: kern/10673: Non-ASCII chars on serial console with RealTek 8139 at 100M FD. Reply-To: Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/10673; it has been noted by GNATS. From: To: FreeBSD-gnats-submit@freebsd.org Cc: Subject: kern/10673: Non-ASCII chars on serial console with RealTek 8139 at 100M FD. Date: Fri, 19 Mar 1999 17:17:56 +0000 >Number: 10673 >Category: kern >Synopsis: Non-ASCII chars on serial console with RealTek 8139 at 100M FD. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Mar 19 09:20:02 PST 1999 >Closed-Date: >Last-Modified: >Originator: Paul Rose >Release: FreeBSD 3.1-STABLE i386 from just before 1st March 1999. >Organization: >Environment: Apologies for not knowing the exact day of the release, or any appropriate CVS IDs to include. The machine has a RealTek 8139 10/100BaseTX card. The console is via the serial port, and /boot/loader.rc contains 'set console=comconsole'. sio0 has the following entry in the kernel config. device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 The link between the NIC and the switch is 100Mbps full duplex. The following line is contained in /etc/rc.conf, which I've broken up here onto two lines. ifconfig_rl0="inet 194.159.80.4 netmask 0xfffffff8 media 100baseTX mediaopt full-duplex" >Description: Upon booting the machine, all the relevant boot messages appear via the serial console. It detects the RealTek card, and sets it up initially as 10Mbps half-duplex. During the init scripts, when rc.network is run to configure the interfaces it gets this far: Doing initial network setup: hostname lo0 and then begins to output non-ASCII and control characters to the serial console such that the console becomes unreadable, though it does continue to boot. Logging into the machine, checking dmesg, and the interface shows that it has set itself to 100Mbps full-duplex and appears to work correctly. Booting with boot -v gives the following for rl0 rl0: rev 0x10 int a irq 19 on pci0.9.0 using shared irq19. rl0: Ethernet address: 00:a0:d2:1a:b7:65 rl0: PHY status word: 782d rl0: 10Mbps half-duplex mode supported rl0: 10Mbps full-duplex mode supported rl0: 100Mbps half-duplex mode supported rl0: 100Mbps full-duplex mode supported rl0: autoneg supported rl0: autoneg complete, link status good (half-duplex, 10Mbps) bpf: rl0 attached On leaving the media and mediaopt options from ifconfig_rl0, the card defaults itself to 10Mbs half-duplex and when rc.network is run outputs only ASCII chars as expected and does not lead to the same 'rubbish' on the serial console. Only when the card was set to 100Mbps full-duplex did the non-ASCII chars get printed via the serial console. This was repeatable each time the machine was rebooted. The problem was not present when a different brand/make of NIC was swapped with the RealTek, and set to 100Mbps full-duplex. >How-To-Repeat: Hopefully this will be repeatable each time you reboot a machine that has its console go via the serial port, and has a RealTek 8139 card which you have to set to 100Mbps full-duplex through rc.conf. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message