From: Adrian Hunter <adrian.hunter@intel.com>
To: Andreas Radke <andreas.radke@mailbox.org>, linux-mmc@vger.kernel.org
Cc: ulf.hansson@linaro.org
Subject: Re: constant media change events - hardware or driver problem?
Date: Tue, 25 Oct 2022 19:55:03 +0300 [thread overview]
Message-ID: <534dfadc-5f68-df2a-6c85-c2c221d8c7e0@intel.com> (raw)
In-Reply-To: <20221025153602.3cacaae6@workstation64>
On 25/10/22 16:36, Andreas Radke wrote:
> My Zotac Ci323 system with builtin sd-card reader keeps firing off
> media change events" DISK_MEDIA_CHANGE=1". It may be a driver or
> hardware problem and was detected by some systemd changes introduced
> between v250 and v251.
> Please have a look at https://github.com/systemd/systemd/issues/25021.
>
> I've already updated to latest Zotac bios 2K210510. There's
> currently no related kernel module loaded due to blacklisting
> sdhci_pci/sdhci/cqhci/mmc_core modules.
>
> I can stop the mess when inserting an unneeded sd-card into the slot.
>
> lspci -vvs 00:10.0
> 00:10.0 SD Host controller: Intel Corporation Atom/Celeron/Pentium
> Processor x5-E8000/J3xxx/N3xxx Series MMC Controller (rev 21) (prog-if
> 01) Subsystem: ZOTAC International (MCO) Ltd. Device b301 Control: I/O-
> Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
> FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
>> TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line
>> Size: 64 bytes Interrupt: pin A routed to IRQ 11
> Region 0: Memory at 81516000 (32-bit, non-prefetchable)
> [size=4K] Capabilities: [80] Power Management version 3
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable-
> DSel=0 DScale=0 PME- Kernel modules: sdhci_pci
>
> Can you help me to find out if there's something wrong in the linux
> kernel / maybe a driver or subsystem bug or if this a hardware issue?
>
> Should I file some kernel bug?
I may be misreading this, but the device causing the media change events seems to be:
/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1/1-5.1:1.0/host2/target2:0:0/2:0:0:0/block/sdb
and the driver is ums-realtek which is a USB Storage driver for "Realtek Card Reader support".
In that case it does not involve the kernel mmc subsystem at all.
As you listed above, there is an SD Host controller PCI device 00:10.0.
Is there a reason to think that it is also involved?
next prev parent reply other threads:[~2022-10-25 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 13:36 constant media change events - hardware or driver problem? Andreas Radke
2022-10-25 16:55 ` Adrian Hunter [this message]
2022-10-25 17:22 ` Andreas Radke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=534dfadc-5f68-df2a-6c85-c2c221d8c7e0@intel.com \
--to=adrian.hunter@intel.com \
--cc=andreas.radke@mailbox.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox