** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1042213 Title: [quantal] Kernel oops with NFS mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042213/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs From [email protected] Thu Aug 30 09:51:02 2012 Return-path: <[email protected]> Envelope-to: [email protected] Delivery-date: Thu, 30 Aug 2012 09:51:02 -0700 Received: from exprod5mx203.postini.com ([64.18.0.62] helo=psmtp.com) by mail-archive.com with smtp (Exim 4.69) (envelope-from <[email protected]>) id 1T77xO-0002XK-KJ for [email protected]; Thu, 30 Aug 2012 09:51:02 -0700 Received: from mombin.canonical.com ([91.189.95.16]) by exprod5mx203.postini.com ([64.18.4.10]) with SMTP; Thu, 30 Aug 2012 16:51:02 GMT Received: from localhost ([127.0.0.1] helo=mombin.canonical.com) by mombin.canonical.com with esmtp (Exim 4.71) (envelope-from <[email protected]>) id 1T77x3-00071A-Pr; Thu, 30 Aug 2012 16:50:41 +0000 Received: from mail-qc0-f170.google.com ([209.85.216.170]) by mombin.canonical.com with esmtp (Exim 4.71) (envelope-from <[email protected]>) id 1T77x2-000715-29 for [email protected]; Thu, 30 Aug 2012 16:50:40 +0000 Received: by qcad42 with SMTP id d42so2665846qca.1 for <[email protected]>; Thu, 30 Aug 2012 09:50:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=785zuy4K+hwd53IVIHuFV46kC9BtazylnIel2McvaUA=; b=VhszfZerV2AkBlFicabYsVeZdLr5/fTDD7iKWPFL+lFAKe8/f233UbV5pIiZWkKBX3 xQn0d++TzzNNPJgLr5wQbouKvFl6AK0axLObHBNfeQI7bLGjmNIKMPNr80kEDROomHGh DMXkwss4EFI+6cqfF659pKiYkTT8g7+LP1rfSV+60UW3tiPH29HFZpqzpznPPFB0vdy1 fnnMDz/o4z1mmHaFrQ6YRbscUpHFU7EMQd1CKejegM5VHUAI4HVKjoo1MK0SIHswWXd8 DaN8XjN3Hg4jvLuK1s6FbT2uQ7qgUJfCtVV2Dz5IjZJ8vMBNf18i//72bNdjwlhuYNFy 0YQQ== Received: by 10.224.1.69 with SMTP id 5mr7138526qae.61.1346345439247; Thu, 30 Aug 2012 09:50:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.74.3 with HTTP; Thu, 30 Aug 2012 09:50:19 -0700 (PDT) In-Reply-To: <CAKGA1bnAkfHCDF0gP9TCabPmBW2CpwPkvyL32_6n8G=jkpl...@mail.gmail.com> References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <CAKGA1bnAkfHCDF0gP9TCabPmBW2CpwPkvyL32_6n8G=jkpl...@mail.gmail.com> From: Matt Sealey <[email protected]> Date: Thu, 30 Aug 2012 11:50:19 -0500 Message-ID: <CAKGA1bmTBULie5USBgjrsiGUcPKOF=o3ctafdysu4imxnha...@mail.gmail.com> Subject: Re: standard U-Boot environment variables/macros across platforms To: Linaro Cross Distro <[email protected]> X-Gm-Message-State: ALoCoQlZzTQhnh1WITZxn0SvPpsW2IH91PLXwyBzuNZKveR7cAFYBuo3HCyNaRZUCDHU+A+AMgHt X-BeenThere: [email protected] X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cross Distro <cross-distro.lists.linaro.org> List-Unsubscribe: <http://lists.linaro.org/mailman/options/cross-distro>, <mailto:[email protected]?subject=unsubscribe> List-Archive: <http://lists.linaro.org/pipermail/cross-distro> List-Post: <mailto:[email protected]> List-Help: <mailto:[email protected]?subject=help> List-Subscribe: <http://lists.linaro.org/mailman/listinfo/cross-distro>, <mailto:[email protected]?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: [email protected] Errors-To: [email protected] X-pstn-neptune: 0/0/0.00/0 X-pstn-levels: (S:99.90000/99.90000 CV:99.9000 FC:95.5390 LC:93.6803 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-dkim: 0 skipped:not-enabled X-pstn-settings: 4 (1.5000:1.5000) s cv gt3 gt2 gt1 r p m c X-pstn-addresses: from <[email protected]> [294/10] Here's something I found at random, I wonder if anyone else saw this in testing any kind of common variables or load addresses? Basically booting a uImage kernel and uImage ramdisk everything is fine. But a zImage and a raw ramdisk, sometimes the kernel decompresses over the ramdisk; the net effect being that the kernel disables initramfs support pretty early and on distros with ramdisks doing the grunt work before rootfs mount, all you'll get after that is some kind of panic and non-bootable system. I am assuming that if the ramdisk is loaded via uImage the header has a length in it, but raw, there is no length for the ramdisk known to U-Boot. This affects properties inserted into the /chosen node. But I can't see anywhere in the Linux decompression code that even bothers to check, so I can't figure out why it would even matter that linux,initrd-end isn't set to the actual last byte of the ramdisk load.. (if that is indeed the case). I would have thought it would have been in the kernel's best interest to not decompress over any memory regions passed in the DT, and all I can really find is conversion from ATAGS to DT entries. Anyway, shouldn't the kernel make sure for complete safety that it not only won't decompress over it's compressed image, but won't decompress over a supplied ramdisk, and how would we inform the kernel of the size if it's just a file loaded into memory at an arbitrary address with no header or otherwise-supplied length? -- Matt Sealey _______________________________________________ cross-distro mailing list [email protected] http://lists.linaro.org/mailman/listinfo/cross-distro
