Hi Bringfried,
On Fri, Dec 17, 2010 at 06:56:49PM +0100, Bringfried Stecklum wrote:
> Thanks for the patch which, however, does not solve the problem. Now I don't
> get the oops immediately upon resume from hibernation but later, on inserting
> the card (2.6.37 is no solution at the moment since m
I figured out that a suspend to memory after resuming from hibernation is a
remedy. When the system is back from suspend, the card is properly reckognised.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo i
I just tried with the irqpoll option which prevents the kernel oops indeed
(unlike without the patch) but I still get the timeout waiting for hardware
interrupt message. The number of irqs seems to be exceedingly high, e.g.
cat /proc/interrupts
CPU0 CPU1
0: 20239
Chris Ball wrote:
Hi Bringfried,
On Fri, Dec 17, 2010 at 11:14:36AM +0100, Bringfried Stecklum wrote:
On resume from hibernation (suspend is fine) a kernel trace happens along with
the well-know "IRQ nobody cared" statement (see below). The interrupt gets
disabled, and since mmc0 is compiled in
Hi Bringfried,
On Fri, Dec 17, 2010 at 11:14:36AM +0100, Bringfried Stecklum wrote:
> On resume from hibernation (suspend is fine) a kernel trace happens along with
> the well-know "IRQ nobody cared" statement (see below). The interrupt gets
> disabled, and since mmc0 is compiled into the kernel,
I recently upgraded from 3.6.31-22 to 3.6.36-1 (Ubuntu kernel nomenclature) and
am quite happy with it apart from the card reader
steck...@extragalactix:~$ lspci |grep Ricoh
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
03:01.1 SD Host controller: Ricoh Co Ltd R5
