Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759758AbYHUTHa (ORCPT ); Thu, 21 Aug 2008 15:07:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752661AbYHUTHU (ORCPT ); Thu, 21 Aug 2008 15:07:20 -0400 Received: from rv-out-0506.google.com ([209.85.198.233]:16853 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752011AbYHUTHT (ORCPT ); Thu, 21 Aug 2008 15:07:19 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=cLEjtDP16OsY3UkMRVM3FImN7xWALwPxY7l75K15J2d7RzCgPt9msvLwRZZeEHDuth oX1HvMEEZdXSL2dCFhTepBfhv2+BsiB5XdQ8PJr/2YSgQbO6JxMfpVQBgI/WcnPRJ+px NJG+uAzK5gE6iCRR0hOQaWIxEZ47X1MhpQ1+I= Message-ID: <86802c440808211207q28c567e6t995ac3fdac082abc@mail.gmail.com> Date: Thu, 21 Aug 2008 12:07:18 -0700 From: "Yinghai Lu" To: "Jeremy Fitzhardinge" Subject: Re: [Bug #11313] Plugging HDMI causes "unable to handle kernel paging request" Cc: "=?ISO-8859-2?Q?Rafa=B3_Mi=B3ecki?=" , "Rafael J. Wysocki" , "Linux Kernel Mailing List" , "Kernel Testers List" , "Ingo Molnar" , "H. Peter Anvin" , "Jack Steiner" , "Alan Jenkins" , "Hugh Dickens" In-Reply-To: <48ADB041.9040806@goop.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Disposition: inline References: <48AB5D17.5030600@goop.org> <48AC3FA4.9080603@goop.org> <48ADB041.9040806@goop.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by alpha id m7LJ7Ydq005567 Content-Length: 1706 Lines: 4 On Thu, Aug 21, 2008 at 11:13 AM, Jeremy Fitzhardinge wrote:> Rafa? Mi?ecki wrote:>> I added full dmesg 5 minutes after adding grepped:>> http://bugzilla.kernel.org/attachment.cgi?id=17331>>>> OK, I think I see the problem (pasted from bugzilla comment):>>>>>>> Some notes as I pick through all the evidence so far:>> - the crash is specifically because there are reserved bits set in the pmd> - the pmd is b02a00043a6001a3 in both cases> - the vaddr is ffff88013a600000 in the first crash, and> ffff81013a6d1c00 in the second> corresponding to the same large-page pmd mapping of phys page 0x13a600000> - this maps to e820 entry> BIOS-e820: 0000000100000000 - 0000000140000000 (usable)> - the corresponding boot-time mapping is>> init_memory_mapping> 0100000000 - 0140000000 page 2M> kernel direct mapping tables up to 140000000 @ b000-11000> ^^^^^^^^^^ this is just estimated. and worst case. > addr 100000000 reusing pgd 201880 0000000000202063> last_map_addr: 140000000 end: 140000000>> !!! and the memory allocated for this pagetable is:> #5 [0000008000 - 000000b000] PGTABLE ==> [0000008000 - 000000b000]> #6 [000000b000 - 000000c000] PGTABLE ==> [000000b000 - 000000c000]> ^^^^^^^^^^^^^^^^^^^^^^^this is correct value used finally.>> IOW, it's mapping using b000-11000, but it has only reserved b000 - c000>> Also, this is right in the middle of the ISA area, which seems risky.> <<<< YH????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?