From owner-freebsd-stable Tue Feb 20 17: 8:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id A334937B401 for ; Tue, 20 Feb 2001 17:08:53 -0800 (PST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.2/8.11.2) with ESMTP id f1L18cg03733; Tue, 20 Feb 2001 20:08:42 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010220200722.02fb4398@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 20 Feb 2001 20:08:37 -0500 To: Steve Horan , freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: dmesg flakeyness In-Reply-To: <20010221120436.W44375@goldenterrace.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:04 PM 2/21/2001 +1100, Steve Horan wrote: >After booting, dmesg works fine, as normal, but after a while, if I do >another dmesg, I get only the last entry, and often the first few >characters are missing. This is a bug in ipfw. Have a look at the ongoing thread below >From: Luigi Rizzo >Message-Id: <200102200330.f1K3UJC42482@iguana.aciri.org> >Subject: Re: Solved: Bridging and dummynet seems to destroy dmesg output >In-Reply-To: <20010220112154.A26373@outblaze.com> from Yusuf Goolamabbas >at "Feb 20, 2001 11:21:54 am" >To: yusufg@outblaze.com (Yusuf Goolamabbas) >Date: Mon, 19 Feb 2001 19:30:19 -0800 (PST) >Cc: jonny@jonny.eng.br, rizzo@aciri.org, freebsd-net@FreeBSD.ORG, > freebsd-stable@FreeBSD.ORG, phk@FreeBSD.ORG, dwmalone@FreeBSD.ORG >X-Mailer: ELM [version 2.4ME+ PL43 (25)] >MIME-Version: 1.0 >Content-Type: text/plain; charset=ISO-8859-1 >Content-Transfer-Encoding: 8bit >Sender: owner-freebsd-stable@FreeBSD.ORG >X-Loop: FreeBSD.ORG >Precedence: bulk >X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (amavis.org) >X-UIDL: HGg!!~\~"!-*]!!IX%"! > > > Luigi, PHK > > > > Any resolution on this ? > >for sure there is no bug in ip_fw.c -- the change mentioned below just >happens to change some symptoms but is no fix. > >The message buffer is not "busted" as the report says, just has >some NULs here and there that (probably) dmesg is not handling >correctly. Poul, do you know more ? > > cheers > luigi -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message