[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
** Tags removed: verification-needed-saucy ** Tags added: verification-done-saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: earlyprintk doesn't work in mach-virt (qemu guest target for kvm on arm) because at boot time, the clock necessary to make pl011 serial port running is not added via device tree (and thus the serial console is not probed) - also see https://lists.gnu.org/archive/html /qemu-devel/2013-10/msg02427.html. Fix: apply the attached patches and recompile a kernel. Test case: try booting a patched (and an unpatched kernel) in kvm guest passing earlyprintk and NO console, and see if it emits any output. -- There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
I can verify that the patch fixes the bug above, with this patch I am able to see messages at boot... [0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.11.0-15-generic-lpae (buildd@kishi02) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-7ubuntu3) ) #22-Ubuntu SMP Tue Dec 3 01:16:52 UTC 2013 (Ubuntu 3.11.0-15.22-generic-lpae 3.11.10) [0.00] CPU: ARMv7 Processor [413fc0f2] revision 2 (ARMv7), cr=30c7387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [0.00] Machine: Dummy Virtual Machine, model: linux,dummy-virt [0.00] cma: CMA: reserved 16 MiB at 3680 [0.00] Memory policy: ECC disabled, Data cache writealloc [0.00] psci: probing function IDs from device-tree [0.00] PERCPU: Embedded 9 pages/cpu @c11f5000 s14400 r8192 d14272 u36864 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260624 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: earlyprintk doesn't work in mach-virt (qemu guest target for kvm on arm) because at boot time, the clock necessary to make pl011 serial port running is not added via device tree (and thus the serial console is not probed) - also see https://lists.gnu.org/archive/html /qemu-devel/2013-10/msg02427.html. Fix: apply the attached patches and recompile a kernel. Test case: try booting a patched (and an unpatched kernel) in kvm guest passing earlyprintk and NO console, and see if it emits any output. -- There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- saucy' to 'verification-done-saucy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: earlyprintk doesn't work in mach-virt (qemu guest target for kvm on arm) because at boot time, the clock necessary to make pl011 serial port running is not added via device tree (and thus the serial console is not probed) - also see https://lists.gnu.org/archive/html /qemu-devel/2013-10/msg02427.html. Fix: apply the attached patches and recompile a kernel. Test case: try booting a patched (and an unpatched kernel) in kvm guest passing earlyprintk and NO console, and see if it emits any output. -- There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: earlyprintk doesn't work in mach-virt (qemu guest target for kvm on arm) because at boot time, the clock necessary to make pl011 serial port running is not added via device tree (and thus the serial console is not probed) - also see https://lists.gnu.org/archive/html /qemu-devel/2013-10/msg02427.html. Fix: apply the attached patches and recompile a kernel. Test case: try booting a patched (and an unpatched kernel) in kvm guest passing earlyprintk and NO console, and see if it emits any output. -- There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
due to the nature of the issue encountered log files that will aid in diagnosing the problem might be missing. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: Confirmed Bug description: SRU Justification: Impact: earlyprintk doesn't work in mach-virt (qemu guest target for kvm on arm) because at boot time, the clock necessary to make pl011 serial port running is not added via device tree (and thus the serial console is not probed) - also see https://lists.gnu.org/archive/html /qemu-devel/2013-10/msg02427.html. Fix: apply the attached patches and recompile a kernel. Test case: try booting a patched (and an unpatched kernel) in kvm guest passing earlyprintk and NO console, and see if it emits any output. -- There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
** Description changed: + SRU Justification: + + Impact: earlyprintk doesn't work in mach-virt (qemu guest target for kvm + on arm) because at boot time, the clock necessary to make pl011 serial + port running is not added via device tree (and thus the serial console + is not probed) - also see https://lists.gnu.org/archive/html/qemu- + devel/2013-10/msg02427.html. + + Fix: apply the attached patches and recompile a kernel. + + Test case: try booting a patched (and an unpatched kernel) in kvm guest + passing earlyprintk and NO console, and see if it emits any output. + + -- + There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: earlyprintk doesn't work in mach-virt (qemu guest target for kvm on arm) because at boot time, the clock necessary to make pl011 serial port running is not added via device tree (and thus the serial console is not probed) - also see https://lists.gnu.org/archive/html /qemu-devel/2013-10/msg02427.html. Fix: apply the attached patches and recompile a kernel. Test case: try booting a patched (and an unpatched kernel) in kvm guest passing earlyprintk and NO console, and see if it emits any output. -- There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
This patch is a temporary fix. ** Patch added: Patch to enable earlyprintk via the PL011. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+attachment/3900688/+files/0001-Patch-to-enable-earlyprintk-via-the-PL011.-Because-t.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: New Bug description: There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: Incomplete Bug description: There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248233] Re: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248233 Title: [saucy][armhf] No early printk because there's no defined device tree binding for earlyprintk UART Status in “linux” package in Ubuntu: Incomplete Bug description: There is no earlyprintk via the PL011 because there's no defined device tree binding for earlyprintk UART to get the PL011 to work you'll need to tweak the kernel a bit. kernel doesn't ever add the clock to its list, and then it refuses to probe for the PL011. This is a temporary fix, ideally the call should be done in some generic location rather than in every machine's init function.) The alternative would be for the kernel to be fixed to follow its own device tree binding documentation and not require clocks/clock-names properties on the pl011 node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
