Date: Thu, 1 Feb 2001 11:40:07 -0800 (PST) From: Luigi Rizzo <rizzo@aciri.org> To: jonny@jonny.eng.br (Joao Carlos Mendes Luis) Cc: rizzo@aciri.org, yusufg@outblaze.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: Solved: Bridging and dummynet seems to destroy dmesg output Message-ID: <200102011940.f11Je7561000@iguana.aciri.org> In-Reply-To: <3A79B707.3DF0B6D@jonny.eng.br> from Joao Carlos Mendes Luis at "Feb 1, 2001 5:20:39 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
thanks for tracking this problem -- it also explains why i did not see it in my environment, as i have a mostly 4.2-R system with new code in net/ and netinet/ cheers luigi > Hi, > > I found the problem! > > I started searching for the point where ipfw writes to the msgbuf, and > like all other kernel modules, it uses the log(9) function. But differently > from the other modules, ip_fw.c uses a LOG_SECURITY argument. I removed it, > recompiled, reboot, and BINGO! Probably the log(9) function does not expect a > facility parameter, as it is assumed to be LOG_KERNEL. > > Searching the cvsweb tree, I assume the changes that made it fail were > made to kern/subr_prf.c, and not directly to netinet/ip_fw.c. Probably a > longer search should be made to detect if any other call to log(9) uses this > approach. (CC: to phk, who made the change to kern/subr_prf.c, 1.61.2.1, at > 2000.01.16) > > Hoping this is the final solution and waiting for the cvs commit, thanks > to everybody, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102011940.f11Je7561000>