Activity log for bug #1169117

Date Who What changed Old value New value Message
2013-04-15 09:45:17 Marius B. Kotsbak bug added bug
2013-04-15 09:45:50 Marius B. Kotsbak bug task added linux (Ubuntu)
2013-04-15 09:46:02 Marius B. Kotsbak bug watch added http://bugzilla.kernel.org/show_bug.cgi?id=54791
2013-04-15 09:46:02 Marius B. Kotsbak bug task added linux
2013-04-15 09:49:16 Launchpad Janitor linux (Ubuntu): status New Confirmed
2013-04-15 09:49:16 Launchpad Janitor modemmanager (Ubuntu): status New Confirmed
2013-04-15 09:50:03 Marius B. Kotsbak summary MBIM kernel suppport should be disabled until userspace support available MBIM kernel suppport should be disabled until userspace support available (breaks Ericsson H5321 etc.)
2013-04-15 10:01:26 Till Kamppeter linux (Ubuntu): importance Undecided High
2013-04-15 10:01:27 Till Kamppeter modemmanager (Ubuntu): importance Undecided High
2013-04-15 10:01:31 Till Kamppeter linux (Ubuntu): importance High Critical
2013-04-15 10:01:33 Till Kamppeter modemmanager (Ubuntu): importance High Critical
2013-04-15 10:01:57 Till Kamppeter summary MBIM kernel suppport should be disabled until userspace support available (breaks Ericsson H5321 etc.) REGRESSION: MBIM kernel suppport should be disabled until userspace support available (breaks Ericsson H5321 etc.)
2013-04-15 10:02:11 Till Kamppeter tags regression-release
2013-04-15 10:04:37 Till Kamppeter linux (Ubuntu): milestone ubuntu-13.04
2013-04-15 10:04:39 Till Kamppeter modemmanager (Ubuntu): milestone ubuntu-13.04
2013-04-15 11:01:49 Bug Watch Updater linux: status Unknown Fix Released
2013-04-15 11:01:49 Bug Watch Updater linux: importance Unknown Medium
2013-04-15 12:25:09 Marius B. Kotsbak description "commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices") introduced a new policy, preferring MBIM for dual NCM/MBIM functions if the cdc_mbim driver was enabled. This caused a regression for users wanting to use NCM." This could be solved in different ways: 1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content: options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. "commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices")     introduced a new policy, preferring MBIM for dual NCM/MBIM functions if     the cdc_mbim driver was enabled. This caused a regression for users     wanting to use NCM." This could be solved in different ways: 1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content:   options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. See also bug #1102343.
2013-04-15 12:56:56 Marius B. Kotsbak bug task added linux (Debian)
2013-04-15 12:57:17 Marius B. Kotsbak linux (Debian): status New Fix Committed
2013-04-15 12:58:06 Marius B. Kotsbak description "commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices")     introduced a new policy, preferring MBIM for dual NCM/MBIM functions if     the cdc_mbim driver was enabled. This caused a regression for users     wanting to use NCM." This could be solved in different ways: 1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content:   options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. See also bug #1102343. "commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices")     introduced a new policy, preferring MBIM for dual NCM/MBIM functions if     the cdc_mbim driver was enabled. This caused a regression for users     wanting to use NCM." This could be solved in different ways: 1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content:   options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. 3) Debian has solved it by patching the kernel to reverse the default to be not to use MBIM: http://web.archiveorange.com/archive/v/dbmrrKybrWTJ0XZGsB3B http://lists.debian.org/debian-kernel/2013/03/msg00611.html See also bug #1102343.
2013-04-15 13:51:22 Marius B. Kotsbak modemmanager (Ubuntu): status Confirmed Invalid
2013-04-15 16:24:41 Joseph Salisbury tags regression-release raring regression-release
2013-04-15 17:37:34 Joseph Salisbury linux (Ubuntu): importance Critical High
2013-05-28 04:05:06 Jorgen Smith bug added subscriber Jorgen Smith
2013-06-06 14:41:29 Manuel Xosé Lemos bug added subscriber Manuel Xosé Lemos
2013-06-23 08:58:03 Gabriel Ebner bug added subscriber Gabriel Ebner
2013-07-25 19:30:27 SebG bug added subscriber SebG
2013-09-21 21:43:39 zlatko bug added subscriber zlatko
2014-01-03 04:53:01 penalvch description "commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices")     introduced a new policy, preferring MBIM for dual NCM/MBIM functions if     the cdc_mbim driver was enabled. This caused a regression for users     wanting to use NCM." This could be solved in different ways: 1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content:   options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. 3) Debian has solved it by patching the kernel to reverse the default to be not to use MBIM: http://web.archiveorange.com/archive/v/dbmrrKybrWTJ0XZGsB3B http://lists.debian.org/debian-kernel/2013/03/msg00611.html See also bug #1102343. "commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices")     introduced a new policy, preferring MBIM for dual NCM/MBIM functions if     the cdc_mbim driver was enabled. This caused a regression for users     wanting to use NCM." This could be solved in different ways: 1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content:   options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. 3) Debian has solved it by patching the kernel to reverse the default to be not to use MBIM: http://web.archiveorange.com/archive/v/dbmrrKybrWTJ0XZGsB3B http://lists.debian.org/debian-kernel/2013/03/msg00611.html See also bug #1102343. WORKAROUND: Add in /etc/modprobe.d/cdc_ncm.conf : options cdc_ncm prefer_mbim=N
2014-01-03 05:25:37 penalvch description "commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices")     introduced a new policy, preferring MBIM for dual NCM/MBIM functions if     the cdc_mbim driver was enabled. This caused a regression for users     wanting to use NCM." This could be solved in different ways: 1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content:   options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. 3) Debian has solved it by patching the kernel to reverse the default to be not to use MBIM: http://web.archiveorange.com/archive/v/dbmrrKybrWTJ0XZGsB3B http://lists.debian.org/debian-kernel/2013/03/msg00611.html See also bug #1102343. WORKAROUND: Add in /etc/modprobe.d/cdc_ncm.conf : options cdc_ncm prefer_mbim=N "commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices")     introduced a new policy, preferring MBIM for dual NCM/MBIM functions if     the cdc_mbim driver was enabled. This caused a regression for users     wanting to use NCM." For background on this change please see Bug #1102343. This could be solved in different ways: 1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support 2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content:   options cdc_ncm prefer_mbim=N This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package? The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1. 3) Debian has solved it by patching the kernel to reverse the default to be not to use MBIM: http://lists.alioth.debian.org/pipermail/kernel-svn-changes/2013-March/018852.html http://lists.debian.org/debian-kernel/2013/03/msg00611.html WORKAROUND: Add in /etc/modprobe.d/cdc_ncm.conf : options cdc_ncm prefer_mbim=N
2014-01-03 05:28:47 penalvch linux (Ubuntu): importance High Low
2014-01-03 05:28:47 penalvch linux (Ubuntu): status Confirmed Triaged
2014-01-03 05:28:47 penalvch linux (Ubuntu): milestone ubuntu-13.04 ubuntu-14.04-feature-freeze
2014-01-03 05:29:36 penalvch linux (Debian): status Fix Committed Invalid