* Matthijs van Duin <matthijsvanduin@xxxxxxxxx> [161013 13:25]: > It would indeed be very useful to have a reproducible case on an > uptodate kernel, but it is definitely not specific to his hardware. > Someone on the beagleboard forum also hit this issue, but sporadically: > > https://groups.google.com/d/msg/beagleboard/5ZwTUQwGSx4/r15mENdfAwAJ > > I'll quote my reply to it: > > On 4 October 2016 at 21:00, Matthijs van Duin <matthijsvanduin@xxxxxxxxx> wrote: > > I've also run into this once during an apt-get upgrade, leaving the system > > in a pretty hosed state. I managed to recover it but it required a lot of > > effort. Although evidently rare, this is clearly a very serious issue. > > > > The direct cause is edma_prep_slave_sg() failing to allocate memory for the > > struct edma_desc. I don't know whether the kernel is genuinely out of memory > > or if it simply cannot free it up immediately (the allocation is done with > > GPF_ATOMIC), and whether this is because it is filled with a backlog of > > writes or whether a leak of some sort is going on. > > > > Instead of deferring until memory is available, or even just proceeding > > without DMA, the omap_hsmmc driver immediately fails the request with an > > error, thus pretty much guaranteeing loss of data or even filesystem > > corruption. I personally think this is completely unacceptable behaviour of > > a block driver. Yes I can see that being a problem. The fact that omap_hsmmc does not fail back to PIO mode is just strange. We've had the omap1 drivers/mmc/host/omap.c work with and without DMA no problem, no idea why this would not be required also for omap_hsmmc too. > > I've been meaning to persue this matter on the linux-mmc and/or linux-omap > > lists, but since it was a single isolated incident and I have lots of other > > stuff to do I haven't been able to find the time and motivation yet. > > If Ankur has a reproducible case then I think it's time to get > motivated. Ankur, can you please try 4.7 or 4.8 ? Yes please. And also let's set up a new bug in bugzilla.kernel.org for this. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
