This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1739939

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
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/1739939

Title:
  Update Ubuntu-4.15.0 config to support Intel Atom devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the mainline kernel was patched with 'serdev: Add ACPI support'
  (commit 53c7626356c7584e82510d86394a6dcd80525614) and 'serdev: enable
  TTY port controller support by default' (commit
  22b276a4072087e7b7f1723ccd8a1aa18fab8bbf) and 'Bluetooth: hci_bcm: Add
  serdev support' (commit 33cd149e767be9afbab9fcd3d5165a2de62313c8) the
  mainline kernel the config needs CONFIG_SERIAL_DEV_BUS=m changing to
  CONFIG_SERIAL_DEV_BUS=y and CONFIG_BT_HCIUART_BCM=y to keep sound and
  BT working on Intel Atom devices.

  Currently the latest Ubuntu config for 4.15 (see 0006-configs-based-
  on-Ubuntu-4.15.0-2.3.patch) still only has CONFIG_SERIAL_DEV_BUS=m

  The config needs to be update to take into consideration the
  implications of the aforementioned patches together with the settings
  identified.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739939/+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

Reply via email to