OK; this is a(nother) "page fault while in kernel mode," but I suspect
it's one I hadn't seen mentioned yet.  The "good news" is that it is
eminently reproducible.  :-}  Also, I was able to boot kernel.old OK, so
hat should decrease the probability that the problem is (strictly)
somewhere in userland.  As usual (for me), this is on my laptop.

Recent CVSup history:
CVSup begin from cvsup14.freebsd.org at Fri Jun 15 03:47:01 PDT 2001
CVSup ended from cvsup14.freebsd.org at Fri Jun 15 04:07:33 PDT 2001
CVSup begin from cvsup14.freebsd.org at Sat Jun 16 03:47:00 PDT 2001
CVSup ended from cvsup14.freebsd.org at Sat Jun 16 03:52:48 PDT 2001
CVSup begin from cvsup14.freebsd.org at Sun Jun 17 03:47:00 PDT 2001
CVSup ended from cvsup14.freebsd.org at Sun Jun 17 03:52:46 PDT 2001

(I had built each of -STABLE & -CURRENT after each one, and booted each
successfully (running at least a few things), save for today's -CURRENT.
And yes, I always buildworld, kernel, installworld, mergemaster.)

The first couple of lines are from the console log:

Initial rc.i386 initialization: apm.
Configuring syscons: blank_time moused.

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0xc
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc018fe1a
stack pointer           = 0x10:0xce5a4d40
frame pointer           = 0x10:0xce5a4d5c
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 363 (ln)
kernel: type 12 trap, code =0
Stopped at      dsp_clone+0xee: movl    0xc(%ebx),%edx
db> trace
dsp_clone(0,ce5a4dc4,3,ce5a44a8,c17ae818) at dsp_clone+0xee
devfs_lookupx(ce5a4e24,c17ae018,1,0,cc36c760) at devfs_lookupx+0x2b1
devfs_lookup(ce5a4e24,cd233da0,ce5a4ed0,ce5a4ea8,cc36c760) at devfs_lookup+0x31
lookup(ce5a4ea8,cc36c87c,cc36c760,cc36c760,cc36c760) at lookup+0x291
namei(ce5a4ea8,cc36c87c,cc36c760,2,bfbffe65) at namei+0x177
lstat(cc36c760,ce5a4f80,bfbffdc4,bfbffe65,bfbffe5b) at lstat+0x41
syscall(2f,2f,2f,bfbffe5b,bfbffe65) at syscall+0x71d
syscall_with_err_pushed() at syscall_with_err_pushed+0x1b
db> show locks
exclusive (sleep mutex) Giant (0xc047eb20) locked @ /usr/src/sys/vm/vm_fault.c:213

Now, back on 13 June, I had added another line to /etc/rc.devfs -- the
line symlinking /dev/dsp0 to /dev/dsp; here are the lines I've added:
# Setup DEVFS, ie permissions, links etc.
ln -fs /dev/ttyv0 /dev/vga
ln -fs /dev/sysmouse /dev/mouse
ln -fs /dev/mixer0 /dev/mixer
ln -fs /dev/dsp0 /dev/dsp
chmod a+r /dev/apm

I note also that I tried looking at last week's -cvs-all (mailing list)
archive, but I can't find it.  I see today's (the start of this week's);
I see weeks prior to last; just not last week.  And I see last week's
for (say) -current; no problem.  Help?

I'll try removing/commenting that last "dsp" line in /etc/rc.devfs just
after sending this off....

David H. Wolfskill                              [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to