Date: Fri, 26 Feb 1999 09:52:33 -0800 From: Mike Smith <mike@smith.net.au> To: Andrew Heybey <ath@niksun.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Advice wanted on tracking down bug (or hw problem?) in 3.1R Message-ID: <199902261752.JAA08432@dingo.cdrom.com> In-Reply-To: Your message of "Thu, 25 Feb 1999 14:35:23 EST." <199902251935.OAA06361@stiegl.niksun.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I have just submitted PR kern/10243, but I thought I would ask for > some advice on hackers as well. > > The bug is that under certain loads, read(2) can return corrupted data > (ie data that are not in the file on disk). The instances I have seen > are relatively small amounts (8-64 bytes) of corrupt data at the end > of a 4k page. The corrupt data is from a file previously read or > another position in the current file. I have also seen this problem > in 3.0-RELEASE but not in 2.2.8-RELEASE. Can you look at the corrupt data and see if you can identify it? In particular, look for objects that look like IP addresses, MAC addresses, pointers into kernel space, ascii text, etc. This is usually the best way to work out where the data is coming from. > I would sure appreciate it if someone with a larger collection of > clues than I would take a look at this or give me some advice as to > where I should start looking. We do appear to have at least one 'sniper' bug in the kernel at the moment; this might be the same one or another. -- \\ 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-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902261752.JAA08432>