For the last couple of days I have been plagued by many many diagnostics from checkpages(), in conjunction with things like:

  rc: note: sys: trap: fault read addr=0x0 pc=0x000101c4
  rc 50675: suicide: sys: trap: fault read addr=0x0 pc=0x000101c4

The kernel print buffer holds corresponding entries like:

  coral# 10618 dns: checked 136 page table entries
  dns 10618: suicide: sys: trap: fault write addr=0x0 pc=0x00015cea
  26591 rfcmirror: checked 270 page table entries
  37326 rc: checked 51 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  47773 rc: checked 57 page table entries
  50675 rc: checked 53 page table entries
  coral# rm '#s/dns'
  coral# ndb/dns -r
  coral# 55270 rfcmirror: checked 146 page table entries
  55270 rfcmirror: checked 146 page table entries
  66218 rfcmirror: checked 146 page table entries
  70615 rfcmirror: checked 62 page table entries
  70615 rfcmirror: checked 62 page table entries
  70644 tcp567: checked 39 page table entries
  70644 tcp567: checked 39 page table entries
  71354 rfcmirror: checked 46 page table entries
  71354 rfcmirror: checked 46 page table entries


Yes, these were two different events.  These just happened to be what I captured for later reference.  Three events, really; the 'rc' complaints are from me running 'mk' in various source trees.

I have always seen these 'checked nnn page table entries' messages, but for the last couple of days they are everywhere.  And processes are failing hand-over-fist.  Forking processes in rc seems to be a sure-fire way to provoke this.  I cannot get through a 'mk' of any significant piece of software, and /n/sources/contrib/lyndon/rfcmirror is very good at borking things, too.

Is anyone else seeing this?  I'm running bleeding edge labs code, compiled from a pull from this afternoon.  (And I have been running very up-to-date labs pulls all the way along.)

This is all running in a Parallels VM on a Mac, the same VM I have been using as a terminal for several years.  What changed was switching over to a CPU kernel.  The VM has 1GB of RAM now, but was quite happy running 9pcf (vs 9pccpuf now) in 256 MB, and that terminal kernel ran the same suite of commands just fine.  (This is objtype=386.)


--lyndon