[Kernel-packages] [Bug 1300623] Re: bluetoothd crashs after resuming from Suspend to RAM.

[Shih-Yuan Lee]

** Description changed:

  bluetoothd crashs after resuming from Suspend to RAM when it plays music
  through Bluetooth audio output.
+ 
+ ➜  crash  apport-retrace -g _usr_sbin_bluetoothd.0.crash
+ GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
+ Copyright (C) 2012 Free Software Foundation, Inc.
+ License GPLv3+: GNU GPL version 3 or later 
+ This is free software: you are free to change and redistribute it.
+ There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
+ and "show warranty" for details.
+ This GDB was configured as "x86_64-linux-gnu".
+ For bug reporting instructions, please see:
+ .
+ Reading symbols from /usr/sbin/bluetoothd...Reading symbols from 
/usr/lib/debug/usr/sbin/bluetoothd...done.
+ done.
+ [New LWP 1053]
+ warning: Can't read pathname for load map: Input/output error.
+ [Thread debugging using libthread_db enabled]
+ Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
+ Core was generated by `/usr/sbin/bluetoothd'.
+ Program terminated with signal 6, Aborted.
+ #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
+ (gdb) bt
+ #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
+ #1  0x7f0107c04bab in abort () from /lib/x86_64-linux-gnu/libc.so.6
+ #2  0x7f0107c3ee2e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
+ #3  0x7f0107c49626 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
+ #4  0x7f0108a5c0b7 in g_slist_foreach (list=, 
func=0x7f0108a47b60 , user_data=0x0)
+ at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:840
+ #5  0x7f0108a5c0db in g_slist_free_full (list=0x7f0107f817d8, 
free_func=)
+ at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:177
+ #6  0x7f0108f4a3b1 in client_free (data=0x7f01096e05f0) at 
audio/unix.c:113
+ #7  0x7f0108f4be79 in client_cb (cond=, 
data=0x7f01096e05f0, chan=) at audio/unix.c:1767
+ #8  0x7f0108a41d13 in g_main_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:2539
+ #9  g_main_context_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3075
+ #10 0x7f0108a42060 in g_main_context_iterate (dispatch=1, 
block=, context=0x7f01096c6070, self=)
+ at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3146
+ #11 g_main_context_iterate (context=0x7f01096c6070, block=, 
dispatch=1, self=)
+ at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3083
+ #12 0x7f0108a4245a in g_main_loop_run (loop=0x7f01096c61e0) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3340
+ #13 0x7f0108f2c1fe in main (argc=1, argv=0x7fffd72297f8) at src/main.c:539
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Apr  1 15:19:56 2014
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-precise-amd64-20120703-2
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-precise-amd64-20120703-2
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  ProcEnviron:
-  LC_CTYPE=en_US.UTF-8
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/zsh
+  LC_CTYPE=en_US.UTF-8
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic 
root=UUID=3972ee07-72c0-4241-9b17-f4c82bd1b139 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
-  hci0:Type: BR/EDR  Bus: USB
-   BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
-   UP RUNNING PSCAN 
-   RX bytes:1339 acl:0 sco:0 events:56 errors:0
-   TX bytes:735 acl:0 sco:0 commands:56 errors:0
- --- 
- ApportVersion: 2.0.1-0ubuntu8
- Architecture: amd64
- DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-precise-amd64-20120703-2
- DistroRelease: Ubuntu 12.04
- In

[Kernel-packages] [Bug 1300623] Re: bluetoothd crashs after resuming from Suspend to RAM.

[Shih-Yuan Lee]

** Tags added: patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1300623

Title:
  bluetoothd crashs after resuming from Suspend to RAM.

Status in “bluez” package in Ubuntu:
  New

Bug description:
  bluetoothd crashs after resuming from Suspend to RAM when it plays
  music through Bluetooth audio output.

  # apport-retrace -g _usr_sbin_bluetoothd.0.crash
  GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  .
  Reading symbols from /usr/sbin/bluetoothd...Reading symbols from 
/usr/lib/debug/usr/sbin/bluetoothd...done.
  done.
  [New LWP 1053]
  warning: Can't read pathname for load map: Input/output error.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/bluetoothd'.
  Program terminated with signal 6, Aborted.
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  (gdb) bt
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7f0107c04bab in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2  0x7f0107c3ee2e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #3  0x7f0107c49626 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #4  0x7f0108a5c0b7 in g_slist_foreach (list=, 
func=0x7f0108a47b60 , user_data=0x0)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:840
  #5  0x7f0108a5c0db in g_slist_free_full (list=0x7f0107f817d8, 
free_func=)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:177
  #6  0x7f0108f4a3b1 in client_free (data=0x7f01096e05f0) at 
audio/unix.c:113
  #7  0x7f0108f4be79 in client_cb (cond=, 
data=0x7f01096e05f0, chan=) at audio/unix.c:1767
  #8  0x7f0108a41d13 in g_main_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:2539
  #9  g_main_context_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3075
  #10 0x7f0108a42060 in g_main_context_iterate (dispatch=1, 
block=, context=0x7f01096c6070, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3146
  #11 g_main_context_iterate (context=0x7f01096c6070, block=, 
dispatch=1, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3083
  #12 0x7f0108a4245a in g_main_loop_run (loop=0x7f01096c61e0) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3340
  #13 0x7f0108f2c1fe in main (argc=1, argv=0x7fffd72297f8) at src/main.c:539

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Apr  1 15:19:56 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic 
root=UUID=3972ee07-72c0-4241-9b17-f4c82bd1b139 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:1339 acl:0 sco:0 events:56 errors:0
    TX bytes:735 acl:0 sco:0 commands:56 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1300623/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1300623] Re: bluetoothd crashs after resuming from Suspend to RAM.

[Shih-Yuan Lee]

** Description changed:

+ [Impact]
+ 
+  * It is very annoying to see Bluetooth daemon crash after suspending and 
resuming when playing music through Bluetooth audio output.
+  * The better user experience should be that Ubuntu will automatically 
reconnect to the Bluetooth audio output and play music through it.
+ 
+ [Test Case]
+ 
+  * Pairing Bluetooth audio device.
+  * Playing music through Bluetooth audio output.
+  * Suspending the system.
+  * Resuming the system.
+ 
+ [Regression Potential]
+ 
+  * No obvious regression exists.
+ 
+ [Other Info]
+  
+  * The patch is just to check if the device still exists in devices list 
before removed from the list. If it exists, do what should do as original 
steps. If not, do nothing.
+ 
  bluetoothd crashs after resuming from Suspend to RAM when it plays music
  through Bluetooth audio output.
  
  # apport-retrace -g _usr_sbin_bluetoothd.0.crash
  GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  .
  Reading symbols from /usr/sbin/bluetoothd...Reading symbols from 
/usr/lib/debug/usr/sbin/bluetoothd...done.
  done.
  [New LWP 1053]
  warning: Can't read pathname for load map: Input/output error.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/bluetoothd'.
  Program terminated with signal 6, Aborted.
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  (gdb) bt
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7f0107c04bab in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2  0x7f0107c3ee2e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #3  0x7f0107c49626 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #4  0x7f0108a5c0b7 in g_slist_foreach (list=, 
func=0x7f0108a47b60 , user_data=0x0)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:840
  #5  0x7f0108a5c0db in g_slist_free_full (list=0x7f0107f817d8, 
free_func=)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:177
  #6  0x7f0108f4a3b1 in client_free (data=0x7f01096e05f0) at 
audio/unix.c:113
  #7  0x7f0108f4be79 in client_cb (cond=, 
data=0x7f01096e05f0, chan=) at audio/unix.c:1767
  #8  0x7f0108a41d13 in g_main_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:2539
  #9  g_main_context_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3075
  #10 0x7f0108a42060 in g_main_context_iterate (dispatch=1, 
block=, context=0x7f01096c6070, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3146
  #11 g_main_context_iterate (context=0x7f01096c6070, block=, 
dispatch=1, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3083
  #12 0x7f0108a4245a in g_main_loop_run (loop=0x7f01096c61e0) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3340
  #13 0x7f0108f2c1fe in main (argc=1, argv=0x7fffd72297f8) at src/main.c:539
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Apr  1 15:19:56 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic 
root=UUID=3972ee07-72c0-4241-9b17-f4c82bd1b139 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING PSCAN
  

[Kernel-packages] [Bug 1300623] Re: bluetoothd crashs after resuming from Suspend to RAM.

[Shih-Yuan Lee]

** Branch unlinked: lp:~fourdollars/ubuntu/precise/bluez/lp1300623

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1300623

Title:
  bluetoothd crashs after resuming from Suspend to RAM.

Status in “bluez” package in Ubuntu:
  Fix Released
Status in “bluez” source package in Precise:
  Fix Committed
Status in “bluez” source package in Quantal:
  Won't Fix
Status in “bluez” source package in Saucy:
  Triaged
Status in “bluez” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * It is very annoying to see Bluetooth daemon crash after suspending and 
resuming when playing music through Bluetooth audio output.
   * The better user experience should be that Ubuntu will automatically 
reconnect to the Bluetooth audio output and play music through it.

  [Test Case]

   * Pairing Bluetooth audio device.
   * Playing music through Bluetooth audio output.
   * Suspending the system.
   * Resuming the system.

  [Regression Potential]

   * No obvious regression exists.

  [Other Info]
   
   * The patch is just to check if the device still exists in devices list 
before removed from the list. If it exists, do what should do as original 
steps. If not, do nothing.

  bluetoothd crashs after resuming from Suspend to RAM when it plays
  music through Bluetooth audio output.

  # apport-retrace -g _usr_sbin_bluetoothd.0.crash
  GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  .
  Reading symbols from /usr/sbin/bluetoothd...Reading symbols from 
/usr/lib/debug/usr/sbin/bluetoothd...done.
  done.
  [New LWP 1053]
  warning: Can't read pathname for load map: Input/output error.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/bluetoothd'.
  Program terminated with signal 6, Aborted.
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  (gdb) bt
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7f0107c04bab in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2  0x7f0107c3ee2e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #3  0x7f0107c49626 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #4  0x7f0108a5c0b7 in g_slist_foreach (list=, 
func=0x7f0108a47b60 , user_data=0x0)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:840
  #5  0x7f0108a5c0db in g_slist_free_full (list=0x7f0107f817d8, 
free_func=)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:177
  #6  0x7f0108f4a3b1 in client_free (data=0x7f01096e05f0) at 
audio/unix.c:113
  #7  0x7f0108f4be79 in client_cb (cond=, 
data=0x7f01096e05f0, chan=) at audio/unix.c:1767
  #8  0x7f0108a41d13 in g_main_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:2539
  #9  g_main_context_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3075
  #10 0x7f0108a42060 in g_main_context_iterate (dispatch=1, 
block=, context=0x7f01096c6070, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3146
  #11 g_main_context_iterate (context=0x7f01096c6070, block=, 
dispatch=1, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3083
  #12 0x7f0108a4245a in g_main_loop_run (loop=0x7f01096c61e0) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3340
  #13 0x7f0108f2c1fe in main (argc=1, argv=0x7fffd72297f8) at src/main.c:539

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Apr  1 15:19:56 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic 
root=UUID=3972ee07-72c0-4241-9b17-f4c82bd1b139 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012

[Kernel-packages] [Bug 1300623] Re: bluetoothd crashs after resuming from Suspend to RAM.

[Shih-Yuan Lee]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1300623

Title:
  bluetoothd crashs after resuming from Suspend to RAM.

Status in “bluez” package in Ubuntu:
  Fix Released
Status in “bluez” source package in Precise:
  Fix Committed
Status in “bluez” source package in Quantal:
  Won't Fix
Status in “bluez” source package in Saucy:
  Triaged
Status in “bluez” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * It is very annoying to see Bluetooth daemon crash after suspending and 
resuming when playing music through Bluetooth audio output.
   * The better user experience should be that Ubuntu will automatically 
reconnect to the Bluetooth audio output and play music through it.

  [Test Case]

   * Pairing Bluetooth audio device.
   * Playing music through Bluetooth audio output.
   * Suspending the system.
   * Resuming the system.

  [Regression Potential]

   * No obvious regression exists.

  [Other Info]
   
   * The patch is just to check if the device still exists in devices list 
before removed from the list. If it exists, do what should do as original 
steps. If not, do nothing.

  bluetoothd crashs after resuming from Suspend to RAM when it plays
  music through Bluetooth audio output.

  # apport-retrace -g _usr_sbin_bluetoothd.0.crash
  GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  .
  Reading symbols from /usr/sbin/bluetoothd...Reading symbols from 
/usr/lib/debug/usr/sbin/bluetoothd...done.
  done.
  [New LWP 1053]
  warning: Can't read pathname for load map: Input/output error.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/bluetoothd'.
  Program terminated with signal 6, Aborted.
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  (gdb) bt
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7f0107c04bab in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2  0x7f0107c3ee2e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #3  0x7f0107c49626 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #4  0x7f0108a5c0b7 in g_slist_foreach (list=, 
func=0x7f0108a47b60 , user_data=0x0)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:840
  #5  0x7f0108a5c0db in g_slist_free_full (list=0x7f0107f817d8, 
free_func=)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:177
  #6  0x7f0108f4a3b1 in client_free (data=0x7f01096e05f0) at 
audio/unix.c:113
  #7  0x7f0108f4be79 in client_cb (cond=, 
data=0x7f01096e05f0, chan=) at audio/unix.c:1767
  #8  0x7f0108a41d13 in g_main_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:2539
  #9  g_main_context_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3075
  #10 0x7f0108a42060 in g_main_context_iterate (dispatch=1, 
block=, context=0x7f01096c6070, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3146
  #11 g_main_context_iterate (context=0x7f01096c6070, block=, 
dispatch=1, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3083
  #12 0x7f0108a4245a in g_main_loop_run (loop=0x7f01096c61e0) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3340
  #13 0x7f0108f2c1fe in main (argc=1, argv=0x7fffd72297f8) at src/main.c:539

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Apr  1 15:19:56 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic 
root=UUID=3972ee07-72c0-4241-9b17-f4c82bd1b139 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2

[Kernel-packages] [Bug 1300623] Re: bluetoothd crashs after resuming from Suspend to RAM.

[Shih-Yuan Lee]

I have verified by bluez 4.98-2ubuntu7.1 and it does fix the crash
issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1300623

Title:
  bluetoothd crashs after resuming from Suspend to RAM.

Status in “bluez” package in Ubuntu:
  Fix Released
Status in “bluez” source package in Precise:
  Fix Committed
Status in “bluez” source package in Quantal:
  Won't Fix
Status in “bluez” source package in Saucy:
  Triaged
Status in “bluez” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * It is very annoying to see Bluetooth daemon crash after suspending and 
resuming when playing music through Bluetooth audio output.
   * The better user experience should be that Ubuntu will automatically 
reconnect to the Bluetooth audio output and play music through it.

  [Test Case]

   * Pairing Bluetooth audio device.
   * Playing music through Bluetooth audio output.
   * Suspending the system.
   * Resuming the system.

  [Regression Potential]

   * No obvious regression exists.

  [Other Info]
   
   * The patch is just to check if the device still exists in devices list 
before removed from the list. If it exists, do what should do as original 
steps. If not, do nothing.

  bluetoothd crashs after resuming from Suspend to RAM when it plays
  music through Bluetooth audio output.

  # apport-retrace -g _usr_sbin_bluetoothd.0.crash
  GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  For bug reporting instructions, please see:
  .
  Reading symbols from /usr/sbin/bluetoothd...Reading symbols from 
/usr/lib/debug/usr/sbin/bluetoothd...done.
  done.
  [New LWP 1053]
  warning: Can't read pathname for load map: Input/output error.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/bluetoothd'.
  Program terminated with signal 6, Aborted.
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  (gdb) bt
  #0  0x7f0107c01445 in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7f0107c04bab in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2  0x7f0107c3ee2e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #3  0x7f0107c49626 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #4  0x7f0108a5c0b7 in g_slist_foreach (list=, 
func=0x7f0108a47b60 , user_data=0x0)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:840
  #5  0x7f0108a5c0db in g_slist_free_full (list=0x7f0107f817d8, 
free_func=)
  at /build/buildd/glib2.0-2.32.4/./glib/gslist.c:177
  #6  0x7f0108f4a3b1 in client_free (data=0x7f01096e05f0) at 
audio/unix.c:113
  #7  0x7f0108f4be79 in client_cb (cond=, 
data=0x7f01096e05f0, chan=) at audio/unix.c:1767
  #8  0x7f0108a41d13 in g_main_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:2539
  #9  g_main_context_dispatch (context=0x7f01096c6070) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3075
  #10 0x7f0108a42060 in g_main_context_iterate (dispatch=1, 
block=, context=0x7f01096c6070, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3146
  #11 g_main_context_iterate (context=0x7f01096c6070, block=, 
dispatch=1, self=)
  at /build/buildd/glib2.0-2.32.4/./glib/gmain.c:3083
  #12 0x7f0108a4245a in g_main_loop_run (loop=0x7f01096c61e0) at 
/build/buildd/glib2.0-2.32.4/./glib/gmain.c:3340
  #13 0x7f0108f2c1fe in main (argc=1, argv=0x7fffd72297f8) at src/main.c:539

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Apr  1 15:19:56 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  ProcEnviron:
   LC_CTYPE=en_US.UTF-8
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic 
root=UUID=3972ee07-72c0-4241-9b17-f4c82bd1b139 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/

[Kernel-packages] [Bug 1303819] Re: Bluetooth menu's content disappeared after resume.

[Shih-Yuan Lee]

I uploaded two screenshots, i.e. BluetoothMenuBefore.png and 
BluetoothMenuAfter.png.
You can compare them to see the problem.

** Attachment added: "BluetoothMenuBefore.png"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1303819/+attachment/4071976/+files/BluetoothMenuBefore.png

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1303819

Title:
  Bluetooth menu's content disappeared after resume.

Status in “bluez” package in Ubuntu:
  New

Bug description:
  * Reproducing Steps
  1. Playing music through Bluetooth audio ouput.
  2. Suspending the system.
  3. Resuming the system.
  4. Check Bluethooth menu's content

  * Expected Result
  The Bluetooth menu's content is not affected.

  * Actual Result
  The Bluetooth menu's content disappeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7.1
  ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31
  Uname: Linux 3.5.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Apr  7 19:08:01 2014
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic 
root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:6082 acl:32 sco:0 events:625 errors:0
TX bytes:949448 acl:1140 sco:0 commands:45 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1303819/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1303819] [NEW] Bluetooth menu's content disappeared after resume.

[Shih-Yuan Lee]

Public bug reported:

* Reproducing Steps
1. Playing music through Bluetooth audio ouput.
2. Suspending the system.
3. Resuming the system.
4. Check Bluethooth menu's content

* Expected Result
The Bluetooth menu's content is not affected.

* Actual Result
The Bluetooth menu's content disappeared.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7.1
ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31
Uname: Linux 3.5.0-48-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Mon Apr  7 19:08:01 2014
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude E6230
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic 
root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 098M9Y
dmi.board.vendor: Dell Inc.
dmi.board.version: X03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6230
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:6082 acl:32 sco:0 events:625 errors:0
TX bytes:949448 acl:1140 sco:0 commands:45 errors:0

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug package-from-proposed precise running-unity

** Attachment added: "BluetoothMenuAfter.png"
   
https://bugs.launchpad.net/bugs/1303819/+attachment/4071960/+files/BluetoothMenuAfter.png

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1303819

Title:
  Bluetooth menu's content disappeared after resume.

Status in “bluez” package in Ubuntu:
  New

Bug description:
  * Reproducing Steps
  1. Playing music through Bluetooth audio ouput.
  2. Suspending the system.
  3. Resuming the system.
  4. Check Bluethooth menu's content

  * Expected Result
  The Bluetooth menu's content is not affected.

  * Actual Result
  The Bluetooth menu's content disappeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7.1
  ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31
  Uname: Linux 3.5.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Apr  7 19:08:01 2014
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic 
root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:6082 acl:32 sco:0 events:625 errors:0
TX bytes:949448 acl:1140 sco:0 commands:45 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1303819/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1303819] Re: Bluetooth menu's content disappeared after resume.

[Shih-Yuan Lee]

** Description changed:

+ [Impact]
+ 
+  * It is very annoying to see Bluetooth menu's content disappeared after 
suspending and resuming when playing music through Bluetooth audio output.
+  * The better user experience is still seeing Bluetooth menu's content.
+ 
+ [Test Case]
+ 
+  * Pairing Bluetooth audio device.
+  * Playing music through Bluetooth audio output.
+  * Suspending the system.
+  * Resuming the system.
+ 
+ [Regression Potential]
+ 
+  * No obvious regression exists.
+ 
+ [Other Info]
+ 
+  * The patch is to reset default_adapter_id's value to -1, then it can
+ send the signal 'DefaultAdapterChanged' next time when new default
+ adapter is set.
+ 
  * Reproducing Steps
  1. Playing music through Bluetooth audio ouput.
  2. Suspending the system.
  3. Resuming the system.
  4. Check Bluethooth menu's content
  
  * Expected Result
  The Bluetooth menu's content is not affected.
  
  * Actual Result
  The Bluetooth menu's content disappeared.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7.1
  ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31
  Uname: Linux 3.5.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Apr  7 19:08:01 2014
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic 
root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
-  hci0:Type: BR/EDR  Bus: USB
-   BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
-   UP RUNNING PSCAN 
-   RX bytes:6082 acl:32 sco:0 events:625 errors:0
-   TX bytes:949448 acl:1140 sco:0 commands:45 errors:0
+  hci0:Type: BR/EDR  Bus: USB
+   BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
+   UP RUNNING PSCAN
+   RX bytes:6082 acl:32 sco:0 events:625 errors:0
+   TX bytes:949448 acl:1140 sco:0 commands:45 errors:0

** Tags added: patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1303819

Title:
  Bluetooth menu's content disappeared after resume.

Status in “bluez” package in Ubuntu:
  New

Bug description:
  [Impact]

   * It is very annoying to see Bluetooth menu's content disappeared after 
suspending and resuming when playing music through Bluetooth audio output.
   * The better user experience is still seeing Bluetooth menu's content.

  [Test Case]

   * Pairing Bluetooth audio device.
   * Playing music through Bluetooth audio output.
   * Suspending the system.
   * Resuming the system.

  [Regression Potential]

   * No obvious regression exists.

  [Other Info]

   * The patch is to reset default_adapter_id's value to -1, then it can
  send the signal 'DefaultAdapterChanged' next time when new default
  adapter is set.

  * Reproducing Steps
  1. Playing music through Bluetooth audio ouput.
  2. Suspending the system.
  3. Resuming the system.
  4. Check Bluethooth menu's content

  * Expected Result
  The Bluetooth menu's content is not affected.

  * Actual Result
  The Bluetooth menu's content disappeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7.1
  ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31
  Uname: Linux 3.5.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Apr  7 19:08:01 2014
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic 
root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latit

[Kernel-packages] [Bug 1303819] Re: Bluetooth menu's content disappeared after resume.

[Shih-Yuan Lee]

@seb128,
I don't know if this issue has been reported upstream.
If not, I will try to report it and fix it in upstream.

@vdragon,
Please see 'Bug attachments' in the right to find 'BluetoothMenuAfter.png'.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1303819

Title:
  Bluetooth menu's content disappeared after resume.

Status in “bluez” package in Ubuntu:
  New

Bug description:
  [Impact]

   * It is very annoying to see Bluetooth menu's content disappeared after 
suspending and resuming when playing music through Bluetooth audio output.
   * The better user experience is still seeing Bluetooth menu's content.

  [Test Case]

   * Pairing Bluetooth audio device.
   * Playing music through Bluetooth audio output.
   * Suspending the system.
   * Resuming the system.

  [Regression Potential]

   * No obvious regression exists.

  [Other Info]

   * The patch is to reset default_adapter_id's value to -1, then it can
  send the signal 'DefaultAdapterChanged' next time when new default
  adapter is set.

  * Reproducing Steps
  1. Playing music through Bluetooth audio ouput.
  2. Suspending the system.
  3. Resuming the system.
  4. Check Bluethooth menu's content

  * Expected Result
  The Bluetooth menu's content is not affected.

  * Actual Result
  The Bluetooth menu's content disappeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7.1
  ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31
  Uname: Linux 3.5.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Apr  7 19:08:01 2014
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic 
root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:6082 acl:32 sco:0 events:625 errors:0
    TX bytes:949448 acl:1140 sco:0 commands:45 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1303819/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1303819] Re: Bluetooth menu's content disappeared after resume.

[Shih-Yuan Lee]

I have verified bluez 4.98-2ubuntu7.2  on precise and it works fine.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1303819

Title:
  Bluetooth menu's content disappeared after resume.

Status in “bluez” package in Ubuntu:
  Fix Released
Status in “bluez” source package in Precise:
  Fix Committed
Status in “bluez” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * It is very annoying to see Bluetooth menu's content disappeared after 
suspending and resuming when playing music through Bluetooth audio output.
   * The better user experience is still seeing Bluetooth menu's content.

  [Test Case]

   * Pairing Bluetooth audio device.
   * Playing music through Bluetooth audio output.
   * Suspending the system.
   * Resuming the system.

  [Regression Potential]

   * No obvious regression exists.

  [Other Info]

   * The patch is to reset default_adapter_id's value to -1, then it can
  send the signal 'DefaultAdapterChanged' next time when new default
  adapter is set.

  * Reproducing Steps
  1. Playing music through Bluetooth audio ouput.
  2. Suspending the system.
  3. Resuming the system.
  4. Check Bluethooth menu's content

  * Expected Result
  The Bluetooth menu's content is not affected.

  * Actual Result
  The Bluetooth menu's content disappeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bluez 4.98-2ubuntu7.1
  ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31
  Uname: Linux 3.5.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Apr  7 19:08:01 2014
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E6230
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-48-generic 
root=UUID=8da8a808-6d55-4e04-a813-3f1217ab4f35 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 098M9Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/19/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn098M9Y:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6230
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: 74:DE:2B:D4:BB:8E  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:6082 acl:32 sco:0 events:625 errors:0
    TX bytes:949448 acl:1140 sco:0 commands:45 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1303819/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1315221] Re: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260

[Shih-Yuan Lee]

@gianluca,

It seems that you are using a preloaded Ubuntu system.
What is your hardware vendor and preloaded Ubuntu series?
Did you ever upgrade the system from Ubuntu 12.04 to Ubuntu 14.04?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1315221

Title:
  8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
  connection/becomes unusable on Intel 7260

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Intel 7260 network card regularly shows very poor performance
  and/or loses its connection entirely. On several occasions I have been
  unable to reestablish an association with the AP without rebooting.
  This occurs even if the laptop is within a few feet of the AP. I did
  not have this problem on 12.04 with a quantal backport kernel.

  Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 
6b)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Thu May  1 22:59:32 2014
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elb5375 F pulseaudio
   /dev/snd/controlC0:  elb5375 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (94 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315221/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1315221] Re: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260

[Shih-Yuan Lee]

@gianluca,

Could you also provide the list of `dkms status`?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1315221

Title:
  8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
  connection/becomes unusable on Intel 7260

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Intel 7260 network card regularly shows very poor performance
  and/or loses its connection entirely. On several occasions I have been
  unable to reestablish an association with the AP without rebooting.
  This occurs even if the laptop is within a few feet of the AP. I did
  not have this problem on 12.04 with a quantal backport kernel.

  Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 
6b)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Thu May  1 22:59:32 2014
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elb5375 F pulseaudio
   /dev/snd/controlC0:  elb5375 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (94 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315221/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1315221] Re: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260

[Shih-Yuan Lee]

@gianluca,

If you are using the Linux kernel from Ubuntu 14.04, such as 
3.13.0-{39,40,43}-generic, those DKMS packages should not affect your system.
You can remove them by `sudo apt-get purge oem-audio-hda-daily-lts-quantal 
oem-wireless-bluetooth-intel-7260` if you think they are redundant.
`uname -r` can check the kernel version.

BTW, `ubuntu-drivers devices` may also provide the helpful information.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1315221

Title:
  8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
  connection/becomes unusable on Intel 7260

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Intel 7260 network card regularly shows very poor performance
  and/or loses its connection entirely. On several occasions I have been
  unable to reestablish an association with the AP without rebooting.
  This occurs even if the laptop is within a few feet of the AP. I did
  not have this problem on 12.04 with a quantal backport kernel.

  Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 
6b)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Thu May  1 22:59:32 2014
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elb5375 F pulseaudio
   /dev/snd/controlC0:  elb5375 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (94 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315221/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1369633] Re: 4k laptop eDP display not working on newer laptops

[Shih-Yuan Lee]

I have verified kernel 3.13.0-37.64 from trusty-proposed and it does fix
the problem.

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1369633

Title:
  4k laptop eDP display not working on newer laptops

Status in HWE Next Project:
  New
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Committed

Bug description:
  Impact: Some new laptops with 4k screens are starting to use dp 1.2
  only feature of supporting 5.4ghz link rates over displayport which
  was not turned on until 3.15 even though the plumbing for it was
  (mostly) there.  This should only make more devices work since it has
  to advertise support for the feature in the dpcd. previously dp 1.2
  screens which needed 5.4ghz link rates were forced to use 2.7ghz
  instead, which would not provide enough bandwidth for some high
  resolution/high bandwidth screens. It only affects haswell for trusty,
  broadwell is handled through i915_bdw module which already as this fix
  and the fix was upstream in 3.15-rc1 so utopic is unaffected.

  Fix: Allow the 5.4ghz link rate over displayport.

  This has been tested on an affected OEM laptop with a 4K display that
  requires 5.4ghz link rate to light up (without it the display never
  turns on) as well as 2 other haswell machines to be sure it doesn't
  regress.

   [ 5.297037] [drm:intel_modeset_stage_output_state] [CONNECTOR:16:eDP-1] to 
[CRTC:5]
   [ 5.297038] [drm:intel_modeset_affected_pipes] set mode pipe masks: modeset: 
1, prepare: 1, disable: 0
   [ 5.297040] [drm:connected_sink_compute_bpp] [CONNECTOR:16:eDP-1] checking 
for sink bpp constrains
   [ 5.297042] [drm:intel_dp_compute_config] DP link computation with max lane 
count 4 max bw 14 pixel clock 533250KHz
   [ 5.297045] [drm:intel_dp_compute_config] DP link bw 14 lane count 4 clock 
54 bpp 24
   [ 5.297046] [drm:intel_dp_compute_config] DP link bw required 1279800 
available 1728000
   [ 5.297047] [drm:intel_modeset_pipe_config] plane bpp: 24, pipe bpp: 24, 
dithering: 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1369633/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1318218] Re: SATA problems on MacBook Pro 11, 1?

[Shih-Yuan Lee]

I heard that some SSHD devices may cause this issue on current kernel of trusty.
`sudo hdparm -I /dev/sda | grep Model` can be used to get the disk model name.
Using the kernel parameter 'libata.noacpi=1' may be able to solve this problem.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1318218

Title:
  SATA problems on MacBook Pro 11,1?

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 14.04 next to MacOS following the guide at
  https://help.ubuntu.com/community/MacBookPro11-1/Saucy/

  Looking into dmesg, I constantlz get entries like
  [  276.380934] ata1: SError: { PHYRdyChg }
  [  276.380943] ata1: hard resetting link
  [  277.103527] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [  277.103999] ata1.00: unexpected _GTF length (8)
  [  277.104504] ata1.00: unexpected _GTF length (8)
  [  277.104507] ata1.00: configured for UDMA/33
  [  277.104629] ata1: EH complete
  [  277.206319] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe 
frozen
  [  277.206328] ata1: irq_stat 0x0040, PHY RDY changed
  [  277.206333] ata1: SError: { PHYRdyChg }
  [  277.206343] ata1: hard resetting link
  [  277.927757] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [  277.928425] ata1.00: unexpected _GTF length (8)
  [  277.929040] ata1.00: unexpected _GTF length (8)
  [  277.929051] ata1.00: configured for UDMA/33
  [  277.929168] ata1: EH complete
  [  278.030944] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe 
frozen
  [  278.030952] ata1: irq_stat 0x0040, PHY RDY changed
  [  278.030957] ata1: SError: { PHYRdyChg }
  [  278.030965] ata1: hard resetting link
  [  278.752008] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [  278.752582] ata1.00: unexpected _GTF length (8)
  [  278.753140] ata1.00: unexpected _GTF length (8)
  [  278.753147] ata1.00: configured for UDMA/33
  [  278.753231] ata1: EH complete
  [  278.853417] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe 
frozen
  [  278.853424] ata1: irq_stat 0x0040, PHY RDY changed
  [  278.853427] ata1: SError: { PHYRdyChg }
  [  278.853434] ata1: hard resetting link
  [  279.576258] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [  279.576881] ata1.00: unexpected _GTF length (8)
  [  279.577417] ata1.00: unexpected _GTF length (8)
  [  279.577427] ata1.00: configured for UDMA/33
  [  279.577491] ata1: EH complete
  [  279.677753] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe 
frozen
  [  279.677762] ata1: irq_stat 0x0040, PHY RDY changed
  [  279.677767] ata1: SError: { PHYRdyChg }
  [  279.66] ata1: hard resetting link
  [  280.400449] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [  280.401147] ata1.00: unexpected _GTF length (8)
  [  280.401722] ata1.00: unexpected _GTF length (8)
  [  280.401733] ata1.00: configured for UDMA/33
  [  280.401809] ata1: EH complete
  [  280.502117] ata1: exception Emask 0x10 SAct 0x0 SErr 0x1 action 0xe 
frozen
  [  280.502127] ata1: irq_stat 0x0040, PHY RDY changed
  [  280.502132] ata1: SError: { PHYRdyChg }

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.47
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  markus 1663 F pulseaudio
   /dev/snd/controlC1:  markus 1663 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat May 10 19:33:44 2014
  HibernationDevice: RESUME=UUID=c71381d2-e2f3-4c96-94ea-57b8986afd08
  InstallationDate: Installed on 2014-05-09 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=7584bc70-893a-4291-a1cb-4680f5e09d22 ro libata.force=noncq quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B03.1310291227
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B03.1310291227:bd10/29/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F97

[Kernel-packages] [Bug 1381168] Re: Audio playing back too fast over HDMI on haswell.

[Shih-Yuan Lee]

I have verified linux kernel 3.13.0-40.68 from trusty-proposed and it
does fix the audio playback too fast issue.

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381168

Title:
  Audio playing back too fast over HDMI on haswell.

Status in HWE Next Project:
  New
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  This commit is part of a series that fixes HDMI audio playing back too fast 
on certain haswell machines that we have hit in HWE. By itself this patch does 
nothing but adding the new function, we are waiting for the proper fix on the 
audio side to go through the upstream stable trees and shipping them in a DKMS 
package for OEMs in the interim.

  For future reference,
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e4d9e51
  is the other commit needed.

  [Reproduce Steps]
  1. Connect to an external monitor via HDMI port on an affected machine
  2. Change the audio output from internal speaker to HDMI
  3. Play a sound

  [Results]
  Expected: Can play the sound without any problem
  Actual: The audio will played more quickly than internal speaker

  [tl;dr]
  We need this part in ASAP if possible so an audio DKMS can be used in the 
interim while discussions are going on upstream about the stable backport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381168/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work

[Shih-Yuan Lee]

I have verified systemd 204-5ubuntu20.9 and it does fix the problem.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1339998

Title:
  [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not
  work

Status in HWE Next Project:
  Fix Released
Status in HWE Next trusty series:
  In Progress
Status in HWE Next utopic series:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  In Progress
Status in “linux” package in Ubuntu:
  Fix Released
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Won't Fix
Status in “systemd” source package in Trusty:
  Fix Committed

Bug description:
  CID: 201402-14663 Dell Latitude 12 Rugged Extreme

  The microphone mute key does not work on this system, so as its LED

  Steps:
  1. Install 14.04 + update (3.13.0-30), boot to desktop
  2. Try to mute the microphone with the hotkey (fn+F4)

  Expected results:
  * Mic mute key should work, its LED should be lit and the "Mute" option for 
input device should be ticked after you press the mic mute key.

  Actual result:
  * Nothing happened.

  Debugging information:
  ubuntu@201402-14663:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 248 press
  keycode 248 release
  keycode 248 press
  keycode 248 release
  keycode 248 press
  keycode 248 release
  keycode  29 press
  ^Ccaught signal 2, cleaning up...

  xev cannot detect any microphone mute key event

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1501 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1501 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Wed Jul  9 23:57:11 2014
  HibernationDevice: RESUME=UUID=b68f02ad-f5e4-4eb9-b88d-e85f60666734
  InstallationDate: Installed on 2014-07-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude 12 Rugged Extreme (7204)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed 
root=UUID=bdd00fe9-0df9-4b71-92c5-5f94c533f725 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0TH1GJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd05/12/2014:svnDellInc.:pnLatitude12RuggedExtreme(7204):pvr01:rvnDellInc.:rn0TH1GJ:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 12 Rugged Extreme (7204)
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1339998/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work

[Shih-Yuan Lee]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1339998

Title:
  [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not
  work

Status in HWE Next Project:
  Fix Released
Status in HWE Next utopic series:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in “linux” package in Ubuntu:
  Fix Released
Status in “systemd” package in Ubuntu:
  Fix Released

Bug description:
  CID: 201402-14663 Dell Latitude 12 Rugged Extreme

  The microphone mute key does not work on this system, so as its LED

  Steps:
  1. Install 14.04 + update (3.13.0-30), boot to desktop
  2. Try to mute the microphone with the hotkey (fn+F4)

  Expected results:
  * Mic mute key should work, its LED should be lit and the "Mute" option for 
input device should be ticked after you press the mic mute key.

  Actual result:
  * Nothing happened.

  Debugging information:
  ubuntu@201402-14663:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 248 press
  keycode 248 release
  keycode 248 press
  keycode 248 release
  keycode 248 press
  keycode 248 release
  keycode  29 press
  ^Ccaught signal 2, cleaning up...

  xev cannot detect any microphone mute key event

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1501 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1501 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Wed Jul  9 23:57:11 2014
  HibernationDevice: RESUME=UUID=b68f02ad-f5e4-4eb9-b88d-e85f60666734
  InstallationDate: Installed on 2014-07-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude 12 Rugged Extreme (7204)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed 
root=UUID=bdd00fe9-0df9-4b71-92c5-5f94c533f725 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0TH1GJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd05/12/2014:svnDellInc.:pnLatitude12RuggedExtreme(7204):pvr01:rvnDellInc.:rn0TH1GJ:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 12 Rugged Extreme (7204)
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1339998/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Shih-Yuan Lee]

https://askubuntu.com/questions/617513/bluetooth-not-connecting-to-
devices-even-though-it-recognizes-them also.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1454450

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_open+0xe1/0xa90 [bluetooth]
  [ 5579.876266]  [] hci_power_on+0x40/0x200 [bluetooth]
  [ 5579.876284] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd will 
not be loaded
  [ 5579.876286] Bluetooth: hc

[Kernel-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Shih-Yuan Lee]

http://askubuntu.com/questions/613614/bluetooth-not-working-in-
ubuntu-15-04 also mentioned this firmware.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1454450

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_open+0xe1/0xa90 [bluetooth]
  [ 5579.876266]  [] hci_power_on+0x40/0x200 [bluetooth]
  [ 5579.876284] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd will 
not be loaded
  [ 5579.876286] Bluetooth: hci0: BC

[Kernel-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Shih-Yuan Lee]

I noticed the following two lines.

[ 9442.157844] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd will not 
be loaded
[ 9442.157846] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-216f.hcd not 
found

Did you try the firmware as
https://wiki.archlinux.org/index.php/Dell_XPS_13_%282015%29#Bluetooth
mentioned.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1454450

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_

[Kernel-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Shih-Yuan Lee]

@cribari: What is the result?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1454450

Title:
  Bluetooth mouse laggy and erratic

Status in HWE Next Project:
  Triaged
Status in bluez package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_open+0xe1/0xa90 [bluetooth]
  [ 5579.876266]  [] hci_power_on+0x40/0x200 [bluetooth]
  [ 5579.876284] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd will 
not be loaded
  [ 5579.876286] Bluetoot

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

It seems the following commit in vivid is also needed for the better
support for trusty and utopic.

Author: Seth Forshee 
AuthorDate: Fri Mar 20 11:06:52 2015 -0500
Commit: Andy Whitcroft 
CommitDate: Fri Mar 27 10:44:38 2015 +

HID: multitouch: Add support for button type usage

According to [1], Windows Precision Touchpad devices must supply
a button type usage in the device capabilities feature report. A
value of 0 indicates that the device contains a depressible
button (i.e. it's a click-pad) whereas a value of 1 indicates
a non-depressible button. Add support for this usage and set
INPUT_PROP_BUTTONPAD on the touchpad input device whenever a
depressible button is present.

[1] https://msdn.microsoft.com/en-
us/library/windows/hardware/dn467314(v=vs.85).aspx

Signed-off-by: Seth Forshee 
Reviewed-by: Benjamin Tissoires 
Signed-off-by: Jiri Kosina 

(cherry picked from commit 2c6e0277e1eab3df5db81c59e408b7b1c14b1b72
 git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git)
Acked-by: Stefan Bader 
Acked-by: Chris J Arges 
Signed-off-by: Andy Whitcroft 

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

We found under some extreme system usage that comment #2 can fix the
problem.

Run some application/operation (e.g: Play youtube on background, launch
libreoffice for awhile (about 5-10min) or insert USB to copy some files
: The touchpad cursor were no function after some operation, sometime it
scrolling automatically or keep send press signal.

Without the patch of comment #2, when the issue occurred we also check
the touchpad event on ttyl1 by "evtest", we can found the event keeping
output without move cursor/click touchpad.

Our observation is the HiDPI platform may have more loading cause this
issue and sometimes its also cause xorg crash.

** Attachment added: "Screenshot from 2015-05-27 17_24_59.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456881/+attachment/4406011/+files/Screenshot%20from%202015-05-27%2017_24_59.png

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

Because the hardware has some problem that it will miss some packs of the 
touchpad events randomly.
It will cause some unpredictable results, but Seth's commit just avoid some 
situation that will cause the abnormal behavior under the condition of comment 
#4.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

Regarding comment #2, #4 & #8, our QA just still reproduce the problem by 
Seth's commit today.
Our QA can not reproduce the problem yesterday by using the same patch.
Sorry for any inconvenience.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

I have verified Linux kernel 3.16.0-39.53 and the right button works.

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

I have verified Linux kernel 3.13.0-54.91 but the right button doesn't work.
In fact, the touchpad doesn't work at all.

** Tags removed: verification-needed-trusty
** Tags added: verification-failed-trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

@Adam,

I mean Linux kernel 3.13 doesn't support the touchpad of Dell XPS 13 (2015) in 
I2C mode originally.
It may need more patches to make the touchpad in I2C mode work.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

The touchpad of Dell XPS 13 (2015) in I2C mode never works with trusty 3.13 
kernel.
However the touchpad of Dell XPS 13 (2015) in PS/2 mode does work with trusty 
3.13 kernel by default.
I need to use osi_acpi="Windows 2013" to make it function in I2C mode with 
trusty 3.13 kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

The touchpad of Dell XPS 13 (2015) in I2C mode doesn't work at all.
So there is no regression that I can tell.
It doesn't work worse.
It doesn't work better either.
Maybe it does work on some platform, however I don't know.

** Tags removed: verification-failed-trusty
** Tags added: verification-needed-trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

@kengyu:
There is no event for the touchpad of Dell XPS 13 (2015) in I2C mode with 
trusty-updates and trusty-proposed kernel.
No cursor, no left button, no right button, no tap, just nothing at all.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

@Adam,

It still doesn't work by 
http://kernel.ubuntu.com/~adamlee/lp1456881_all_patches/.
There is no event by evtest at all.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Shih-Yuan Lee]

synaptic-i2c-hid is created by AceLan.
I am not the original creator.
AceLan may know more details for it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1456881

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires 
  Tested-by: Jason Ekstrand 
  Signed-off-by: Jiri Kosina 

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1456881/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

There is a patch for 0x10ec2088 but it is not included in
https://github.com/torvalds/linux/blob/v3.19/sound/soc/codecs/rt286.c.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

No, there is some obscure BIOS/EC implementation that refuses  to enable
I2S audio mode for Linux kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

I saw 0x10ec2088 in the latest kernel tree of 
https://github.com/torvalds/linux/blob/master/sound/soc/codecs/rt286.c.
It should be included in the next v3.20 release.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1417363] Re: touchpad stops working after suspend/resume on XPS13 2015

[Shih-Yuan Lee]

I have verified Linux kernel 3.16.0-31-generic and it does fix this
issue.

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1417363

Title:
  touchpad stops working after suspend/resume on XPS13 2015

Status in HWE Next Project:
  Fix Released
Status in HWE Next utopic series:
  Fix Committed
Status in HWE Next vivid series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  The touchpad on XPS13 2015 would work in I2C mode with kernel 3.16+ and it 
would stop working after resume from suspend with an utopic kernel. This issue 
can be fixed by introducing two commits from upstream:
  109571c - HID: i2c-hid: call the hid driver's suspend and resume callbacks
  5b44c53 - HID: i2c-hid: Do not free buffers in i2c_hid_stop()

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1417363/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

** Tags removed: kernel-bug-exists-upstream-3.19-rc7
** Tags added: kernel-bug-exists-upstream-3.19

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

I just tested the mainline Linux kernel 3.19~rc7-vivid in Ubuntu 15.04
and the followings are the result.

$ dmesg -t | egrep "(audio|rt286|INT343)"
dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0

   
rt286 i2c-INT343A:00: Device with ID register 8802 is not rt286
sst-acpi INT3438:00: DesignWare DMA Controller, 8 channels
input: DLL0665:01 06CB:76AD UNKNOWN as 
/devices/pci:00/INT3433:00/i2c-1/i2c-DLL0665:01/0018:06CB:76AD.0001/input/input12
haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 
01, - version: 00.00, build 68, source commit id: 
445e02b38dd3ac603ab1ffdc4785fbe589bfde31
broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered
platform broadwell-audio: Driver broadwell-audio requests probe deferral
broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered
platform broadwell-audio: Driver broadwell-audio requests probe deferral
broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered
platform broadwell-audio: Driver broadwell-audio requests probe deferral
broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered
platform broadwell-audio: Driver broadwell-audio requests probe deferral
broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered
platform broadwell-audio: Driver broadwell-audio requests probe deferral
broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered
platform broadwell-audio: Driver broadwell-audio requests probe deferral
broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered
platform broadwell-audio: Driver broadwell-audio requests probe deferral

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chass

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

I also found the similar error message in the kern.log of comment #17.

rt286 i2c-INT343A:00: Device with ID register  is not rt286

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

After checking linux/sound/soc/codecs/rt286.c, the ID register must be
0x10ec0286.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

However it becomes worse.

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446/+attachment/4312902/+files/dmesg.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

I made a patch to skip checking ID register for v3.19-rc7.

** Patch added: "0001-ASoC-rt286-skip-checking-id-register-by-dmi.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446/+attachment/4312901/+files/0001-ASoC-rt286-skip-checking-id-register-by-dmi.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

@Sam,

I want to force the Linux kernel only to accept "Windows 8.1" probing.
https://www.kernel.org/doc/Documentation/kernel-parameters.txt

It seems the BIOS will probe "Windows 7" first and then "Windows 8.1" no matter 
if "Windows 7" is probed or not.
And Linux kernel will accept any OS probing if it is in the following table.
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/acpi/acpica/utosi.c#n87

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

I can see the following message when I installed "Windows 8.1" in the
system storage, and then booted Ubuntu vivid live system by the USB
stick.

rt286 i2c-INT343A:00: Device with ID register 10ec2088 is not rt286

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446/+attachment/4313642/+files/dmesg.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

However 0x10ec2088 is not supported by the Linux kernel v3.19-rc7.

https://github.com/torvalds/linux/blob/v3.19-rc7/sound/soc/codecs/rt286.c

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1413446] Re: Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

[Shih-Yuan Lee]

Yes, I hope it can be merged into v3.19.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1413446

Title:
  Audio broken on 2015 XPS 13 (9343) in I2S mode in Ubuntu 14.10/15.04

Status in Dell Sputnik:
  Confirmed
Status in HWE Next Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  (This is a public bug report for LP1402828.)

  This system has a dual-mode audio with an HDA and an I2S interface.
  Which shows up depends on the reported _OSI from the last cold boot.
  Since the kernels in Ubuntu 14.10/15.04 (15.04 uses 3.18 currently)
  report an _OSI of "Windows 2013", I2S mode is used for audio.

  A workaround is to pass acpi_os="!Windows 2013" as a kernel parameter,
  but this is non-optimal since the mode of the touchpad is affected. It
  also results in an alternate, less used and tested path in the
  firmware to be used.

  See the attached dmesg log for details on where the failure happens.
  Notably,

  $ dmesg -t | egrep "(audio|snd|INT3438)"
  dmar: ACPI device "INT3438:00" under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( -> 0002)
  snd_hda_intel :00:03.0: irq 50 for MSI/MSI-X
  haswell-pcm-audio haswell-pcm-audio: error: ADSP boot timeout
  broadwell-audio broadwell-audio: ASoC: CPU DAI System Pin not registered
  platform broadwell-audio: Driver broadwell-audio requests probe deferral

  There's also a failure to load the codec firmware after a
  suspend/resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 21 20:47:40 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (80 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (14 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1413446/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

[Shih-Yuan Lee]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625932

Title:
  Backlight does not change when adjust it higher than 50% after S3

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1625932/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1085684] CurrentDmesg.txt

[Shih-Yuan Lee]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1085684/+attachment/3765606/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1085684

Title:
  User namespace: missing

Status in “linux” package in Ubuntu:
  Confirmed
Status in “lxc” package in Debian:
  New

Bug description:
  root@HP-DL160G6:~# uname -a
  Linux HP-DL160G6 3.5.0-19-generic #30-Ubuntu SMP Tue Nov 13 17:48:01 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  root@HP-DL160G6:~# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.10
  DISTRIB_CODENAME=quantal
  DISTRIB_DESCRIPTION="Ubuntu 12.10"
  root@HP-DL160G6:~# lxc-checkconfig
  Kernel config /proc/config.gz not found, looking in other places...
  Found kernel config file /boot/config-3.5.0-19-generic
  --- Namespaces ---
  Namespaces: enabled
  Utsname namespace: enabled
  Ipc namespace: enabled
  Pid namespace: enabled
  User namespace: missing
  Network namespace: enabled
  Multiple /dev/pts instances: enabled

  --- Control groups ---
  Cgroup: enabled
  Cgroup clone_children flag: enabled
  Cgroup device: enabled
  Cgroup sched: enabled
  Cgroup cpu account: enabled
  Cgroup memory controller: enabled
  Cgroup cpuset: enabled

  --- Misc ---
  Veth pair device: enabled
  Macvlan: enabled
  Vlan: enabled
  File capabilities: enabled

  Note : Before booting a new kernel, you can check its configuration
  usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.5.0-19-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085684/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1085684] Re: User namespace: missing

[Shih-Yuan Lee]

ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sylee  2922 F pulseaudio
 /dev/snd/pcmC0D0p:   sylee  2922 F...m pulseaudio
DistroRelease: Ubuntu 13.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=78943c2e-a16a-4a72-9835-85187d8a6c02
InstallationDate: Installed on 2013-04-29 (101 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Apple Inc. iMac8,1
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=bbc59666-57af-47a9-bc9f-5ae520fbd4be ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-27-generic N/A
 linux-backports-modules-3.8.0-27-generic  N/A
 linux-firmware1.106
Tags:  raring
Uname: Linux 3.8.0-27-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
WifiSyslog:
 
dmi.bios.date: 02/09/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM81.88Z.00C1.B00.0802091538
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F226BEC8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F226BEC8
dmi.modalias: 
dmi:bvnAppleInc.:bvrIM81.88Z.00C1.B00.0802091538:bd02/09/08:svnAppleInc.:pniMac8,1:pvr1.0:rvnAppleInc.:rnMac-F226BEC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F226BEC8:
dmi.product.name: iMac8,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.


** Tags added: raring

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1085684

Title:
  User namespace: missing

Status in “linux” package in Ubuntu:
  Confirmed
Status in “lxc” package in Debian:
  New

Bug description:
  root@HP-DL160G6:~# uname -a
  Linux HP-DL160G6 3.5.0-19-generic #30-Ubuntu SMP Tue Nov 13 17:48:01 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  root@HP-DL160G6:~# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.10
  DISTRIB_CODENAME=quantal
  DISTRIB_DESCRIPTION="Ubuntu 12.10"
  root@HP-DL160G6:~# lxc-checkconfig
  Kernel config /proc/config.gz not found, looking in other places...
  Found kernel config file /boot/config-3.5.0-19-generic
  --- Namespaces ---
  Namespaces: enabled
  Utsname namespace: enabled
  Ipc namespace: enabled
  Pid namespace: enabled
  User namespace: missing
  Network namespace: enabled
  Multiple /dev/pts instances: enabled

  --- Control groups ---
  Cgroup: enabled
  Cgroup clone_children flag: enabled
  Cgroup device: enabled
  Cgroup sched: enabled
  Cgroup cpu account: enabled
  Cgroup memory controller: enabled
  Cgroup cpuset: enabled

  --- Misc ---
  Veth pair device: enabled
  Macvlan: enabled
  Vlan: enabled
  File capabilities: enabled

  Note : Before booting a new kernel, you can check its configuration
  usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.5.0-19-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085684/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1085684] AlsaInfo.txt

[Shih-Yuan Lee]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1085684/+attachment/3765603/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1085684

Title:
  User namespace: missing

Status in “linux” package in Ubuntu:
  Confirmed
Status in “lxc” package in Debian:
  New

Bug description:
  root@HP-DL160G6:~# uname -a
  Linux HP-DL160G6 3.5.0-19-generic #30-Ubuntu SMP Tue Nov 13 17:48:01 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  root@HP-DL160G6:~# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.10
  DISTRIB_CODENAME=quantal
  DISTRIB_DESCRIPTION="Ubuntu 12.10"
  root@HP-DL160G6:~# lxc-checkconfig
  Kernel config /proc/config.gz not found, looking in other places...
  Found kernel config file /boot/config-3.5.0-19-generic
  --- Namespaces ---
  Namespaces: enabled
  Utsname namespace: enabled
  Ipc namespace: enabled
  Pid namespace: enabled
  User namespace: missing
  Network namespace: enabled
  Multiple /dev/pts instances: enabled

  --- Control groups ---
  Cgroup: enabled
  Cgroup clone_children flag: enabled
  Cgroup device: enabled
  Cgroup sched: enabled
  Cgroup cpu account: enabled
  Cgroup memory controller: enabled
  Cgroup cpuset: enabled

  --- Misc ---
  Veth pair device: enabled
  Macvlan: enabled
  Vlan: enabled
  File capabilities: enabled

  Note : Before booting a new kernel, you can check its configuration
  usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.5.0-19-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085684/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1085684] BootDmesg.txt

[Shih-Yuan Lee]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1085684/+attachment/3765604/+files/BootDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1085684

Title:
  User namespace: missing

Status in “linux” package in Ubuntu:
  Confirmed
Status in “lxc” package in Debian:
  New

Bug description:
  root@HP-DL160G6:~# uname -a
  Linux HP-DL160G6 3.5.0-19-generic #30-Ubuntu SMP Tue Nov 13 17:48:01 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  root@HP-DL160G6:~# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.10
  DISTRIB_CODENAME=quantal
  DISTRIB_DESCRIPTION="Ubuntu 12.10"
  root@HP-DL160G6:~# lxc-checkconfig
  Kernel config /proc/config.gz not found, looking in other places...
  Found kernel config file /boot/config-3.5.0-19-generic
  --- Namespaces ---
  Namespaces: enabled
  Utsname namespace: enabled
  Ipc namespace: enabled
  Pid namespace: enabled
  User namespace: missing
  Network namespace: enabled
  Multiple /dev/pts instances: enabled

  --- Control groups ---
  Cgroup: enabled
  Cgroup clone_children flag: enabled
  Cgroup device: enabled
  Cgroup sched: enabled
  Cgroup cpu account: enabled
  Cgroup memory controller: enabled
  Cgroup cpuset: enabled

  --- Misc ---
  Veth pair device: enabled
  Macvlan: enabled
  Vlan: enabled
  File capabilities: enabled

  Note : Before booting a new kernel, you can check its configuration
  usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.5.0-19-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085684/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1085684] CRDA.txt

[Shih-Yuan Lee]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1085684/+attachment/3765605/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1085684

Title:
  User namespace: missing

Status in “linux” package in Ubuntu:
  Confirmed
Status in “lxc” package in Debian:
  New

Bug description:
  root@HP-DL160G6:~# uname -a
  Linux HP-DL160G6 3.5.0-19-generic #30-Ubuntu SMP Tue Nov 13 17:48:01 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux
  root@HP-DL160G6:~# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.10
  DISTRIB_CODENAME=quantal
  DISTRIB_DESCRIPTION="Ubuntu 12.10"
  root@HP-DL160G6:~# lxc-checkconfig
  Kernel config /proc/config.gz not found, looking in other places...
  Found kernel config file /boot/config-3.5.0-19-generic
  --- Namespaces ---
  Namespaces: enabled
  Utsname namespace: enabled
  Ipc namespace: enabled
  Pid namespace: enabled
  User namespace: missing
  Network namespace: enabled
  Multiple /dev/pts instances: enabled

  --- Control groups ---
  Cgroup: enabled
  Cgroup clone_children flag: enabled
  Cgroup device: enabled
  Cgroup sched: enabled
  Cgroup cpu account: enabled
  Cgroup memory controller: enabled
  Cgroup cpuset: enabled

  --- Misc ---
  Veth pair device: enabled
  Macvlan: enabled
  Vlan: enabled
  File capabilities: enabled

  Note : Before booting a new kernel, you can check its configuration
  usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig
  --- 
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.5.0-19-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085684/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] [NEW] Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

Public bug reported:

Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in linux package in Ubuntu:
  New

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

This issue also affects trusty.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Wily:
  New
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Tags added: trusty vivid wily

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Wily:
  New
Status in linux source package in Wily:
  Fix Committed

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Changed in: debian-installer (Ubuntu Wily)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Description changed:

+ [Impact]
+ 
+  * The users can not use netboot.iso to install Ubuntu on eMMC storage.
+ 
+ [Test Case]
+ 
+  * Download netboot.iso from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
+  * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
+  * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.
+ 
+ [Regression Potential]
+ 
+  * None
+ 
+ [Other Info]
+  
+  * None
+ 
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]
   
   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Description changed:

  [Impact]
  
-  * The users can not use netboot.iso to install Ubuntu on eMMC storage.
+  * The users can not use netboot.iso to install Ubuntu on eMMC storage.
  
  [Test Case]
  
-  * Download netboot.iso from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
-  * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
-  * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.
+  * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
+  * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
+  * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.
  
  [Regression Potential]
  
-  * None
+  * None
  
  [Other Info]
-  
-  * None
+ 
+  * None
  
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  New
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

** Also affects: oem-priority/wily
   Importance: Undecided
   Status: New

** Changed in: oem-priority/wily
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

This issue also needs to update the debian-installer in
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/ or we can not verify it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

Could you help to update the debian-installer netboot images, such as
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/vivid-netboot/mini.iso and
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/netboot/mini.iso so I can verify this issue?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Changed in: oem-priority/trusty
   Status: New => Fix Released

** Changed in: oem-priority/trusty
   Status: Fix Released => In Progress

** Changed in: oem-priority
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1475055] Re: The wireless on this machine (Dell XPS 13 9343) is constantly crashing

[Shih-Yuan Lee]

** Summary changed:

- The wireless on this machine (Dell XPS 15 9343) is constantly crashing
+ The wireless on this machine (Dell XPS 13 9343) is constantly crashing

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1475055

Title:
  The wireless on this machine (Dell XPS 13 9343) is constantly crashing

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  I've included a dmesg from after a point when the wireless is no
  longer working. Also, I experience frequent panics (caps lock
  blinking). I don't know if that is related since I haven't yet been
  able to get any information after such a crash. When it crashes that
  way, I generally have to power cycle the machine, let it boot to the
  dell logo, and then power cycle the machine again to get it to boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wt 1864 F pulseaudio
   /dev/snd/controlC0:  wt 1864 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 15 16:04:36 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  HibernationDevice: RESUME=UUID=25d5c49f-dec3-4600-906b-5942cd316c4e
  InstallationDate: Installed on 2015-04-29 (77 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=33afd237-d4ef-43f9-a375-d5693be6aaff ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-22-generic N/A
   linux-backports-modules-3.19.0-22-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (76 days ago)
  dmi.bios.date: 05/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1475055/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Tags removed: verification-done-vivid
** Tags added: verification-failed-vivid

** Tags added: verification-done-wily

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** No longer affects: debian-installer (Ubuntu Vivid)

** Tags removed: verification-failed-vivid vivid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

** Bug watch added: GNOME Bug Tracker #744278
   https://bugzilla.gnome.org/show_bug.cgi?id=744278

** Also affects: unity-settings-daemon via
   https://bugzilla.gnome.org/show_bug.cgi?id=744278
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381625

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Changed in: debian-installer (Ubuntu Trusty)
   Status: New => Fix Released

** Changed in: oem-priority/trusty
   Status: In Progress => Fix Released

** Changed in: debian-installer (Ubuntu Trusty)
   Status: Fix Released => Fix Committed

** Changed in: oem-priority/trusty
   Status: Fix Released => Fix Committed

** Changed in: oem-priority
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project trusty series:
  Fix Committed
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

** Changed in: oem-priority/trusty
   Status: Fix Committed => Fix Released

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

** Changed in: debian-installer (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

I didn't use any preseed config. I just download the mini.iso and make an 
installation USB stick by it.
Then I plug the USB stick into a laptop that only has an eMMC system storage 
inside to do the installation test manually.
During the installation, I will connect to Internet to download other udeb 
packages and this is the usual usage for mini.iso.

http://archive.ubuntu.com/ubuntu/dists/wily-proposed/main/installer-
amd64/current/images/netboot/mini.iso works and /proc/version_signature
shows "Ubuntu 4.2.0-16.19-generic 4.2.3".

http://archive.ubuntu.com/ubuntu/dists/vivid-proposed/main/installer-
amd64/current/images/netboot/mini.iso doesn't work and
/proc/version_signature shows "Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6".

http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/vivid-netboot/mini.iso works and
/proc/version_signature shows "Ubuntu 3.19.0-32.37~14.04.1-generic
3.19.8-ckt7".

http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/utopic-netboot/mini.iso doesn't work and
/proc/version_signature shows "Ubuntu 3.16.0-52.71~14.04.1-generic
3.16.7-ckt8".

http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-
amd64/current/images/netboot/mini.iso works and /proc/version_signature
shows "Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27".

It is expected that "Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27",
"Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7" and "Ubuntu
4.2.0-16.19-generic 4.2.3" work and "Ubuntu 3.19.0-30.33-generic
3.19.8-ckt6" doesn't work.

It is not expected that "Ubuntu 3.16.0-52.71~14.04.1-generic
3.16.7-ckt8" doesn't work but we don't maintain utopic now so it is
probably OK.

The only problem left now is that http://archive.ubuntu.com/ubuntu/dists
/vivid-proposed/main/installer-amd64/current/images/netboot/mini.iso is
not up to date.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1502772] Re: Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

[Shih-Yuan Lee]

http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-
amd64/current/images/vivid-netboot/mini.iso works and
/proc/version_signature shows "Ubuntu 3.19.0-32.37~14.04.1-generic
3.19.8-ckt7".

http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-
amd64/current/images/netboot/mini.iso works and /proc/version_signature
shows "Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27".

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1502772

Title:
  Linux kernel in Ubuntu doesn't provide mmc-modules udeb.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in OEM Priority Project wily series:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in debian-installer source package in Trusty:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in debian-installer source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Released
Status in debian-installer source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * The users can not use netboot.iso to install Ubuntu on eMMC
  storage.

  [Test Case]

   * Download netboot.iso of trusty/utopic/vivid from 
http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/
   * Use netboot.iso to burn an installation CD/DVD or make an installation USB 
stick.
   * Use this installation media on a platform with eMMC storage to install 
Ubuntu system.

  [Regression Potential]

   * None

  [Other Info]

   * None

  Linux kernel in Ubuntu doesn't provide mmc-modules udeb like 
https://packages.debian.org/unstable/mmc-modules-4.2.0-1-amd64-di in Debian.
  So it makes us unable to install the Ubuntu system into eMMC storage via 
netboot, aka 
http://archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/current/images/netboot/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1502772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

Since Linux kernel v3.18-rc1, it contains

commit e6755fb78e8f20ecadf2a4080084121336624ad9
Author: Jani Nikula 
Date:   Tue Aug 12 17:11:42 2014 +0300

drm/i915: switch off backlight for backlight class 0 brightness

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381625

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

This bug probably targets on how to avoid this driver behavior's change.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381625

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

Reverting that commit can easily fix this issue or we need to fix all
userspace programs related to the brightness control.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1381625

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060914] Re: kernel NULL pointer dereference in ipu6 driver

[Shih-Yuan Lee]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060914

Title:
  kernel NULL pointer dereference in ipu6 driver

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  pr 11 14:43:43 OCBYM2-DVT1-C3 kernel: BUG: kernel NULL pointer dereference, 
address: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: supervisor read access in kernel 
mode
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: error_code(0x) - not-present 
page
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PGD 0 P4D 0 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Oops:  [#1] PREEMPT SMP NOPTI
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CPU: 16 PID: 568 Comm: (udev-worker) 
Tainted: G   O   6.8.0-22-generic #22-Ubuntu
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Hardware name: Dell Inc. Precision 
5490/, BIOS 1.1.0 02/07/2024
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RIP: 0010:__wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Code: 55 48 89 e5 41 57 41 56 41 55 41 
54 53 48 89 fb 48 83 c3 08 48 83 ec 08 48 8b 47 08 89 75 d4 89 55 d0 48 39 c3 
74 51 4d 89 c7 <4c> 8b 00 41 89 ce 48 8d 78 e8 4d 8d 68 e8 eb 25 74 0c 41 83 e4 
01
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RSP: 0018:b5ebc3063768 EFLAGS: 
00010086
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RAX:  RBX: 
8fb79e181d50 RCX: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RDX:  RSI: 
0003 RDI: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RBP: b5ebc3063798 R08: 
 R09: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R10:  R11: 
 R12: 8fb79e181d48
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R13: 0003 R14: 
0246 R15: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: FS:  77cceb6148c0() 
GS:8fc6cf60() knlGS:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CR2:  CR3: 
0001068ae003 CR4: 00f70ef0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR0:  DR1: 
 DR2: 
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR3:  DR6: 
07f0 DR7: 0400
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PKRU: 5554
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Call Trace:
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? show_regs+0x6d/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __die+0x24/0x80
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? page_fault_oops+0x99/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? do_user_addr_fault+0x2ee/0x6b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? exc_page_fault+0x83/0x1b0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? asm_exc_page_fault+0x27/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __wake_up_common+0x2f/0xb0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __wake_up+0x37/0x70
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __vb2_queue_cancel+0xcd/0x300 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_core_queue_release+0x23/0x70 
[videobuf2_common]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  vb2_queue_release+0xe/0x20 
[videobuf2_v4l2]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_queue_cleanup+0x12/0x20 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_isys_video_cleanup+0x2e/0x40 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  
ipu_isys_csi2_be_soc_cleanup+0x37/0x50 [intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_unregister_subdevices+0x40/0xa0 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_probe+0x5c5/0xb80 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? kernfs_create_link+0x66/0xe0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_probe+0x72/0x130 [intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  really_probe+0x1c4/0x410
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_probe_device+0x8c/0x180
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_probe_device+0x24/0xd0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  __driver_attach+0x10b/0x210
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx___driver_attach+0x10/0x10
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_for_each_dev+0x8a/0xf0
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_attach+0x1e/0x30
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  bus_add_driver+0x156/0x260
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  driver_register+0x5e/0x130
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ? __pfx_isys_driver_init+0x10/0x10 
[intel_ipu6_isys]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  ipu_bus_register_driver+0x16/0x20 
[intel_ipu6]
  Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel:  isys_driver_init+0x1

[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently

[Shih-Yuan Lee]

** Changed in: oem-somerville-tentacool-meta (Ubuntu Jammy)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2007875

Title:
  Ubuntu 22.04 XPS 13 plus 9320  kernel 6.0 OEM and 5.19 breaks wifi
  frequently

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in oem-somerville-tentacool-meta package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Jammy:
  Invalid
Status in linux-firmware source package in Kinetic:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Kinetic:
  Invalid
Status in linux-firmware source package in Lunar:
  Fix Released
Status in oem-somerville-tentacool-meta source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and
  -73 firmware are supported bug missing. On one user reported issue,
  this fixes WiFi stability on 5G band.

  [Fix]

  New upstreamed firmware revision fixes this issue.

  [Test Case]

  1. Boot hwe-5.19 kernel
  2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded
  3. Browse the web, usually takes between 1 and 5 minutes
  4. Networking will cut out

  [Where problems could occur]

  This affects only users need both backport-iwlwifi-dkms and hwe-5.19
  kernel on WiFi stability.

  [Other Info]

  While Kinetic and above have them all, only Jammy is nominated.

  == original bug report ==

  I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320).
  Recently I received some kernel updates, the 5.19 kernel used in 22.10
  and a 6.0 oem kernel. Both updates break wifi. It seems to only do so
  on newer 5.7 GHz access points.

  1. Boot latest 6.0 oem kernel
  2. Browse the web, usually takes between 1 and 5 minutes.
  3. Networking will cut out.

  Disabling networking and starting again will fix it until it happens
  again in a few minutes. This will repeat indefinitely, essentially
  making wireless useless.

  The attached dmesg log reliably shows up when it fails, showing
  iwlwifi failing and a (network?) hardware reset request.

  It witnessed this happen months ago on 22.10, which led me to using
  the Dell stock 22.04 image. But it seems even the newer OEM kernel is
  affected.

  A workaround is to select the older 5.15 kernel in grub. I find on
  this laptop, one must hit escape precisely 1 second after seeing the
  Dell logo on boot. Alternatively one could edit /etc/grub/default and
  set a longer timeout.

  Let me know if this bug report would be better to go to Dell as a
  support request instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-osp1 in Ubuntu.
https://bugs.launchpad.net/bugs/1857409

Title:
  alsa/sof: load different firmware on different platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware)
  on all platforms, but mainline kernel already supported the multi
  firmwares on differnt platforms, and OEM project needs us to
  support the mutli-firmware names in the ubuntu kernel

  [Fix]
  cherry-pick 3 upstream patches, then on cnl platforms, it will
  load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl
  platforms, it will load sof-cfl.ri

  
  [Test Case]
  Prepare the firmware from https://github.com/thesofproject/linux-firmware
  master branch, then boot the kernel with these patches.

  [Regression Risk]
  Low, just let different platforms load differnt firmware, and these
  patches are in the upstream kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1857409/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849947

Title:
  Dell XPS 13 (7390) Display Flickering - 19.10

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  Hi there,
  I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to 
replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, 
there is one issue which occurs frequently whereby the display flickers and 
becomes unusable. The best way to describe the appearance is that the image 
becomes heavily distorted. 

  Sometimes it only happens for a split second, other times it is
  permanently distorted. When this happens, simply closing the laptop
  lip and re-opening seems to put the display back into it's correct
  state.

  I didn't experience this issue on 18.04 LTS which is why I believe
  it's a Software Bug within 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 11:11:43 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2019-10-25 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0G2D0W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1849947/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1875254] Re: Intermittent display blackouts on event

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-osp1 in Ubuntu.
https://bugs.launchpad.net/bugs/1875254

Title:
  Intermittent display blackouts on event

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [Impact]
  When audio device enters runpm D3(idle for 7 seconds) and then wakes it up to 
make a sound, it flicks the screen.
  This behavior could be observed while plug/remove AC cable or USB disk, or 
open a terminal and press backsapce key.

  [Fix]
  This issue could be fixed by this commit, it fixes the flicker during 
boot-time, but it also fixes the flicker during rumtime wakeup.
  1ee48a61aa57 drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK only

  Audio drivers communicate with i915 over HDA bus multiple times during system 
boot-up and each of these transactions result in matching
  get_power/put_power calls to i915, and depending on the platform,
  a modeset change causing visible flicker.
  
  GLK is the only platform with minimum CDCLK significantly lower
  than BCLK, and thus for GLK setting a higher CDCLK is mandatory.

  For other platforms, minimum CDCLK is close but below 2*BCLK
  (e.g. on ICL, CDCLK=176.4kHz with BCLK=96kHz). Spec-wise the constraint
  should be set, but in practise no communication errors have been
  reported and the downside if set is the flicker observed at boot-time.

  [Test]
  Verified on Dell XPS 13 9300

  [Regression Potential]
  Low, it fixes below commit which contains in ubuntu kernel and should have 
been applied on ubuntu kernel, too.
  Fixes: f6ec9483091f ("drm/i915: extend audio CDCLK>=2*BCLK constraint to more 
platforms")

  =

  Issues with the screen going black for a second on certain events on a dell 
XPS 9370 2 in 1, especially when on battery.
  Seems to be a known bug in arch 
(https://wiki.archlinux.org/index.php/Dell_XPS_13_2-in-1_(7390)).
  Last 5.6.7 kernel tested and the issues has disappears but pb with sound card.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lucie  2232 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=056fd229-d014-4b3b-a581-1b646105d1ed ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1875254/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

linux/5.15.0-28.29 kernel in jammy-proposed has the kernel panic on Dell
Latitude 9420.

** Tags removed: verification-done-jammy
** Tags added: verification-failed-jammy

** Attachment added: "PXL_20220429_040458788.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5584835/+files/PXL_20220429_040458788.jpg

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  Upgra

[Kernel-packages] [Bug 1956426] Re: MIssing firmware for Intel Visual Sensing Controller

[Shih-Yuan Lee]

** Tags added: oem-priority originate-from-1949435 somerville

** Changed in: oem-priority
   Status: New => Fix Committed

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1956426

Title:
  MIssing firmware for Intel Visual Sensing Controller

Status in OEM Priority Project:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Need firmware blob for Intel Visual Sensing Controller for IPU6 cameras on
  Intel Alder Lake platforms.

  [Fix]

  Two commits from upstream repo https://github.com/intel/ivsc-firmware main
  branch. While Intel has no plan to upstream their IPU6 driver before
  kernel camera API is out, the firmware blobs will probably stay where they
  are until the plan changed.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  This is a follow-up for bug 1955383, which at the time being SRU-ed, Intel
  has not yet published these ivsc fw for redistribution.

  Focal is nomiated to support oem-5.14 kernel.

  == original bug report ==

  This is a followup for bug 1955383 that ivsc firmware was not publicly
  released at the time submitting other Intel IPU6 works for Alder Lake
  platform. They're now available in https://github.com/intel/ivsc-
  firmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1956426/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1938531] Re: support signed v4l2loopback dkms build

[Shih-Yuan Lee]

** Tags added: oem-priority originate-from-1949435 somerville

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1938531

Title:
  support signed v4l2loopback dkms build

Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  v4l2loopback is used as a critical role on Intel IPU6 camera platforms,
  which takes userspace middleware involvements to correctly configure
  hardware sensors. While all the legacy camera applications are not yet
  learned how to support libcamera, v4l2loopback and a v4l2-relayd step in
  as a video streaming proxy for backward compatibility.

  To preinstall v4l2loopback kernel module on secureboot systems, signed
  modules should be used.

  [Fix]

  All Ubuntu specific changes to enable signed v4l2loopback dkms builds.

  [Test Case]

  Install signed modules package and check `modinfo v4l2loopback`.

  [Where problems could occur]

  N/A.

  [Other Info]

  This adds current revision of v4l2loopback in the ubuntu archive. While
  some other fixes are also needed for v4l2loopback/focal, expects version
  bumps recently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938531/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Incomplete
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

I confirmed that linux-oem-20.04d 5.14.0.1015.15 in focal-proposed can
make the MIPI camera workable.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Incomplete
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svn

[Kernel-packages] [Bug 1956426] Re: MIssing firmware for Intel Visual Sensing Controller

[Shih-Yuan Lee]

I have checked linux-firmware 1.187.25 in focal-proposed and it can
enable the MIPI camera on the laptop.

** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1956426

Title:
  MIssing firmware for Intel Visual Sensing Controller

Status in OEM Priority Project:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Need firmware blob for Intel Visual Sensing Controller for IPU6 cameras on
  Intel Alder Lake platforms.

  [Fix]

  Two commits from upstream repo https://github.com/intel/ivsc-firmware main
  branch. While Intel has no plan to upstream their IPU6 driver before
  kernel camera API is out, the firmware blobs will probably stay where they
  are until the plan changed.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  This is a follow-up for bug 1955383, which at the time being SRU-ed, Intel
  has not yet published these ivsc fw for redistribution.

  Focal is nomiated to support oem-5.14 kernel.

  == original bug report ==

  This is a followup for bug 1955383 that ivsc firmware was not publicly
  released at the time submitting other Intel IPU6 works for Alder Lake
  platform. They're now available in https://github.com/intel/ivsc-
  firmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1956426/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955689] Re: Add Bluetooth support for Qualcomm WCN6856

[Shih-Yuan Lee]

** Tags added: oem-priority originate-from-1939648 sutton

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1955689

Title:
  Add Bluetooth support for Qualcomm WCN6856

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Confirmed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  WCN6856 Bluetooth doesn't work.

  [Fix]
  Backport firmware blobs and driver support to make it work by loading
  correct firmwares.
   
  [Test]
  Bluetooth scanning and pairing work, and continue to do so after several
  suspend/resume cycles.

  [Where problems could occur]
  The upstream version of btusb_generate_qca_nvm_name() adds several
  missing le*_to_cpu() macros, so if this device was ever used on a Big
  Endian system, this is a behavioral change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955689/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms

[Shih-Yuan Lee]

@Shengyao,

Please check LP: #1955689 instead.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1955383

Title:
  Support Intel IPU6 MIPI camera on Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Incomplete
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  == kernel driver SRU ==

  [SRU Justification]

  [Impact]

  To support Intel IPU6 MIPI camera on Alder Lake platforms.

  [Fix]

  Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has
  been addressed by bug 1921345 and 1939539. They are backported from
  https://github.com/intel/ipu6-drivers.

  Further works to enable IPU6 camera on Alder Lake platforms depend on a
  few more fixes from same ipu6-drivers repository, as well as an extra
  https://github.com/intel/ivsc-driver for Intel Vision Sensing
  Controller(IVSC).

  [Test Case]

  This depends on an integral of enablement components inclusive of the
  kernel drivers that are being proposed, firmware, updates for the
  userspace camera hardware abstration layer library and a gstreamer
  element as what we have for Tiger Lake platforms.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  [Other Info]

  Jammy is planned, but yet the support for 5.15 kernel is not yet started
  from Intel side.

  == linux-firmware SRU ==

  [SRU Justification]

  [Impact]

  Intel IPU6 MIPI camera on Alder Lake platform takes a different fw
  blob.

  [Fix]

  While Intel has no intention to upstream IPU6 driver before kernel
  camera is out, it's available in
  https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its
  main branch.

  [Test Case]

  This would take both kernel and firmware fixes, as well as updates for
  the userspace middleware, gstreamer element plugin, to enable the device.
  With all of them in position, one should be able to browse camera with
  legacy camera apps like cheese.

  [Where problems could occur]

  It's confirmed Intel IPU6 MIPI camera doesn't support suspend at
  streaming.

  == original bug report ==

  This depends on following componenets:
  * ipu6ep firmware in 
https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d
  * Intel VSC fw version 1.2.3.439 (not yet available publicly)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 9320
  Package: linux-firmware 1.187.23+staging.38 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.23+staging.38
  Tags: third-party-packages focal
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 0.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.2.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3:
  dmi.product.family: XPS
  dmi.product.name: XPS 9320
  dmi.

[Kernel-packages] [Bug 1983574] [NEW] /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

[Shih-Yuan Lee]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
$ lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
$ apt-cache policy linux-image-5.15.0-43-generic
linux-image-5.15.0-43-generic:
  Installed: 5.15.0-43.46~20.04.1
  Candidate: 5.15.0-43.46~20.04.1
  Version table:
 *** 5.15.0-43.46~20.04.1 500
500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status

3) What you expected to happen
/sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

4) What happened instead
/sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-09-22 (1047 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
Tags:  focal
Uname: Linux 5.15.0-43-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
_MarkForUpload: True

** Affects: linux-hwe-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-collected focal

** Tags added: apport-collected

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.
  
  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-09-22 (1047 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
+ Tags:  focal
+ Uname: Linux 5.15.0-43-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
+ _MarkForUpload: True

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1983574

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.

[Kernel-packages] [Bug 1983574] ProcCpuinfoMinimal.txt

[Shih-Yuan Lee]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1983574/+attachment/5607009/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1983574

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983574/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1983574] Dependencies.txt

[Shih-Yuan Lee]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1983574/+attachment/5607008/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1983574

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983574/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1983574] ProcEnviron.txt

[Shih-Yuan Lee]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1983574/+attachment/5607010/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1983574

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983574/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1983574] Re: /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

[Shih-Yuan Lee]

base_frequency will only exist if the HWP feature is enabled in the
processor, i.e there is a 'hwp' in the flags of /proc/cpuinfo.

Refer to https://www.kernel.org/doc/html/v5.0/admin-
guide/pm/intel_pstate.html

** Changed in: linux-hwe-5.15 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1983574

Title:
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency is missing for
  Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz

Status in linux-hwe-5.15 package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy linux-image-5.15.0-43-generic
  linux-image-5.15.0-43-generic:
Installed: 5.15.0-43.46~20.04.1
Candidate: 5.15.0-43.46~20.04.1
Version table:
   *** 5.15.0-43.46~20.04.1 500
  500 http://mirror01.idc.hinet.net/ubuntu focal-updates/main amd64 
Packages
  500 http://mirror01.idc.hinet.net/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency should exist.

  4) What happened instead
  /sys/devices/system/cpu/cpufreq/policy0/base_frequency doesn't exist.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-22 (1047 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Tags:  focal
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (836 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd microk8s plugdev 
sambashare sbuild sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983574/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive

[Shih-Yuan Lee]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1998154

Title:
  dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under
  universe archive

Status in OEM Priority Project:
  New
Status in dkms package in Ubuntu:
  New

Bug description:
  [Description]

  The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in
  universe archive.

  https://packages.ubuntu.com/search?keywords=gcc-12
  gcc-12 is under main for kinect, and the patches are cherry-picked from 
kinect/stable, I suppose it is a mistake for jammy in universe.

  [debian/changelog]

  dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium

  Cherry-pick patches from kinetic/stable to address building dkms
  modules correctly for HWE kernels (LP: #1991664):

  Fix dkms-autopkgtest when a given dkms package is built into the
  kernel already of the same version. (i.e. zfs-linux on Ubuntu).

  Use exact compiler for dkms as used to build the kernel, when
  possible.

  Depend on gcc-12 to build modules for HWE kernels correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998154/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1935892] Re: OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not and cause no nvidia driver after oem kernel transition

[Shih-Yuan Lee]

linux-modules-nvidia-460-oem-20.04 needs to become a dummy transitional package 
of linux-modules-nvidia-460-oem-20.04b.
Just like linux-oem-20.04 has become a dummy transitional package of 
linux-oem-20.04b.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-oem-5.6 in
Ubuntu.
https://bugs.launchpad.net/bugs/1935892

Title:
  OEM 5.6 kernel is now transited to 5.10 but pre-signed nvidia is not
  and cause no nvidia driver after oem kernel transition

Status in OEM Priority Project:
  New
Status in linux-restricted-modules-oem-5.6 package in Ubuntu:
  New

Bug description:
  If end user install nvidia driver using 20.04.2 stock image without
  connecting network and they will get the 5.6 oem kernel + 5.6 nvidia
  driver (linux-modules-nvidia-*).

  After the installation, the user will get 5.10 kernel + nvidia pre-
  signed 5.6 driver after dist-upgrade.

  It will cause there is no nvidia driver in the system.

  Below shows the candidates packages:

  # apt policy linux-oem-20.04
  linux-oem-20.04:
    Installed: (none)
    Candidate: 5.10.0.1034.35
    Version table:
   5.10.0.1034.35 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
   5.10.0.1033.34 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   5.6.0.1007.7 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  # apt policy linux-modules-nvidia-460-oem-20.04
  linux-modules-nvidia-460-oem-20.04:
    Installed: (none)
    Candidate: 5.6.0-1056.60
    Version table:
   5.6.0-1056.60 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1935892/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

[Shih-Yuan Lee]

I saw oem-stella.cmit-meowth-meta 20.04ubuntu11 in 
http://hp.archive.canonical.com/dists/focal/stella.cmit/binary-amd64/Packages 
depends on oem-fix-gfx-nvidia-1868199, but I can not find 
oem-fix-gfx-nvidia-1868199 on http://hp.archive.canonical.com/pool/public/o/. 
So the dependencies of oem-stella.cmit-meowth-meta in OEM archive is broken.

Have we checked the installation without Internet? Will it still fail?

** Also affects: oem-priority
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1914374

Title:
  Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

Status in OEM Priority Project:
  New
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubiquity source package in Focal:
  Invalid
Status in ubuntu-drivers-common source package in Focal:
  In Progress
Status in ubiquity source package in Groovy:
  Invalid
Status in ubuntu-drivers-common source package in Groovy:
  New

Bug description:
  I've installed the focal-desktop-amd64.iso image with SHA-256 sum
  b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
  http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
  15 G7 laptop (CID 202009-28216).

  There are multiple issues:

  * The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
  * The screen resolution is 3840x2160 but there is no scaling, so everything 
is tiny.
  * The touchpad does not work.
  * WLAN does not work.
  * Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
  * No sound.

  $ cat /proc/version_signature
  Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

  $ lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1914374/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2002763] Re: Missing how to uninstall (back to generic kernel) in OEMKernel wiki

[Shih-Yuan Lee]

Dell Precision 5560 is managed by oem-somerville-pidgey-meta.
Dell XPS 13 9310 is managed by oem-somerville-bulbasaur-meta.

You can simply purge those Debian packages and then reboot the system to use 
the generic kernel.
`sudo apt-get purge oem-somerville-pidgey-meta` or `sudo apt-get purge 
oem-somerville-bulbasaur-meta`.

** Changed in: linux-oem-5.10 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/2002763

Title:
  Missing how to uninstall (back to generic kernel) in OEMKernel wiki

Status in linux-oem-5.10 package in Ubuntu:
  Invalid

Bug description:
  In OEMKernel wiki(https://wiki.ubuntu.com/Kernel/OEMKernel), How to install 
is documented, but how to uninstall OEMKernel or back to the generic kernel?
  It's not documented.

  Maybe that's why this issue is fired:
  https://ubuntuforums.org/showthread.php?t=2470860

  And I also take almost harf an hour to search and still cannot find
  how to back to the generic kernel.

  Here is my case:
  Confirmed with HighPoint just now, their Linux driver cann't support OEM 
Kernel currently. So I want to back to the generic kernel. But how? shoudn't be 
documented in Wiki?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/2002763/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp