On 27 January 2017 at 20:20, Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxxxx> wrote: > Ulf Hansson <ulf.hansson@xxxxxxxxxx> writes: > >> On 16 January 2017 at 15:23, Gabriel Krisman Bertazi >> <krisman@xxxxxxxxxxxxxxx> wrote: >>> One of our kernelCI boxes hanged at boot because a faulty eSDHC device >>> was triggering spurious CARD_INT interrupts for SD cards, causing CMD52 >>> reads, which are not allowed for SD devices. This adds a sanity check >>> to the interruption path, preventing that illegal command from getting >>> sent if the CARD_INT interruption should be disabled. >>> >>> This quirk allows that particular machine to resume boot despite the >>> faulty hardware, instead of getting hung dealing with thousands of >>> mishandled interrupts. >>> >>> Suggested-by: Adrian Hunter <adrian.hunter@xxxxxxxxx> >>> Signed-off-by: Gabriel Krisman Bertazi <krisman@xxxxxxxxxxxxxxx> >>> CC: Ulf Hansson <ulf.hansson@xxxxxxxxxx> >>> CC: linux-mmc@xxxxxxxxxxxxxxx >> >> Thanks, applied for next with update commit msg header and by removing >> the CCs from the changelog. > > Hi Ulf, > > Thanks for applying. Although, I saw it got queued to the next merge > window, but I we believe it to be -rc material, since it fixes a hang > in our kernelCI boxes[1], and is preventing us from testing other features > in this box. Can you consider submitting it to Linus for the next -rc? > it will be much appreciated! I can do that, but perhaps this should then be tagged for stable as well? Or was this a regression in 4.10? Kind regards Uffe > > [1] <https://kernelci.org/boot/id/5881c81859b5140b59f6c3ae/> > > Thanks. > > -- > Gabriel Krisman Bertazi -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
