Maybe whoever committed the supposedly innocuous dev_t changes should
back it out.
Just a thought.
-Matt
Matthew Dillon
<dil...@backplane.com>
:
:It looks like something has come unstuck:
:
:Fatal trap 12: page fault while in kernel mode
:mp_lock = 00000002; cpuid = 0; lapic.id = 00000000
:fault virtual address = 0x28
:fault code = supervisor read, page not present
:instruction pointer = 0x8:0xc017bb67
:stack pointer = 0x10:0xc5d97de4
:frame pointer = 0x10:0xc5d97df0
: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 = 2 (pagedaemon)
:interrupt mask = net bio cam <- SMP: XXX
:kernel: type 12 trap, code=0
:Stopped at spec_strategy+0x93: movl 0x28(%edx),%eax
: ^^^^^^^^^^^ %edx = null
:db> trace
:spec_strategy(c5d97e1c) at spec_strategy+0x93
:swap_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at
swap_pager_putpages+0x3e1
:default_pager_putpages(c02904fc,c5d97ecc,2,0,c5d97e60) at
default_pager_putpages+0x17
:vm_pageout_flush(c5d97ecc,2,0,c5d97eb0,c02182cf) at vm_pageout_flush+0x91
:vm_pageout_clean(c04d6b60,80000000,c013e290,2000,c5d97f78) at
vm_pageout_clean+0x1f1
:vm_pageout_scan(80000000,c02789c0,c02789c0,c5d97fac,c013e2c3) at
vm_pageout_scan+0x45e
:vm_pageout(c5d8fdf7,c0255500,c02789c0,c020c640,c020c748) at vm_pageout+0x221
:kproc_start(c02789c0) at kproc_start+0x33
:fork_trampoline(10b8a0,d88e0000,18b8c08e,8e000000,24448be0) at
fork_trampoline+0x30
:db> ps
: pid proc addr uid ppid pgrp flag stat wmesg wchan cmd
: 438 c680da40 c6818000 495 282 277 000004 3 biord c332d9c0 p4d
: 437 c5d8c340 c6802000 433 417 415 004084 3 piperd c6760660 tee
: 436 c680dd00 c6810000 433 417 415 004004 3 biord c33626f8 p4
: 418 c680dba0 c6815000 433 415 415 004084 3 piperd c6760700 mail
: 417 c680de60 c680e000 433 415 415 004084 3 wait c680de60 sh
:[..]
:
:The offending line in spec_strategy is:
: (*bdevsw(bp->b_dev)->d_strategy)(bp);
:
:d_strategy was null.. I'm still looking.
:
:(I think this is the first time the box paged out since booting a few hours
:ago, it's got 128M, but p4d has got a lot of stuff to deal with and can hit
:a vsize of 70MB or so.)
:
:Cheers,
:-Peter
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
