On Jan 13,  9:11am, jmmv@menta.net ("Julio M. Merino Vidal") wrote:
-- Subject: Re: System freeze

| Ugh, it happened again.  This time I exited X windows just when starting
| to notice problems (the audio player for example stopped playing) and
| X became irresponsible (though I could move the mouse).
| 
| When in the console, I saw that message appearing continuously, but it
| didn't crash.  I.e., I had no network connectivity at all, and some
| apps were stalled (kill -9 couldn't kill them):
| 
| Jan 13 00:27:09 dawn /netbsd: vr0: unable to allocate Tx cluster
| Jan 13 00:27:40 dawn last message repeated 32 times
| Jan 13 00:28:20 dawn last message repeated 17 times
| Jan 13 00:29:00 dawn /netbsd: nfs_timer: ignoring error 55
| Jan 13 00:29:31 dawn last message repeated 3042 times
| Jan 13 00:30:38 dawn last message repeated 6763 times
| Jan 13 00:30:38 dawn /netbsd: nfs_timer: ignoring error 50
| Jan 13 00:30:42 dawn last message repeated 371 times
| 
| (this is because I tried an 'umount /archive' during the failure, which
| is nfs-mounted.)
| 
| Well, vr seems to be kind of unstable.  I've seen multiple panics in
| xhalf() at bootup (during dhclient) since I have this card (more than
| a year), but it hadn't caused any more issues up until now :(  Dunno
| if this has something to do with my recent upgrade from 2.99.10 to
| 2.99.12.
| 

>From the messages it appears that something is leaking memory. You might
want to check the code to make sure that it does not leak.

christos