[Bug 1196618] New: RPi3/RPi4: Occasional "error -110 whilst initialising SD card" on boot
https://bugzilla.suse.com/show_bug.cgi?id=1196618 Bug ID: 1196618 Summary: RPi3/RPi4: Occasional "error -110 whilst initialising SD card" on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/2218590/modules/jour nal_check/steps/10 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@suse.de Reporter: fvogt@suse.com QA Contact: qa-bugs@suse.de CC: guillaume.gardet@opensuse.org Found By: openQA Blocker: Yes Leap 15.4: https://openqa.opensuse.org/tests/2218590#step/journal_check/10 Tumbleweed: https://openqa.opensuse.org/tests/2218201#step/journal_check/10 This does not always happen, e.g.: https://openqa.opensuse.org/tests/2192626 ## Observation openQA test in scenario opensuse-15.4-JeOS-for-RPi-aarch64-jeos@RPi4 fails in [journal_check](https://openqa.opensuse.org/tests/2218590/modules/journal_check/steps/10) ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [5.1](https://openqa.opensuse.org/tests/2076851) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensuse&am...) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196618 https://bugzilla.suse.com/show_bug.cgi?id=1196618#c1 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume.gardet@arm.com --- Comment #1 from Guillaume GARDET <guillaume.gardet@arm.com> --- openQA uses a USB-SD-Mux device [0] to flash the uSD, so this may have an impact. [0]: https://linux-automation.com/en/products/usb-sd-mux.html -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196618 https://bugzilla.suse.com/show_bug.cgi?id=1196618#c2 --- Comment #2 from openQA Review <openqa-review@suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi4 https://openqa.opensuse.org/tests/2247463 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 28 days if nothing changes in this ticket. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196618 https://bugzilla.suse.com/show_bug.cgi?id=1196618#c3 Ivan Ivanov <ivan.ivanov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan.ivanov@suse.com --- Comment #3 from Ivan Ivanov <ivan.ivanov@suse.com> --- (In reply to Guillaume GARDET from comment #1)
openQA uses a USB-SD-Mux device [0] to flash the uSD, so this may have an impact.
Maybe is uSD card itself. Any chances to change them? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196618 https://bugzilla.suse.com/show_bug.cgi?id=1196618#c4 --- Comment #4 from Guillaume GARDET <guillaume.gardet@arm.com> --- (In reply to Ivan Ivanov from comment #3)
(In reply to Guillaume GARDET from comment #1)
openQA uses a USB-SD-Mux device [0] to flash the uSD, so this may have an impact.
Maybe is uSD card itself. Any chances to change them?
I think this is related to the combination of fast uSD card and USB-SD-Mux hardware. See: https://github.com/linux-automation/usbsdmux#troubleshooting Quote: "Some single board computers, especially Raspberry Pi model 4s, do not work with new/fast micro SD cards, due to drive strength issues at high frequencies. Use old and slow micro SD cards with these devices. Another workaround is the replacement of resistors R101 and R102 with 0�� parts. This modifications does however void the EMC compliance statement provided by the Linux Automation GmbH." I do not have slower uSD card available. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196618 https://bugzilla.suse.com/show_bug.cgi?id=1196618#c5 --- Comment #5 from openQA Review <openqa-review@suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi4 https://openqa.opensuse.org/tests/2271683#step/journal_check/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 28 days if nothing changes in this ticket. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196618 https://bugzilla.suse.com/show_bug.cgi?id=1196618#c6 --- Comment #6 from openQA Review <openqa-review@suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi4 https://openqa.opensuse.org/tests/2318030#step/journal_check/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 56 days if nothing changes in this ticket. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196618 https://bugzilla.suse.com/show_bug.cgi?id=1196618#c7 --- Comment #7 from openQA Review <openqa-review@suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi4 https://openqa.opensuse.org/tests/2450361#step/journal_check/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 112 days if nothing changes in this ticket. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196618 https://bugzilla.suse.com/show_bug.cgi?id=1196618#c8 --- Comment #8 from Ivan Ivanov <ivan.ivanov@suse.com> --- Fabian, could we close this bug? It doesn't seem that we can do anything here. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com