< I noticed it since last summer, too. Using both vi and vile.
I have not seen it recently. My most recent crashes all involve
triple-faults. A new machine, running very fresh -current, hasn't been
up for long enough to evoke this bug. (It did spend much of the last
96 hours compiling crappy
On Sat, 26 Jan 2002, David O'Brien wrote:
> On Fri, Jan 25, 2002 at 03:51:08PM -0800, Jos Backus wrote:
> > Recent -current on my system at work exhibits processes getting stuck in the
> > ``inode'' state, causing the system to become unusable and requiring a reboot.
> >
> > I have been seeing thi
On Sat, Jan 26, 2002 at 02:43:24AM -0800, David O'Brien wrote:
> I have been living with this in -CURRENT since mid-summer. I am lucky to
> have 1 week uptimes.
Wow. My home system seems to do much better than that and I track -current
very closely on both my home and work system. But I'm not us
> On Fri, Jan 25, 2002 at 03:51:08PM -0800, Jos Backus wrote:
> > Recent -current on my system at work exhibits processes getting stuck in the
> > ``inode'' state, causing the system to become unusable and requiring a reboot.
> >
> > I have been seeing this for about a week now; anyone else?
>
On Fri, Jan 25, 2002 at 03:51:08PM -0800, Jos Backus wrote:
> Recent -current on my system at work exhibits processes getting stuck in the
> ``inode'' state, causing the system to become unusable and requiring a reboot.
>
> I have been seeing this for about a week now; anyone else?
I have been l
Recent -current on my system at work exhibits processes getting stuck in the
``inode'' state, causing the system to become unusable and requiring a reboot.
I have been seeing this for about a week now; anyone else?
--
Jos Backus _/ _/_/_/Santa Clara, CA
