Bug#1065611: Additional support for SolidRun HoneyComb
Hi Diederik, May I ask if you are analyzing dts manually, or whether you are aware of an automatic tool? sincerely Josua Mayer Am 12.03.24 um 18:04 schrieb Diederik de Haas: > Hi Josua, > > On Tuesday, 12 March 2024 16:28:06 CET Josua Mayer wrote: >> I believe I found the answer: >> EDAC_MPC85XX is for power-pc only, >> EDAC_LAYERSCAPE is for arm (see drivers/edac/layerscape_edac.c). > You're right. In the commit I referenced earlier (ea2eb9a8b6207ee4), > I misinterpreted the commit message. > That commit also created ``drivers/edac/fsl_ddr_edac.c`` which got the arch > independent (or at least dual arch) parts. Its header has this: > ``` > * Support Power-based SoCs including MPC85xx, MPC86xx, MPC83xx and > * ARM-based Layerscape SoCs including LS2xxx. Originally split > * out from mpc85xx_edac EDAC driver. > ``` > >> Am 12.03.24 um 16:13 schrieb Josua Mayer: >>> Thank you for taking care of this! >>> First the additional changes you found seem reasonable. > Excellent, then I'll make a MR for them (except EDAC_MPC85XX): > - drivers/hwmon/pmbus: Enable PMBUS, SENSORS_PMBUS and >SENSORS_LTC2978 as modules > - drivers/nvmem: Enable NVMEM_LAYERSCAPE_SFP as module > - drivers/rtc: Enable RTC_DRV_FSL_FTM_ALARM as module > - drivers/soc/fsl: Enable FSL_RCPM > >>> Regarding edac - I checked NXPs reference BSP for LX2160, >>> and their linux fork has the same status, driver can not be enabled on >>> arm64. >>> However I also agree it should be enabled if it were possible. >>> The driver appears to setup ecc bit error interrupts so that hey can be >>> reported by Linux. >>> ... >>> I may have access to an lx2160a system with ecc memory within the coming >>> week, so I could test (on vendor kernel based on 5.10 only) whether any >>> problems show up. If not, perhaps a patch to the kernel is advisable. > As EDAC_LAYERSCAPE got enabled in 5.5.17-1 via bug 948576 (with a patch from > you), ECC support should already work with the Stable 6.1 kernel (or newer). > >>> Am 07.03.24 um 13:34 schrieb Diederik de Haas: >>>> On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: >>>> >>>>> LX2160 SoC early silicon revisions have a pci-e generation 4 >>>>> controller. >>>>> It requires a different driver from newer gen-3 silicon. >>>>> >>>>> This affects the SolidRun Honeycomb Workstation which >>>>> is otherwise fully supported in Debian. >>>> I cloned bug report #1061116 into #1065611 to discuss some additional >>>> support for the SolidRun HoneyComb. >>>> >>>> I analyzed the HoneyComb dts file and the following included .dtsi >>>> files: >>>> - arch/arm64/boot/dts/freescale/fsl-lx2160a-clearfog-itx.dtsi >>>> - arch/arm64/boot/dts/freescale/fsl-lx2160a-cex7.dtsi >>>> - arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi > If my MR gets merged, then there's truly full support in Debian :) > > Cheers, > Diederik
Bug#1065611: Additional support for SolidRun HoneyComb
Hi Diederik, I believe I found the answer: EDAC_MPC85XX is for power-pc only, EDAC_LAYERSCAPE is for arm (see drivers/edac/layerscape_edac.c). br Josua Am 12.03.24 um 16:13 schrieb Josua Mayer: > Hi Diederik, > > Thank you for taking care of this! > First the additional changes you found seem reasonable. > > Regarding edac - I checked NXPs reference BSP for LX2160, > and their linux fork has the same status, driver can not be enabled on arm64. > > However I also agree it should be enabled if it were possible. > The driver appears to setup ecc bit error interrupts so that hey can be > reported by Linux. > > Here is what other qoriq drivers do: > drivers/crypto/caam/Kconfig: depends on FSL_SOC || ARCH_MXC || > ARCH_LAYERSCAPE > > I may have access to an lx2160a system with ecc memory within the coming week, > so I could test (on vendor kernel based on 5.10 only) whether any problems > show up. > If not, perhaps a patch to the kernel is advisable. > > Am 07.03.24 um 13:34 schrieb Diederik de Haas: > >> Hi Josua, >> >> On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: >>> LX2160 SoC early silicon revisions have a pci-e generation 4 controller. >>> It requires a different driver from newer gen-3 silicon. >>> >>> This affects the SolidRun Honeycomb Workstation which >>> is otherwise fully supported in Debian. >> I cloned bug report #1061116 into #1065611 to discuss some additional >> support >> for the SolidRun HoneyComb. >> >> I analyzed the HoneyComb dts file and the following included .dtsi files: >> - arch/arm64/boot/dts/freescale/fsl-lx2160a-clearfog-itx.dtsi >> - arch/arm64/boot/dts/freescale/fsl-lx2160a-cex7.dtsi >> - arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi >> >> If I exclude the kernel modules from 1061116 and 1061117, then I still have >> the following list of additional modules to enable: >> - drivers/edac: Enable EDAC_MPC85XX >> - drivers/hwmon/pmbus: Enable PMBUS, SENSORS_PMBUS and >> SENSORS_LTC2978 as modules >> - drivers/nvmem: Enable NVMEM_LAYERSCAPE_SFP as module >> - drivers/rtc: Enable RTC_DRV_FSL_FTM_ALARM as module >> - drivers/soc/fsl: Enable FSL_RCPM >> >> If you agree that this is a good list I can make a MR to get them enabled. >> A MR for 1061116 and 1061117 has just been merged in our 'master' branch. >> >> But I ran into an issue when looking at the ``EDAC_MPC85XX`` stanza >> in``drivers/edac/Kconfig``: >> ``depends on FSL_SOC && EDAC=y`` >> >> But ``FSL_SOC`` is (only) defined in ``arch/powerpc/Kconfig``, which means >> ``EDAC_MPC85XX`` can not be enabled on ``arm64``. >> That module was found based on ``compatible = >> "fsl,qoriq-memory-controller"``, >> which sounds like something you would want to have. >> >> Upstream commit ea2eb9a8b6207ee4 has the following commit message: >> ``` >> EDAC, fsl-ddr: Separate FSL DDR driver from MPC85xx >> >> The mpc85xx-compatible DDR controllers are used on ARM-based SoCs too. >> Carve out the DDR part from the mpc85xx EDAC driver in preparation to >> support both architectures. >> ``` >> Which I interpret as all (?) the preparations for supporting both powerpc >> and >> ARM were made, but they forgot to update the strict dependency of >> ``EDAC_MPC85XX`` to powerpc to actually support both architectures? >> >> Can you shed some light on this? >> >> Cheers, >> Diederik
Bug#1065611: Additional support for SolidRun HoneyComb
Hi Diederik, Thank you for taking care of this! First the additional changes you found seem reasonable. Regarding edac - I checked NXPs reference BSP for LX2160, and their linux fork has the same status, driver can not be enabled on arm64. However I also agree it should be enabled if it were possible. The driver appears to setup ecc bit error interrupts so that hey can be reported by Linux. Here is what other qoriq drivers do: drivers/crypto/caam/Kconfig: depends on FSL_SOC || ARCH_MXC || ARCH_LAYERSCAPE I may have access to an lx2160a system with ecc memory within the coming week, so I could test (on vendor kernel based on 5.10 only) whether any problems show up. If not, perhaps a patch to the kernel is advisable. Am 07.03.24 um 13:34 schrieb Diederik de Haas: > Hi Josua, > > On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: >> LX2160 SoC early silicon revisions have a pci-e generation 4 controller. >> It requires a different driver from newer gen-3 silicon. >> >> This affects the SolidRun Honeycomb Workstation which >> is otherwise fully supported in Debian. > I cloned bug report #1061116 into #1065611 to discuss some additional support > for the SolidRun HoneyComb. > > I analyzed the HoneyComb dts file and the following included .dtsi files: > - arch/arm64/boot/dts/freescale/fsl-lx2160a-clearfog-itx.dtsi > - arch/arm64/boot/dts/freescale/fsl-lx2160a-cex7.dtsi > - arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi > > If I exclude the kernel modules from 1061116 and 1061117, then I still have > the following list of additional modules to enable: > - drivers/edac: Enable EDAC_MPC85XX > - drivers/hwmon/pmbus: Enable PMBUS, SENSORS_PMBUS and > SENSORS_LTC2978 as modules > - drivers/nvmem: Enable NVMEM_LAYERSCAPE_SFP as module > - drivers/rtc: Enable RTC_DRV_FSL_FTM_ALARM as module > - drivers/soc/fsl: Enable FSL_RCPM > > If you agree that this is a good list I can make a MR to get them enabled. > A MR for 1061116 and 1061117 has just been merged in our 'master' branch. > > But I ran into an issue when looking at the ``EDAC_MPC85XX`` stanza > in``drivers/edac/Kconfig``: > ``depends on FSL_SOC && EDAC=y`` > > But ``FSL_SOC`` is (only) defined in ``arch/powerpc/Kconfig``, which means > ``EDAC_MPC85XX`` can not be enabled on ``arm64``. > That module was found based on ``compatible = > "fsl,qoriq-memory-controller"``, > which sounds like something you would want to have. > > Upstream commit ea2eb9a8b6207ee4 has the following commit message: > ``` > EDAC, fsl-ddr: Separate FSL DDR driver from MPC85xx > > The mpc85xx-compatible DDR controllers are used on ARM-based SoCs too. > Carve out the DDR part from the mpc85xx EDAC driver in preparation to > support both architectures. > ``` > Which I interpret as all (?) the preparations for supporting both powerpc and > ARM were made, but they forgot to update the strict dependency of > ``EDAC_MPC85XX`` to powerpc to actually support both architectures? > > Can you shed some light on this? > > Cheers, > Diederik
Bug#1061117: linux-image-6.1.0-17-arm64: please enable support for lx2160a serdes runtime configuration
Package: src:linux Version: 6.1.69-1 Severity: important X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, Please enable support for lx2160a serdes configuration driver in arm64 flavour: CONFIG_PHY_FSL_LYNX_28G This driver is essential for supporting the SFP+ connectors on SolidRun Honeycomb Workstation. Since mainline added references to SerDes via "phys" properties in v5.18, Debian can not probe the netdev's, breaking all 10Gbps NICs. Ideally this will be enabled for current stable release, too. Sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 6.1.0-17-arm64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.1.69-1 (2023-12-30) ** Command line: arm-smmu.disable-bypass=0 console=ttyAMA0,38400n8 quiet ** Not tainted ** Kernel log: [4.330447] alg: No test for authenc(hmac(md5),cbc(aes)) (authenc-hmac-md5-cbc-aes-caam-qi2) [4.330532] alg: No test for echainiv(authenc(hmac(md5),cbc(aes))) (echainiv-authenc-hmac-md5-cbc-aes-caam-qi2) [4.334627] audit: type=1400 audit(1705595241.215:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=525 comm="apparmor_parser" [4.335982] audit: type=1400 audit(1705595241.215:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=526 comm="apparmor_parser" [4.335991] audit: type=1400 audit(1705595241.215:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=526 comm="apparmor_parser" [4.336012] alg: No test for echainiv(authenc(hmac(sha1),cbc(aes))) (echainiv-authenc-hmac-sha1-cbc-aes-caam-qi2) [4.336100] alg: No test for authenc(hmac(sha224),cbc(aes)) (authenc-hmac-sha224-cbc-aes-caam-qi2) [4.336178] alg: No test for echainiv(authenc(hmac(sha224),cbc(aes))) (echainiv-authenc-hmac-sha224-cbc-aes-caam-qi2) [4.339390] alg: No test for echainiv(authenc(hmac(sha256),cbc(aes))) (echainiv-authenc-hmac-sha256-cbc-aes-caam-qi2) [4.339495] alg: No test for authenc(hmac(sha384),cbc(aes)) (authenc-hmac-sha384-cbc-aes-caam-qi2) [4.339619] alg: No test for echainiv(authenc(hmac(sha384),cbc(aes))) (echainiv-authenc-hmac-sha384-cbc-aes-caam-qi2) [4.340663] audit: type=1400 audit(1705595241.219:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=528 comm="apparmor_parser" [4.340674] audit: type=1400 audit(1705595241.219:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=528 comm="apparmor_parser" [4.340680] audit: type=1400 audit(1705595241.219:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=528 comm="apparmor_parser" [4.342833] alg: No test for echainiv(authenc(hmac(sha512),cbc(aes))) (echainiv-authenc-hmac-sha512-cbc-aes-caam-qi2) [4.342951] alg: No test for authenc(hmac(md5),cbc(des3_ede)) (authenc-hmac-md5-cbc-des3_ede-caam-qi2) [4.343067] alg: No test for echainiv(authenc(hmac(md5),cbc(des3_ede))) (echainiv-authenc-hmac-md5-cbc-des3_ede-caam-qi2) [4.343743] alg: No test for echainiv(authenc(hmac(sha1),cbc(des3_ede))) (echainiv-authenc-hmac-sha1-cbc-des3_ede-caam-qi2) [4.344850] alg: No test for echainiv(authenc(hmac(sha224),cbc(des3_ede))) (echainiv-authenc-hmac-sha224-cbc-des3_ede-caam-qi2) [4.345868] alg: No test for echainiv(authenc(hmac(sha256),cbc(des3_ede))) (echainiv-authenc-hmac-sha256-cbc-des3_ede-caam-qi2) [4.346863] alg: No test for echainiv(authenc(hmac(sha384),cbc(des3_ede))) (echainiv-authenc-hmac-sha384-cbc-des3_ede-caam-qi2) [4.347587] alg: No test for echainiv(authenc(hmac(sha512),cbc(des3_ede))) (echainiv-authenc-hmac-sha512-cbc-des3_ede-caam-qi2) [4.347693] alg: No test for authenc(hmac(md5),cbc(des)) (authenc-hmac-md5-cbc-des-caam-qi2) [4.347810] alg: No test for echainiv(authenc(hmac(md5),cbc(des))) (echainiv-authenc-hmac-md5-cbc-des-caam-qi2) [4.348851] alg: No test for echainiv(authenc(hmac(sha1),cbc(des))) (echainiv-authenc-hmac-sha1-cbc-des-caam-qi2) [4.349882] alg: No test for echainiv(authenc(hmac(sha224),cbc(des))) (echainiv-authenc-hmac-sha224-cbc-des-caam-qi2) [4.350874] alg: No test for echainiv(authenc(hmac(sha256),cbc(des))) (echainiv-authenc-hmac-sha256-cbc-des-caam-qi2) [4.351895] alg: No test for echainiv(authenc(hmac(sha384),cbc(des))) (echainiv-authenc-hmac-sha384-cbc-des-caam-qi2) [4.352897] alg: No test for echainiv(authenc(hmac(sha512),cbc(des))) (echainiv-authenc-hmac-sha512-cbc-des-caam-qi2) [4.353008] alg: No test for authenc(hmac(md5),rfc3
Bug#1061116: linux-image-6.1.0-17-arm64: please enable support for lx2160a pcie gen4 controller on early silicon
Package: src:linux Version: 6.1.69-1 Severity: normal X-Debbugs-Cc: jo...@solid-run.com Dear Maintainer, Please enable "PCIE_LAYERSCAPE_GEN4" for arm64 flavour, in addition to already enabled "PCIE_LAYERSCAPE". LX2160 SoC early silicon revisions have a pci-e generation 4 controller. It requires a different driver from newer gen-3 silicon. This affects the SolidRun Honeycomb Workstation which is otherwise fully supported in Debian. Ideally the config option wll be enabled for debian stable, too. -- Package-specific info: ** Version: Linux version 6.1.0-17-arm64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.1.69-1 (2023-12-30) ** Command line: arm-smmu.disable-bypass=0 console=ttyAMA0,38400n8 quiet ** Not tainted ** Kernel log: [4.330447] alg: No test for authenc(hmac(md5),cbc(aes)) (authenc-hmac-md5-cbc-aes-caam-qi2) [4.330532] alg: No test for echainiv(authenc(hmac(md5),cbc(aes))) (echainiv-authenc-hmac-md5-cbc-aes-caam-qi2) [4.334627] audit: type=1400 audit(1705595241.215:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=525 comm="apparmor_parser" [4.335982] audit: type=1400 audit(1705595241.215:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=526 comm="apparmor_parser" [4.335991] audit: type=1400 audit(1705595241.215:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=526 comm="apparmor_parser" [4.336012] alg: No test for echainiv(authenc(hmac(sha1),cbc(aes))) (echainiv-authenc-hmac-sha1-cbc-aes-caam-qi2) [4.336100] alg: No test for authenc(hmac(sha224),cbc(aes)) (authenc-hmac-sha224-cbc-aes-caam-qi2) [4.336178] alg: No test for echainiv(authenc(hmac(sha224),cbc(aes))) (echainiv-authenc-hmac-sha224-cbc-aes-caam-qi2) [4.339390] alg: No test for echainiv(authenc(hmac(sha256),cbc(aes))) (echainiv-authenc-hmac-sha256-cbc-aes-caam-qi2) [4.339495] alg: No test for authenc(hmac(sha384),cbc(aes)) (authenc-hmac-sha384-cbc-aes-caam-qi2) [4.339619] alg: No test for echainiv(authenc(hmac(sha384),cbc(aes))) (echainiv-authenc-hmac-sha384-cbc-aes-caam-qi2) [4.340663] audit: type=1400 audit(1705595241.219:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=528 comm="apparmor_parser" [4.340674] audit: type=1400 audit(1705595241.219:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=528 comm="apparmor_parser" [4.340680] audit: type=1400 audit(1705595241.219:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=528 comm="apparmor_parser" [4.342833] alg: No test for echainiv(authenc(hmac(sha512),cbc(aes))) (echainiv-authenc-hmac-sha512-cbc-aes-caam-qi2) [4.342951] alg: No test for authenc(hmac(md5),cbc(des3_ede)) (authenc-hmac-md5-cbc-des3_ede-caam-qi2) [4.343067] alg: No test for echainiv(authenc(hmac(md5),cbc(des3_ede))) (echainiv-authenc-hmac-md5-cbc-des3_ede-caam-qi2) [4.343743] alg: No test for echainiv(authenc(hmac(sha1),cbc(des3_ede))) (echainiv-authenc-hmac-sha1-cbc-des3_ede-caam-qi2) [4.344850] alg: No test for echainiv(authenc(hmac(sha224),cbc(des3_ede))) (echainiv-authenc-hmac-sha224-cbc-des3_ede-caam-qi2) [4.345868] alg: No test for echainiv(authenc(hmac(sha256),cbc(des3_ede))) (echainiv-authenc-hmac-sha256-cbc-des3_ede-caam-qi2) [4.346863] alg: No test for echainiv(authenc(hmac(sha384),cbc(des3_ede))) (echainiv-authenc-hmac-sha384-cbc-des3_ede-caam-qi2) [4.347587] alg: No test for echainiv(authenc(hmac(sha512),cbc(des3_ede))) (echainiv-authenc-hmac-sha512-cbc-des3_ede-caam-qi2) [4.347693] alg: No test for authenc(hmac(md5),cbc(des)) (authenc-hmac-md5-cbc-des-caam-qi2) [4.347810] alg: No test for echainiv(authenc(hmac(md5),cbc(des))) (echainiv-authenc-hmac-md5-cbc-des-caam-qi2) [4.348851] alg: No test for echainiv(authenc(hmac(sha1),cbc(des))) (echainiv-authenc-hmac-sha1-cbc-des-caam-qi2) [4.349882] alg: No test for echainiv(authenc(hmac(sha224),cbc(des))) (echainiv-authenc-hmac-sha224-cbc-des-caam-qi2) [4.350874] alg: No test for echainiv(authenc(hmac(sha256),cbc(des))) (echainiv-authenc-hmac-sha256-cbc-des-caam-qi2) [4.351895] alg: No test for echainiv(authenc(hmac(sha384),cbc(des))) (echainiv-authenc-hmac-sha384-cbc-des-caam-qi2) [4.352897] alg: No test for echainiv(authenc(hmac(sha512),cbc(des))) (echainiv-authenc-hmac-sha512-cbc-des-caam-qi2) [4.353008] alg: No test for authenc(hmac(md5),rfc3686(ctr(aes))) (authenc-hmac-md5-rfc3686-ctr-aes-caam-qi2) [4.353112] alg: No test for seqiv(authenc(hmac(md5),rfc3686(ctr(aes (seqiv-authenc-hmac-md5-rfc3686-ctr-aes-caam-qi2) [4.353323] alg: No test for seqiv(authenc(hmac(sha1),rfc3686(ctr(aes (seqiv-authenc-hmac-sha1-rfc3686-ctr-aes-caam-qi2) [4.353425] alg:
Bug#1043354: linux-image-6.1.0-10-armmp: please enable analog devices ethernet phy driver "adin"
Package: src:linux Version: 6.1.38-2+sr1 Severity: normal Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Please enable the "adin" driver for analog devices ADIN1300 ethernet phy. SolidRun i.MX6 SoMs revision 1.9 and later replaced the original Atheros ethernet PHY with ADIN1300. This combination is fully supported in Linux 6.1. Therefore please enable the kernel module for armhf target. Sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 6.1.0-10-armmp (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.1.38-2+sr1 (2023-08-03) ** Command line: console=ttymxc0,115200 deferred_probe_timeout=10 ahci_imx.hotplug=1 cma=128M log_level=7 net.ifnames=0 ** Tainted: C (1024) * staging driver was loaded ** Kernel log: [ 18.664358] Registered IR keymap rc-empty [ 18.716304] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 18.759979] imx-ipuv3 240.ipu: IPUv3H probed [ 18.774524] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 18.800230] imx-ipuv3 280.ipu: IPUv3H probed [ 18.815890] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0 [ 18.848755] mc: Linux media interface: v0.10 [ 18.947000] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 18.953152] videodev: Linux video capture interface: v2.00 [ 19.011893] dwhdmi-imx 12.hdmi: Detected HDMI TX controller v1.30a with HDCP (DWC HDMI 3D TX PHY) [ 19.040476] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 19.078395] imx_media_common: module is from the staging directory, the quality is unknown, you have been warned. [ 19.096468] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 19.103221] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 19.136549] imx6_media: module is from the staging directory, the quality is unknown, you have been warned. [ 19.167734] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 19.211360] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 19.217588] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 19.242861] CAN device driver interface [ 19.311072] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0 [ 19.330363] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 19.337504] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 19.352112] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 19.359277] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 19.382870] fsl-ssi-dai 2028000.ssi: No cache defaults, reading back from HW [ 19.419980] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops imx_drm_exit [imxdrm]) [ 19.429343] coda 204.vpu: firmware: direct-loading firmware vpu/vpu_fw_imx6q.bin [ 19.454390] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops imx_drm_exit [imxdrm]) [ 19.461379] coda 204.vpu: Using fallback firmware vpu/vpu_fw_imx6q.bin [ 19.511767] coda 204.vpu: Firmware code revision: 46076 [ 19.517435] coda 204.vpu: Initialized CODA960. [ 19.522318] coda 204.vpu: Firmware version: 3.1.1 [ 19.538475] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops imx_drm_exit [imxdrm]) [ 19.582536] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops imx_drm_exit [imxdrm]) [ 19.614946] coda 204.vpu: coda-jpeg-encoder registered as video0 [ 19.626811] imx-drm display-subsystem: bound 12.hdmi (ops dw_hdmi_imx_ops [dw_hdmi_imx]) [ 19.678814] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [ 19.688579] coda 204.vpu: coda-jpeg-decoder registered as video1 [ 19.705350] imx_thermal 20c8000.anatop:tempmon: Extended Commercial CPU temperature grade - max:105C critical:100C passive:95C [ 19.726904] coda 204.vpu: coda-video-encoder registered as video2 [ 19.746329] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 19.768188] coda 204.vpu: coda-video-decoder registered as video3 [ 19.823963] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 19.888081] caam 210.crypto: Entropy delay = 3200 [ 19.953984] caam 210.crypto: Instantiated RNG4 SH0 [ 20.014746] caam 210.crypto: Instantiated RNG4 SH1 [ 20.051209] caam 210.crypto: device ID = 0x0a160100 (Era 4) [ 20.057950] caam 210.crypto: job rings = 2, qi = 0 [ 20.258432] sgtl5000 0-000a: sgtl5000 revision 0x11 [ 20.320280] sgtl5000 0-000a: Using internal LDO instead of VDDD: check ER1 erratum [ 20.553197] debugfs: File 'Headphone Jack' in directory 'dapm' already present! [ 20.687846] imx6_media_csi: module is from the staging directory, the quality is unknown, you have been warned. [ 20.694504] imx6_media_csi: module is from the staging directory, the quality
Bug#993859: linux-image-5.10.0-8-armmp: HDMI audio playback broken on i.MX6 HummingBoard
Package: src:linux Version: 5.10.46-4 Severity: normal X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, During testing I found that audio playback to the HDMI port produces just loud noise. I was playing the amarok jingle as a test: ogg123 -d alsa -o dev:dmix:CARD=DWHDMI first_run_jingle.ogg Hopefully I'll find some time to investiaget - find a point where it still worked, and bisect. Sincerely Josua Mayer This worked previously, but I can put my finger on when exactly. CVhanges since then: -- Package-specific info: ** Version: Linux version 5.10.0-8-armmp (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-4 (2021-08-03) ** Command line: console=ttymxc0,115200 deferred_probe_timeout=10 ahci_imx.hotplug=1 log_level=7 net.ifnames=0 cma=128M ** Tainted: WCE (9728) * kernel issued warning * staging driver was loaded * unsigned module was loaded ** Kernel log: [ 12.069422] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 12.096480] systemd[1]: Reached target Local Encrypted Volumes. [ 12.120468] systemd[1]: Reached target Paths. [ 12.140339] systemd[1]: Reached target Remote File Systems. [ 12.160262] systemd[1]: Reached target Slices. [ 12.176432] systemd[1]: Reached target Swap. [ 12.193295] systemd[1]: Listening on fsck to fsckd communication Socket. [ 12.216699] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 12.241412] systemd[1]: Listening on Journal Audit Socket. [ 12.265183] systemd[1]: Listening on Journal Socket (/dev/log). [ 12.289322] systemd[1]: Listening on Journal Socket. [ 12.318746] systemd[1]: Listening on udev Control Socket. [ 12.341053] systemd[1]: Listening on udev Kernel Socket. [ 12.365221] systemd[1]: Condition check resulted in Huge Pages File System being skipped. [ 12.379484] systemd[1]: Mounting POSIX Message Queue File System... [ 12.416554] systemd[1]: Mounting Kernel Debug File System... [ 12.461157] systemd[1]: Mounting Kernel Trace File System... [ 12.502351] systemd[1]: Starting Create list of static device nodes for the current kernel... [ 12.537094] systemd[1]: Starting Load Kernel Module configfs... [ 12.569557] systemd[1]: Starting Load Kernel Module drm... [ 12.601128] systemd[1]: Starting Load Kernel Module fuse... [ 12.672399] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [ 12.711060] fuse: init (API version 7.32) [ 12.726776] systemd[1]: Starting File System Check on Root Device... [ 12.768988] systemd[1]: Starting Journal Service... [ 12.818378] systemd[1]: Starting Load Kernel Modules... [ 12.866644] systemd[1]: Starting Coldplug All udev Devices... [ 12.981618] systemd[1]: Mounted POSIX Message Queue File System. [ 13.014393] systemd[1]: Mounted Kernel Debug File System. [ 13.068936] systemd[1]: Mounted Kernel Trace File System. [ 13.115109] systemd[1]: Finished Create list of static device nodes for the current kernel. [ 13.159261] systemd[1]: modprobe@configfs.service: Succeeded. [ 13.185653] systemd[1]: Finished Load Kernel Module configfs. [ 13.226694] systemd[1]: modprobe@drm.service: Succeeded. [ 13.248464] systemd[1]: Finished Load Kernel Module drm. [ 13.286712] systemd[1]: modprobe@fuse.service: Succeeded. [ 13.310263] systemd[1]: Finished Load Kernel Module fuse. [ 13.351342] systemd[1]: Finished File System Check on Root Device. [ 13.395286] systemd[1]: Finished Load Kernel Modules. [ 13.448559] systemd[1]: Mounting FUSE Control File System... [ 13.494279] systemd[1]: Mounting Kernel Configuration File System... [ 13.554210] systemd[1]: Started File System Check Daemon to report status. [ 13.610566] systemd[1]: Starting Remount Root and Kernel File Systems... [ 13.682070] systemd[1]: Starting Apply Kernel Variables... [ 13.754329] systemd[1]: Mounted FUSE Control File System. [ 13.823376] systemd[1]: Mounted Kernel Configuration File System. [ 13.927190] systemd[1]: Finished Apply Kernel Variables. [ 13.932734] EXT4-fs (mmcblk1p1): re-mounted. Opts: (null) [ 13.982485] systemd[1]: Started Journal Service. [ 14.285169] systemd-journald[170]: Received client request to flush runtime journal. [ 14.329445] systemd-journald[170]: File /var/log/journal/2ebf67f9996a43629433b9fd557084ee/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 16.708767] random: crng init done [ 16.712184] random: 7 urandom warning(s) missed due to ratelimiting [ 17.413602] Registered IR keymap rc-empty [ 17.500182] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 17.513362] imx-ipuv3 240.ipu: IPUv3H probed [ 17.588254] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 17.764881] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0 [ 17.871183
Bug#987019: (no subject)
Hi Vincent, Thanks for your quick reply (which I failed to notice ) So I did a test today with GPIO_MXC=m, and initramfs-tools in default configuration. gpio_mxc module is included in initramfs automatically, and the system can boot from microSD just fine. Therefore, setting it as a module would do. Yours sincerely Josua mayer
Bug#987365: linux-image-5.10.0-6-armmp: please enabvle support for i.mx6 mipi-csi capture devices
Package: src:linux Version: 5.10.28-1 Severity: wishlist Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Please enable support for the mipi-csi capture devices on i.MX6 SoCs, as used e.g. by the SolidRun i.MX6 HummingBoard (config patch attached). Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 5.10.0-6-armmp (debian-kernel@lists.debian.org) (arm-linux-gnueabihf-gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) ** Command line: console=ttymxc0,115200 deferred_probe_timeout=10 ahci_imx.hotplug=1 log_level=7 net.ifnames=0 ** Tainted: WCE (9728) * kernel issued warning * staging driver was loaded * unsigned module was loaded ** Kernel log: [ 11.819025] systemd[1]: modprobe@fuse.service: Succeeded. [ 11.834720] systemd[1]: Finished Load Kernel Module fuse. [ 11.859671] systemd[1]: Finished Load Kernel Modules. [ 11.879573] systemd[1]: Finished Remount Root and Kernel File Systems. [ 11.915841] systemd[1]: Mounting FUSE Control File System... [ 11.955104] systemd[1]: Mounting Kernel Configuration File System... [ 11.998308] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [ 12.007284] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. [ 12.023562] systemd[1]: Starting Load/Save Random Seed... [ 12.050667] systemd[1]: Starting Apply Kernel Variables... [ 12.078727] systemd[1]: Starting Create System Users... [ 12.114011] systemd[1]: Started Journal Service. [ 12.303087] systemd-journald[173]: Received client request to flush runtime journal. [ 14.239809] Registered IR keymap rc-empty [ 14.289888] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 14.302153] imx-ipuv3 240.ipu: IPUv3H probed [ 14.329978] imx-ipuv3 280.ipu: IPUv3H probed [ 14.344837] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 14.469667] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0 [ 14.512465] random: crng init done [ 14.515899] random: 7 urandom warning(s) missed due to ratelimiting [ 14.560825] imx_media_common: module is from the staging directory, the quality is unknown, you have been warned. [ 14.618396] imx6_media: module is from the staging directory, the quality is unknown, you have been warned. [ 14.626716] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 14.644798] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 14.651935] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 14.661415] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 14.708623] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 14.740237] coda 204.vpu: firmware: direct-loading firmware vpu/vpu_fw_imx6q.bin [ 14.756779] coda 204.vpu: Using fallback firmware vpu/vpu_fw_imx6q.bin [ 14.768056] coda 204.vpu: Firmware code revision: 46076 [ 14.773727] coda 204.vpu: Initialized CODA960. [ 14.778621] coda 204.vpu: Firmware version: 3.1.1 [ 14.785300] coda 204.vpu: encoder registered as video0 [ 14.795329] coda 204.vpu: decoder registered as video1 [ 14.801191] coda 204.vpu: encoder registered as video2 [ 14.807040] coda 204.vpu: decoder registered as video3 [ 14.813297] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 14.819955] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 14.830926] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 14.837222] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 14.843443] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 14.850929] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0 [ 14.864206] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops imx_drm_exit [imxdrm]) [ 14.938450] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops imx_drm_exit [imxdrm]) [ 14.991703] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops imx_drm_exit [imxdrm]) [ 15.041668] CAN device driver interface [ 15.074860] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops imx_drm_exit [imxdrm]) [ 15.140711] dwhdmi-imx 12.hdmi: Detected HDMI TX controller v1.30a with HDCP (DWC HDMI 3D TX PHY) [ 15.175608] fsl-ssi-dai 2028000.ssi: No cache defaults, reading back from HW [ 15.225615] imx-drm display-subsystem: bound 12.hdmi (ops dw_hdmi_imx_ops [dw_hdmi_imx]) [ 15.293255] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [ 15.347856] imx-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 15.899289] sgtl5000 0-000a: Error reading chip id -6 [ 16.087363] imx_thermal 20c8000.anatop:tempmon: Extended Commercial CPU temperature grade - max:105C critical:100C passive:95C [ 16.168504] sd 0:0:0:0
Bug#987361: linux-image-5.10.0-6-armmp: bluetooth broken on i.MX6 Cubox-i and related devices
Package: src:linux Version: 5.10.28-1 Severity: important Tags: patch X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Bluetooth drivers for the two chips used on SolidRun i.MX6 SoMs have recently disappeared from the debian kernel package. Please re-add them, patch attached and verified with both BCM4330 and WL1837. Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 5.10.0-6-armmp (debian-kernel@lists.debian.org) (arm-linux-gnueabihf-gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) ** Command line: root=/dev/mmcblk1p1 console=ttymxc0,115200 deferred_probe_timeout=10 log_level=7 net.ifnames=0 ** Tainted: WE (8704) * kernel issued warning * unsigned module was loaded ** Kernel log: [ 10.481988] systemd[1]: Mounting Kernel Debug File System... [ 10.510173] systemd[1]: Mounting Kernel Trace File System... [ 10.539156] systemd[1]: Starting Create list of static device nodes for the current kernel... [ 10.570585] systemd[1]: Starting Load Kernel Module configfs... [ 10.598475] systemd[1]: Starting Load Kernel Module drm... [ 10.631165] systemd[1]: Starting Load Kernel Module fuse... [ 10.654693] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [ 10.664703] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [ 10.675493] fuse: init (API version 7.32) [ 10.698147] systemd[1]: Starting Journal Service... [ 10.734232] systemd[1]: Starting Load Kernel Modules... [ 10.763521] systemd[1]: Starting Remount Root and Kernel File Systems... [ 10.799102] systemd[1]: Starting Coldplug All udev Devices... [ 10.835732] systemd[1]: Mounted POSIX Message Queue File System. [ 10.844498] EXT4-fs (mmcblk1p1): re-mounted. Opts: (null) [ 10.869237] systemd[1]: Mounted Kernel Debug File System. [ 10.891964] systemd[1]: Mounted Kernel Trace File System. [ 10.917529] systemd[1]: Finished Create list of static device nodes for the current kernel. [ 10.949890] systemd[1]: modprobe@configfs.service: Succeeded. [ 10.958122] systemd[1]: Finished Load Kernel Module configfs. [ 10.985586] systemd[1]: modprobe@drm.service: Succeeded. [ 10.993079] systemd[1]: Finished Load Kernel Module drm. [ 11.021581] systemd[1]: modprobe@fuse.service: Succeeded. [ 11.029043] systemd[1]: Finished Load Kernel Module fuse. [ 11.051899] systemd[1]: Started Journal Service. [ 11.258052] systemd-journald[196]: Received client request to flush runtime journal. [ 11.288371] systemd-journald[196]: File /var/log/journal/9bbcae0a3ade4af68637450cb7940ea7/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 12.656525] Registered IR keymap rc-empty [ 12.661105] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0 [ 12.672050] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 12.703052] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input1 [ 12.842870] rc rc0: two consecutive events of type space [ 12.847048] imx-ipuv3 240.ipu: IPUv3H probed [ 12.858932] etnaviv etnaviv: bound 13.gpu (ops gpu_ops [etnaviv]) [ 12.875330] imx-ipuv3 280.ipu: IPUv3H probed [ 12.875434] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv]) [ 12.964800] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv]) [ 12.972142] etnaviv-gpu 13.gpu: model: GC2000, revision: 5108 [ 13.069408] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007 [ 13.077309] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215 [ 13.086018] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0 [ 13.092640] coda 204.vpu: firmware: failed to load vpu_fw_imx6q.bin (-2) [ 13.099867] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 13.109337] coda 204.vpu: Direct firmware load for vpu_fw_imx6q.bin failed with error -2 [ 13.183812] coda 204.vpu: firmware: failed to load vpu/vpu_fw_imx6q.bin (-2) [ 13.191344] coda 204.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed with error -2 [ 13.191801] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0 [ 13.208912] coda 204.vpu: firmware: failed to load v4l-coda960-imx6q.bin (-2) [ 13.218928] coda 204.vpu: Direct firmware load for v4l-coda960-imx6q.bin failed with error -2 [ 13.230904] coda 204.vpu: firmware request failed [ 13.449889] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops imx_drm_exit [imxdrm]) [ 13.479351] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops imx_drm_exit [imxdrm]) [ 13.500464] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops imx_drm_exit [imxdrm]) [ 13.519712] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops imx_drm_exit [imxdrm]) [ 13.532962] dwhdmi-imx 12.hdmi: Detected HDMI TX controller v1.30a with HDCP
Bug#987019: (no subject)
Dear Maintainers, I have found a configuration change that makes the microSD port function again, verified by rebuilding 5.10.0-6: diff --git a/debian/config/armhf/config b/debian/config/armhf/config index bdf0fa118db1..7c39d00d7aae 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -343,6 +343,7 @@ CONFIG_GPIO_DA9052=m CONFIG_GPIO_PALMAS=y CONFIG_GPIO_TWL4030=y CONFIG_GPIO_TWL6040=y +CONFIG_GPIO_MXC=y ## ## file: drivers/gpu/drm/Kconfig Yours sincerely Josua Mayer
Bug#987019: linux-image-5.10.0-6-armmp: microSD not recognized on i.MX6 HummingBoard
Package: src:linux Version: 5.10.28-1 Severity: important X-Debbugs-Cc: josua.maye...@gmail.com Dear Maintainer, Since the 5.10.0-5-armmp kernel package, microSD does no longer function on the i.MX6 Hummingboard Pro. The last known-working version is: 5.9.0-0.bpo.5-armmp Judging from a diff of the .config files between the 2 versions, the likely cause is removal of the GPIO driver for i.MX SoCs via CONFIG_GPIO_MXC. I will b reporting if re-enabling of that setting fixes the problem. Yours sincerely Josua Mayer ** Model information Hardware: Freescale i.MX6 Quad/DualLite (Device Tree) Revision: Device Tree model: SolidRun HummingBoard Dual/Quad ** PCI devices: 00:00.0 PCI bridge [0604]: Synopsys, Inc. DWC_usb3 / PCIe bridge [16c3:abcd] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport ** USB devices: Bus 002 Device 002: ID 04b4:6570 Cypress Semiconductor Corp. Unprogrammed CY7C65632/34 hub HX2VL Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 5.9.0-0.bpo.5-armmp (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-5.10.0-6-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.140 ii kmod28-1 ii linux-base 4.6 Versions of packages linux-image-5.10.0-6-armmp recommends: pn apparmor pn firmware-linux-free Versions of packages linux-image-5.10.0-6-armmp suggests: pn debian-kernel-handbook pn linux-doc-5.10 Versions of packages linux-image-5.10.0-6-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree ii firmware-misc-nonfree 20210315-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano ii firmware-ti-connectivity 20210315-2 pn xen-hypervisor -- no debconf information
Bug#948576: closed by Debian FTP Masters (reply to Ben Hutchings ) (Bug#948576: fixed in linux 5.5.17-1)
Thanks! \o/ Am 17.04.20 um 05:03 schrieb Debian Bug Tracking System: > This is an automatic notification regarding your Bug report > which was filed against the src:linux package: > > #948576: linux: please enable support for the layerscape SoCs and the > Honeycomb workstation board > > It has been closed by Debian FTP Masters > (reply to Ben Hutchings ). > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Debian FTP Masters > (reply to Ben Hutchings ) > by > replying to this email. > >
Bug#951409: (no subject)
Hi Joel, I have already opened a bug report requesting the comphy driver be enabled in Debian. Sadly I did not notice the regression, so I only marked it as low priority...: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948298 But clearly it was a breaking change between buster and buster-backports now. Yours sincerely Josua Mayer
Bug#948576: Update - tested with 5.5.4
Hi everybody, I have rebased my patch on 5.5.4-1~exp1 from the packaging master branch. While at it I have also cleaned it up removing any options that were implicitly selected, leaving only those that really need to be enabled manually. Boot tested, everything that worked before still does, namely the standalone ethernet port, USB, microSD and eMMC. Please consider enabling these config options - The device-tree for the Honeycomb Workstation has been merged with 5.6-rc1 and it would be great to have Debian work as pieces start landing upstream. Yours sincerely Josua Mayer >From 17590120f8352874ba1b7c686c3c3fd46c0c Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Tue, 18 Feb 2020 21:36:40 +0100 Subject: [PATCH] enable support for the Honeycomb arm64 workstation This enables support for the Layerscape architecture in general, as well as - drivers for the Soc listed in (fsl-lx2160a.dtsi) - drivers for peripherals listed in (fsl-lx2160a-cex7.dtsi) . Signed-off-by: Josua Mayer --- debian/config/arm64/config | 47 ++ 1 file changed, 47 insertions(+) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index a2638cf1307a..0796f1fd3f59 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -56,6 +56,7 @@ CONFIG_KVM=y CONFIG_ARCH_SUNXI=y CONFIG_ARCH_BCM2835=y CONFIG_ARCH_HISI=y +CONFIG_ARCH_LAYERSCAPE=y CONFIG_ARCH_MESON=y CONFIG_ARCH_MVEBU=y CONFIG_ARCH_QCOM=y @@ -100,6 +101,7 @@ CONFIG_ANDROID=y CONFIG_SATA_AHCI_PLATFORM=m CONFIG_AHCI_CEVA=m CONFIG_AHCI_MVEBU=m +CONFIG_AHCI_QORIQ=m CONFIG_AHCI_TEGRA=m CONFIG_AHCI_XGENE=m CONFIG_SATA_AHCI_SEATTLE=m @@ -117,6 +119,11 @@ CONFIG_HISILICON_LPC=y CONFIG_QCOM_EBI2=y CONFIG_TEGRA_ACONNECT=y +## +## file: drivers/bus/fsl-mc/Kconfig +## +CONFIG_FSL_MC_BUS=y + ## ## file: drivers/char/hw_random/Kconfig ## @@ -182,6 +189,7 @@ CONFIG_SUN8I_DE2_CCU=y CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y ## end choice CONFIG_CPUFREQ_DT=m +CONFIG_QORIQ_CPUFREQ=m ## ## file: drivers/cpufreq/Kconfig.arm @@ -203,6 +211,11 @@ CONFIG_CRYPTO_DEV_QCE=m CONFIG_CRYPTO_DEV_QCOM_RNG=m CONFIG_CRYPTO_DEV_SAFEXCEL=m +## +## file: drivers/crypto/caam/Kconfig +## +CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=m + ## ## file: drivers/crypto/cavium/cpt/Kconfig ## @@ -249,6 +262,7 @@ CONFIG_QCOM_HIDMA=m ## file: drivers/edac/Kconfig ## CONFIG_EDAC=y +CONFIG_EDAC_LAYERSCAPE=m CONFIG_EDAC_THUNDERX=m CONFIG_EDAC_XGENE=m @@ -278,6 +292,7 @@ CONFIG_GPIO_ZYNQ=m CONFIG_GPIO_PCA953X=y CONFIG_GPIO_PCA953X_IRQ=y CONFIG_GPIO_MAX77620=y +CONFIG_GPIO_MPC8XXX=y ## ## file: drivers/gpu/drm/Kconfig @@ -388,6 +403,7 @@ CONFIG_I2C_HID=m ## ## file: drivers/hwmon/Kconfig ## +CONFIG_SENSORS_LM90=m CONFIG_SENSORS_XGENE=m ## @@ -406,6 +422,7 @@ CONFIG_I2C=y CONFIG_I2C_BCM2835=m CONFIG_I2C_DESIGNWARE_PLATFORM=m CONFIG_I2C_GPIO=m +CONFIG_I2C_IMX=m CONFIG_I2C_MESON=m CONFIG_I2C_MV64XXX=m CONFIG_I2C_PXA=m @@ -418,6 +435,11 @@ CONFIG_I2C_XLP9XX=m CONFIG_I2C_CROS_EC_TUNNEL=m CONFIG_I2C_XGENE_SLIMPRO=m +## +## file: drivers/i2c/muxes/Kconfig +## +CONFIG_I2C_MUX_PCA954x=m + ## ## file: drivers/iio/accel/Kconfig ## @@ -560,6 +582,7 @@ CONFIG_MMC_QCOM_DML=y CONFIG_MMC_SDHCI_ACPI=m CONFIG_MMC_SDHCI_PLTFM=m CONFIG_MMC_SDHCI_OF_ARASAN=m +CONFIG_MMC_SDHCI_OF_ESDHC=m CONFIG_MMC_SDHCI_TEGRA=m CONFIG_MMC_SDHCI_F_SDH30=m CONFIG_MMC_SDHCI_IPROC=m @@ -666,6 +689,18 @@ CONFIG_NET_VENDOR_DLINK=y CONFIG_SUNDANCE=m # CONFIG_SUNDANCE_MMIO is not set +## +## file: drivers/net/ethernet/freescale/Kconfig +## +CONFIG_FSL_XGMAC_MDIO=m +CONFIG_NET_VENDOR_FREESCALE=y + +## +## file: drivers/net/ethernet/freescale/dpaa2/Kconfig +## +CONFIG_FSL_DPAA2_ETH=m +CONFIG_FSL_DPAA2_PTP_CLOCK=m + ## ## file: drivers/net/ethernet/hisilicon/Kconfig ## @@ -967,6 +1002,11 @@ CONFIG_AXP288_FUEL_GAUGE=m CONFIG_CHARGER_QCOM_SMBB=m CONFIG_CHARGER_CROS_USBPD=m +## +## file: drivers/ptp/Kconfig +## +CONFIG_PTP_1588_CLOCK_QORIQ=m + ## ## file: drivers/pwm/Kconfig ## @@ -1030,6 +1070,7 @@ CONFIG_RTC_DRV_ARMADA38X=m CONFIG_RTC_DRV_PM8XXX=m CONFIG_RTC_DRV_TEGRA=y CONFIG_RTC_DRV_XGENE=y +CONFIG_RTC_DRV_PCF2127=m ## ## file: drivers/scsi/Kconfig @@ -1042,6 +1083,11 @@ CONFIG_SCSI_DMX3191D=m CONFIG_SCSI_HISI_SAS=m CONFIG_SCSI_HISI_SAS_PCI=m +## +## file: drivers/soc/fsl/Kconfig +## +CONFIG_FSL_MC_DPIO=m + ## ## file: drivers/soc/bcm/Kconfig ## @@ -1075,6 +1121,7 @@ CONFIG_SPI_ARMADA_3700=m CONFIG_SPI_BCM2835=m CONFIG_SPI_BCM2835AUX=m CONFIG_SPI_MESON_SPIFC=m +CONFIG_SPI_NXP_FLEXSPI=m CONFIG_SPI_ROCKCHIP=m CONFIG_SPI_QUP=m CONFIG_SPI_TEGRA114=m -- 2.25.0
Bug#948576: linux: please enable support for the layerscape SoCs and the Honeycomb workstation board
Source: linux
Severity: wishlist
Tags: patch
Dear Maintainer,
Please enable a set of drivers requried for the layerscape based arm64
honeycomb board.
It is a mini-itx board for use as a workstation machine. Its support in
mainline is not complete yet,
but many bits are already functional.
I am attaching a patch for enabling the options I have found through reading
the dts from RMKs cex7 branch.
Changes were tested on 5.5-rc5 built from the debian kernel packaging tree.
Some drivers are currently enabled implicitly, i.e. not listed in either
debian/config/{,arm64/}config:
CONFIG_PTP_1588_CLOCK=m
CONFIG_I2C_MUX=m
CONFIG_SENSORS_LM90=m
CONFIG_RTC_DRV_PCF2127=m
CONFIG_ARM_GIC_V3_ITS_FSL_MC=y
^^ Not sure how you decide when to make options explicit, and when not ... so
these are *not* included in my attached patch!
The PCI Express driver is still pending inclusion in Linux:
https://patchwork.kernel.org/patch/11253015/
Once that lands, CONFIG_PCIE_LAYERSCAPE_GEN4=m should also be enabled.
Yours sincerely
Josua Mayer
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.5.0-rc5-arm64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
>From 216cdc9faf2cdcbdd593af90a8b7bacc4195c2ac Mon Sep 17 00:00:00 2001
From: Josua Mayer
Date: Thu, 9 Jan 2020 23:36:15 +
Subject: [PATCH] enable support for the Honeycomb arm64 workstation
This enables support for the Layerscape architecture in general,
as well as
- drivers for the Soc listed in (fsl-lx2160a.dtsi)
- drivers for peripherals listed in (fsl-lx2160a-cex7.dtsi)
.
Some drivers are currently enabled implicitly, i.e. not listed in either
debian/config/{,arm64/}config:
CONFIG_PTP_1588_CLOCK=m
CONFIG_I2C_MUX=m
CONFIG_SENSORS_LM90=m
CONFIG_RTC_DRV_PCF2127=m
CONFIG_ARM_GIC_V3_ITS_FSL_MC=y
The PCI Express driver is still pending inclusion in Linux:
https://patchwork.kernel.org/patch/11253015/
Once that lands, CONFIG_PCIE_LAYERSCAPE_GEN4=m should also be enabled.
Signed-off-by: Josua Mayer
---
debian/config/arm64/config | 51 ++
1 file changed, 51 insertions(+)
diff --git a/debian/config/arm64/config b/debian/config/arm64/config
index 9841e44ce42f..285d881310fc 100644
--- a/debian/config/arm64/config
+++ b/debian/config/arm64/config
@@ -67,6 +67,7 @@ CONFIG_ARCH_THUNDER2=y
CONFIG_ARCH_VEXPRESS=y
CONFIG_ARCH_XGENE=y
CONFIG_ARCH_ZYNQMP=y
+CONFIG_ARCH_LAYERSCAPE=y
##
## file: drivers/acpi/Kconfig
@@ -102,6 +103,7 @@ CONFIG_AHCI_MVEBU=m
CONFIG_AHCI_TEGRA=m
CONFIG_AHCI_XGENE=m
CONFIG_SATA_AHCI_SEATTLE=m
+CONFIG_AHCI_QORIQ=m
##
## file: drivers/bluetooth/Kconfig
@@ -116,6 +118,11 @@ CONFIG_HISILICON_LPC=y
CONFIG_QCOM_EBI2=y
CONFIG_TEGRA_ACONNECT=y
+##
+## file: drivers/bus/fsl-mc/Kconfig
+##
+CONFIG_FSL_MC_BUS=y
+
##
## file: drivers/char/hw_random/Kconfig
##
@@ -147,6 +154,7 @@ CONFIG_TCG_TIS_I2C_INFINEON=m
CONFIG_COMMON_CLK_RK808=y
CONFIG_COMMON_CLK_HI655X=y
CONFIG_COMMON_CLK_XGENE=y
+CONFIG_CLK_QORIQ=y
##
## file: drivers/clk/bcm/Kconfig
@@ -181,6 +189,7 @@ CONFIG_SUN8I_DE2_CCU=y
CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y
## end choice
CONFIG_CPUFREQ_DT=m
+CONFIG_QORIQ_CPUFREQ=m
##
## file: drivers/cpufreq/Kconfig.arm
@@ -202,6 +211,11 @@ CONFIG_CRYPTO_DEV_QCE=m
CONFIG_CRYPTO_DEV_QCOM_RNG=m
CONFIG_CRYPTO_DEV_SAFEXCEL=m
+##
+## file: drivers/crypto/caam/Kconfig
+##
+CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=m
+
##
## file: drivers/crypto/cavium/cpt/Kconfig
##
@@ -250,6 +264,7 @@ CONFIG_QCOM_HIDMA=m
CONFIG_EDAC=y
CONFIG_EDAC_THUNDERX=m
CONFIG_EDAC_XGENE=m
+CONFIG_EDAC_LAYERSCAPE=m
##
## file: drivers/extcon/Kconfig
@@ -277,6 +292,7 @@ CONFIG_GPIO_ZYNQ=m
CONFIG_GPIO_PCA953X=y
CONFIG_GPIO_PCA953X_IRQ=y
CONFIG_GPIO_MAX77620=y
+CONFIG_GPIO_MPC8XXX=y
##
## file: drivers/gpu/drm/Kconfig
@@ -388,6 +404,7 @@ CONFIG_I2C_HID=m
## file: drivers/hwmon/Kconfig
##
CONFIG_SENSORS_XGENE=m
+CONFIG_SENSORS_LM90=m
##
## file: drivers/hwspinlock/Kconfig
@@ -398,6 +415,7 @@ CONFIG_HWSPINLOCK_QCOM=m
## file: drivers/i2c/Kconfig
##
CONFIG_I2C=y
+CONFIG_I2C_MUX=m
##
## file: drivers/i2c/busses/Kconfig
@@ -416,6 +434,12 @@ CONFIG_I2C_THUNDERX=m
CONFIG_I2C_XLP9XX=m
CONFIG_I2C_CROS_EC_TUNNEL=m
CONFIG_I2C_XGENE_SLIMPRO=m
+CONFIG_I2C_IMX=m
+
+##
+## file: drivers/i2c/muxes/Kconfig
+##
+CONFIG_I2C_MUX_PCA954x=m
##
## file: drivers/iio/accel/Kconfig
@@ -572,6 +596,7 @@ CONFIG_MMC_DW_ROCKCHIP=m
CONFIG_MMC_SUNXI=m
CONFIG_MMC_BCM2835=m
CONFIG_MMC_SDHCI_XENON=m
+CONFIG_MMC_SDHCI_OF_ESDHC=m
##
## file: drivers/mtd/spi-nor/Kconfig
@@ -660,6 +685,18 @@ CONFIG_NET_VENDOR_DLINK=y
CONFIG_SUNDANCE=m
# CONFIG_SUNDANCE_MMIO is not set
+##
+## file: drivers/net/ethernet/freesc
Bug#948298: linux-image-5.3.0-0.bpo.2-armmp: please enable armada 38x comphy driver for armmp
Package: src:linux Version: 5.3.9-2~bpo10+1sr1 Severity: normal Tags: patch Dear Maintainer, As of Linux v5.1 a special comphy driver was introduced for Armada 38x SoCs. It is actively referenced by the dts for the Clearfog Base and Clearfog Pro - and used by the new Clearfog GTR (which has its device-tree posted to lkml in v3). Please enable this driver as a module for the armmp kernel flavour. I am attaching the patch to enable this module - and the dmesg of when I verified that the resulting kernel works as expected. Also, it would be nice if this change could make it into buster-backports ;) Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 5.3.0-0.bpo.2-armmp (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 5.3.9-2~bpo10+1sr1 (2020-01-06) ** Command line: console=ttyS0,115200 log_level=7 net.ifnames=0 ** Not tainted ** Kernel log: ** Model information [6.952015] usb 4-1: Manufacturer: TOSHIBA [6.956130] usb 4-1: SerialNumber: 0E70657012733A39 [6.967191] usb-storage 4-1:1.0: USB Mass Storage device detected [6.973990] scsi host4: usb-storage 4-1:1.0 [6.978439] usbcore: registered new interface driver usb-storage [6.985921] usbcore: registered new interface driver uas [6.986841] libphy: mdio: probed [7.118832] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.181531] libphy: mdio: probed [7.299011] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.352811] libphy: mdio: probed [7.478658] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.541070] libphy: mdio: probed [7.655533] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.716804] libphy: mdio: probed [7.832195] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [7.895216] libphy: mdio: probed [8.004389] scsi 4:0:0:0: Direct-Access TOSHIBA TransMemory 5.00 PQ: 0 ANSI: 0 CCS [8.017642] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.026886] sd 4:0:0:0: [sda] 2013184 512-byte logical blocks: (1.03 GB/983 MiB) [8.034467] sd 4:0:0:0: [sda] Write Protect is off [8.039301] sd 4:0:0:0: [sda] Mode Sense: 23 00 00 00 [8.039469] sd 4:0:0:0: [sda] No Caching mode page found [8.044814] sd 4:0:0:0: [sda] Assuming drive cache: write through [8.054320] sda: sda1 [8.058169] sd 4:0:0:0: [sda] Attached SCSI removable disk [8.080803] libphy: mdio: probed [8.212177] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.275624] libphy: mdio: probed [8.397802] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.460802] libphy: mdio: probed [8.580273] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.643294] libphy: mdio: probed [8.763092] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [8.830193] libphy: mdio: probed [8.900734] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [8.967203] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [9.028725] libphy: mdio: probed [9.110343] mv88e6085 f1072004.mdio-mii:04: switch 0x3900 detected: Marvell 88E6390, revision 1 [9.141298] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. [9.172705] libphy: mdio: probed [9.954303] systemd[1]: Inserted module 'autofs4' [ 10.019965] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 10.041719] systemd[1]: Detected architecture arm. [ 10.068617] systemd[1]: Set hostname to . [ 10.081427] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument [ 10.595635] mv88e6085 f1072004.mdio-mii:04 lan8 (uninitialized): PHY [!soc!internal-regs!mdio@72004!switch0@4!mdio:01] driver [Marvell 88E6390] [ 10.608585] mv88e6085 f1072004.mdio-mii:04 lan8 (uninitialized): phy: setting supported 00,,22ef advertising 00,,22ef [ 10.612489] mv88e6085 f1072004.mdio-mii:04 lan7 (uninitialized): PHY [!soc!internal-regs!mdio@72004!switch0@4!mdio:02] driver [Marvell 88E6390] [ 10.622680] random: systemd: uninitialized urandom read (16 bytes read) [ 10.625451] mv88e6085 f1072004.mdio-mii:04 lan7 (uninitialized): phy: setting supported 00,,22ef advertising 00,,22ef [ 10.635967] mv88e6085 f1072004.mdio-mii:04 lan6 (uninitialized): PHY [!soc!internal-regs!mdio@72004!switch0@4!mdio:03] driver [Marvell 88E6390] [ 10.636784] random: systemd: uninitialized
Bug#931707: linux: HW_RANDOM_OMAP disabled for arm64 --> please enable
Source: linux Severity: normal Dear Maintainer, While testing Debian 10 on a Marvell 8040 SoC I found that the rng and SSH were coming up extremely slow, taking over a minute to start. This is caused by somebody disabling the rng driver for arm64 kernels a long time ago: linux (4.14.13-1) unstable; urgency=medium ... [ Riku Voipio ] * [arm64] disable CONFIG_HW_RANDOM_OMAP until the IRQ storm bug is fixed What is this IRQ storm bug? Has it been fixed? Can we re-enable this driver? Yours sincerely Josua Mayer -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.1.0-trunk-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#918589: linux-image-4.19.0-1-amd64: please enable support for audio in Lenovo Yoga 11e Chromebook (3th generation)
Package: src:linux Version: 4.19.12-1 Severity: wishlist Dear Maintainer, Audio does not currently work on above mentioned laptop. The device features a Celeron N3150 and appears to use its intgerated audio capabilities. A little googling suggests that the audio codec is an es8316. I will try to enable support for it in the kernel config and report back if I can get it to work. Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64 root=/dev/mmcblk0p3 ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 97.980302] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.981828] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.983457] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.984813] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.986170] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.987501] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.989000] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.990282] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.991571] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.992839] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.994135] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.995482] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.996798] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.998065] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 97.999604] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.000826] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.002081] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.003398] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.004643] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.006184] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.007846] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.009493] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.010953] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.012306] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.013663] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.015286] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.016743] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.017971] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.019268] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.020595] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.021812] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.023104] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.024365] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.025951] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.027168] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.028436] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.030084] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.031830] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.033416] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.034657] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.036004] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.037715] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.039271] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.040893] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.042504] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.043768] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.044989] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.046278] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.047994] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.049937] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.051464] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.053224] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.054554] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.056055] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.057614] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.059051] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.060446] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.061740] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.063135] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.064442] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.065701] elan_i2c i2c-ELAN:00: invalid report id data (ff) [ 98.067016] elan_i2c i2c-ELAN:00: invalid report
Bug#918156: some omitted details
I forgot to mention some important bits: 1. this is for armmp flavour only 2. the options I chose enable some more by default that I did not list 3. maybe all HCIUART drivers should be enabled, just like on x86?
Bug#918156: linux-image-4.18.0-0.bpo.3-armmp: please enable support for Ti WL1838 Bluetooth
Package: src:linux Version: 4.18.20-2~bpo9+1 Severity: wishlist Tags: patch Dear Maintainer, Please enable support for above mentioned bluetooth chip. It is used in SolidRun Ltd. i.MX6 MicroSOMs since revision 1.5, thereby applying to all Hummingboards and Cuboxes with a recent SoM. I enabled the necessary options and tested with a local build of 4.20 from the debian kernel source tree, and am attaching the diff. Yours sincerely Josua Mayer -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Hardware: Freescale i.MX6 Quad/DualLite (Device Tree) Revision: Device Tree model: SolidRun HummingBoard2 Dual/Quad (1.5som+emmc) ** PCI devices: 00:00.0 PCI bridge [0604]: Synopsys, Inc. Device [16c3:abcd] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: dwc3_haps ** USB devices: Bus 002 Device 002: ID 04b4:6570 Cypress Semiconductor Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.20.0-trunk-armmp (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.18.0-0.bpo.3-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.130 ii kmod23-2 ii linux-base 4.5 Versions of packages linux-image-4.18.0-0.bpo.3-armmp recommends: ii apparmor 2.11.0-3+deb9u2 ii firmware-linux-free 3.4 ii irqbalance 1.1.0-2.3 Versions of packages linux-image-4.18.0-0.bpo.3-armmp suggests: pn debian-kernel-handbook pn linux-doc-4.18 Versions of packages linux-image-4.18.0-0.bpo.3-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree ii firmware-misc-nonfree 20180825+dfsg-1~bpo9+1 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano ii firmware-ti-connectivity 20161130-4 pn xen-hypervisor -- no debconf information >From 38737c0c24a8d7c23b46cd0a28e8dcf932ce06e1 Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Thu, 3 Jan 2019 20:59:05 +0100 Subject: [PATCH] armmp: enable BT_HCIUART_LL This allows using the wl1837-st bluetooth chip on the SolidRun i.MX6 SoMs Revision 1.5. Signed-off-by: Josua Mayer --- debian/config/armhf/config | 4 1 file changed, 4 insertions(+) diff --git a/debian/config/armhf/config b/debian/config/armhf/config index 48d26fea8269..e390fe168b42 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -179,6 +179,10 @@ CONFIG_DMA_CMA=y ## ## file: drivers/bluetooth/Kconfig ## +CONFIG_BT_HCIUART=m +CONFIG_BT_HCIUART_3WIRE=y +CONFIG_BT_HCIUART_LL=y +CONFIG_BT_HCIUART_SERDEV=y CONFIG_BT_WILINK=m ## -- 2.20.1
Bug#908967: initramfs-tools: mount fails with rootfstype=auto
Package: initramfs-tools Version: 0.130 Severity: normal Dear Maintainer, I encountered a strange problem mounting the rootfs with a freshly debootstrapped system. Note: possible duplicate of #845302 but due to the details I found it probably warrants its own topic. Steps: - used debootstrap with --variant=minbase to create an armhf rootfs - added custom packages such as vendor kernel, systemd, initramfs-tools - created extlinux.conf to boot - bootargs: root=UUID=... rootfstype=auto rootwait Observations: - root=/dev/mmcblk0p1 rootfstype=auto: fails - root=/dev/mmcblk0p1 rootfstype=ext4: works - root=UUID=... rootfstype=ext4: works How did I find this? I added "set -x" to - /usr/share/initramfs-tools/init - /usr/share/initramfs-tools/scripts/init-bottom/udev The serial console then finally revealed what is going wrong. When it fails (rootfstype=auto): + [ auto != unknown ] + mount -r -t auto /dev/mmcblk0p1 /root mount: No such device When it works (rootfstype=ext4): + [ ext4 != unknown ] + mount -r -t ext4 /dev/mmcblk0p1 /root [9.979060] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null) So I see two solutions: - If rootfstype=auto, and the actual type is known through a previous call to blkid, e.g. while running fsck, use the known type - fix the mount command to deal with type auto I am submitting the full boot logs by email as follow-up. Yours sincerely Josua Mayer -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 8.5M Sep 16 20:04 /boot/initrd.img-4.9.124-imx6-sr -- /proc/cmdline root=UUID=febfadf2-ffa2-48ad-9802-d7b67b5e7818 rootfstype=ext4 rootwait -- /proc/filesystems ext3 ext2 ext4 vfat fuseblk f2fs -- lsmod Module Size Used by bnep 20480 2 mxc_v4l2_capture 40960 0 ipu_bg_overlay_sdc 16384 1 mxc_v4l2_capture ipu_still 16384 1 mxc_v4l2_capture ipu_prp_enc16384 1 mxc_v4l2_capture ipu_csi_enc16384 1 mxc_v4l2_capture ipu_fg_overlay_sdc 20480 1 mxc_v4l2_capture hci_uart 49152 0 btbcm 16384 1 hci_uart nvmem_core 24576 1 hci_uart ov5647_camera_mipi 36864 0 v4l2_int_device16384 3 ov5647_camera_mipi,ipu_csi_enc,mxc_v4l2_capture xt_connmark16384 2 iptable_nat16384 0 nf_conntrack_ipv4 16384 3 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 1 nf_nat_ipv4 nf_conntrack 106496 4 nf_conntrack_ipv4,xt_connmark,nf_nat_ipv4,nf_nat iptable_mangle 16384 1 iptable_filter 16384 0 ir_lirc_codec 16384 0 galcore 372736 0 ir_rc6_decoder 16384 0 lirc_dev 20480 1 ir_lirc_codec rc_rc6_mce 16384 0 gpio_ir_recv 16384 0 bluetooth 360448 12 hci_uart,bnep,btbcm rfkill 24576 4 bluetooth ip_tables 24576 3 iptable_mangle,iptable_filter,iptable_nat x_tables 28672 4 iptable_mangle,ip_tables,iptable_filter,xt_connmark imx_sdma 28672 8 virt_dma 16384 1 imx_sdma -- /etc/initramfs-tools/modules -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=auto KEYMAP=n COMPRESS=gzip DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : unused devices: -- mkinitramfs hooks /etc/initramfs-tools/hooks/: imx-sdma /usr/share/initramfs-tools/hooks: dmsetup fsck fuse keymap klibc-utils kmod ntfs_3g resume thermal udev -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.9.124-imx6-sr (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii initramfs-tools-core 0.130 ii linux-base4.5 initramfs-tools recommends no packages. Versions of packages initramfs-tools suggests: pn bash-completion -- no debconf information
Bug#906054: Tested
ngth (SMF) : 0m Length (50um) : 150m Length (62.5um) : 70m Length (Copper) : 0m Length (OM3) : 0m Laser wavelength : 850nm Vendor name : AVAGO Vendor OUI: 00:17:6a Vendor PN : AFBR-57R5AEZ Vendor rev: Option values : 0x00 0x1a Option: RX_LOS implemented Option: TX_FAULT implemented Option: TX_DISABLE implemented BR margin, max: 0% BR margin, min: 0% Vendor SN : A90751H94G Date code : 071221 Optical diagnostics support : Yes Laser bias current: 0.000 mA Laser output power: 0. mW / -inf dBm Receiver signal average optical power : 0. mW / -inf dBm Module temperature: 41.08 degrees C / 105.95 degrees F Module voltage: 3.3189 V Alarm/warning flags implemented : Yes Laser bias current high alarm : Off Laser bias current low alarm : On Laser bias current high warning : Off Laser bias current low warning: On Laser output power high alarm : Off Laser output power low alarm : On Laser output power high warning : Off Laser output power low warning: On Module temperature high alarm : Off Module temperature low alarm : Off Module temperature high warning : Off Module temperature low warning: Off Module voltage high alarm : Off Module voltage low alarm : Off Module voltage high warning : Off Module voltage low warning: Off Laser rx power high alarm : Off Laser rx power low alarm : On Laser rx power high warning : Off Laser rx power low warning: On Laser bias current high alarm threshold : 10.000 mA Laser bias current low alarm threshold: 2.000 mA Laser bias current high warning threshold : 10.000 mA Laser bias current low warning threshold : 2.000 mA Laser output power high alarm threshold : 0.7000 mW / -1.55 dBm Laser output power low alarm threshold: 0.0500 mW / -13.01 dBm Laser output power high warning threshold : 0.6000 mW / -2.22 dBm Laser output power low warning threshold : 0.1000 mW / -10.00 dBm Module temperature high alarm threshold : 100.00 degrees C / 212.00 degrees F Module temperature low alarm threshold: -40.00 degrees C / -40.00 degrees F Module temperature high warning threshold : 85.00 degrees C / 185.00 degrees F Module temperature low warning threshold : -10.00 degrees C / 14.00 degrees F Module voltage high alarm threshold : 3.9000 V Module voltage low alarm threshold: 2.7000 V Module voltage high warning threshold : 3.6300 V Module voltage low warning threshold : 2.9700 V Laser rx power high alarm threshold : 6.5500 mW / 8.16 dBm Laser rx power low alarm threshold: 0. mW / -inf dBm Laser rx power high warning threshold : 1.1000 mW / 0.41 dBm Laser rx power low warning threshold : 0.0490 mW / -13.10 dBm >From 2ac29b08004b43ed280c3935dd775d7488dc0bbe Mon Sep 17 00:00:00 2001 From: Josua Mayer Date: Mon, 13 Aug 2018 18:42:45 +0200 Subject: [PATCH] armmp: enable SFP support Signed-off-by: Josua Mayer --- debian/config/armhf/config | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debian/config/armhf/config b/debian/config/armhf/config index 79ee427b5..a7121d185 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -839,6 +839,8 @@ CONFIG_SKFP=m ## file: drivers/net/phy/Kconfig ## CONFIG_MDIO_SUN4I=y +CONFIG_PHYLINK=m +CONFIG_SFP=m ## ## file: drivers/net/wireless/broadcom/brcm80211/Kconfig -- 2.18.0
Bug#906054: linux-image-4.18.0-rc5-armmp: Please enable support for SFP modules
Package: src:linux Version: 4.18~rc5-1~exp1 Severity: normal Dear Maintainer, With the release of linux 4.14 support for SFP pages has been introduced. Please enable support for this in the armmp and arm64 flavours. To name two devices that have an SFP port and can run debian testing: - solidrun clearfog (armhf) - marvell macchiatobin (arm64) The config option is declared in drivers/net/phy/Kconfig. Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 4.18.0-rc5-armmp (debian-kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.18~rc5-1~exp1 (2018-07-19) ** Command line: console=ttyS0,115200 log_level=7 ** Not tainted ** Kernel log: [4.370612] xhci-hcd f10f8000.usb3: irq 49, io mem 0xf10f8000 [4.376577] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.18 [4.384886] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.392136] usb usb4: Product: xHCI Host Controller [4.397033] usb usb4: Manufacturer: Linux 4.18.0-rc5-armmp xhci-hcd [4.403319] usb usb4: SerialNumber: f10f8000.usb3 [4.408405] hub 4-0:1.0: USB hub found [4.412195] hub 4-0:1.0: 1 port detected [4.416332] xhci-hcd f10f8000.usb3: xHCI Host Controller [4.421697] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5 [4.429790] xhci-hcd f10f8000.usb3: Host supports USB 3.0 SuperSpeed [4.436290] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM. [4.75] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.18 [4.452770] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.460015] usb usb5: Product: xHCI Host Controller [4.460964] mvebu-pcie soc:pcie: PCI host bridge to bus :00 [4.464910] usb usb5: Manufacturer: Linux 4.18.0-rc5-armmp xhci-hcd [4.464913] usb usb5: SerialNumber: f10f8000.usb3 [4.481873] ata2: SATA link down (SStatus 0 SControl 300) [4.487368] pci_bus :00: root bus resource [io 0x1000-0xf] [4.488374] hub 5-0:1.0: USB hub found [4.494057] pci_bus :00: root bus resource [mem 0xe000-0xe7ff] [4.497548] hub 5-0:1.0: 1 port detected [4.504344] pci_bus :00: root bus resource [bus 00-ff] [4.504452] pci :00:02.0: [11ab:6828] type 01 class 0x060400 [4.531154] pci :00:03.0: [11ab:6828] type 01 class 0x060400 [4.533396] PCI: bus0: Fast back to back transfers disabled [4.539034] pci :00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [4.540534] libphy: mv88e6xxx SMI: probed [4.547067] pci :00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring [4.547176] pci :01:00.0: [168c:003c] type 00 class 0x028000 [4.559162] pci :01:00.0: reg 0x10: [mem 0x-0x001f 64bit] [4.559188] pci :01:00.0: reg 0x30: [mem 0x-0x pref] [4.559291] pci :01:00.0: supports D1 D2 [4.559419] pci :00:02.0: ASPM: current common clock configuration is broken, reconfiguring [4.588832] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [4.591384] ata3: SATA link down (SStatus 0 SControl 300) [4.595836] PCI: bus1: Fast back to back transfers enabled [4.605962] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01 [4.606019] ata1.00: ATA-10: 32GB SATA Flash Drive, SFPS925A, max UDMA/133 [4.612921] ata1.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 32) [4.620224] PCI: bus2: Fast back to back transfers enabled [4.625742] pci_bus :02: busn_res: [bus 02-ff] end is updated to 02 [4.625771] pci :00:02.0: BAR 8: assigned [mem 0xe000-0xe02f] [4.630724] ata4: SATA link down (SStatus 0 SControl 300) [4.632602] pci :01:00.0: BAR 0: assigned [mem 0xe000-0xe01f 64bit] [4.645343] pci :01:00.0: BAR 0: error updating (0xe004 != 0x) [4.645353] ata1.00: configured for UDMA/133 [4.652590] pci :01:00.0: BAR 0: error updating (high 0x00 != 0x) [4.652596] pci :01:00.0: BAR 6: assigned [mem 0xe020-0xe020 pref] [4.671623] pci :00:02.0: PCI bridge to [bus 01] [4.673105] scsi 0:0:0:0: Direct-Access ATA 32GB SATA Flash 925A PQ: 0 ANSI: 5 [4.676614] pci :00:02.0: bridge window [mem 0xe000-0xe02f] [4.691545] pci :00:03.0: PCI bridge to [bus 02] [4.692950] sd 0:0:0:0: [sda] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB) [4.696594] pcieport :00:02.0: enabling device (0140 -> 0142) [4.705364] sd 0:0:0:0: [sda] Write Protect is off [4.715059] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.715739] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.726012] sda: sda1 sda2 sda3 < sda5 > [4.731729] sd 0:0:0:0: [sda] Attached SCSI removable disk [4.783902] random: fast init done [
Bug#906052: checked history
I have found no earlier version where this worked with the debian kernel. All of the following exhibit the problem with similar errors: - linux-image-4.9.0-7-armmp_4.9.110-3+deb9u1_armhf.deb - linux-image-4.16.0-2-armmp_4.16.16-2_armhf.deb - linux-image-4.18.0-rc5-armmp_4.18~rc5-1~exp1_armhf.deb So maybe this should be addresses directly to linux.
Bug#906052: linux-image-4.17.0-1-armmp: Compex WLE900VX (ath10k) doesn't probe
Package: src:linux Version: 4.17.8-1 Severity: normal Dear Maintainer, The Compex pci express wifi module fails to probe apparently because it isn't waking up. I can't see anything wrong here, and the module used to work with older (vendor) kernels. Any clues what is going on? Yours sincerely Josua Mayer -- Package-specific info: ** Version: Linux version 4.17.0-1-armmp (debian-kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20) ** Command line: console=ttyS0,115200 log_level=7 ** Not tainted ** Kernel log: [4.416771] xhci-hcd f10f8000.usb3: irq 49, io mem 0xf10f8000 [4.422722] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.17 [4.431024] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.438269] usb usb4: Product: xHCI Host Controller [4.443161] usb usb4: Manufacturer: Linux 4.17.0-1-armmp xhci-hcd [4.449273] usb usb4: SerialNumber: f10f8000.usb3 [4.454319] hub 4-0:1.0: USB hub found [4.458105] hub 4-0:1.0: 1 port detected [4.462249] xhci-hcd f10f8000.usb3: xHCI Host Controller [4.467591] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 5 [4.475109] xhci-hcd f10f8000.usb3: Host supports USB 3.0 SuperSpeed [4.481601] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM. [4.489774] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.17 [4.498067] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.505312] usb usb5: Product: xHCI Host Controller [4.507447] libphy: mv88e6xxx SMI: probed [4.510205] usb usb5: Manufacturer: Linux 4.17.0-1-armmp xhci-hcd [4.510210] usb usb5: SerialNumber: f10f8000.usb3 [4.525199] mvebu-pcie soc:pcie: PCI host bridge to bus :00 [4.531163] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [4.537424] pci_bus :00: root bus resource [io 0x1000-0xf] [4.538185] hub 5-0:1.0: USB hub found [4.543750] pci_bus :00: root bus resource [mem 0xe000-0xe7ff] [4.547530] hub 5-0:1.0: 1 port detected [4.554399] ata1.00: ATA-10: 32GB SATA Flash Drive, SFPS925A, max UDMA/133 [4.565229] ata1.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 31/32) [4.573566] pci_bus :00: root bus resource [bus 00-ff] [4.579734] pci :00:02.0: [11ab:6828] type 01 class 0x060400 [4.579934] pci :00:03.0: [11ab:6828] type 01 class 0x060400 [4.581309] PCI: bus0: Fast back to back transfers disabled [4.586922] pci :00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring [4.594958] pci :00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring [4.603149] ata1.00: configured for UDMA/133 [4.607484] pci :01:00.0: [168c:003c] type 00 class 0x028000 [4.607516] pci :01:00.0: reg 0x10: [mem 0x-0x001f 64bit] [4.607542] pci :01:00.0: reg 0x30: [mem 0x-0x pref] [4.607632] pci :01:00.0: supports D1 D2 [4.607759] scsi 0:0:0:0: Direct-Access ATA 32GB SATA Flash 925A PQ: 0 ANSI: 5 [4.607790] pci :00:02.0: ASPM: current common clock configuration is broken, reconfiguring [4.624813] sd 0:0:0:0: [sda] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB) [4.632799] sd 0:0:0:0: [sda] Write Protect is off [4.637615] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.637642] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.647734] sda: sda1 sda2 sda3 < sda5 > [4.652559] sd 0:0:0:0: [sda] Attached SCSI removable disk [4.658927] PCI: bus1: Fast back to back transfers enabled [4.664475] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01 [4.665827] PCI: bus2: Fast back to back transfers enabled [4.671365] pci_bus :02: busn_res: [bus 02-ff] end is updated to 02 [4.671391] pci :00:02.0: BAR 8: assigned [mem 0xe000-0xe02f] [4.678247] pci :01:00.0: BAR 0: assigned [mem 0xe000-0xe01f 64bit] [4.685609] pci :01:00.0: BAR 0: error updating (0xe004 != 0x) [4.692890] pci :01:00.0: BAR 0: error updating (high 0x00 != 0x) [4.700416] pci :01:00.0: BAR 6: assigned [mem 0xe020-0xe020 pref] [4.706967] random: fast init done [4.707688] pci :00:02.0: PCI bridge to [bus 01] [4.716066] pci :00:02.0: bridge window [mem 0xe000-0xe02f] [4.722883] pci :00:03.0: PCI bridge to [bus 02] [4.730477] pcieport :00:02.0: enabling device (0140 -> 0142) [5.339193] Marvell 88E1540 mv88e6xxx-0:00: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:00, irq=64) [5.431158] Marvell 88E1540 mv88e6xxx-0:01: attached PHY driver [Marvell 88E1540] (mii_bus:phy_addr=mv88e6xxx-0:01, irq=65) [5.521407] Marvell 88E1540 mv88e6xxx-0:02: attached PHY driver
Bug#876774: tested with 4.16-rc6, patch
Greetings once again, I have now rebuilt the current kernel package from sid, with the necessary config changes. So far it boots, and network works. I haven't tested anything else yet. Please find attached the patch for enabling the missing options. br Josua Mayer >From b7411e73b05896e024f4059f7ae5c27ad2942992 Mon Sep 17 00:00:00 2001 From: Josua Mayer <josua.maye...@gmail.com> Date: Tue, 3 Apr 2018 23:40:53 +0200 Subject: [PATCH] enable support for dove cubox This enables CONFIG_MACH_DOVE, and a few device-specific drivers. Signed-off-by: Josua Mayer <josua.maye...@gmail.com> --- debian/config/armhf/config | 17 + 1 file changed, 17 insertions(+) diff --git a/debian/config/armhf/config b/debian/config/armhf/config index d54d43eee..16e65cceb 100644 --- a/debian/config/armhf/config +++ b/debian/config/armhf/config @@ -78,6 +78,7 @@ CONFIG_MACH_ARMADA_375=y CONFIG_MACH_ARMADA_38X=y CONFIG_MACH_ARMADA_39X=y CONFIG_MACH_ARMADA_XP=y +CONFIG_MACH_DOVE=y ## ## file: arch/arm/mach-omap1/Kconfig @@ -134,6 +135,7 @@ CONFIG_ARCH_WM8850=y ## file: arch/arm/mm/Kconfig ## CONFIG_ARM_THUMBEE=y +CONFIG_CACHE_TAUROS2=y ## ## file: arch/arm/plat-omap/Kconfig @@ -197,6 +199,7 @@ CONFIG_COMMON_CLK_MAX77686=m CONFIG_COMMON_CLK_RK808=m CONFIG_COMMON_CLK_S2MPS11=m CONFIG_CLK_TWL6040=m +CONFIG_COMMON_CLK_SI5351=m ## ## file: drivers/cpufreq/Kconfig @@ -438,6 +441,7 @@ CONFIG_I2C_MESON=m ## CONFIG_I2C_ARB_GPIO_CHALLENGE=m CONFIG_I2C_MUX_PCA954x=m +CONFIG_I2C_MUX_PINCTRL=m ## ## file: drivers/iio/Kconfig @@ -641,6 +645,7 @@ CONFIG_MMC_WMT=m CONFIG_MMC_SUNXI=m CONFIG_MMC_BCM2835=m CONFIG_MMC_MESON_MX_SDIO=m +CONFIG_MMC_SDHCI_DOVE=m ## ## file: drivers/mtd/Kconfig @@ -754,6 +759,7 @@ CONFIG_E100=m CONFIG_MVMDIO=m CONFIG_MVNETA=m CONFIG_MVPP2=m +CONFIG_MV643XX_ETH=m ## ## file: drivers/net/ethernet/microchip/Kconfig @@ -882,6 +888,11 @@ CONFIG_PHY_SUN4I_USB=m CONFIG_PHY_SUN9I_USB=m ## +## file: drivers/phy/marvell/Kconfig +## +CONFIG_PHY_MVEBU_SATA=m + +## ## file: drivers/phy/rockchip/Kconfig ## CONFIG_PHY_ROCKCHIP_DP=m @@ -1080,6 +1091,7 @@ CONFIG_SPI_MESON_SPIFC=m ## CONFIG_ROCKCHIP_THERMAL=m CONFIG_ARMADA_THERMAL=y +CONFIG_DOVE_THERMAL=m ## ## file: drivers/thermal/broadcom/Kconfig @@ -1335,6 +1347,11 @@ CONFIG_SND_SOC_IMX_MC13783=m CONFIG_SND_SIMPLE_CARD=m ## +## file: sound/soc/kirkwood/Kconfig +## +CONFIG_SND_KIRKWOOD_SOC=m + +## ## file: sound/soc/omap/Kconfig ## CONFIG_SND_OMAP_SOC=m -- 2.13.6
Bug#876774: linux-image-4.9.0-3-armmp: please enable missing configuration options for dove cubox
Package: src:linux Version: 4.9.30-2+deb9u5 Severity: wishlist Tags: patch Dear Maintainer, Please enable the required config options for supporting the SolidRun CuBox (Dove). This machine is extremely well supported in Mainline and it would be great if it could become a first-class citizen of Debian. Note that not only the 4.9.0-armmp is affected, but also any later kernel package at this point. I'd be happy to test any version after enabling the missing options! But getting it into stretch would be supreme. I have collected these missing options: CONFIG_MACH_DOVE=y CONFIG_CACHE_TAUROS2=y CONFIG_CPU_PJ4=y CONFIG_DOVE_CLK=y CONFIG_DOVE_THERMAL=n CONFIG_MMC_SDHCI_DOVE=n CONFIG_ORION_IRQCHIP=y CONFIG_ORION_TIMER=y CONFIG_PHY_MVEBU_SATA=y CONFIG_PINCTRL_DOVE=y CONFIG_COMMON_CLK_SI5351=m CONFIG_I2C_MUX_PINCTRL=m CONFIG_MMC_SDHCI_DOVE=m CONFIG_MV643XX_ETH=m CONFIG_PHY_MVEBU_SATA=m CONFIG_SND_KIRKWOOD_SOC=m CONFIG_DOVE_THERMAL=m # This one is not needed, it is present on the SoC, but not exposed by the Cubox CONFIG_DRM_ARMADA=m I have built mainline 4.9.45 from the armmp .config, and above options to verify that it actually does work! Yours sincerely Josua Mayer -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Hardware: Marvell Dove Revision: Device Tree model: SolidRun CuBox ** PCI devices: ** USB devices: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armhf (armv7l) Kernel: Linux 4.9.45-dove-cubox (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.9.0-3-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.130 ii kmod23-2 ii linux-base 4.5 Versions of packages linux-image-4.9.0-3-armmp recommends: ii firmware-linux-free 3.4 ii irqbalance 1.1.0-2.3 Versions of packages linux-image-4.9.0-3-armmp suggests: pn debian-kernel-handbook pn linux-doc-4.9 Versions of packages linux-image-4.9.0-3-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#855472: (no subject)
This is about linux-image-4.9.0-1-armmp in stretch, armhf.
Bug#855472: display drivers missing for gta04 board
Package: src:linux Version: 4.9.6-3 Severity: normal Tags: upstream Dear Maintainers, Please enable following set of configs to support the display on GTA04 phone: CONFIG_DRM_OMAP_PANEL_TPO_TD028TTEC1=m CONFIG_PWM_OMAP_DMTIMER=m This enables the driver for the connected display, and the pwm driver that is used for backlight. br Josua Mayer
Bug#847779: omap2-nand not auto-loaded on gta04
Package: linux-image-4.9.0-rc8-armmp-unsigned: src:linux Version: 4.9~rc8-1~exp1 Message-ID: <148146021121.356.16709761149479929183.reportbug@localhost> X-Mailer: reportbug 6.6.6 Date: Sun, 11 Dec 2016 12:43:31 + X-Debbugs-Cc: josua.maye...@gmail.com Severity: normal Dear Maintainer, While doing some more tests on the GTA04 board I found that the nand flash works just fine *after* manually loading omap2-nand. The kernel should know to load that module on its own, why it doesn't is still to be found. -- Package-specific info: ** Version: Linux version 4.9.0-rc8-armmp (debian-kernel@lists.debian.org) (gcc version 6.2.1 20161124 (Debian 6.2.1-5) ) #1 SMP Debian 4.9~rc8-1~exp1 (2016-12-05) ** Command line: console=ttyO2,115200n8 root=/dev/mmcblk0p1 rootfstype=ext2 rootwait ** Tainted: E (8192) * Unsigned module has been loaded. ** Kernel log: [ 11.949829] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:758: group 6, block bitmap and bg descriptor inconsistent: 5945 vs 5947 free clusters [ 12.437194] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:758: group 1, block bitmap and bg descriptor inconsistent: 26419 vs 26417 free clusters [ 12.556365] EXT4-fs error (device mmcblk0p1): ext4_mb_generate_buddy:758: group 2, block bitmap and bg descriptor inconsistent: 18241 vs 18243 free clusters [ 14.364379] 4805.dss supply vdda_video not found, using dummy regulator [ 14.476654] OMAP DSS rev 2.0 [ 14.514038] omapdss_dss 4805.dss: bound 48050400.dispc (ops dispc_component_ops [omapdss]) [ 14.592834] omapdss_dss 4805.dss: bound 48050c00.encoder (ops venc_component_ops [omapdss]) [ 14.893432] omap_ssi 48058000.ssi-controller: ssi controller 0 initialized (2 ports)! [ 14.959777] omap_ssi_port 4805a000.ssi-port: couldn't get cawake gpio (err=-2)! [ 15.034698] omap_ssi_port: probe of 4805a000.ssi-port failed with error -2 [ 15.130096] omap_ssi_port 4805b000.ssi-port: couldn't get cawake gpio (err=-2)! [ 15.185852] omap_ssi_port: probe of 4805b000.ssi-port failed with error -2 [ 15.261901] input: twl4030_pwrbutton as /devices/platform/6800.ocp/4807.i2c/i2c-0/0-0048/4807.i2c:twl@48:pwrbutton/input/input1 [ 15.357574] input: twl4030:vibrator as /devices/platform/6800.ocp/4807.i2c/i2c-0/0-0048/4807.i2c:twl@48:audio/twl4030-vibra/input/input2 [ 15.437683] 4807.i2c:twl@48:madc supply vusb3v1 not found, using dummy regulator [ 15.552154] twl4030_bci 4807.i2c:twl@48:bci: could not request vac iio channel [ 16.300292] Driver for 1-wire Dallas network protocol. [ 16.335479] input: TSC2007 Touchscreen as /devices/platform/6800.ocp/48072000.i2c/i2c-1/1-0048/input/input3 [ 16.499816] omap_hdq 480b2000.1w: OMAP HDQ Hardware Rev 0.5. Driver in Interrupt mode [ 16.508819] at24 1-0050: 8192 byte 24c64 EEPROM, writable, 1 bytes/write [ 16.631317] omap-sham 480c3000.sham: hw accel on OMAP rev 0.9 [ 17.195587] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec [ 17.245086] OF: graph: no port node found in /ocp@6800/isp@480bc000/ports [ 17.292327] 480bc000.isp supply vdd-csiphy1 not found, using dummy regulator [ 17.419189] 480bc000.isp supply vdd-csiphy2 not found, using dummy regulator [ 17.456146] backlight supply power not found, using dummy regulator [ 17.519348] omap3isp 480bc000.isp: Revision 15.0 found [ 17.547027] connector-analog-tv connector: failed to find video source [ 17.595306] iommu: Adding device 480bc000.isp to group 0 [ 17.671722] omap-iommu 480bd400.mmu: 480bd400.mmu: version 1.1 [ 17.753997] OF: ERROR: Bad of_node_put() on /ocp@6800/i2c@4807/twl@48/audio [ 17.762023] CPU: 0 PID: 230 Comm: systemd-udevd Tainted: G E 4.9.0-rc8-armmp #1 Debian 4.9~rc8-1~exp1 [ 17.772827] Hardware name: Generic OMAP36xx (Flattened Device Tree) [ 17.779418] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) [ 17.787506] [] (show_stack) from [] (dump_stack+0x90/0xa4) [ 17.795074] [] (dump_stack) from [] (of_node_release+0xa0/0xa4) [ 17.803070] [] (of_node_release) from [] (kobject_put+0xc8/0x224) [ 17.811248] [] (kobject_put) from [] (of_node_put+0x24/0x28) [ 17.818969] [] (of_node_put) from [] (of_find_node_by_name+0x8c/0xdc) [ 17.827545] [] (of_find_node_by_name) from [] (twl4030_soc_probe+0x8c/0x438 [snd_soc_twl4030]) [ 17.838439] [] (twl4030_soc_probe [snd_soc_twl4030]) from [] (snd_soc_codec_drv_probe+0x28/0x2c [snd_soc_core]) [ 17.850860] [] (snd_soc_codec_drv_probe [snd_soc_core]) from [] (soc_probe_component+0x22c/0x374 [snd_soc_core]) [ 17.863342] [] (soc_probe_component [snd_soc_core]) from [] (snd_soc_register_card+0x4b8/0xe7c [snd_soc_core]) [ 17.875640] [] (snd_soc_register_card [snd_soc_core]) from [] (devm_snd_soc_register_card+0x48/0x80 [snd_soc_core]) [ 17.888397] [] (devm_snd_soc_register_card [snd_soc_core]) from [] (omap_twl4030_probe+0x130/0x1e4 [snd_soc_omap_twl4030]) [ 17.901763] [] (omap_twl4030_probe
Bug#847775: solved in 4.9
With the current kernel in testing, namely 4.9.0-rc8-armmp, the omap-aes module is loading just fine. So when 4.9 hits testing, this bug should be done.
Bug#847775: promised serial console logfile
Forgot attaching the log to the report, so here goes nothing omap-aes.log Description: Binary data
Bug#847775: linux-image-4.8.0-2-armmp: kernel crashes while loading omap-aes module
Package: src:linux Version: 4.8.11-1 Severity: important Dear Maintainer, I booted latest debian unstable on my gta04 board and noticed that the system crashes as soon as omap-aes is loaded (which happens automatically unless blacklisted). The same crash also happens on 4.8.0-1, but I do not know when it started since I am only now bringing the armmp package to this board. Please find the serial log attached to this report. -- Package-specific info: ** Version: Linux version 4.8.0-2-armmp (debian-kernel@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.11-1 (2016-12-02) ** Command line: console=ttyO2,115200n8 root=/dev/mmcblk0p1 rootfstype=ext2 rootwait ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 17.647674] omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP AF was not initialized! [ 17.739471] omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP histogram was not initialized! [ 17.805541] iommu: Removing device 480bc000.isp from group 0 [ 17.852447] omap3isp: probe of 480bc000.isp failed with error -22 [ 17.865447] backlight supply power not found, using dummy regulator [ 18.646972] OF: ERROR: Bad of_node_put() on /ocp/i2c@4807/twl@48/audio [ 18.654174] CPU: 0 PID: 214 Comm: systemd-udevd Not tainted 4.8.0-2-armmp #1 Debian 4.8.11-1 [ 18.663024] Hardware name: Generic OMAP36xx (Flattened Device Tree) [ 18.669616] [] (unwind_backtrace) from [] (show_stack+0x20/0x24) [ 18.677734] [] (show_stack) from [] (dump_stack+0x98/0xac) [ 18.685302] [] (dump_stack) from [] (of_node_release+0xa0/0xa4) [ 18.693328] [] (of_node_release) from [] (kobject_put+0xe0/0x1ec) [ 18.701538] [] (kobject_put) from [] (of_node_put+0x24/0x28) [ 18.709289] [] (of_node_put) from [] (of_find_node_by_name+0x8c/0xdc) [ 18.717834] [] (of_find_node_by_name) from [] (twl4030_soc_probe+0x8c/0x424 [snd_soc_twl4030]) [ 18.728790] [] (twl4030_soc_probe [snd_soc_twl4030]) from [] (snd_soc_codec_drv_probe+0x28/0x2c [snd_soc_core]) [ 18.741210] [] (snd_soc_codec_drv_probe [snd_soc_core]) from [] (soc_probe_component+0x22c/0x370 [snd_soc_core]) [ 18.753723] [] (soc_probe_component [snd_soc_core]) from [] (snd_soc_register_card+0x4dc/0xe68 [snd_soc_core]) [ 18.766082] [] (snd_soc_register_card [snd_soc_core]) from [] (devm_snd_soc_register_card+0x48/0x80 [snd_soc_core]) [ 18.778839] [] (devm_snd_soc_register_card [snd_soc_core]) from [] (omap_twl4030_probe+0x138/0x1f0 [snd_soc_omap_twl4030]) [ 18.792266] [] (omap_twl4030_probe [snd_soc_omap_twl4030]) from [] (platform_drv_probe+0x5c/0xc0) [ 18.803375] [] (platform_drv_probe) from [] (driver_probe_device+0x238/0x43c) [ 18.812683] [] (driver_probe_device) from [] (__driver_attach+0x100/0x10c) [ 18.821685] [] (__driver_attach) from [] (bus_for_each_dev+0x8c/0xd0) [ 18.830291] [] (bus_for_each_dev) from [] (driver_attach+0x2c/0x30) [ 18.838653] [] (driver_attach) from [] (bus_add_driver+0x210/0x28c) [ 18.847045] [] (bus_add_driver) from [] (driver_register+0x88/0x108) [ 18.855529] [] (driver_register) from [] (__platform_driver_register+0x50/0x58) [ 18.864990] [] (__platform_driver_register) from [] (omap_twl4030_driver_init+0x1c/0x24 [snd_soc_omap_twl4030]) [ 18.877380] [] (omap_twl4030_driver_init [snd_soc_omap_twl4030]) from [] (do_one_initcall+0x60/0x1a4) [ 18.54] [] (do_one_initcall) from [] (do_init_module+0x74/0x1e4) [ 18.897338] [] (do_init_module) from [] (load_module+0x2064/0x2690) [ 18.905731] [] (load_module) from [] (SyS_finit_module+0xdc/0x110) [ 18.914062] [] (SyS_finit_module) from [] (__sys_trace_return+0x0/0x10) [ 18.932922] backlight supply power not found, using dummy regulator [ 18.965820] [ cut here ] [ 18.970703] WARNING: CPU: 0 PID: 6 at /build/linux-89XnL_/linux-4.8.11/include/linux/kref.h:46 kobject_get+0xac/0xb0 [ 18.981689] Modules linked in: joydev omapdrm(+) drm_kms_helper snd_soc_simple_card(+) snd_soc_simple_card_utils drm snd_soc_omap_twl4030(+) evdev connector_analog_tv pwm_bl cpufreq_dt snd_soc_omap_mcbsp omap3_isp snd_soc_omap w1_smem omap_wdt videobuf2_dma_contig snd_soc_twl4030 videobuf2_memops videobuf2_v4l2 omap_sham omap_hdq snd_soc_core videobuf2_core at24 wire nvmem_core tsc2007 snd_pcm_dmaengine spi_omap2_mcspi twl4030_wdt snd_pcm snd_timer snd twl4030_vibra soundcore twl4030_charger ff_memless twl4030_pwrbutton twl4030_madc pwm_twl pwm_twl_led industrialio omapdss omap_ssi hsi sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache phy_generic pbias_regulator ti_abb_regulator ohci_omap3 phy_twl4030_usb omap2430 omap_hsmmc phy_omap_control ehci_omap ohci_hcd [ 19.055664] musb_hdrc ehci_hcd udc_core usbcore usb_common [ 19.060150] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 4.8.0-2-armmp #1 Debian 4.8.11-1 [ 19.068695] Hardware name: Generic OMAP36xx (Flattened Device Tree) [ 19.075286] Workqueue: deferwq deferred_probe_work_func [ 19.080780] []
Bug#847770: linux-image-4.8.0-1-armmp: tca-6507 driver missing - required to turn on wifi chip
Package: src:linux Version: 4.8.7-1 Severity: normal Tags: upstream Dear Maintainer, I started running the standard debian armmp kernel on the GTA04 and noticed that some driver are missing. For starters this bug is about wireless lan. The device features a Marvell 8686 module which is supported by the libertas driver. On this specific board, the wifi chip is switched on and off by a TCA 6507. Please consider enabling the driver for this chip in the armmp config: CONFIG_LEDS_TCA6507 -- Package-specific info: ** Version: Linux version 4.8.0-1-armmp (debian-kernel@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13) ** Command line: console=ttyO2,115200n8 root=/dev/mmcblk0p1 rootfstype=ext2 rootwait ** Tainted: W (512) * Taint on warning. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Hardware: Generic OMAP36xx (Flattened Device Tree) Revision: Device Tree model: Goldelico GTA04A4 ** Loaded modules: joydev omapdrm drm_kms_helper drm snd_soc_simple_card snd_soc_omap_twl4030 snd_soc_simple_card_utils evdev connector_analog_tv pwm_bl cpufreq_dt w1_smem snd_soc_omap_mcbsp omap3_isp snd_soc_omap snd_soc_twl4030 videobuf2_dma_contig omap_wdt videobuf2_memops videobuf2_v4l2 omap_hdq omap_sham videobuf2_core snd_soc_core wire at24 snd_pcm_dmaengine nvmem_core spi_omap2_mcspi tsc2007 snd_pcm twl4030_wdt snd_timer snd twl4030_charger twl4030_madc soundcore twl4030_pwrbutton twl4030_vibra ff_memless pwm_twl industrialio pwm_twl_led omapdss omap_ssi hsi sunrpc ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb mbcache phy_generic pbias_regulator ti_abb_regulator omap2430 phy_omap_control ohci_omap3 phy_twl4030_usb omap_hsmmc ehci_omap musb_hdrc ohci_hcd udc_core ehci_hcd usbcore usb_common ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 4.8.0-1-armmp (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-4.8.0-1-armmp depends on: ii initramfs-tools [linux-initramfs-tool] 0.125 ii kmod23-1 ii linux-base 4.5 Versions of packages linux-image-4.8.0-1-armmp recommends: ii firmware-linux-free 3.4 ii irqbalance 1.1.0-2 Versions of packages linux-image-4.8.0-1-armmp suggests: pn debian-kernel-handbook pn linux-doc-4.8 Versions of packages linux-image-4.8.0-1-armmp is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
