Date: Wed, 28 Apr 1999 21:22:18 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Dmitrij Tejblum <tejblum@arc.hq.cti.ru> Cc: Dmitrij Tejblum <dt@freebsd.org>, cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/alpha/alpha pmap.c Message-ID: <Pine.BSF.4.05.9904282121010.41254-100000@herring.nlsystems.com> In-Reply-To: <199904282007.AAA89272@arc.hq.cti.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Apr 1999, Dmitrij Tejblum wrote: > > On Wed, 28 Apr 1999, Dmitrij Tejblum wrote: > > > > > dt 1999/04/28 08:52:11 PDT > > > > > > Modified files: > > > sys/alpha/alpha pmap.c > > > Log: > > > pmap_emulate_reference: don't ever lose PV_TABLE_MOD bit on page. If > > > PV_TABLE_REF cleared before PV_TABLE_MOD, the page may get fault on read again. > > > > > > On fault on write, pmap_emulate_reference mark the page dirty with > > > vm_page_dirty. That decrease ill effects of the bug. > > > > > > The problem probably become more serious after my rev.1.18 a week ago. > > > > Is this connected with the 'pv_table for %x is inconsistent' panic? I > > have seen this a couple of times recently but I haven't managed to debug > > it. > > I don't think so: the code in question only touch flags, it doesn't touch > addresses. > > I haven't seen the panic. > > (I just discovered that freshly built kernel panic on boot in > run_interrupt_driven_config_hooks+0x68 due to a memory access fault. :-| > Ideas?) I haven't seen that one. I have to put my alpha debugging environment back together - it relies on building kernels over NFS and that is totally busted without Matt's NFS patch... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9904282121010.41254-100000>