From mboxrd@z Thu Jan 1 00:00:00 1970 From: konrad wilk Subject: Re: [BUG] Bad page map in process after migration (Debian #711249) Date: Tue, 11 Jun 2013 13:01:31 -0400 Message-ID: <51B757EB.2050707@oracle.com> References: <1370969055.24512.346.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1370969055.24512.346.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Boris Ostrovsky , xen-devel List-Id: xen-devel@lists.xenproject.org On 6/11/2013 12:44 PM, Ian Campbell wrote: > A Debian user has reported this with the 3.2 kernel, it sounds vaguely > familiar, but neither I nor google can quite put my finger on it. Does > it ring any bells? > > [1295549.783990] BUG: Bad page map in process java pte:00000166 pmd:3bacb067 > [1295549.784005] page:ffffea0000000000 count:-1 mapcount:-128 mapping: (null) index:0x0 > [1295549.784036] page flags: 0x14(referenced|dirty) > [1295549.784044] addr:00007f879a6a2000 vm_flags:00100077 anon_vma:ffff88003cb472a0 mapping: (null) index:7f879a6a2 > [1295549.784052] Pid: 13198, comm: java Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2+deb7u2 > [1295549.784058] Call Trace: > [1295549.784070] [] ? print_bad_pte+0x1a5/0x1bd > [1295549.784075] [] ? pte_pfn+0x5/0xe > [1295549.784083] [] ? unmap_vmas+0x4d5/0x6ca > [1295549.784095] [] ? zap_page_range+0x90/0xb8 > [1295549.784108] [] ? mmap_region+0x353/0x44a > [1295549.784122] [] ? should_resched+0x5/0x23 > [1295549.784133] [] ? sys_madvise+0x3d2/0x5fc > [1295549.784147] [] ? recalc_sigpending+0x23/0x3c > [1295549.784156] [] ? __set_task_blocked+0x5e/0x65 > [1295549.784168] [] ? spin_unlock_irq+0xa/0xb > [1295549.784178] [] ? sigprocmask+0x5c/0x63 > [1295549.784191] [] ? system_call_fastpath+0x16/0x1b > [1295549.784201] Disabling lock debugging due to kernel taint > > There's a bit more info and a full dmesg in > http://bugs.debian.org/711249 Thank you. Boris, Did you fix a similar issue in v3.9? There was the cgroup one which I thought had a similar back-track?