From owner-freebsd-alpha Fri Jun 21 5:37:40 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from courriel.etsmtl.ca (courriel.etsmtl.ca [142.137.3.24]) by hub.freebsd.org (Postfix) with ESMTP id 6B07E37B40D for ; Fri, 21 Jun 2002 05:37:33 -0700 (PDT) Received: from dactyl (142.137.20.176 [142.137.20.176]) by courriel.etsmtl.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id MAQKTM1M; Fri, 21 Jun 2002 08:37:24 -0400 From: "Normand Leclerc" To: Subject: RE: Serial console dying, 4.5 - 4.6 Date: Fri, 21 Jun 2002 08:37:11 -0400 Message-ID: <000501c21920$5fefe3c0$b014898e@dactyl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <20020619130607.GM43253@cicely5.cicely.de> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Yes, I can see messages from echo to console and ttyd0 and I can see kernel messages. What I don't understand is why would the machine fall in debug? And I don't see any abnormal reboots either (uptime is fine). To get the console back, a shutdown -r does fine. Oh, and yes, I have a PC164... Actually a 164sx. The only thing I can find is that the host on which the serial console is directed to is not always turned on. My null modem has all the lines (e.g. CTS/RTS/DTR) Normand Leclerc > -----Original Message----- > From: owner-freebsd-alpha@FreeBSD.ORG [mailto:owner-freebsd- > alpha@FreeBSD.ORG] On Behalf Of Bernd Walter > Sent: June 19, 2002 9:06 AM > To: Normand Leclerc > Cc: freebsd-alpha@FreeBSD.ORG > Subject: Re: Serial console dying, 4.5 - 4.6 > > On Wed, Jun 19, 2002 at 08:42:17AM -0400, Normand Leclerc wrote: > > I have already reported this. My serial console works fine then, for > > no reason, it drops dead. > > > > I have a new thought about what is going on: my sio0 is falling into > > low level console. Neither I or getty can access the device because it > > is busy but the kernel can (sends some syslog messages). What could > > make the serial console drop from flag 0x30 to 0x40 ? > > It's known that on some machines the serial fails after breaking into > debugger and rebooting from there - you need a hard reset in that case. > E.g. on PC164. > > Can you echo foo > /dev/console > and/or echo foo > /dev/ttyd0 ? > > Do you see kernel messages? > e.g. tcpdump and look out for promiscuous message. > > The sio flags are irelevant as the important ones are only checked at > kernel start. > > -- > B.Walter COSMO-Project http://www.cosmo-project.de > ticso@cicely.de Usergroup info@cosmo-project.de > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message