FS#49705 - [linux] 4.6.x SD Host controller: O2 Micro, Inc. Device 8621 (rev 01) does't work.

Attached to Project: Arch Linux
Opened by eugen (jales79) - Tuesday, 14 June 2016, 05:31 GMT
Last edited by Toolybird (Toolybird) - Saturday, 27 May 2023, 07:29 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
SD Cardreader doesn't work.
dmesg message: mmc0: Unknown controller version (3). You may experience problems.
SD Host controller: O2 Micro, Inc. Device 8621 (rev 01) does't work.

Additional info:
* package version(s)
* config and/or log files etc.

my Notebook: in attach.
Kernel:4.6.2-1-ARCH



Steps to reproduce:
   ds-lifebook-e756-de.pdf (821.7 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 27 May 2023, 07:29 GMT
Reason for closing:  No response
Additional comments about closing:  Plus it's old and stale. If still an issue, please report upstream.
Comment by Doug Newgard (Scimmia) - Wednesday, 15 June 2016, 14:40 GMT
Is it supposed to work?
Comment by eugen (jales79) - Wednesday, 15 June 2016, 17:29 GMT
Hi,
sorry for my english :-)

Is it supposed to work? -> yes.
Comment by Clayton Craft (craftyguy) - Saturday, 24 June 2017, 23:18 GMT
I also see this. When I insert an SD card, my system (Intel NUC NUC6i7KYK) kernel panics. This is on 4.11.6. I know of sdhci module quirk parameters that can be set, but setting some (like 0x400, 0x4, 0x8000) don't seem to help. The kernel output when a SD card is plugged in is attached.


   o2_kernel_panic.log (167.4 KiB)
Comment by Daniel (8472) - Friday, 09 March 2018, 18:17 GMT
Same problem here (1217:8621), failing with the recent kernels (LTS (4.14.19-1-lts or 4.14.24-1-lts) and non-LTS (4.15.3-2 or 4.15.7-1)).
The debug_quirks2="0x10000" which was working some time ago stopped working.

However, craftyguy's (thx for the tip) mentioned values 0x8000 and 0x4 (not the 0x400) seems to have helped (at least to me).
Comment by mattia (nTia89) - Sunday, 27 February 2022, 11:25 GMT
I cannot reproduce the issue. Is it still valid for you?

Loading...