Date: Wed, 04 Mar 1998 16:13:52 -0800 From: Mike Smith <mike@smith.net.au> To: Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au> Cc: shimon@simon-shapiro.org, current@FreeBSD.ORG Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) Message-ID: <199803050013.QAA22992@dingo.cdrom.com> In-Reply-To: Your message of "Thu, 05 Mar 1998 10:30:05 %2B1030." <34FDEB05.9CA1F531@dsto.defence.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> There was a time when it didn't happen at all...hmmm was that 2.1R ? > or maybe 2.2-CURRENT sometime after that. Yeah, before the message was actually printed. Let's take all those annoying warning messages out of the kernel, so that you can't tell what is going wrong. It works for Microsoft, after all. > Simon Shapiro wrote: > > > > How about getting rid of that ``%d more silo overflow..'' message? I am > > too limited in my understanding device drivers to see why that happens. You could try reading the manpage, just for starters. > > I though that UARTs and RS-232C were well understood. Na und? They're sufficiently well understood for unrecoverable error conditions to be detected and reported. What more do you want? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803050013.QAA22992>