Re: Card detect IRQ errors

2009-04-27 Thread David Brownell
On Monday 27 April 2009, Grazvydas Ignotas wrote:
> 
> With current l-o head when I insert or remove SD card I'm getting this:
> 
> [   20.733489] [ cut here ]
> [   20.738159] WARNING: at kernel/irq/handle.c:366 
> handle_IRQ_event+0x4c/0x14c()
> [   20.745330] BUG: IRQ handler called from non-hardirq
> context!Modules linked in:
> ...
> [   20.822753] ---[ end trace 2ca2d8ba630dd6b5 ]---
> [   20.869415] mmc0: card 8001 removed
> 
> Has anyone else seen this?

Regresssion caused by 044d408409cc4e1bc75c886e27ca85c270db104c.

Notice the message is internally broken, too -- no newline.

Try reverting that, things will still behave just fine.

--
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: Card detect IRQ errors

2009-04-27 Thread Gadiyar, Anand
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org 
> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of 
> Grazvydas Ignotas
> Sent: Monday, April 27, 2009 2:43 PM
> To: linux-omap@vger.kernel.org
> Cc: David Brownell
> Subject: Card detect IRQ errors
> 
> With current l-o head when I insert or remove SD card I'm getting this:
> 
> [   20.733489] [ cut here ]
> [   20.738159] WARNING: at kernel/irq/handle.c:366 
> handle_IRQ_event+0x4c/0x14c()
> [   20.745330] BUG: IRQ handler called from non-hardirq
> context!Modules linked in:
> [   20.752685] [<8002b388>] (unwind_backtrace+0x0/0xdc) from
> [<80048128>] (warn_slowpath+0x64/0x88)
> [   20.761596] [<80048128>] (warn_slowpath+0x64/0x88) from
> [<8006a80c>] (handle_IRQ_event+0x4c/0x14c)
> [   20.770629] [<8006a80c>] (handle_IRQ_event+0x4c/0x14c) from
> [<8006bde8>] (handle_edge_irq+0x10c/0x14c)
> [   20.780029] [<8006bde8>] (handle_edge_irq+0x10c/0x14c) from
> [<801862a8>] (handle_twl4030_sih+0x9c/0xd0)
> [   20.789520] [<801862a8>] (handle_twl4030_sih+0x9c/0xd0) from
> [<801861b0>] (twl4030_irq_thread+0x108/0x164)
> [   20.799255] [<801861b0>] (twl4030_irq_thread+0x108/0x164) from
> [<80059708>] (kthread+0x54/0x80)
> [   20.808044] [<80059708>] (kthread+0x54/0x80) from [<8004ab68>]
> (do_exit+0x0/0x56c)
> [   20.815704] [<8004ab68>] (do_exit+0x0/0x56c) from 
> [<8ecf0ae0>] (0x8ecf0ae0)
> [   20.822753] ---[ end trace 2ca2d8ba630dd6b5 ]---
> [   20.869415] mmc0: card 8001 removed
> 
> Has anyone else seen this?


Me too. Was just about to report it.

I get this with a 3430 SDP and mainline kernel. No MMC card inserted.

- Anand
--
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


Card detect IRQ errors

2009-04-27 Thread Grazvydas Ignotas
With current l-o head when I insert or remove SD card I'm getting this:

[   20.733489] [ cut here ]
[   20.738159] WARNING: at kernel/irq/handle.c:366 handle_IRQ_event+0x4c/0x14c()
[   20.745330] BUG: IRQ handler called from non-hardirq
context!Modules linked in:
[   20.752685] [<8002b388>] (unwind_backtrace+0x0/0xdc) from
[<80048128>] (warn_slowpath+0x64/0x88)
[   20.761596] [<80048128>] (warn_slowpath+0x64/0x88) from
[<8006a80c>] (handle_IRQ_event+0x4c/0x14c)
[   20.770629] [<8006a80c>] (handle_IRQ_event+0x4c/0x14c) from
[<8006bde8>] (handle_edge_irq+0x10c/0x14c)
[   20.780029] [<8006bde8>] (handle_edge_irq+0x10c/0x14c) from
[<801862a8>] (handle_twl4030_sih+0x9c/0xd0)
[   20.789520] [<801862a8>] (handle_twl4030_sih+0x9c/0xd0) from
[<801861b0>] (twl4030_irq_thread+0x108/0x164)
[   20.799255] [<801861b0>] (twl4030_irq_thread+0x108/0x164) from
[<80059708>] (kthread+0x54/0x80)
[   20.808044] [<80059708>] (kthread+0x54/0x80) from [<8004ab68>]
(do_exit+0x0/0x56c)
[   20.815704] [<8004ab68>] (do_exit+0x0/0x56c) from [<8ecf0ae0>] (0x8ecf0ae0)
[   20.822753] ---[ end trace 2ca2d8ba630dd6b5 ]---
[   20.869415] mmc0: card 8001 removed

Has anyone else seen this?
--
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