Re: URGENT: [diagnostic] cache_lock: blocked on 0xda5265a8 ""

["Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>]

YONETANI Tomokazu wrote:
> > I didn't look at the code, but you probably check for the dumpdev to be 
> > used?  Overwriting swap with memory contents would be disastrous.
> All it does is call dumpsys() and decrement the variable `dumping'
> which gets incremented before calling dev_ddump().  dumpsys() already
> checks to see if dumpdev is set.

yes, but usually it wouldn't care that dumpdev == swapdev.  when continuing to run, this is rather bad.

but thinking about it... why wouldn't you just do a dd if=/dev/kmem of=mycore?

maybe add some smp synchronisation, and that's it?  I usually go and debug live machines with just kgdb, attaching to the live memory image.

cheers
 simon

--
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \