Date: Mon, 15 Apr 2002 15:47:32 -0700 (PDT) From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Panic (swp_pager_meta_ctl+0x67) in today's -CURRENT Message-ID: <200204152247.g3FMlWlb017721@bunrab.catwhisker.org>
next in thread | raw e-mail | index | archive | help
Have had a touch more turbulence than usual in -CURRENT-land today.
Finally got it built; re-booted, and got the following panic while
setting up an md-resident file system (for /tmp):
...
add net default: gateway 172.16.8.1
Additional routing options:.
Routing daemons:.
Additional daemons: syslogdApr 15 15:22:09 freebeast syslogd: kernel boot file is /boot/kernel/kernel
.
Doing additionalO network setup: lntpdated: time_adjtime = 0.000000 0
New: time_adjtime = 0.290799 290799
ntpd rpcbind.
Starting final network daemons: mountdApr 15 15:22:09 freebeast mountd[182]: bad exports list line /S1/usr
Apr 15 15:22:09 freebeast mountd[182]: bad exports list line /S2/usr
Apr 15 15:22:09 freebeast mountd[182]: bad exports list line /S3/usr
Apr 15 15:22:09 freebeast mountd[182]: bad exports list line /S4/usr
Apr 15 15:22:10 freebeast mountd[182]: could not remount /cdrom: Invalid argument
Apr 15 15:22:10 freebeast mountd[182]: bad exports list line /cdrom -ro -alldirs
nfsd NFS access cache time=2.
ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
Starting standard daemons: inetd cron sshd sendmail-submit sendmail-clientmqueue.
Recovering vi editor sessions:.
Initial rc.i386 initialization:.
Configuring syscons: blanktime.
Additional ABI support:.
Local package initiCalization:reating DISK md10
md10: invalid primary partition table: no magic
md10: invalid primary partition table: no magic
er inode restric
group to 6. per
/dev/md10c: 1048F576 sectors in 3a2 cylinders of 1t tracks, 32768 saectors
l trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 00000000
fault virtual address = 0x8
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0283ba7
stack pointer = 0x10:0xd911cb00
frame pointer = 0x10:0xd911cb10
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 = 229 (newfs)
kernel: type 12 trap, code=0
Stopped at swp_pager_meta_ctl+0x67: cmpl %ebx,0x4(%eax)
db> trace
swp_pager_meta_ctl(d91363c0,1ffff,0,ce59de70,d9120c00) at swp_pager_meta_ctl+0x67
swap_pager_strategy(d91363c0,ce59de70,d911cb60,c01492b0,d91363c0) at swap_pager_strategy+0xdf
vm_pager_strategy(d91363c0,ce59de70,d911cb7c,c0149427,d9120c00) at vm_pager_strategy+0x21
mdstart_swap(d9120c00,ce59de70) at mdstart_swap+0x30
mdstrategy(ce59de70,0,ce59de70,d911cbb8,c01a2fb3) at mdstrategy+0x16f
diskstrategy(ce59de70,d912bc00) at diskstrategy+0xa1
physio(d912bc00,d911cc90,1,d912bc00,d913f0f0) at physio+0x273
spec_write(d911cc24,d911cc38,c01ee513,d911cc24,1000) at spec_write+0x5d
spec_vnoperate(d911cc24,1000,d911cd20,0,1) at spec_vnoperate+0x15
vn_write(d8fd2b04,d911cc90,ce51c300,0,d8fe0728) at vn_write+0x1bb
dofilewrite(d8fe0728,d8fd2b04,3,808c0e0,1000) at dofilewrite+0xb6
write(d8fe0728,d911cd20,0,1000,4000) at write+0x3b
syscall(2f,2f,2f,4000,1000) at syscall+0x24f
syscall_with_err_pushed() at syscall_with_err_pushed+0x1b
--- syscall (4, FreeBSD ELF, write), eip = 0x804cddf, esp = 0xbfbffb1c, ebp = 0xbfbffb38 ---
db> Context switches not allowed in the debugger.
db>
Some notes:
* I was able to bring it up in single-user mode OK.
* The whines about inability to mount certain file systems are just that
-- whines. I have the system set up to boot from any of several slices,
and I have /etc/fstab set up as a symlink to the appropriate one for
the slice in question (to make "cloning a slice" easier). I didn't
bother also making separate /etc/exports files, figuring that the
system would whine, but that the whines would be otherwise benign.
So I don't advise getting too hung up on these. [Move along, now;
nothing here to see....]
* This is my build machine, so until fairly late tonight, it doesn't
have anything else to do. Thus, I can re-create the problem & poke
at it, try things out, ....
* Here's the recent CVSup activity:
# tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org at Fri Apr 12 06:34:50 PDT 2002
CVSup ended from cvsup14.freebsd.org at Fri Apr 12 06:41:34 PDT 2002
CVSup begin from cvsup14.freebsd.org at Sat Apr 13 03:47:02 PDT 2002
CVSup ended from cvsup14.freebsd.org at Sat Apr 13 03:55:58 PDT 2002
CVSup begin from cvsup14.freebsd.org at Sun Apr 14 03:47:02 PDT 2002
CVSup ended from cvsup14.freebsd.org at Sun Apr 14 03:53:45 PDT 2002
CVSup begin from cvsup14.freebsd.org at Mon Apr 15 03:47:02 PDT 2002
CVSup ended from cvsup14.freebsd.org at Mon Apr 15 03:53:59 PDT 2002
CVSup begin from cvsup14.freebsd.org at Mon Apr 15 12:54:16 PDT 2002
CVSup ended from cvsup14.freebsd.org at Mon Apr 15 13:00:59 PDT 2002
* The laptop is still building "everything" as I type; I don't see
much point in repeating this message for it (once -CURRENT finishes
building), so I won't.
I'm open to suggestions for where to poke & prod....
Thanks,
david
--
David H. Wolfskill david@catwhisker.org
Based on my experience as a computing professional, I consider the use of
Microsoft products as components of computing systems to be just as
advisable as using green wood to frame a house... and expect similar results.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204152247.g3FMlWlb017721>