From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: OMAP34xx Date: Tue, 07 Feb 2012 14:09:51 -0800 Message-ID: <87zkcugus0.fsf@ti.com> References: <20120204185453.GB17309@n2100.arm.linux.org.uk> <20120204190109.GL20333@atomide.com> <20120204203453.GD17309@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from na3sys009aog111.obsmtp.com ([74.125.149.205]:54805 "EHLO na3sys009aog111.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757104Ab2BGWKA (ORCPT ); Tue, 7 Feb 2012 17:10:00 -0500 Received: by mail-pz0-f54.google.com with SMTP id c6so8712739dae.27 for ; Tue, 07 Feb 2012 14:09:59 -0800 (PST) In-Reply-To: <20120204203453.GD17309@n2100.arm.linux.org.uk> (Russell King's message of "Sat, 4 Feb 2012 20:34:53 +0000") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Russell King - ARM Linux Cc: Tony Lindgren , linux-omap@vger.kernel.org, Arnd Bergmann , Olof Johansson Russell King - ARM Linux writes: [...] > Another problem oopses the kernel at boot in the voltage domain code, > which I suspect this has never been boot tested on OMAP34xx CPUs: > > omap_vc_init_channel: PMIC info requried to configure vc forvdd_core not populated.Hence cannot initialize vc > Unable to handle kernel NULL pointer dereference at virtual address 00000000 > pgd = c0004000 > [00000000] *pgd=00000000 > Internal error: Oops: 5 [#1] PREEMPT > Modules linked in: > CPU: 0 Not tainted (3.3.0-rc2+ #204) > PC is at omap_vp_init+0x5c/0x15c > LR is at omap_vp_init+0x58/0x15c > pc : [] lr : [] psr: 60000013 > sp : c181ff30 ip : c181ff68 fp : c181ff64 > r10: c0407808 r9 : c040786c r8 : c0407814 > r7 : c0026868 r6 : c00264fc r5 : c040ad6c r4 : 00000000 > r3 : 00000040 r2 : 000032c8 r1 : 0000fa00 r0 : 000032c8 > Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel > Control: 10c5387d Table: 80004019 DAC: 00000015 > Process swapper (pid: 1, stack limit = 0xc181e2e8) > Stack: (0xc181ff30 to 0xc1820000) > ff20: c0381d00 c02e9c6d c0383582 c040786c > ff40: c040ad6c c00264fc c0026868 c0407814 00000000 c03d9de4 c181ff8c c181ff68 > ff60: c03db448 c03db830 c02e982c c03fdfb8 c03fe004 c0039988 00000013 00000000 > ff80: c181ff9c c181ff90 c03d9df8 c03db390 c181ffdc c181ffa0 c0008798 c03d9df0 > ffa0: c181ffc4 c181ffb0 c0055a44 c0187050 c0039988 c03fdfb8 c03fe004 c0039988 > ffc0: 00000013 00000000 00000000 00000000 c181fff4 c181ffe0 c03d1284 c0008708 > ffe0: 00000000 c03d1208 00000000 c181fff8 c0039988 c03d1214 1077ce40 01f7ee08 > Backtrace: > [] (omap_vp_init+0x0/0x15c) from [] (omap_voltage_late_init+ > 0xc4/0xfc) > [] (omap_voltage_late_init+0x0/0xfc) from [] (omap2_common_p > m_late_init+0x14/0x54) > r8:00000000 r7:00000013 r6:c0039988 r5:c03fe004 r4:c03fdfb8 > [] (omap2_common_pm_late_init+0x0/0x54) from [] (do_one_init > call+0x9c/0x164) > [] (do_one_initcall+0x0/0x164) from [] (kernel_init+0x7c/0x1 > 20) > [] (kernel_init+0x0/0x120) from [] (do_exit+0x0/0x2cc) > r5:c03d1208 r4:00000000 > Code: e5ca300b e5900034 ebf69027 e5994024 (e5941000) > ---[ end trace aed617dddaf32c3d ]--- > Kernel panic - not syncing: Attempted to kill init! FWIW, this problem has been fixed for some time, and in my for_3.3/cleanup/pm branch (and included in Tony's cleanup branch) which was supposed to be merged for v3.3. Kevin