Re: Severe problem with amd64 -current as of June 13

2013-06-16 Thread STeve Andre'
On 06/16/13 01:05, Philip Guenther wrote: On Sat, Jun 15, 2013 at 7:19 PM, STeve Andre' wrote: On June 13 I updated my tree from 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 p

Re: Severe problem with amd64 -current as of June 13

2013-06-15 Thread STeve Andre'
On 06/16/13 01:05, Philip Guenther wrote: On Sat, Jun 15, 2013 at 7:19 PM, STeve Andre' wrote: On June 13 I updated my tree from 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 p

Re: Severe problem with amd64 -current as of June 13

2013-06-15 Thread Philip Guenther
On Sat, Jun 15, 2013 at 7:19 PM, STeve Andre' wrote: >On June 13 I updated my tree from 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, alb

Re: Severe problem with amd64 -current as of June 13

2013-06-15 Thread STeve Andre'
On 06/16/13 00:23, Amit Kulkarni wrote: > > > > On Sat, Jun 15, 2013 at 9:19 PM, STeve Andre' > 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

Severe problem with amd64 -current as of June 13

2013-06-15 Thread STeve Andre'
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, and the new -current failed shortly after running it. Things would get *very* slow, with co