linux-kernel - Re: LKFT: arm x15: mmc1: cache flush error -110

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK8P3a09YDtmOjpBWQEsKd09aotvUW6tOoxUE=CYxh1g8hNW7A@mail.gmail.com>
Date:   Fri, 14 Feb 2020 10:09:34 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Jens Axboe <axboe@...nel.dk>, Alexei Starovoitov <ast@...nel.org>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        linux-block <linux-block@...r.kernel.org>,
        lkft-triage@...ts.linaro.org,
        open list <linux-kernel@...r.kernel.org>,
        linux-mmc <linux-mmc@...r.kernel.org>,
        John Stultz <john.stultz@...aro.org>,
        Mark Brown <broonie@...nel.org>
Subject: Re: LKFT: arm x15: mmc1: cache flush error -110

On Thu, Feb 13, 2020 at 4:43 PM Naresh Kamboju
<naresh.kamboju@...aro.org> wrote:
>
> 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: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>   git commit: aae1464f46a2403565f75717438118691d31ccf1
>   git describe: v5.5-489-gaae1464f46a2

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

If it's easy for you to reproduce, please run the same test on commit
e4e4c2ff78ed from Mark's regulator tree to narrow it down further.

Added Mark to Cc as well, in case it is indeed one of those.

      Arnd

8<---
> Test output log,
> [   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
> [   37.627387] Aborting journal on device mmcblk1p9-8.
> [   37.635448] systemd[1]: Installed transient /etc/machine-id file.
> [   37.659283] systemd[1]: Couldn't move remaining userspace
> processes, ignoring: Input/output error
> [   37.744027] EXT4-fs error (device mmcblk1p9):
> ext4_journal_check_start:61: Detected aborted journal
> [   37.753322] EXT4-fs (mmcblk1p9): Remounting filesystem read-only
> [   37.917486] systemd-gpt-auto-generator[108]: Failed to dissect:
> Input/output error
> [   37.927825] systemd[104]:
> /lib/systemd/system-generators/systemd-gpt-auto-generator failed with
> exit status 1.
> <>
> [   68.856307] mmc1: Card stuck being busy! mmc_poll_for_busy
> [   68.861838] mmc1: cache flush error -110
> [   68.865812] blk_update_request: I/O error, dev mmcblk1, sector 0 op
> 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
> <>
> [   98.906243] mmc1: Card stuck being busy! mmc_poll_for_busy
> [   98.911774] mmc1: cache flush error -110
> [   98.915747] blk_update_request: I/O error, dev mmcblk1, sector 0 op
> 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
> <>
> Dependency failed for Serial Getty on ttyS2.
> [  128.946258] mmc1: Card stuck being busy! mmc_poll_for_busy
> [  128.951786] mmc1: cache flush error -110
> [  128.955756] blk_update_request: I/O error, dev mmcblk1, sector 0 op
> 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
> [FAILED] Failed to start File System Check on Root Device.
> See 'systemctl status systemd-fsck-root.service' for details.
> [  OK  ] Started Apply Kernel Variables.
> [  OK  ] Reached target Login Prompts.
>          Starting Remount Root and Kernel File Systems...
> [  OK  ] Reached target Timers.
> [  OK  ] Closed Syslog Socket.
> [  OK  ] Started Emergency Shell.
> [  129.227328] EXT4-fs error (device mmcblk1p9): ext4_remount:5354:
> Abort forced by user
> [  OK  ] Reached target Emergency Mode.
> [  OK  ] Reached target Sockets.
> [FAILED] Failed to start Remount Root and Kernel File Systems.
> <>
> You are in emergency mode. After logging in, type \"journalctl -xb\" to view
> system logs, \"systemctl reboot\" to reboot, \"systemctl default\" or \"exit\"
> to boot into default mode.
> Press Enter for maintenance
> auto-login-action timed out after 874 seconds
>
> ref:
> https://lkft.validation.linaro.org/scheduler/job/1137693#L4034
> https://lkft.validation.linaro.org/scheduler/job/1158106#L4048
> https://lkft.validation.linaro.org/scheduler/job/1137690#L3985
> https://lkft.validation.linaro.org/scheduler/job/1137691#L4012
> https://lkft.validation.linaro.org/scheduler/job/1137696#L4043
> https://lkft.validation.linaro.org/scheduler/job/1137699#L4153