On 06/16/13 00:23, Amit Kulkarni wrote: > > > > On Sat, Jun 15, 2013 at 9:19 PM, STeve Andre' <and...@msu.edu > <mailto:and...@msu.edu>> wrote: > > amd64-current seems rather wounded at the moment. I've been > running -current since June 5th with no problems. This is a W500 > thinkpad. > > On June 13 I updated my tree from anoncvs.usa.openbsd.org > <http://anoncvs.usa.openbsd.org>, and > the new -current failed shortly after running it. > > Things would get *very* slow, with continuous disk activity. > It was > sort of possible to switch between screens, albeit after a few > minutes. > Processes would be shown as in a disk wait (D). Eventually the system > freezes completely with the continuous disk activity as evidenced by > my disk LED. > > Going back to the June 5th kernel with the June 13th userland seems > to be working. Looking at the FAQ there are things for -current which > had no relevance to this problem. I then got a new copy of src and > xenocara with the same results. > > Seeing memmove and similar changes, and a fix for at least one arch > makes me wonder if amd64 has a problem. > > Suggestions? > > > i just updated a desktop PC with the 15th June snap and things were > working fine... and the June 10th packages.
Interesting. I updated my tree this afternoon, and built a new kernel which finally had the same problem. It ran for a while fine, but then got very slow and finally froze. This was after 10 or 15 minutes, long enough for me to think that things were OK. Running on the June 5th kernel right now and all is well. I'll try the June 10th snaps, but I think that's missing png? --STeve Andre'
