This bug was fixed in the package linux-raspi2 - 5.3.0-1015.17
---
linux-raspi2 (5.3.0-1015.17) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1015.17 -proposed tracker (LP: #1854744)
* Conflicting mmc modules built in (LP: #1762835)
- [Config] raspi2: Remove upstream mmc
This bug was fixed in the package linux-raspi2 - 4.15.0-1053.57
---
linux-raspi2 (4.15.0-1053.57) bionic; urgency=medium
* bionic/linux-raspi2: 4.15.0-1053.57 -proposed tracker (LP: #1854793)
* Bionic update: upstream stable patchset 2019-11-21 (LP: #1853519)
- raspi2:
This bug was fixed in the package linux-raspi2 - 5.0.0-1024.25
---
linux-raspi2 (5.0.0-1024.25) disco; urgency=medium
* disco/linux-raspi2: 5.0.0-1024.25 -proposed tracker (LP: #1854766)
* -mlong32 is an unknown option (LP: #185263)
- raspi2: [CONFIG] updateconfigs for DMLIB
This bug was fixed in the package linux-raspi2 - 5.3.0-1015.17
---
linux-raspi2 (5.3.0-1015.17) eoan; urgency=medium
* eoan/linux-raspi2: 5.3.0-1015.17 -proposed tracker (LP: #1854744)
* Conflicting mmc modules built in (LP: #1762835)
- [Config] raspi2: Remove upstream mmc
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux-raspi2 (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux-raspi2 (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux-raspi2 (Ubuntu Bionic)
Importance:
** Also affects: linux-raspi2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux-raspi2 (Ubuntu Disco)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error is benign, meaning that the kernel simply tries to load a
driver for a device that is already managed by a different driver and
thus logs an error. I don't believe that this is the cause of the issue
you're seeing.
--
You received this bug notification because you are a member of
Hello @juergh
I believe this issue is also affecting me, I reported this earlier this
year: https://bugs.launchpad.net/ubuntu/+source/linux-
raspi2/+bug/1823655
How are you progressing getting a fix into the kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux-raspi2 (Ubuntu Bionic)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762835
Title:
Conflicting mmc modules built in
To
** Also affects: linux-raspi2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762835
This really needs fixing as it clearly is confusing users. It is a very
visible error message, especially if you boot with 'quite splash' as it
remains on the boot screen for quite a few seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I sent the patch to the kernel mailing list back in April:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091646.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762835
Title:
Raspbian dmesg
** Attachment added: "rasp-dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5120090/+files/rasp-dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is the dmesg with the patched kernel (upstream mmc modules
removed).
** Attachment added: "ubuntu-patched-dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5120013/+files/ubuntu-patched-dmesg.txt
--
You received this bug notification because you
Just for fun I did the reverse - i.e. downstream mmc modules removed and
upstream modules kept in. Note how confusing the mmc module messages are
in dmesg. It is impossible for the casual reader of the dmesg logs to
tell which mmc module are in use.
** Attachment added:
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ The Bionic Linux-raspi2 kernel has both the upstream and downstream pi
+ mmc modules enabled. Running the latest server image users can see this
+ error in dmesg:
+
+ Error: Driver 'sdhost-bcm2835' is already registered, aborting...
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762835
Title:
Conflicting mmc modules built in
To manage notifications about this bug go to:
Attached is a config patch.
Is a device tree change needed too?
** Patch added: "mmc_config.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5111407/+files/mmc_config.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is the Xenial config: It uses bcm2835 and bcm2835_sdhost which is a
mix of the upstream and downstream drivers.
CONFIG_MMC=y
CONFIG_MMC35240=m
CONFIG_MMC_ARMMMCI=y
CONFIG_MMC_BCM2835=y
CONFIG_MMC_BCM2835_DMA=y
CONFIG_MMC_BCM2835_PIO_DMA_BARRIER=2
CONFIG_MMC_BCM2835_SDHOST=y
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1762835
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "4.15 dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5109828/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762835
** Attachment added: "config-4.15.0-1005-raspi2"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5109827/+files/config-4.15.0-1005-raspi2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same problem if I upgrade to 4.15. Note the
sdhci_iproc16384 0
line in lsmod. I can't remember if I had the wifi firmware present when
I ran the 4.13 logs (sorry!).
** Attachment added: "4.15 lsmod results"
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5109819/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762835
** Attachment added: "config-4.13.0-1008-raspi2"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5109820/+files/config-4.13.0-1008-raspi2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "modules.builtin"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5109822/+files/modules.builtin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Results of running lsmod"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1762835/+attachment/5109821/+files/lsmod.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
29 matches
Mail list logo
