From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Romain Goyet" Subject: Re: MMC lockup on 16xx/H2 Date: Thu, 23 Mar 2006 17:27:30 +0100 Message-ID: <8028e5750603230827g697a7b96w@mail.gmail.com> References: <441B143D.2020100@mvista.com> <441B1B73.4030303@indt.org.br> <20060322151935.GC5748@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20060322151935.GC5748@atomide.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: "tony@atomide.com" Cc: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org I had virtually the saim problem on my Palm Tungsten E. I didn't think to enable soft lockup, so my kernel was just hanging, until I disabled MMC... Just to let you know Romain Goyet 2006/3/22, tony@atomide.com : > * Carlos Aguiar [060317 12:27]: > > ext Kevin Hilman wrote: > > > > >I"m seeing a soft lockup in the OMAP MMC driver on my 1623/H2 board. > > >I haven't found it yet, but wondering if anyone else sees this. > > > > > >I'm using the default omap_h2_1610_defconfig plus enabling MMC, > > >MMC_BLOCK and MMC_OMAP (built-in.) The kernel boots fine without > > >these enabled. > > > > > >The soft-lockup catches the problem: > > > > > >[ ... ] > > >usb0: Ethernet Gadget, version: May Day 2005 > > >usb0: using omap_udc, OUT ep2out-bulk IN ep1in-bulk STATUS ep3in-int > > >usb0: MAC e2:f3:92:66:c0:5a > > >usb0: HOST MAC 66:f8:01:66:fb:8d > > >usb0: RNDIS ready > > >otg: b_idle, SWITCH to gadget, ctrl 098021 > > >isp1301_omap 0-002d: ready for dual-role USB ... > > >mice: PS/2 mouse device common for all mice > > >NET: Registered protocol family 2 > > >BUG: soft lockup detected on CPU#0! > > > > > >Pid: 4, comm: events/0 > > >CPU: 0 > > >PC is at mmc_omap_set_ios+0x130/0x154 > > >LR is at schedule_timeout+0x94/0xbc > > >pc : [] lr : [] Not tainted > > >sp : c0325e38 ip : c0325ddc fp : c0325e58 > > >r10: c0354e00 r9 : 00000000 r8 : 00061a80 > > >r7 : c0354eac r6 : 00000879 r5 : c0354f20 r4 : 02dc6c00 > > >r3 : 00000000 r2 : fefb7800 r1 : c0325dc0 r0 : 00000000 > > >Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel > > >Control: 5317F Table: 10004000 DAC: 00000017 > > >[] (show_regs+0x0/0x4c) from [] > > >(softlockup_tick+0x64/0x7c) > > > r4 =3D C0325DF0 > > >[] (softlockup_tick+0x0/0x7c) from [] > > >(do_timer+0x404/0x480) r4 =3D C028475C > > >[] (do_timer+0x0/0x480) from [] > > >(timer_tick+0xb4/0xe4) > > >[] (timer_tick+0x0/0xe4) from [] > > >(omap_mpu_timer_interrupt+) r6 =3D 00000000 r5 =3D 00000000 r4 =3D C= 0283710 > > >[] (omap_mpu_timer_interrupt+0x0/0x6c) from [] > > >(__do_irq+0x) r4 =3D C0232FE8 > > >[] (__do_irq+0x0/0x8c) from [] > > >(do_level_IRQ+0x68/0xc0) > > > r8 =3D C0325DF0 r7 =3D C0354EAC r6 =3D C0325DF0 r5 =3D 0000001E > > > r4 =3D C0278BD8 > > >[] (do_level_IRQ+0x0/0xc0) from [] > > >(asm_do_IRQ+0x54/0x140) > > > r6 =3D FFFFFFFF r5 =3D FEFECB00 r4 =3D C0324000 > > >[] (asm_do_IRQ+0x0/0x140) from [] > > >(__irq_svc+0x24/0x80) > > >[] (mmc_omap_set_ios+0x0/0x154) from [] > > >(mmc_rescan+0x90/0x) r8 =3D C0325E68 r7 =3D 00000000 r6 =3D C0354EAC= r5 =3D > > >00000002 > > > r4 =3D 00000001 > > >[] (mmc_rescan+0x0/0xbc8) from [] > > >(run_workqueue+0xb4/0x108)[] (run_workqueue+0x0/0x108) from > > >[] (worker_thread+0x11c/0) r7 =3D C0325F88 r6 =3D C0325F8C = r5 > > >=3D C02FB6E8 r4 =3D C02FB6F0 > > >[] (worker_thread+0x0/0x170) from [] > > >(kthread+0xe8/0x11c) > > > r8 =3D 00000001 r7 =3D C00503FC r6 =3D C030BF24 r5 =3D C0324000 > > > r4 =3D C02FB6E0 > > >[] (kthread+0x0/0x11c) from [] (do_exit+0x0/0x7e8) > > > > > > > > >_______________________________________________ > > >Linux-omap-open-source mailing list > > >Linux-omap-open-source@linux.omap.com > > >http://linux.omap.com/mailman/listinfo/linux-omap-open-source > > > > > Hi Kevin, > > > > I'm having exactly the same problem. I've found this soft lockup proble= m > > when generating a kernel image to OMAP 1610 and 1710 (using > > omap_h2_1610_defconfig and omap_h3_1710_defconfig in the last updated > > linux-omap-2.6.git tree) with MMC support enabled. > > This seems to be related to some recent I2C changes as they are used for > powering MMC slot on H2 and H3 via tps65010 chip's gpios. MMC works just > fine at least on boards that use omap gpio for the power. > > Tony > _______________________________________________ > Linux-omap-open-source mailing list > Linux-omap-open-source@linux.omap.com > http://linux.omap.com/mailman/listinfo/linux-omap-open-source >