Date: Wed, 06 Oct 2004 18:50:20 +0200 From: Jonas Nagel <fireball@zerouptime.ch> To: Brooks Davis <brooks@FreeBSD.org> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/72263: gifconfig output corruption Message-ID: <20041006184527.20BB.FIREBALL@zerouptime.ch> In-Reply-To: <200410041506.i94F6k3N063672@freefall.freebsd.org> References: <200410041506.i94F6k3N063672@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Submitter requested we close this since it's going to be hard to
> reproduce assuming it is a memory corruption bug. We'll reopen if
> we can find a way to reproduce this.
Ok, well let's reopen this. I just upgraded to 4.10-RELEASE-p3 just to
make sure I didn't fsck up somewhere, and it seems like I can reliably
repeat the issue;
FreeBSD got.zerouptime.ch 4.10-RELEASE-p3 FreeBSD 4.10-RELEASE-p3 #0:
Wed Oct 6 02:49:24 CEST 2004 root@www.zerouptime.ch:/usr/obj/usr/src/sys/F=
W
i386
got# ls -l `which gifconfig`
-r-xr-xr-x 1 root wheel 11432 Oct 6 18:08 /usr/sbin/gifconfig
got# ls -l `which ifconfig`
-r-xr-xr-x 1 root wheel 280788 Oct 6 18:05 /sbin/ifconfig
The corrupted part in the gifconfig remains the same ("physical address z=
=B8P=D5 -->")
apparently.
And the ifconfig output is still empty, too.
--=20
Jonas Nagel <fireball@zerouptime.ch>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041006184527.20BB.FIREBALL>