Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Oct 1995 10:31:31 +0000 ()
From:      Nik Clayton <nik@blueberry.co.uk>
To:        questions@freebsd.org
Subject:   /kernel: Null pmap (cb) at va: 0x0
Message-ID:  <199510191031.KAA00330@elbereth.blueberry.co.uk>

next in thread | raw e-mail | index | archive | help
Hi folks,

While running 2.0.5, on a Pentium with a (thought to be) dodgy chip
cache, I was in the middle a lightly loaded X session (3 xterms, running
2 shells and a copy of elm) when I tried to run Netscape 1.12.

X then promptly died on me, 

Looking /var/log/messages I see

    Oct 19 10:00:01 elbereth /kernel: Null pmap (tb) at va: 0x0
    Oct 19 10:00:01 elbereth last message repeated 6 times
    Oct 19 10:00:01 elbereth /kernel: Null pmap (cb) at va: 0x0
    Oct 19 10:00:01 elbereth /kernel: Null pmap (tb) at va: 0x0
    Oct 19 10:00:01 elbereth last message repeated 8 times
    Oct 19 10:00:01 elbereth /kernel: Null pmap (cb) at va: 0x0
    Oct 19 10:00:01 elbereth /kernel: Null pmap (tb) at va: 0x0

I have never seen this before, and I've been running 2.0.5 since about a
week after it's release.

Messages of that form appear in `messages' from 10:00:00 this morning (I
first logged in at 9:50) and continue until I rebooted the system at
10:10:27. My X system didn't disappear until 10:09, with the following
entries

Oct 19 10:09:08 elbereth /kernel: pid 912: xterm: uid 0: exited on signal 11
Oct 19 10:09:08 elbereth /kernel: pid 896: xclock: uid 1000: exited on signal 11
Oct 19 10:09:08 elbereth /kernel: pid 905: xterm: uid 0: exited on signal 11
Oct 19 10:09:08 elbereth /kernel: pid 897: xload: uid 1000: exited on signal 11
Oct 19 10:09:08 elbereth /kernel: pid 890: xterm: uid 0: exited on signal 11
Oct 19 10:09:08 elbereth /kernel: pid 898: xterm: uid 0: exited on signal 11

A quick

    grep "Null pmap" /var/log/messages*

shows that this is the first time these errors have occured since Aug 26
(as far back as my logs go).

The machine was last rebooted at 18:47 yesterday, so it's not like
there'd been a fantastically long uptime.

Suspicious that this happened at exactly 10:00 I thought maybe something
kicked off by cron caused it. But in /var/cron/log there is just

   Oct 19 10:00:00 elbereth CRON[978]: (root) CMD (/usr/libexec/atrun) 
   root (10/19-10:05:00-982) CMD (/usr/libexec/atrun)

which looks fairly standard to me. 

So, cosmic rays, or something more important?

N
-- 
--+=[ Blueberry Hill                   Blueberry Design                   ]=+--
--+=[ http://www.blueberry.co.uk/      1/9 Chelsea Harbour Design Centre, ]=+--
--+=[ WebMaster@blueberry.co.uk        London, England, SW10 0XE          ]=+--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510191031.KAA00330>