On 2 May, I wrote: > On 2 May, Scott A. Moberly wrote: >> On Fri, May 02, 2003 at 01:43:34PM -0700, Don Lewis wrote: >>> I haven't seen it on my 4/26 machine, though I haven't done anything >>> disc intensive (other than the daily cron jobs) since then. The reports >>> of this problem started showing up on 4/27, so I went hunting for >>> commits during the likely window using cvs diff. There were a number of >>> vm locking changes made during that time, including some changes to >>> vfs_bio.c. That's about as close as anything came to touching the >>> filesystem code. >> >> Just to give a definate start point: >> >> /Makefile.inc1/1.349/Fri May 2 18:26:15 2003//D2003.04.26.05.00.00 >> >> works fine. > > Mine is somewhat newer than that, about 2003.04.27.02.00.00 UTC. I just > ran a buildworld and unpacked ports.tgz and didn't run into any > problems. I'll try stepping forward about 12 hours ... Interesting ... I'm having problems reproducing this problem. The first report of this bug landed in my inbox at about 15:12 UTC on April 27. Someone else who reported the bug claimed to have cvsup'ed at about 10:00 UTC on that day. I just did cvs -R update -Pd -D'4/27/2003 14:00:00 UTC' make buildworld make buildkernel make installkernel and rebooted. I haven't managed to trigger the problem with a simultaneous buildworld and untaring ports.tgz. I even suspected that this problem might be triggered by free memory pressure so I added hw.physmem="128M" to /boot/loader.conf and rebooted. I've pushed the machine heavily into paging, but it still seems to be stable, but painfully sluggish. I just did a cvs diff, and the only change between 14:00 UTC and 16:00 UTC is a patch to if_wi.c.Received on Sat May 03 2003 - 00:43:01 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:06 UTC