Re: commit 6797b4f causes boot hangs with nfsroot
On 03/17/2013 08:57 PM, Paul Walmsley wrote: Hi Jon, On Sat, 16 Mar 2013, Paul Walmsley wrote: Looks like commit 6797b4fe0e554ce71f47038fd929c9ca929a9f3c (ARM: OMAP2+: Prevent potential crash if GPMC probe fails) causes hangs on boot. I suspect it may only occur when the root filesystem is on NFS over GPMC-based Ethernet. Looks like you sent a patch for this a month ago and it just now got merged with v3.9-rc3 as commit 31d9adca82ce65e5c99d045b5fd917c702b6fce3 (ARM: OMAP2+: Fix broken gpmc support). Thanks for fixing this promptly and sorry about the extra noise, Yes I see that just got merged last week so we should be good now. Cheers Jon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: commit 6797b4f causes boot hangs with nfsroot
Hi Jon, On Sat, 16 Mar 2013, Paul Walmsley wrote: Looks like commit 6797b4fe0e554ce71f47038fd929c9ca929a9f3c (ARM: OMAP2+: Prevent potential crash if GPMC probe fails) causes hangs on boot. I suspect it may only occur when the root filesystem is on NFS over GPMC-based Ethernet. Looks like you sent a patch for this a month ago and it just now got merged with v3.9-rc3 as commit 31d9adca82ce65e5c99d045b5fd917c702b6fce3 (ARM: OMAP2+: Fix broken gpmc support). Thanks for fixing this promptly and sorry about the extra noise, - Paul -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
commit 6797b4f causes boot hangs with nfsroot
Hi Jon, Looks like commit 6797b4fe0e554ce71f47038fd929c9ca929a9f3c (ARM: OMAP2+: Prevent potential crash if GPMC probe fails) causes hangs on boot. I suspect it may only occur when the root filesystem is on NFS over GPMC-based Ethernet. Here's the current state of affairs at v3.9-rc1 on the two boards that show the problem: http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/boot/2430sdp/2430sdp_log.txt http://www.pwsan.com/omap/testlogs/test_v3.9-rc1/20130312100243/boot/37xxevm/37xxevm_log.txt and here are the bootlogs after reverting 6797b4f: http://www.pwsan.com/omap/testlogs/trace_boot_hang_3.9-rc/20130316132833/boot/2430sdp/2430sdp_log.txt http://www.pwsan.com/omap/testlogs/trace_boot_hang_3.9-rc/20130316132833/boot/37xxevm/37xxevm_log.txt ... where the boards at least boot to userspace. I don't know what's up with the NFS-related lock problems. Those look like yet another bug that is presumably not OMAP-specific :-( Care to take a look at the commit 6797b4f bug? - Paul -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
