[lkml]   [2020]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: LKFT: arm x15: mmc1: cache flush error -110
On Fri, Feb 14, 2020 at 10:09:34AM +0100, Arnd Bergmann wrote:
> On Thu, Feb 13, 2020 at 4:43 PM Naresh Kamboju

> > arm beagleboard x15 device failed to boot Linux mainline and
> > linux-next kernel due
> > to below error.
> > This error occurred across all x15 device for these kernel version.

> > This regression started happening on x15 from this commit onwards (27th Jan)
> > git branch: master
> > git repo:
> > git commit: aae1464f46a2403565f75717438118691d31ccf1
> > git describe: v5.5-489-gaae1464f46a2

That's Linus' commit:

Merge tag 'regulator-v5.6' of git://

Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.

> Is it only the merge that introduced the issue, or is the branch that got
> merged already broken?

Or is this just the first commit where the problem happened to be
noticed? Commits done just before that on the same day include the
dmaengine and MMC merges which seem potentially relevant:

> > [ 37.606241] mmc1: Card stuck being busy! mmc_poll_for_busy
> > [ 37.611850] mmc1: cache flush error -110
> > [ 37.615883] blk_update_request: I/O error, dev mmcblk1, sector
> > 4302400 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2020-02-14 13:10    [W:0.107 / U:0.756 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site