[Kernel-packages] [Bug 227359] Re: suddenly keyboard event recognition gets really slow after multiple suspend/resumes

[Alvin P. Schmitt]

I am a semi-newbie. I get the problem of keys being echoed to the screen
many seconds after I type them. I am running on a 32 bit machine at 2.6
GHz processor and 4 GB ram. This is with Ubuntu 16.04 and with all the
updates as of 3/30/2017. This is a real problem and is not related to
any of the so called solutions I see posted. I set swappiness = 10 .
Has anyone found a real solution to 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/227359

Title:
  suddenly keyboard event recognition gets really slow after multiple
  suspend/resumes

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xorg

  If I use Xorg for some time (I mean over suspend & resumes, after
  several hours), suddenly the keyboard gets unusable.

  I.e. I have to press a key for 2 seconds or more to get an keyboard
  event under Xorg - and then it is duplicated. But if I press it less
  then 2 seconds, then I don't get any event at all.

  The problem shows with Kde unter Xorg with Hardy. Under Gutsy I had
  the same problem. The problem occurs both with the internal and an
  external usb keyboard.

  As workaround I log out (via mouse which works fine) - and restart the
  X-Server. The new X-Server works fine then for some time, until the
  problem occurs again.

  I have no problems with keys which are 'stuck' or something like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/227359/+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 1677697] Re: linux: 4.10.0-16.18 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

Title:
  linux: 4.10.0-16.18 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-16.18 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1677697/+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 1645521] Re: [Feature] ISH (Intel Sensor Hub) support

[quanxian]

right. thanks

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

Title:
  [Feature] ISH (Intel Sensor Hub) support

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Integrete ISH kernel driver and ISH driver should provoide following 
interface to user
  (1) Batch ModeGet the hardware batch buffer size/count,Set the batch 
timeout value
  (2) Wakeup/non-wakeupchecking if one sensor is wakeup instance or 
non-wakeup instance.For wakeup instance, when batch buffer is full or wait 
timeout, system must be woken up and receive batched sensor events.
  (3) Timestamp  expose the sensor event timestamp to user space for sync
  (4) physical sensors-support exposing following physical 
sensors:Accelerometer,Gyroscope,Magnetic,Field,Pressure,Light,Proximity
  (5) Advanced sensorsupport exposing following advanced sensors:
  Gravity,Linear Acceleration,Rotation Vector,Orientation,Game 
Rotation,Geomagentic Rotation,Step Detector,Step Counter,Terminal,Significant 
motion,Wakeup Gesture,Glance Gesture,Tilt,PanZoon,Lift and Look
  (6)multiple sensor instance support
  (7)private command support  support set/get path for private command set 
and response get, because some advanced sensor needs different special command 
to work properly.
  (8)User defined sensor support--- exposing non-pre-defined sensors.
  Because customer may add a new sensor in firmware, and hope sensor driver can 
expose it as a unknown sensor automatically, then application can use it 
directly without any code change.

  HW: Broxton-p

  Upstream Schedule:
  Basic Sensor Driver: 4.9
  Advanced Sensor Driver: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645521/+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 1645521] Re: [Feature] ISH (Intel Sensor Hub) support

[Robert Hooker]

yeah only the linux task for 17.04 is closed, zesty kernel features are
now done and the rest will have to go into 17.10

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

Title:
  [Feature] ISH (Intel Sensor Hub) support

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Integrete ISH kernel driver and ISH driver should provoide following 
interface to user
  (1) Batch ModeGet the hardware batch buffer size/count,Set the batch 
timeout value
  (2) Wakeup/non-wakeupchecking if one sensor is wakeup instance or 
non-wakeup instance.For wakeup instance, when batch buffer is full or wait 
timeout, system must be woken up and receive batched sensor events.
  (3) Timestamp  expose the sensor event timestamp to user space for sync
  (4) physical sensors-support exposing following physical 
sensors:Accelerometer,Gyroscope,Magnetic,Field,Pressure,Light,Proximity
  (5) Advanced sensorsupport exposing following advanced sensors:
  Gravity,Linear Acceleration,Rotation Vector,Orientation,Game 
Rotation,Geomagentic Rotation,Step Detector,Step Counter,Terminal,Significant 
motion,Wakeup Gesture,Glance Gesture,Tilt,PanZoon,Lift and Look
  (6)multiple sensor instance support
  (7)private command support  support set/get path for private command set 
and response get, because some advanced sensor needs different special command 
to work properly.
  (8)User defined sensor support--- exposing non-pre-defined sensors.
  Because customer may add a new sensor in firmware, and hope sensor driver can 
expose it as a unknown sensor automatically, then application can use it 
directly without any code change.

  HW: Broxton-p

  Upstream Schedule:
  Basic Sensor Driver: 4.9
  Advanced Sensor Driver: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645521/+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 1677959] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1677959

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

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

** Changed in: linux (Ubuntu Yakkety)
   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/1677959

Title:
  change_profile incorrect when using namespaces with a compound stack

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete
Status in linux source package in Zesty:
  Incomplete

Bug description:
  When a compound label is used as part of a target namespace the change
  profile will result in a bad change

  a task confined by profile lxd doing
  change_profile(&:ns://foo//)

  results in a change_profile to

:ns://foo
  and
unconfined

  causing the local system profile to change instead of setting up a stack in 
the sub namespace
  ie.
unconfined//&:ns://foo
  instead of the expected
lxd//&:ns://foo//&:ns://unconfined

  https://github.com/lxc/lxd/issues/2981

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1677959/+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 1645187] Re: 4.4.0-47-generic dm_snapshot random deadlock

[john]

changelog only shows :

linux (4.4.0-71.92) xenial; urgency=low

  * CVE-2017-7184
- xfrm_user: validate XFRM_MSG_NEWAE XFRMA_REPLAY_ESN_VAL replay_window
- xfrm_user: validate XFRM_MSG_NEWAE incoming ESN size harder

 -- Thadeu Lima de Souza Cascardo   Fri, 24 Mar
2017 09:32:49 -0300

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7184

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

Title:
  4.4.0-47-generic dm_snapshot random deadlock

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Server's load become high with tasks in D state, no choice but to reboot the 
system.
  Could be related to the following ? :

  https://bugzilla.kernel.org/show_bug.cgi?id=119841
  https://www.redhat.com/archives/dm-devel/2016-June/msg00399.html
  https://patchwork.kernel.org/patch/9223697/
  https://xen.crc.id.au/bugs/view.php?id=75

  ii  xen-hypervisor-4.4-amd64 4.4.2-0ubuntu0.14.04.7
amd64Xen Hypervisor on AMD64
  ii  linux-image-extra-4.4.0-47-generic   4.4.0-47.68~14.04.1   
amd64Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
  ii  linux-image-4.4.0-47-generic 4.4.0-47.68~14.04.1   
amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP

  kernel messages:
  
  [890070.994700] INFO: task blkback.3.xvda2:5756 blocked for more than 120 
seconds.
  [890070.994758]   Not tainted 4.4.0-47-generic #68~14.04.1-Ubuntu 
  [890070.994806] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [890070.994884] blkback.3.xvda2 D 8800b7ff3928 0  5756  2 
0x
  [890070.994890]  8800b7ff3928 81e13500 8800b6a4be80 
8800b7ff4000
  [890070.994895]  88013a83cc18 88013a83cc00  
fffe0001
  [890070.994898]  8800b7ff3940 817fafc5 8800b6a4be80 
8800b7ff39c0
  [890070.994902] Call Trace:
  [890070.994912]  [] schedule+0x35/0x80
  [890070.994917]  [] rwsem_down_write_failed+0x1da/0x320
  [890070.994923]  [] ? push+0x47/0x50
  [890070.994927]  [] ? dm_kcopyd_copy+0x147/0x1f0
  [890070.994931]  [] call_rwsem_down_write_failed+0x13/0x20
  [890070.994933]  [] ? down_write+0x2d/0x40
  [890070.994939]  [] __origin_write+0x6e/0x210 [dm_snapshot]
  [890070.994944]  [] ? mempool_alloc_slab+0x15/0x20
  [890070.994946]  [] ? mempool_alloc+0x5f/0x150
  [890070.994949]  [] do_origin.isra.14+0x67/0x90 
[dm_snapshot]
  [890070.994952]  [] origin_map+0x62/0x80 [dm_snapshot]
  [890070.994955]  [] __map_bio+0x3a/0x110
  [890070.994957]  [] __split_and_process_bio+0x240/0x3c0
  [890070.994960]  [] dm_make_request+0x6a/0xd0
  [890070.994964]  [] generic_make_request+0xe1/0x1a0 
  [890070.994968]  [] submit_bio+0x77/0x150
  [890070.994971]  [] ? bio_alloc_bioset+0x181/0x2a0
  [890070.994977]  [] dispatch_rw_block_io+0x4fd/0x9b0 
[xen_blkback]
  [890070.994981]  [] ? xen_load_sp0+0x84/0x180
  [890070.994985]  [] __do_block_io_op+0x1f5/0x650 
[xen_blkback]
  [890070.994990]  [] ? del_timer_sync+0x48/0x50
  [890070.994993]  [] ? schedule_timeout+0x16b/0x2d0
  [890070.994997]  [] xen_blkif_schedule+0xd0/0x820 
[xen_blkback]
  [890070.995002]  [] ? finish_task_switch+0x7a/0x290
  [890070.995004]  [] ? __schedule+0x359/0x980
  [890070.995010]  [] ? prepare_to_wait_event+0xf0/0xf0
  [890070.995014]  [] ? xen_blkif_be_int+0x30/0x30 
[xen_blkback]
  [890070.995018]  [] kthread+0xc9/0xe0
  [890070.995021]  [] ? kthread_park+0x60/0x60
  [890070.995025]  [] ret_from_fork+0x3f/0x70
  [890070.995027]  [] ? kthread_park+0x60/0x60

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645187/+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 1677959] [NEW] change_profile incorrect when using namespaces with a compound stack

[John Johansen]

Public bug reported:

When a compound label is used as part of a target namespace the change
profile will result in a bad change

a task confined by profile lxd doing
change_profile(&:ns://foo//)

results in a change_profile to

  :ns://foo
and
  unconfined

causing the local system profile to change instead of setting up a stack in the 
sub namespace
ie.
  unconfined//&:ns://foo
instead of the expected
  lxd//&:ns://foo//&:ns://unconfined

https://github.com/lxc/lxd/issues/2981

** Affects: apparmor
 Importance: Undecided
 Status: New

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

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Yakkety)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Zesty)
 Importance: Undecided
 Status: Incomplete

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   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/1677959

Title:
  change_profile incorrect when using namespaces with a compound stack

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete
Status in linux source package in Zesty:
  Incomplete

Bug description:
  When a compound label is used as part of a target namespace the change
  profile will result in a bad change

  a task confined by profile lxd doing
  change_profile(&:ns://foo//)

  results in a change_profile to

:ns://foo
  and
unconfined

  causing the local system profile to change instead of setting up a stack in 
the sub namespace
  ie.
unconfined//&:ns://foo
  instead of the expected
lxd//&:ns://foo//&:ns://unconfined

  https://github.com/lxc/lxd/issues/2981

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1677959/+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 1658219] Re: flock not mediated by 'k'

[John Johansen]

Note: this bug affects more than just lock mediation permissions. It at
a minimum can also affect the mmap executable (m) permission.

Further work is required to resubmit this fix

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

Title:
  flock not mediated by 'k'

Status in AppArmor:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+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 1645521] Re: [Feature] ISH (Intel Sensor Hub) support

[quanxian]

only one sub-feature commitid provided, still have more commitid for 
sub-feature. Keep tune.
Status should be incomplete.

Thanks

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

Title:
  [Feature] ISH (Intel Sensor Hub) support

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Integrete ISH kernel driver and ISH driver should provoide following 
interface to user
  (1) Batch ModeGet the hardware batch buffer size/count,Set the batch 
timeout value
  (2) Wakeup/non-wakeupchecking if one sensor is wakeup instance or 
non-wakeup instance.For wakeup instance, when batch buffer is full or wait 
timeout, system must be woken up and receive batched sensor events.
  (3) Timestamp  expose the sensor event timestamp to user space for sync
  (4) physical sensors-support exposing following physical 
sensors:Accelerometer,Gyroscope,Magnetic,Field,Pressure,Light,Proximity
  (5) Advanced sensorsupport exposing following advanced sensors:
  Gravity,Linear Acceleration,Rotation Vector,Orientation,Game 
Rotation,Geomagentic Rotation,Step Detector,Step Counter,Terminal,Significant 
motion,Wakeup Gesture,Glance Gesture,Tilt,PanZoon,Lift and Look
  (6)multiple sensor instance support
  (7)private command support  support set/get path for private command set 
and response get, because some advanced sensor needs different special command 
to work properly.
  (8)User defined sensor support--- exposing non-pre-defined sensors.
  Because customer may add a new sensor in firmware, and hope sensor driver can 
expose it as a unknown sensor automatically, then application can use it 
directly without any code change.

  HW: Broxton-p

  Upstream Schedule:
  Basic Sensor Driver: 4.9
  Advanced Sensor Driver: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645521/+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 1677938] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1677938

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

Title:
  ubuntu hyper v vm freezes with high load after windows backup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the upgrade of the LIS tools to 4.4.0-67+ the hyper v vm backup
  is not possible anymore with the windows backup tool on an Ubuntu
  16.04 on a Gen 2 Hyper V VM. I cannot say what is exactly happening
  because there are no log files and just a blank black screen. A second
  hyper v vm is not crashing but cannot be backuped too. Same version of
  Ubuntu and LIS but Gen 1 Hyper V VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677938/+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 1677938] [NEW] ubuntu hyper v vm freezes with high load after windows backup

[Emmanuel Günther]

Public bug reported:

Since the upgrade of the LIS tools to 4.4.0-67+ the hyper v vm backup is
not possible anymore with the windows backup tool on an Ubuntu 16.04 on
a Gen 2 Hyper V VM. I cannot say what is exactly happening because there
are no log files and just a blank black screen. A second hyper v vm is
not crashing but cannot be backuped too. Same version of Ubuntu and LIS
but Gen 1 Hyper V VM.

** 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/1677938

Title:
  ubuntu hyper v vm freezes with high load after windows backup

Status in linux package in Ubuntu:
  New

Bug description:
  Since the upgrade of the LIS tools to 4.4.0-67+ the hyper v vm backup
  is not possible anymore with the windows backup tool on an Ubuntu
  16.04 on a Gen 2 Hyper V VM. I cannot say what is exactly happening
  because there are no log files and just a blank black screen. A second
  hyper v vm is not crashing but cannot be backuped too. Same version of
  Ubuntu and LIS but Gen 1 Hyper V VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677938/+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 1677697] Re: linux: 4.10.0-16.18 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

** Description changed:

  This bug is for tracking the 4.10.0-16.18 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-phase-changed:Thursday, 30. March 2017 18:00 UTC
- kernel-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-phase-changed:Friday, 31. March 2017 00:30 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.10.0-16.18 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- phase: Packaging
- kernel-phase-changed:Friday, 31. March 2017 00:30 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.10.0-16.18 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-16.18 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1677697/+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 1667160] Re: Kernel panic with 4.8.0-1025 through -1031 on RasPi 2

[Markus Birth]

Same problem with 4.8.0-1032.

** Summary changed:

- Kernel panic with 4.8.0-1025 through -1031 on RasPi 2
+ Kernel panic since 4.8.0-1025 on RasPi 2

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

Title:
  Kernel panic since 4.8.0-1025 on RasPi 2

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
  wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
  there's a RTL2838 DVB-T USB stick attached to monitor airplane
  positions for Flightradar24.

  After updateing the kernel from 4.8.0-1024, which runs flawlessly, to
  -1025, there's a kernel panic happening 10-20 seconds after booting up
  to the login prompt. I thought the -1026 fixed that, but it's still no
  worky. The trace is scrolling so fast I can't read anything but the
  last page:

  [<808c76c8>] (sock_sendmsg) from...
  [<808c7778>] (sock_write_iter) from...
  [<802c39c8>] (new_sync_write) from...
  [<802c3a4c>] (__vfs_write) from...
  [<802c48d8>] (vfs_write) from...
  [<802c5ab4>] (SyS_write) from...
  Code: e5922004 e0033002 e353 0a0a (e5902034)
  ---[ end trace 0f53d17efe0c6ba ]---
  Kernel panic - not syncing: Fatal exception in interrupt
  CPU2: stopping
  CPU: 2 PID: 21 Comm: migration/2 Tainted: G  D  4.8.0-1026-raspi2 
#29-Ubuntu
  Hardware name: BCM2709
  [<801120ac>] (unwind_backtrace) from ...
  [<8010d2dc>] (show_stack) from ...
  [<8059c38c>] (handle_IPI) from ...
  [<80101564>] (bcm2836_arm_irqchip_handle_irq) from [<80a49f3c>] 
(__irq_svc+0x5c/0x7c)
  Exception stack(0xbb99de68 to 0xbb99deb0)
  de60:    0004  0001 bac05de0 0001
  de80: bac05dcc  a00e0013  bac05d6c bb99dedc bb99dee0 bb99deb8
  dea0: 801d367c 801d35f4 600e0013 
  [<80a49f3c>] (__irq_svc) from ...
  [<801d35f4>] (multi_cpu_stop) from ...
  [<801d38ec>] (cpu_stopper_thread) from ...
  [<8014b71c>] (smpboot_thread_fn) from ...
  [<80147770>] (kthread) from [<80108e28>] (ret_from_fork+0x14/0x2c)

  
  And then this block repeats with CPU3 and CPU0.

  
  Going back to 4.8.0-1024 makes everything work again.

  
  Affected packages:

  linux-image-4.8.0-1025-raspi2:armhf (4.8.0-1025.28)
  linux-image-4.8.0-1026-raspi2:armhf (4.8.0-1026.29)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 25  2016 seq
   crw-rw 1 root audio 116, 33 Jul 25  2016 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-1024-raspi2.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.10
  Lsusb:
   Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
   Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 
802.11n Wireless Adapter [Realtek RTL8188CUS]
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0xecd3f749 
smsc95xx.macaddr=B8:27:EB:D3:F7:49 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3ea0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: Ubuntu 4.8.0-1024.27-raspi2 4.8.16
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-1024-raspi2 N/A
   linux-backports-modules-4.8.0-1024-raspi2  N/A
   linux-firmware 1.161.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-1024-raspi2 armv7l
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to yakkety on 2016-10-24 (122 days ago)
  UserGroups: adm audio cdrom dialout floppy fuse netdev plugdev sudo users 
video www-data
  _MarkForUpload: False

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

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

[Kernel-packages] [Bug 1673350] Please test proposed package

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted multipath-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.5.0+git1.656f8865-5ubuntu2.5 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in multipath-tools source package in Xenial:
  Fix Committed
Status in hw-detect source package in Yakkety:
  In Progress
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Committed
Status in multipath-tools source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions

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

[Kernel-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted multipath-tools into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.5.0+git1.656f8865-5ubuntu7.3 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: multipath-tools (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: multipath-tools (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in multipath-tools source package in Xenial:
  Fix Committed
Status in hw-detect source package in Yakkety:
  In Progress
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Committed
Status in multipath-tools source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1516025] Re: Realtek ALC3661 Alienware14 / Sountoutput / Jack

[Mohd Imran Jamadar]

** Summary changed:

- Realtek ALC3661 Alienware14 
+ Realtek ALC3661 Alienware14 / Sountoutput / Jack

** Summary changed:

- Realtek ALC3661 Alienware14 / Sountoutput / Jack
+ Realtek ALC3661 Alienware14 / Soundoutput / Jack

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

Title:
  Realtek ALC3661 Alienware14 / Soundoutput / Jack

Status in ALSA driver:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1516025/+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 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

[Tim Gardner]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667527/+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 1516025] Re: Realtek ALC3661 Alienware14

[Mohd Imran Jamadar]

** Tags added: amd64 apport-bug latest-bios-a09 xenial yakkety

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

Title:
  Realtek ALC3661 Alienware14

Status in ALSA driver:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1516025/+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 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

[Joseph Salisbury]

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: Fix Committed

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => In Progress

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

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667527/+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 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Joseph Salisbury]

Per comment #4 -71 does not contain the bug.  However, -71 does not
contain the changes that went into 68 and 69.  Those changes are in
master-next now though.  I built a master-next kernel, which can be
downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1677337/master-next/

Can you see if this kernel has the bug?  If it does, we can bisect the
master-next branch.

Thanks in advance!

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

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
  [8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
  [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
  [8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1

  === 4.11.0-041100rc1-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
  Subsystem: IBM MT27500 Family [ConnectX-3]
  Flags: bus master, fast devsel, latency 0, IRQ 473
  Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
  Memory at 2400 (64-bit, prefetchable) [size=128M]
  [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

[Mathieu Trudel-Lapierre]

The update of shim, grub, mokutil and others to use signed kernels and
modules are mostly done; one further step that needs to happen is to
have grub enforce that kernels are properly signed, and refuse to load
unsigned kernels (rather than falling back from the linuxefi module
which checks signatures, to linux which doesn't).

In the interest of clarity, I'll close the tasks here as Invalid for
what is left as "New", and we'll move this "last step" to bug 1401532
which is clearly about this issue.

** Changed in: grub2-signed (Ubuntu)
   Status: New => Invalid

** Changed in: grub2 (Ubuntu)
   Status: New => Invalid

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

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  Invalid
Status in grub2-signed package in Ubuntu:
  Invalid
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Released
Status in dkms source package in Trusty:
  Fix Released
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Invalid
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Wily:
  Fix Released
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Released
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure 

[Kernel-packages] [Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Mike Rushton]

4.4.0-71-generic is tested as working now.

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

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
  [8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
  [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
  [8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1

  === 4.11.0-041100rc1-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
  Subsystem: IBM MT27500 Family [ConnectX-3]
  Flags: bus master, fast devsel, latency 0, IRQ 473
  Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
  Memory at 2400 (64-bit, prefetchable) [size=128M]
  [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
  Kernel driver in use: mlx4_core
  Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
     

[Kernel-packages] [Bug 1672144] Re: ifup service of network device stay active after driver stop

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-March/083374.html

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  ifup service of network device stay active after driver stop

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  The network device systemd service stay active after unload the module of 
this network device, that call close port (ndo_stop).
  once we try to load the NIC driver again, it try to start the ifup service of 
his NICs and due to the service is already up, so it fail and we didn't see the 
interface with the static configuration =.
  below simple reproduce with the Mellanox ConnectX4 device (driver name 
mlx5_core).

  Also we see this issue with Azure system, Ubuntu 17.04 guest over
  Hyper-v, the  VF failed to start after re-enable SR-IOV from VM's
  vNIC.

  
  For now we have a Work Around that to add a udev rule,
   echo DRIVERS==\"*mlx*\", SUBSYSTEM==\"net\", 
ACTION==\"add\",RUN+=\"/sbin/ifup --force $env{INTERFACE}\" > 
/lib/udev/rules.d/100-up.rules
  Example:
  #:/lib/udev/rules.d# cat 100-up.rules
  DRIVERS=="*mlx*", SUBSYSTEM=="net", ACTION=="add",RUN+="/sbin/ifup --force 
$env{INTERFACE}" 

  ***
  * More info and reproduce *
  ***
  # ifdown ens1f0
  RTNETLINK answers: Cannot assign requested address
  # ifup ens1f0 
  # ifconfig ens1f0 
  ens1f0: flags=4163  mtu 1500
  inet 123.12.23.1  netmask 255.255.0.0  broadcast 123.12.255.255
  inet6 fe80::268a:7ff:fea1:fbdc  prefixlen 64  scopeid 0x20
  ether 24:8a:07:a1:fb:dc  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)   
  RX errors 0  dropped 0  overruns 0  frame 0 
  TX packets 17  bytes 1392 (1.3 KB)  
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  

  # ethtool -i ens1f0 |grep driv
  driver: mlx5_core
  # systemctl status ifup@ens1f 
  ifup@ens1f0.service  ifup@ens1f1.service

  # systemctl status ifup@ens1f0.service 
  * ifup@ens1f0.service - ifup for ens1f0  
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: active (exited) since Sun 2017-03-12 09:40:04 IST; 2h 26min ago
   
   Main PID: 1608 (code=exited, status=0/SUCCESS)   
   
 CGroup: /system.slice/ifup@ens1f0.service  
   

  Mar 12 09:40:04 qa-h-vrt-039 systemd[1]: Started ifup for ens1f0.
  Mar 12 09:40:04 qa-h-vrt-039 sh[1608]: ifup: interface ens1f0 already 
configured
  root@qa-h-vrt-039:/tmp# modprobe -rv mlx5_ib 
  rmmod mlx5_ib
  rmmod mlx5_core  

  # modprobe -rv mlx5_core

  # ifconfig -a |grep ens1f0

  # lsmod |grep mlx5

  # systemctl status ifup@ens1f0.service
  * ifup@ens1f0.service - ifup for ens1f0 
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: active (exited) since Sun 2017-03-12 09:40:04 IST; 2h 27min ago
   Main PID: 1608 (code=exited, status=0/SUCCESS)
 CGroup: /system.slice/ifup@ens1f0.service

  Mar 12 09:40:04 qa-h-vrt-039 systemd[1]: Started ifup for ens1f0.
  Mar 12 09:40:04 qa-h-vrt-039 sh[1608]: ifup: interface ens1f0 already 
configured

  # modprobe mlx5_core

  # ifconfig ens1f0
  ens1f0: flags=4098  mtu 1500
  ether 24:8a:07:a1:fb:dc  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  # cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  
  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto eno1
  iface eno1 inet dhcp

  #ens1f0
  auto ens1f0
  iface ens1f0 inet static
  address 123.12.23.1
  netmask 255.255.0.0
  mtu 1500

  
  *
  * Another repto and investigate *
  *
  once interface is created the system starts a service that is responsible for 
activating it (basically runs ifup).
  so, at first shot everything works.
  at 

[Kernel-packages] [Bug 1672144] Re: ifup service of network device stay active after driver stop

[Tim Gardner]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  ifup service of network device stay active after driver stop

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  The network device systemd service stay active after unload the module of 
this network device, that call close port (ndo_stop).
  once we try to load the NIC driver again, it try to start the ifup service of 
his NICs and due to the service is already up, so it fail and we didn't see the 
interface with the static configuration =.
  below simple reproduce with the Mellanox ConnectX4 device (driver name 
mlx5_core).

  Also we see this issue with Azure system, Ubuntu 17.04 guest over
  Hyper-v, the  VF failed to start after re-enable SR-IOV from VM's
  vNIC.

  
  For now we have a Work Around that to add a udev rule,
   echo DRIVERS==\"*mlx*\", SUBSYSTEM==\"net\", 
ACTION==\"add\",RUN+=\"/sbin/ifup --force $env{INTERFACE}\" > 
/lib/udev/rules.d/100-up.rules
  Example:
  #:/lib/udev/rules.d# cat 100-up.rules
  DRIVERS=="*mlx*", SUBSYSTEM=="net", ACTION=="add",RUN+="/sbin/ifup --force 
$env{INTERFACE}" 

  ***
  * More info and reproduce *
  ***
  # ifdown ens1f0
  RTNETLINK answers: Cannot assign requested address
  # ifup ens1f0 
  # ifconfig ens1f0 
  ens1f0: flags=4163  mtu 1500
  inet 123.12.23.1  netmask 255.255.0.0  broadcast 123.12.255.255
  inet6 fe80::268a:7ff:fea1:fbdc  prefixlen 64  scopeid 0x20
  ether 24:8a:07:a1:fb:dc  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)   
  RX errors 0  dropped 0  overruns 0  frame 0 
  TX packets 17  bytes 1392 (1.3 KB)  
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  

  # ethtool -i ens1f0 |grep driv
  driver: mlx5_core
  # systemctl status ifup@ens1f 
  ifup@ens1f0.service  ifup@ens1f1.service

  # systemctl status ifup@ens1f0.service 
  * ifup@ens1f0.service - ifup for ens1f0  
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: active (exited) since Sun 2017-03-12 09:40:04 IST; 2h 26min ago
   
   Main PID: 1608 (code=exited, status=0/SUCCESS)   
   
 CGroup: /system.slice/ifup@ens1f0.service  
   

  Mar 12 09:40:04 qa-h-vrt-039 systemd[1]: Started ifup for ens1f0.
  Mar 12 09:40:04 qa-h-vrt-039 sh[1608]: ifup: interface ens1f0 already 
configured
  root@qa-h-vrt-039:/tmp# modprobe -rv mlx5_ib 
  rmmod mlx5_ib
  rmmod mlx5_core  

  # modprobe -rv mlx5_core

  # ifconfig -a |grep ens1f0

  # lsmod |grep mlx5

  # systemctl status ifup@ens1f0.service
  * ifup@ens1f0.service - ifup for ens1f0 
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: active (exited) since Sun 2017-03-12 09:40:04 IST; 2h 27min ago
   Main PID: 1608 (code=exited, status=0/SUCCESS)
 CGroup: /system.slice/ifup@ens1f0.service

  Mar 12 09:40:04 qa-h-vrt-039 systemd[1]: Started ifup for ens1f0.
  Mar 12 09:40:04 qa-h-vrt-039 sh[1608]: ifup: interface ens1f0 already 
configured

  # modprobe mlx5_core

  # ifconfig ens1f0
  ens1f0: flags=4098  mtu 1500
  ether 24:8a:07:a1:fb:dc  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  # cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  
  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto eno1
  iface eno1 inet dhcp

  #ens1f0
  auto ens1f0
  iface ens1f0 inet static
  address 123.12.23.1
  netmask 255.255.0.0
  mtu 1500

  
  *
  * Another repto and investigate *
  *
  once interface is created the system starts a service that is responsible for 
activating it (basically runs ifup).
  so, at first shot everything works.
  at the second driver reload:
  Good flow (on good setup 4.9.0-rc5+):
  1. 

[Kernel-packages] [Bug 1672144] Re: ifup service of network device stay active after driver stop

[Leann Ogasawara]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Yakkety)
   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/1672144

Title:
  ifup service of network device stay active after driver stop

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux source package in Yakkety:
  New
Status in linux source package in Zesty:
  Fix Released

Bug description:
  The network device systemd service stay active after unload the module of 
this network device, that call close port (ndo_stop).
  once we try to load the NIC driver again, it try to start the ifup service of 
his NICs and due to the service is already up, so it fail and we didn't see the 
interface with the static configuration =.
  below simple reproduce with the Mellanox ConnectX4 device (driver name 
mlx5_core).

  Also we see this issue with Azure system, Ubuntu 17.04 guest over
  Hyper-v, the  VF failed to start after re-enable SR-IOV from VM's
  vNIC.

  
  For now we have a Work Around that to add a udev rule,
   echo DRIVERS==\"*mlx*\", SUBSYSTEM==\"net\", 
ACTION==\"add\",RUN+=\"/sbin/ifup --force $env{INTERFACE}\" > 
/lib/udev/rules.d/100-up.rules
  Example:
  #:/lib/udev/rules.d# cat 100-up.rules
  DRIVERS=="*mlx*", SUBSYSTEM=="net", ACTION=="add",RUN+="/sbin/ifup --force 
$env{INTERFACE}" 

  ***
  * More info and reproduce *
  ***
  # ifdown ens1f0
  RTNETLINK answers: Cannot assign requested address
  # ifup ens1f0 
  # ifconfig ens1f0 
  ens1f0: flags=4163  mtu 1500
  inet 123.12.23.1  netmask 255.255.0.0  broadcast 123.12.255.255
  inet6 fe80::268a:7ff:fea1:fbdc  prefixlen 64  scopeid 0x20
  ether 24:8a:07:a1:fb:dc  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)   
  RX errors 0  dropped 0  overruns 0  frame 0 
  TX packets 17  bytes 1392 (1.3 KB)  
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0  

  # ethtool -i ens1f0 |grep driv
  driver: mlx5_core
  # systemctl status ifup@ens1f 
  ifup@ens1f0.service  ifup@ens1f1.service

  # systemctl status ifup@ens1f0.service 
  * ifup@ens1f0.service - ifup for ens1f0  
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: active (exited) since Sun 2017-03-12 09:40:04 IST; 2h 26min ago
   
   Main PID: 1608 (code=exited, status=0/SUCCESS)   
   
 CGroup: /system.slice/ifup@ens1f0.service  
   

  Mar 12 09:40:04 qa-h-vrt-039 systemd[1]: Started ifup for ens1f0.
  Mar 12 09:40:04 qa-h-vrt-039 sh[1608]: ifup: interface ens1f0 already 
configured
  root@qa-h-vrt-039:/tmp# modprobe -rv mlx5_ib 
  rmmod mlx5_ib
  rmmod mlx5_core  

  # modprobe -rv mlx5_core

  # ifconfig -a |grep ens1f0

  # lsmod |grep mlx5

  # systemctl status ifup@ens1f0.service
  * ifup@ens1f0.service - ifup for ens1f0 
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: active (exited) since Sun 2017-03-12 09:40:04 IST; 2h 27min ago
   Main PID: 1608 (code=exited, status=0/SUCCESS)
 CGroup: /system.slice/ifup@ens1f0.service

  Mar 12 09:40:04 qa-h-vrt-039 systemd[1]: Started ifup for ens1f0.
  Mar 12 09:40:04 qa-h-vrt-039 sh[1608]: ifup: interface ens1f0 already 
configured

  # modprobe mlx5_core

  # ifconfig ens1f0
  ens1f0: flags=4098  mtu 1500
  ether 24:8a:07:a1:fb:dc  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  # cat /etc/network/interfaces
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  
  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto eno1
  iface eno1 inet dhcp

  #ens1f0
  auto ens1f0
  iface ens1f0 inet static
  address 123.12.23.1
  netmask 255.255.0.0
  mtu 1500

  
  *
  * Another repto and investigate *
  *
  once interface is created the system starts a service that is responsible for 
activating it (basically runs ifup).
  so, at first shot everything works.
  at the second driver reload:
  Good flow (on good setup 4.9.0-rc5+):
  1. driver is 

[Kernel-packages] [Bug 1674938] Re: linux: 4.4.0-70.91 -proposed tracker

[Manfred Hampl]

Why have all changes from 4.4.0-69 been reverted?

Especially patch https://patchwork.kernel.org/patch/9483577/ has cured a
critical bug and finally provided a working system again, but with
4.4.0-70 all devices using the rtlwifi kernel module again produce a
null pointer dereference kernel panic, see Bug #1666421

I would like to call this a regression.

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

Title:
  linux: 4.4.0-70.91 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1674939
  derivatives: 1674940,1674941,1674944,1674945
  -- swm properties --
  boot-testing-requested: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+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 1677697] Re: linux: 4.10.0-16.18 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.10.0-16.18 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-phase-changed:Thursday, 30. March 2017 18:00 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.10.0-16.18 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-phase-changed:Thursday, 30. March 2017 18:00 UTC
  kernel-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.10.0-16.18 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the 4.10.0-16.18 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  kernel-phase-changed:Thursday, 30. March 2017 18:00 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1677697/+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 1677685] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From b...@us.ibm.com 2017-03-30 13:48 EDT---
They are targeted for Yakkety, and the last one was submitted by the 
maintainer, so essentially it's pretty much accepted.

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

Title:
  Target: Configfs Crashes and kernel crash fixes

Status in linux package in Ubuntu:
  New

Bug description:
  A number of patches that need to be backported for target subsystem.

  target: Don't BUG_ON during NodeACL dynamic -> explicit conversion
  https://patchwork.kernel.org/patch/9560085/

  target: Use correct SCSI status during EXTENDED_COPY exception
  https://patchwork.kernel.org/patch/9560083/

  target: Fix early transport_generic_handle_tmr abort scenario
  https://patchwork.kernel.org/patch/9560077/

  target: Fix multi-session dynamic se_node_acl double free OOPs
  https://patchwork.kernel.org/patch/9560081/

  target: Fix COMPARE_AND_WRITE ref leak for non GOOD status
  https://patchwork.kernel.org/patch/9560065/

  target: Fix NULL dereference during LUN lookup + active I/O shutdown
  https://patchwork.kernel.org/patch/9587799/

  target: Avoid mappedlun symlink creation during lun shutdown
  https://lkml.org/lkml/2017/3/30/180

   
  Contact Information = Bryant G. Ly/b...@us.ibm.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677685/+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 1677697] [NEW] linux: 4.10.0-16.18 -proposed tracker

[Tim Gardner]

Public bug reported:

This bug is for tracking the 4.10.0-16.18 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux (Ubuntu Zesty)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed kernel-release-tracking-bug zesty

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Tags added: zesty

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  linux: 4.10.0-16.18 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow 

[Kernel-packages] [Bug 1516025] Re: Realtek ALC3661 Alienware14

[Mohd Imran Jamadar]

** Tags removed: amd64 apport-bug latest-bios-a09 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/1516025

Title:
  Realtek ALC3661 Alienware14

Status in ALSA driver:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1516025/+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 1516025] Re: Realtek ALC3661 Alienware14

[Mohd Imran Jamadar]

** Attachment added: "no sub-woofer output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516025/+attachment/4850692/+files/sound_4.0.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/1516025

Title:
  Realtek ALC3661 Alienware14

Status in ALSA driver:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1516025/+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 1516025] Re: Realtek ALC3661 Alienware14

[Mohd Imran Jamadar]

https://launchpad.net/~penalvch

Ref to comment no #7 and upon testing upstream kernel, i confirm the bug
to exist.

Kernel tested was,  
linux-image-4.10.0-041000-generic_4.10.0-041000.201702191831_amd64.deb & 
4.8.0-45-generic

Please advise, still see analog  4.o surround sound option, with no option for 
sub-woofer option to toggle.
But if i plug in my headphone jack w/o mic, and if i select 4.0 output i can 
hear in my headphones sound Rear Left and Rear Right, soundoutput. 
michttps://goo.gl/images/HaFA3W



** Attachment added: "4.0.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1516025/+attachment/4850691/+files/4.0.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/1516025

Title:
  Realtek ALC3661 Alienware14

Status in ALSA driver:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1516025/+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 1677685] Re: Target: Configfs Crashes and kernel crash fixes

[Tim Gardner]

The first 6 patches are already merged upstream and are present in
Zesty. The 7th has yet to be accepted by a maintainer. To what releases
are these patches targeted ?

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

Title:
  Target: Configfs Crashes and kernel crash fixes

Status in linux package in Ubuntu:
  New

Bug description:
  A number of patches that need to be backported for target subsystem.

  target: Don't BUG_ON during NodeACL dynamic -> explicit conversion
  https://patchwork.kernel.org/patch/9560085/

  target: Use correct SCSI status during EXTENDED_COPY exception
  https://patchwork.kernel.org/patch/9560083/

  target: Fix early transport_generic_handle_tmr abort scenario
  https://patchwork.kernel.org/patch/9560077/

  target: Fix multi-session dynamic se_node_acl double free OOPs
  https://patchwork.kernel.org/patch/9560081/

  target: Fix COMPARE_AND_WRITE ref leak for non GOOD status
  https://patchwork.kernel.org/patch/9560065/

  target: Fix NULL dereference during LUN lookup + active I/O shutdown
  https://patchwork.kernel.org/patch/9587799/

  target: Avoid mappedlun symlink creation during lun shutdown
  https://lkml.org/lkml/2017/3/30/180

   
  Contact Information = Bryant G. Ly/b...@us.ibm.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677685/+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 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Karlyn Fielding]

I can confirm that the issue remains with the latest 4.10.7 mainline
kernel build for Ubuntu.

Same specs as before:
Dell XPS13 DE (9360)
TB16 Dock
Ubuntu 16.04 ( installed as shipped from Dell )

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:09 ubuntu kernel: usb 4-1.2: reset SuperSpeed USB device number 
3 using xhci_hcd

  I can't seem to make this bug appear with any other type of USB
  traffic. I've reported it to the realtek kernel dev team and they

[Kernel-packages] [Bug 1673211] Re: linux-lts-trusty: 3.13.0-114.161~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Tags removed: block-proposed-precise

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

Title:
  linux-lts-trusty: 3.13.0-114.161~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1673207
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1673211/+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 1673207] Re: linux: 3.13.0-114.161 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Confirmed

** Tags removed: block-proposed-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/1673207

Title:
  linux: 3.13.0-114.161 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1673211
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1673207/+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 1677685] target: Avoid mappedlun symlink creation during lun shutdown

[bugproxy]

Default Comment by Bridge

** Attachment added: "target: Avoid mappedlun symlink creation during lun 
shutdown"
   
https://bugs.launchpad.net/bugs/1677685/+attachment/4850665/+files/0001-target-Avoid-mappedlun-symlink-creation-during-lun-s.patch

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  Target: Configfs Crashes and kernel crash fixes

Status in linux package in Ubuntu:
  New

Bug description:
  A number of patches that need to be backported for target subsystem.

  target: Don't BUG_ON during NodeACL dynamic -> explicit conversion
  https://patchwork.kernel.org/patch/9560085/

  target: Use correct SCSI status during EXTENDED_COPY exception
  https://patchwork.kernel.org/patch/9560083/

  target: Fix early transport_generic_handle_tmr abort scenario
  https://patchwork.kernel.org/patch/9560077/

  target: Fix multi-session dynamic se_node_acl double free OOPs
  https://patchwork.kernel.org/patch/9560081/

  target: Fix COMPARE_AND_WRITE ref leak for non GOOD status
  https://patchwork.kernel.org/patch/9560065/

  target: Fix NULL dereference during LUN lookup + active I/O shutdown
  https://patchwork.kernel.org/patch/9587799/

  target: Avoid mappedlun symlink creation during lun shutdown
  https://lkml.org/lkml/2017/3/30/180

   
  Contact Information = Bryant G. Ly/b...@us.ibm.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677685/+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 1677685] [NEW] Target: Configfs Crashes and kernel crash fixes

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

A number of patches that need to be backported for target subsystem.

target: Don't BUG_ON during NodeACL dynamic -> explicit conversion
https://patchwork.kernel.org/patch/9560085/

target: Use correct SCSI status during EXTENDED_COPY exception
https://patchwork.kernel.org/patch/9560083/

target: Fix early transport_generic_handle_tmr abort scenario
https://patchwork.kernel.org/patch/9560077/

target: Fix multi-session dynamic se_node_acl double free OOPs
https://patchwork.kernel.org/patch/9560081/

target: Fix COMPARE_AND_WRITE ref leak for non GOOD status
https://patchwork.kernel.org/patch/9560065/

target: Fix NULL dereference during LUN lookup + active I/O shutdown
https://patchwork.kernel.org/patch/9587799/

target: Avoid mappedlun symlink creation during lun shutdown
https://lkml.org/lkml/2017/3/30/180

 
Contact Information = Bryant G. Ly/b...@us.ibm.com

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64 bugnameltc-153041 severity-medium 
targetmilestone-inin1610
-- 
Target: Configfs Crashes and kernel crash fixes
https://bugs.launchpad.net/bugs/1677685
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1636656] Re: [Hyper-V] netvsc: fix incorrect receive checksum offloading

[Brad Figg]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Committed => 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/1636656

Title:
  [Hyper-V] netvsc: fix incorrect receive checksum offloading

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  The Hyper-V netvsc driver was looking at the incorrect status bits
  in the checksum info. It was setting the receive checksum unnecessary
  flag based on the IP header checksum being correct. The checksum
  flag is skb is about TCP and UDP checksum status. Because of this
  bug, any packet received with bad TCP checksum would be passed
  up the stack and to the application causing data corruption.
  The problem is reproducible via netcat and netem.

  This had a side effect of not doing receive checksum offload
  on IPv6. The driver was also also always doing checksum offload
  independent of the checksum setting done via ethtool.

  Signed-off-by: Stephen Hemminger 

  https://patchwork.ozlabs.org/patch/685660/

  When this patch is committed I will include the commit ID in this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636656/+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 1677673] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  System soft-freezes, BUG: unable to handle kernel NULL pointer
  dereference at 0018 in journalctl

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded to 17.04. It appears that now leaving the system
  locked for long enough now makes it unable to respond to any input but
  SysRq.

  This apepars to be the only relevant bit in `journalctl --boot -1`:

  BUG: unable to handle kernel NULL pointer dereference at 0018
  IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  PGD 0 

  Oops: 0002 [#1] SMP
  Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci 
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
  CPU: 3 PID: 3826 Comm: chrome Tainted: G   OE   4.10.0-14-generic 
#16-Ubuntu
  Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
  task: 99ddb372da00 task.stack: b0ec037dc000
  RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  RSP: 0018:b0ec037df880 EFLAGS: 00010246
  RAX: 99dd0367b880 RBX: 0003 RCX: 0003
  RDX:  RSI: 99ddb737e000 RDI: 99de4ad9
  RBP: b0ec037df8d8 R08:  R09: 
  R10:  R11: 0001 R12: 99ddc994a000
  R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000
  FS:  7fd3a0fa7b00() GS:99de5e58() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0018 CR3: 000174607000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
   ? __alloc_pages_nodemask+0xff/0x260
   gen8_alloc_va_range+0x23d/0x470 [i915]
   i915_vma_bind+0x7e/0x170 [i915]
   __i915_vma_do_pin+0x2a5/0x450 [i915]
   i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
   i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
   i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
   ? radix_tree_lookup_slot+0x22/0x50
   ? shmem_getpage_gfp+0xf9/0xc10
   i915_gem_execbuffer2+0xa1/0x1e0 [i915]
   drm_ioctl+0x21b/0x4c0 [drm]
   ? i915_gem_execbuffer+0x310/0x310 [i915]
   ? __seccomp_filter+0x67/0x250
   do_vfs_ioctl+0xa3/0x610
   ? __secure_computing+0x3f/0xd0
   ? syscall_trace_enter+0xcd/0x2e0
   SyS_ioctl+0x79/0x90
   do_syscall_64+0x5b/0xc0
   entry_SYSCALL64_slow_path+0x25/0x25
  RIP: 0033:0x7fd39a33a907
  RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010
  RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907
  RDX: 76323860 RSI: c0406469 RDI: 000e
  RBP: 76323860 R08:  R09: 
  R10: 0038 R11: 0246 R12: c0406469
  R13: 000e R14:  R15: 
  Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 
08 0f 1f 44 00
  RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 
b0ec037df880
  CR2: 0018
  ---[ end trace 2a4103476767c23b ]---

  I walked to my computer 12 minutes later, finding it soft-locked as
  described above.

  I realize that this appears somewhat far removed from the real cause
  of the problem, so please let me know what other data I can provide to
  facilitate the debugging process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sraffa 2780 F pulseaudio
   /dev/snd/controlC0:  sraffa 2780 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 30 17:44:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
  InstallationDate: Installed on 2015-11-02 (514 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E7250
  ProcFB: 0 inteldrmfb
  

[Kernel-packages] [Bug 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

[Brad Figg]

** Also affects: linux (Ubuntu Yakkety)
   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/1667527

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667527/+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 1667531] Re: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

[Joseph Salisbury]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Please include bondvf.sh from kernel git tools/hv/ in /usr/sbin

  commit fd7aabb062fa1a8331a786d617744de220eaf002
  Author: Haiyang Zhang 
  Date:   Fri Dec 2 15:55:38 2016 -0800

  tools: hv: Enable network manager for bonding scripts on RHEL

  We found network manager is necessary on RHEL to make the synthetic
  NIC, VF NIC bonding operations handled automatically. So, enabling
  network manager here.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

  commit 178cd55f086629cf0bad9c66c793a7e2bcc3abb6
  Author: Haiyang Zhang 
  Date:   Mon Jul 11 17:06:42 2016 -0700

  tools: hv: Add a script to help bonding synthetic and VF NICs

  This script helps to create bonding network devices based on synthetic NIC
  (the virtual network adapter usually provided by Hyper-V) and the matching
  VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can
  function as one network device, and fail over to the synthetic NIC if VF 
is
  down.

  Mayjor distros (RHEL, Ubuntu, SLES) supported by Hyper-V are supported by
  this script.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667531/+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 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

[Joseph Salisbury]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667527/+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 1672785] Re: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown

[Joseph Salisbury]

** Changed in: linux (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: linux (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver
  device shutdown

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Mellanox has submitted the following patch upstream that's important
  for SR-IOV in Azure.

  Please integrate it into the Mellanox mlx4 drivers for lts-xenial,
  HWE, Zesty, and Azure custom.

  https://patchwork.ozlabs.org/patch/738305/

  From: Jack Morgenstein 

  Some Hypervisors detach VFs from VMs by instantly causing an FLR event
  to be generated for a VF.

  In the mlx4 case, this will cause that VF's comm channel to be disabled
  before the VM has an opportunity to invoke the VF device's "shutdown"
  method.

  For such Hypervisors, there is a race condition between the VF's
  shutdown method and its internal-error detection/reset thread.

  The internal-error detection/reset thread (which runs every 5 seconds) also
  detects a disabled comm channel. If the internal-error detection/reset
  flow wins the race, we still get delays (while that flow tries repeatedly
  to detect comm-channel recovery).

  The cited commit fixed the command timeout problem when the
  internal-error detection/reset flow loses the race.

  This commit avoids the unneeded delays when the internal-error
  detection/reset flow wins.

  Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown")
  Signed-off-by: Jack Morgenstein 
  Reported-by: Simon Xiao 
  Signed-off-by: Tariq Toukan 
  ---
   drivers/net/ethernet/mellanox/mlx4/cmd.c  | 11 +++
   drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++
   include/linux/mlx4/device.h   |  1 +
   3 files changed, 23 insertions(+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672785/+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 1674273] Re: Resolver ignores ndots option

[Alberto Salvia Novella]

** Changed in: glibc (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: glibc (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Resolver ignores ndots option

Status in glibc package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in glibc source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This is a re-report of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202 since that
  one was apparently closed as no-fix simply because it was too old.

  This still occurs in xenial.

  Original description:
  Regardless of ndots option in /etc/resolv.conf, when NXDOMAIN is returned 
from the DNS server then resolver always try another attempt with the original 
name extended by what is in search option.
  For example, if you're looking for very.long.url.nowhere and there is a line 
"search ubuntu.com" in resolv.conf you will get addres of server 
very.long.url.nowhere.ubuntu.com if such exists. It is incorrect, it should 
occurs only for urls having less that ndots option dots in its name.

  My system is a standard Ubuntu Xenial desktop amd64 using network
  manager and the default configured Wired Connection 1 (i.e. DHCP).

  To reproduce:
  - sudo install /dev/fd/0 /etc/NetworkManager/dnsmasq.d/domain 
<<<'log-queries=extra'
  - sudo killall dnsmasq
  - ping some.long.non-existent.name
  - Watch /var/log/syslog

  In my case:
  Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 query[A] 
some.long.non-existent.name from 127.0.0.1
  Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 forwarded 
some.long.non-existent.name to 192.168.5.1
  Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 reply 
some.long.non-existent.name is NXDOMAIN
  Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 query[A] 
some.long.non-existent.name.sebunger.dnsalias.org from 127.0.0.1
  Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 forwarded 
some.long.non-existent.name.sebunger.dnsalias.org to 192.168.5.1
  Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply 
some.long.non-existent.name.sebunger.dnsalias.org is 
  Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply 
sebunger.dnsalias.org is 203.173.156.30

  My /etc/resolv.conf (which is a sym-link to ../run/resolvconf/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 127.0.1.1
  search sebunger.dnsalias.org
  options ndots:1

  (I added the options ndots with no effect)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=/dev/mapper/vg0-root ro rootdelay=120 quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  RfKill:
   
  Tags:  xenial xenial
  Uname: Linux 4.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy kvm lpadmin plugdev sambashare 
ssh sudo users video
  _MarkForUpload: True
  dmi.bios.date: 06/12/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: GA-MA770-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd06/12/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1677673] [NEW] System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl

[bp]

Public bug reported:

I just upgraded to 17.04. It appears that now leaving the system locked
for long enough now makes it unable to respond to any input but SysRq.

This apepars to be the only relevant bit in `journalctl --boot -1`:

BUG: unable to handle kernel NULL pointer dereference at 0018
IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
PGD 0 

Oops: 0002 [#1] SMP
Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci 
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
CPU: 3 PID: 3826 Comm: chrome Tainted: G   OE   4.10.0-14-generic 
#16-Ubuntu
Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
task: 99ddb372da00 task.stack: b0ec037dc000
RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
RSP: 0018:b0ec037df880 EFLAGS: 00010246
RAX: 99dd0367b880 RBX: 0003 RCX: 0003
RDX:  RSI: 99ddb737e000 RDI: 99de4ad9
RBP: b0ec037df8d8 R08:  R09: 
R10:  R11: 0001 R12: 99ddc994a000
R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000
FS:  7fd3a0fa7b00() GS:99de5e58() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 0018 CR3: 000174607000 CR4: 003406e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
Call Trace:
 gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
 ? __alloc_pages_nodemask+0xff/0x260
 gen8_alloc_va_range+0x23d/0x470 [i915]
 i915_vma_bind+0x7e/0x170 [i915]
 __i915_vma_do_pin+0x2a5/0x450 [i915]
 i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
 i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
 i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
 ? radix_tree_lookup_slot+0x22/0x50
 ? shmem_getpage_gfp+0xf9/0xc10
 i915_gem_execbuffer2+0xa1/0x1e0 [i915]
 drm_ioctl+0x21b/0x4c0 [drm]
 ? i915_gem_execbuffer+0x310/0x310 [i915]
 ? __seccomp_filter+0x67/0x250
 do_vfs_ioctl+0xa3/0x610
 ? __secure_computing+0x3f/0xd0
 ? syscall_trace_enter+0xcd/0x2e0
 SyS_ioctl+0x79/0x90
 do_syscall_64+0x5b/0xc0
 entry_SYSCALL64_slow_path+0x25/0x25
RIP: 0033:0x7fd39a33a907
RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010
RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907
RDX: 76323860 RSI: c0406469 RDI: 000e
RBP: 76323860 R08:  R09: 
R10: 0038 R11: 0246 R12: c0406469
R13: 000e R14:  R15: 
Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 
08 0f 1f 44 00
RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 
b0ec037df880
CR2: 0018
---[ end trace 2a4103476767c23b ]---

I walked to my computer 12 minutes later, finding it soft-locked as
described above.

I realize that this appears somewhat far removed from the real cause of
the problem, so please let me know what other data I can provide to
facilitate the debugging process.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-14-generic 4.10.0-14.16
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  sraffa 2780 F pulseaudio
 /dev/snd/controlC0:  sraffa 2780 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Thu Mar 30 17:44:00 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
InstallationDate: Installed on 2015-11-02 (514 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Latitude E7250
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-14-generic N/A
 linux-backports-modules-4.10.0-14-generic  N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-03-29 (0 days ago)
dmi.bios.date: 11/18/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0V8RX3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 

[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl

[bp]

** Attachment added: "WikiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+attachment/4850653/+files/WikiSyslog.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/1677673

Title:
  System soft-freezes, BUG: unable to handle kernel NULL pointer
  dereference at 0018 in journalctl

Status in linux package in Ubuntu:
  New

Bug description:
  I just upgraded to 17.04. It appears that now leaving the system
  locked for long enough now makes it unable to respond to any input but
  SysRq.

  This apepars to be the only relevant bit in `journalctl --boot -1`:

  BUG: unable to handle kernel NULL pointer dereference at 0018
  IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  PGD 0 

  Oops: 0002 [#1] SMP
  Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci 
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
  CPU: 3 PID: 3826 Comm: chrome Tainted: G   OE   4.10.0-14-generic 
#16-Ubuntu
  Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
  task: 99ddb372da00 task.stack: b0ec037dc000
  RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  RSP: 0018:b0ec037df880 EFLAGS: 00010246
  RAX: 99dd0367b880 RBX: 0003 RCX: 0003
  RDX:  RSI: 99ddb737e000 RDI: 99de4ad9
  RBP: b0ec037df8d8 R08:  R09: 
  R10:  R11: 0001 R12: 99ddc994a000
  R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000
  FS:  7fd3a0fa7b00() GS:99de5e58() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0018 CR3: 000174607000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
   ? __alloc_pages_nodemask+0xff/0x260
   gen8_alloc_va_range+0x23d/0x470 [i915]
   i915_vma_bind+0x7e/0x170 [i915]
   __i915_vma_do_pin+0x2a5/0x450 [i915]
   i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
   i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
   i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
   ? radix_tree_lookup_slot+0x22/0x50
   ? shmem_getpage_gfp+0xf9/0xc10
   i915_gem_execbuffer2+0xa1/0x1e0 [i915]
   drm_ioctl+0x21b/0x4c0 [drm]
   ? i915_gem_execbuffer+0x310/0x310 [i915]
   ? __seccomp_filter+0x67/0x250
   do_vfs_ioctl+0xa3/0x610
   ? __secure_computing+0x3f/0xd0
   ? syscall_trace_enter+0xcd/0x2e0
   SyS_ioctl+0x79/0x90
   do_syscall_64+0x5b/0xc0
   entry_SYSCALL64_slow_path+0x25/0x25
  RIP: 0033:0x7fd39a33a907
  RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010
  RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907
  RDX: 76323860 RSI: c0406469 RDI: 000e
  RBP: 76323860 R08:  R09: 
  R10: 0038 R11: 0246 R12: c0406469
  R13: 000e R14:  R15: 
  Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 
08 0f 1f 44 00
  RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 
b0ec037df880
  CR2: 0018
  ---[ end trace 2a4103476767c23b ]---

  I walked to my computer 12 minutes later, finding it soft-locked as
  described above.

  I realize that this appears somewhat far removed from the real cause
  of the problem, so please let me know what other data I can provide to
  facilitate the debugging process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sraffa 2780 F pulseaudio
   /dev/snd/controlC0:  sraffa 2780 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 30 17:44:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
  InstallationDate: Installed on 2015-11-02 (514 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell 

[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl

[bp]

Scrubbed PII from attachments.

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+attachment/4850652/+files/JournalErrors.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/1677673

Title:
  System soft-freezes, BUG: unable to handle kernel NULL pointer
  dereference at 0018 in journalctl

Status in linux package in Ubuntu:
  New

Bug description:
  I just upgraded to 17.04. It appears that now leaving the system
  locked for long enough now makes it unable to respond to any input but
  SysRq.

  This apepars to be the only relevant bit in `journalctl --boot -1`:

  BUG: unable to handle kernel NULL pointer dereference at 0018
  IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  PGD 0 

  Oops: 0002 [#1] SMP
  Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci 
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
  CPU: 3 PID: 3826 Comm: chrome Tainted: G   OE   4.10.0-14-generic 
#16-Ubuntu
  Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
  task: 99ddb372da00 task.stack: b0ec037dc000
  RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  RSP: 0018:b0ec037df880 EFLAGS: 00010246
  RAX: 99dd0367b880 RBX: 0003 RCX: 0003
  RDX:  RSI: 99ddb737e000 RDI: 99de4ad9
  RBP: b0ec037df8d8 R08:  R09: 
  R10:  R11: 0001 R12: 99ddc994a000
  R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000
  FS:  7fd3a0fa7b00() GS:99de5e58() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0018 CR3: 000174607000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
   ? __alloc_pages_nodemask+0xff/0x260
   gen8_alloc_va_range+0x23d/0x470 [i915]
   i915_vma_bind+0x7e/0x170 [i915]
   __i915_vma_do_pin+0x2a5/0x450 [i915]
   i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
   i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
   i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
   ? radix_tree_lookup_slot+0x22/0x50
   ? shmem_getpage_gfp+0xf9/0xc10
   i915_gem_execbuffer2+0xa1/0x1e0 [i915]
   drm_ioctl+0x21b/0x4c0 [drm]
   ? i915_gem_execbuffer+0x310/0x310 [i915]
   ? __seccomp_filter+0x67/0x250
   do_vfs_ioctl+0xa3/0x610
   ? __secure_computing+0x3f/0xd0
   ? syscall_trace_enter+0xcd/0x2e0
   SyS_ioctl+0x79/0x90
   do_syscall_64+0x5b/0xc0
   entry_SYSCALL64_slow_path+0x25/0x25
  RIP: 0033:0x7fd39a33a907
  RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010
  RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907
  RDX: 76323860 RSI: c0406469 RDI: 000e
  RBP: 76323860 R08:  R09: 
  R10: 0038 R11: 0246 R12: c0406469
  R13: 000e R14:  R15: 
  Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 
08 0f 1f 44 00
  RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 
b0ec037df880
  CR2: 0018
  ---[ end trace 2a4103476767c23b ]---

  I walked to my computer 12 minutes later, finding it soft-locked as
  described above.

  I realize that this appears somewhat far removed from the real cause
  of the problem, so please let me know what other data I can provide to
  facilitate the debugging process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sraffa 2780 F pulseaudio
   /dev/snd/controlC0:  sraffa 2780 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 30 17:44:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
  InstallationDate: Installed on 2015-11-02 (514 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release 

[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl

[bp]

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+attachment/4850655/+files/PulseList.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/1677673

Title:
  System soft-freezes, BUG: unable to handle kernel NULL pointer
  dereference at 0018 in journalctl

Status in linux package in Ubuntu:
  New

Bug description:
  I just upgraded to 17.04. It appears that now leaving the system
  locked for long enough now makes it unable to respond to any input but
  SysRq.

  This apepars to be the only relevant bit in `journalctl --boot -1`:

  BUG: unable to handle kernel NULL pointer dereference at 0018
  IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  PGD 0 

  Oops: 0002 [#1] SMP
  Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci 
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
  CPU: 3 PID: 3826 Comm: chrome Tainted: G   OE   4.10.0-14-generic 
#16-Ubuntu
  Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
  task: 99ddb372da00 task.stack: b0ec037dc000
  RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  RSP: 0018:b0ec037df880 EFLAGS: 00010246
  RAX: 99dd0367b880 RBX: 0003 RCX: 0003
  RDX:  RSI: 99ddb737e000 RDI: 99de4ad9
  RBP: b0ec037df8d8 R08:  R09: 
  R10:  R11: 0001 R12: 99ddc994a000
  R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000
  FS:  7fd3a0fa7b00() GS:99de5e58() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0018 CR3: 000174607000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
   ? __alloc_pages_nodemask+0xff/0x260
   gen8_alloc_va_range+0x23d/0x470 [i915]
   i915_vma_bind+0x7e/0x170 [i915]
   __i915_vma_do_pin+0x2a5/0x450 [i915]
   i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
   i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
   i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
   ? radix_tree_lookup_slot+0x22/0x50
   ? shmem_getpage_gfp+0xf9/0xc10
   i915_gem_execbuffer2+0xa1/0x1e0 [i915]
   drm_ioctl+0x21b/0x4c0 [drm]
   ? i915_gem_execbuffer+0x310/0x310 [i915]
   ? __seccomp_filter+0x67/0x250
   do_vfs_ioctl+0xa3/0x610
   ? __secure_computing+0x3f/0xd0
   ? syscall_trace_enter+0xcd/0x2e0
   SyS_ioctl+0x79/0x90
   do_syscall_64+0x5b/0xc0
   entry_SYSCALL64_slow_path+0x25/0x25
  RIP: 0033:0x7fd39a33a907
  RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010
  RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907
  RDX: 76323860 RSI: c0406469 RDI: 000e
  RBP: 76323860 R08:  R09: 
  R10: 0038 R11: 0246 R12: c0406469
  R13: 000e R14:  R15: 
  Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 
08 0f 1f 44 00
  RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 
b0ec037df880
  CR2: 0018
  ---[ end trace 2a4103476767c23b ]---

  I walked to my computer 12 minutes later, finding it soft-locked as
  described above.

  I realize that this appears somewhat far removed from the real cause
  of the problem, so please let me know what other data I can provide to
  facilitate the debugging process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sraffa 2780 F pulseaudio
   /dev/snd/controlC0:  sraffa 2780 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 30 17:44:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
  InstallationDate: Installed on 2015-11-02 (514 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. 

[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl

[bp]

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+attachment/4850654/+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/1677673

Title:
  System soft-freezes, BUG: unable to handle kernel NULL pointer
  dereference at 0018 in journalctl

Status in linux package in Ubuntu:
  New

Bug description:
  I just upgraded to 17.04. It appears that now leaving the system
  locked for long enough now makes it unable to respond to any input but
  SysRq.

  This apepars to be the only relevant bit in `journalctl --boot -1`:

  BUG: unable to handle kernel NULL pointer dereference at 0018
  IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  PGD 0 

  Oops: 0002 [#1] SMP
  Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci 
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
  CPU: 3 PID: 3826 Comm: chrome Tainted: G   OE   4.10.0-14-generic 
#16-Ubuntu
  Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
  task: 99ddb372da00 task.stack: b0ec037dc000
  RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  RSP: 0018:b0ec037df880 EFLAGS: 00010246
  RAX: 99dd0367b880 RBX: 0003 RCX: 0003
  RDX:  RSI: 99ddb737e000 RDI: 99de4ad9
  RBP: b0ec037df8d8 R08:  R09: 
  R10:  R11: 0001 R12: 99ddc994a000
  R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000
  FS:  7fd3a0fa7b00() GS:99de5e58() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0018 CR3: 000174607000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
   ? __alloc_pages_nodemask+0xff/0x260
   gen8_alloc_va_range+0x23d/0x470 [i915]
   i915_vma_bind+0x7e/0x170 [i915]
   __i915_vma_do_pin+0x2a5/0x450 [i915]
   i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
   i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
   i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
   ? radix_tree_lookup_slot+0x22/0x50
   ? shmem_getpage_gfp+0xf9/0xc10
   i915_gem_execbuffer2+0xa1/0x1e0 [i915]
   drm_ioctl+0x21b/0x4c0 [drm]
   ? i915_gem_execbuffer+0x310/0x310 [i915]
   ? __seccomp_filter+0x67/0x250
   do_vfs_ioctl+0xa3/0x610
   ? __secure_computing+0x3f/0xd0
   ? syscall_trace_enter+0xcd/0x2e0
   SyS_ioctl+0x79/0x90
   do_syscall_64+0x5b/0xc0
   entry_SYSCALL64_slow_path+0x25/0x25
  RIP: 0033:0x7fd39a33a907
  RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010
  RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907
  RDX: 76323860 RSI: c0406469 RDI: 000e
  RBP: 76323860 R08:  R09: 
  R10: 0038 R11: 0246 R12: c0406469
  R13: 000e R14:  R15: 
  Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 
08 0f 1f 44 00
  RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 
b0ec037df880
  CR2: 0018
  ---[ end trace 2a4103476767c23b ]---

  I walked to my computer 12 minutes later, finding it soft-locked as
  described above.

  I realize that this appears somewhat far removed from the real cause
  of the problem, so please let me know what other data I can provide to
  facilitate the debugging process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sraffa 2780 F pulseaudio
   /dev/snd/controlC0:  sraffa 2780 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 30 17:44:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
  InstallationDate: Installed on 2015-11-02 (514 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: 

[Kernel-packages] [Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl

[bp]

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

Title:
  System soft-freezes, BUG: unable to handle kernel NULL pointer
  dereference at 0018 in journalctl

Status in linux package in Ubuntu:
  New

Bug description:
  I just upgraded to 17.04. It appears that now leaving the system
  locked for long enough now makes it unable to respond to any input but
  SysRq.

  This apepars to be the only relevant bit in `journalctl --boot -1`:

  BUG: unable to handle kernel NULL pointer dereference at 0018
  IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  PGD 0 

  Oops: 0002 [#1] SMP
  Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress 
ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel 
pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci 
i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100
  CPU: 3 PID: 3826 Comm: chrome Tainted: G   OE   4.10.0-14-generic 
#16-Ubuntu
  Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015
  task: 99ddb372da00 task.stack: b0ec037dc000
  RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  RSP: 0018:b0ec037df880 EFLAGS: 00010246
  RAX: 99dd0367b880 RBX: 0003 RCX: 0003
  RDX:  RSI: 99ddb737e000 RDI: 99de4ad9
  RBP: b0ec037df8d8 R08:  R09: 
  R10:  R11: 0001 R12: 99ddc994a000
  R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000
  FS:  7fd3a0fa7b00() GS:99de5e58() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0018 CR3: 000174607000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Call Trace:
   gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
   ? __alloc_pages_nodemask+0xff/0x260
   gen8_alloc_va_range+0x23d/0x470 [i915]
   i915_vma_bind+0x7e/0x170 [i915]
   __i915_vma_do_pin+0x2a5/0x450 [i915]
   i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
   i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
   i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915]
   ? radix_tree_lookup_slot+0x22/0x50
   ? shmem_getpage_gfp+0xf9/0xc10
   i915_gem_execbuffer2+0xa1/0x1e0 [i915]
   drm_ioctl+0x21b/0x4c0 [drm]
   ? i915_gem_execbuffer+0x310/0x310 [i915]
   ? __seccomp_filter+0x67/0x250
   do_vfs_ioctl+0xa3/0x610
   ? __secure_computing+0x3f/0xd0
   ? syscall_trace_enter+0xcd/0x2e0
   SyS_ioctl+0x79/0x90
   do_syscall_64+0x5b/0xc0
   entry_SYSCALL64_slow_path+0x25/0x25
  RIP: 0033:0x7fd39a33a907
  RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010
  RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907
  RDX: 76323860 RSI: c0406469 RDI: 000e
  RBP: 76323860 R08:  R09: 
  R10: 0038 R11: 0246 R12: c0406469
  R13: 000e R14:  R15: 
  Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 
ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 
08 0f 1f 44 00
  RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 
b0ec037df880
  CR2: 0018
  ---[ end trace 2a4103476767c23b ]---

  I walked to my computer 12 minutes later, finding it soft-locked as
  described above.

  I realize that this appears somewhat far removed from the real cause
  of the problem, so please let me know what other data I can provide to
  facilitate the debugging process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sraffa 2780 F pulseaudio
   /dev/snd/controlC0:  sraffa 2780 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 30 17:44:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640
  InstallationDate: Installed on 2015-11-02 (514 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E7250
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet 

[Kernel-packages] [Bug 1672785] Re: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown

[Brad Figg]

** Also affects: linux (Ubuntu Yakkety)
   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/1672785

Title:
  [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver
  device shutdown

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Mellanox has submitted the following patch upstream that's important
  for SR-IOV in Azure.

  Please integrate it into the Mellanox mlx4 drivers for lts-xenial,
  HWE, Zesty, and Azure custom.

  https://patchwork.ozlabs.org/patch/738305/

  From: Jack Morgenstein 

  Some Hypervisors detach VFs from VMs by instantly causing an FLR event
  to be generated for a VF.

  In the mlx4 case, this will cause that VF's comm channel to be disabled
  before the VM has an opportunity to invoke the VF device's "shutdown"
  method.

  For such Hypervisors, there is a race condition between the VF's
  shutdown method and its internal-error detection/reset thread.

  The internal-error detection/reset thread (which runs every 5 seconds) also
  detects a disabled comm channel. If the internal-error detection/reset
  flow wins the race, we still get delays (while that flow tries repeatedly
  to detect comm-channel recovery).

  The cited commit fixed the command timeout problem when the
  internal-error detection/reset flow loses the race.

  This commit avoids the unneeded delays when the internal-error
  detection/reset flow wins.

  Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown")
  Signed-off-by: Jack Morgenstein 
  Reported-by: Simon Xiao 
  Signed-off-by: Tariq Toukan 
  ---
   drivers/net/ethernet/mellanox/mlx4/cmd.c  | 11 +++
   drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++
   include/linux/mlx4/device.h   |  1 +
   3 files changed, 23 insertions(+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672785/+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 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity

[Mike Rushton]

4.8.0-45.48~16.04.1 from xenial updates works

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

Title:
  Mellanox Technologies MT27500 Family [ConnectX-3] no network
  connectivity

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
  Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
  brought up and assigned an ip via MAAS. This is where functionality
  stops on this kernel. Pinging the MAAS server  which is connected
  directly(no switch) fails. There's no traffic  from tcpdump.

  linux-image-generic-hwe-16.04 4.8.0.44.16 fails
  mainline kernel 4.10.0-041000-generic fails
  mainline kernel 4.11.0-041100rc1-generic resolves the issue.

  Both the test server (ppc64le) and MAAS server(amd64) need the
  upgraded kernel to work.

  === 4.4.0-70-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
   Subsystem: IBM MT27500 Family [ConnectX-3]
   Flags: bus master, fast devsel, latency 0, IRQ 473
   Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
   Memory at 2400 (64-bit, prefetchable) [size=128M]
   [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
   Kernel driver in use: mlx4_core
   Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   56000baseCR4/Full
   56000baseSR4/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Advertised link modes:  1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
   4baseSR4/Full
   Advertised pause frame use: Symmetric
   Advertised auto-negotiation: Yes
   Link partner advertised link modes:  4baseCR4/Full
   Link partner advertised pause frame use: No
   Link partner advertised auto-negotiation: Yes
   Speed: 4Mb/s
   Duplex: Full
   Port: Direct Attach Copper
   PHYAD: 0
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0014 (20)
    link ifdown
   Link detected: yes

  dmesg
  [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [3.494624] mlx4_core: Initializing 0008:01:00.0
  [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass

  [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device 
supports 8.0GT/s
  [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports 
x8
  [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 
2014)
  [8.472907] mlx4_en 0008:01:00.0: Activating port:1
  [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings
  [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings
  [8.481694] mlx4_en: 0008:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port
  [8.482320] mlx4_en 0008:01:00.0: registered PHC clock
  [8.485058] mlx4_en 0008:01:00.0: Activating port:2
  [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings
  [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings
  [8.491791] mlx4_en: 0008:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 
stride:1536
  [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port
  [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0
  [8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1

  === 4.11.0-041100rc1-generic ===

  lspci -v
  0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family 
[ConnectX-3]
  Subsystem: IBM MT27500 Family [ConnectX-3]
  Flags: bus master, fast devsel, latency 0, IRQ 473
  Memory at 3fe2 (64-bit, non-prefetchable) [size=1M]
  Memory at 2400 (64-bit, prefetchable) [size=128M]
  [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M]
  Capabilities: 
  Kernel driver in use: mlx4_core
  Kernel modules: mlx4_core

  ethtool enP8p1s0
  Settings for enP8p1s0:
   Supported ports: [ FIBRE ]
   Supported link modes:   1000baseKX/Full
   1baseKX4/Full
   1baseKR/Full
   4baseCR4/Full
  

[Kernel-packages] [Bug 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads

[Steve Beattie]

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7184

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1575

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1576

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

Title:
  apparmor_parser hangs indefinitely when called by multiple threads

Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug surfaced when starting ~50 LXC container with LXD in parallel
  multiple times:

  # Create the containers
  for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done

  # Exectute this loop multiple times until you observe errors.
  for c in c foo{1..50}; do lxc restart $c & done

  After this you can

  ps aux | grep apparmor

  and you should see output similar to:

  root 19774  0.0  0.0  12524  1116 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19775  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19776  0.0  0.0  13592  3224 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19778  0.0  0.0  13592  3384 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19780  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19782  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19783  0.0  0.0  13592  3388 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19784  0.0  0.0  13592  3252 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19794  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
  root 19795  0.0  0.0  13592  3256 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25

  apparmor_parser remains stuck even after all LXC/LXD commands have
  exited.

  dmesg output yields lines like:

  [41902.815174] audit: type=1400 audit(1480191089.678:43):
  apparmor="STATUS" operation="profile_load" profile="unconfined" name
  ="lxd-foo30_" pid=12545 comm="apparmor_parser"

  and cat /proc/12545/stack shows:

  [] aa_remove_profiles+0x88/0x270
  21:19   brauner  [] profile_remove+0x144/0x2e0
  21:19   brauner  [] __vfs_write+0x18/0x40
  21:19   brauner  [] vfs_write+0xb8/0x1b0
  21:19   brauner  [] SyS_write+0x55/0xc0
  21:19   brauner  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  21:19   brauner  [] 0x

  This looks like a potential kernel bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1645037/+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 1660842] Re: apparmor not checking error if security_pin_fs() fails

[Steve Beattie]

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7184

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1575

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1576

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

Title:
  apparmor not checking error if security_pin_fs() fails

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  The error condition of security_pin_fs() was not being checked which
  will result can result in an oops or use after free, due to the fs pin
  count not being incremented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660842/+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 1648903] Re: Permission denied and inconsistent behavior in complain mode with 'ip netns list' command

[Steve Beattie]

This was incorrectly closed in the kernel security update, re-opening.

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7184

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

Title:
  Permission denied and inconsistent behavior in complain mode with 'ip
  netns list' command

Status in AppArmor:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  On 16.04 with Ubuntu 4.4.0-53.74-generic 4.4.30

  With this profile:

  #include 

  profile test (attach_disconnected,complain) {
  #include 

  /{,usr/}{,s}bin/ip ixr,  # COMMENT OUT THIS RULE TO SEE WEIRDNESS

  capability sys_admin,
  capability net_admin,
  capability sys_ptrace,

  network netlink raw,

  ptrace (trace),

  / r,
  /run/netns/ rw,
  /run/netns/* rw,

  mount options=(rw, rshared) -> /run/netns/,
  mount options=(rw, bind) /run/netns/ -> /run/netns/,
  mount options=(rw, bind) / -> /run/netns/*,
  mount options=(rw, rslave) /,
  mount options=(rw, rslave), # LP: #1648245
  umount /sys/,
  umount /,

  
  /bin/dash ixr,
  }

  Everything is fine when I do:
  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  $

  and there are no ALLOWED entries in syslog.

  
  However, if I comment out the '/{,usr/}{,s}bin/ip ixr,' rule, I get a 
permission denied and a bunch of ALLOWED entries:

  $ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p 
test -- sh -c 'ip netns list'
  open("/proc/self/ns/net"): Permission denied
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.862629] audit: type=1400 
audit(1481324889.782:469): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="test" pid=4314 comm="apparmor_parser"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870339] audit: type=1400 
audit(1481324889.790:470): apparmor="ALLOWED" operation="exec" profile="test" 
name="/bin/ip" pid=4317 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 
ouid=0 target="test//null-/bin/ip"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870559] audit: type=1400 
audit(1481324889.790:471): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/etc/ld.so.cache" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870628] audit: type=1400 
audit(1481324889.790:472): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libdl-2.23.so" 
pid=4317 comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870703] audit: type=1400 
audit(1481324889.790:473): apparmor="ALLOWED" operation="open" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870861] audit: type=1400 
audit(1481324889.790:474): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/bin/ip" pid=4317 comm="ip" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870913] audit: type=1400 
audit(1481324889.790:475): apparmor="ALLOWED" operation="file_mprotect" 
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=4317 
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871019] audit: type=1400 
audit(1481324889.790:476): apparmor="ALLOWED" operation="create" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871066] audit: type=1400 
audit(1481324889.790:477): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871099] audit: type=1400 
audit(1481324889.790:478): apparmor="ALLOWED" operation="setsockopt" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871128] audit: type=1400 
audit(1481324889.790:479): apparmor="ALLOWED" operation="bind" 
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink" 
sock_type="raw" protocol=0 requested_mask="bind" denied_mask="bind"
  Dec  9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871672] audit: type=1400 
audit(1481324889.794:480): apparmor="ALLOWED" operation="getsockname" 
profile="test//null-/bin/ip" pid=4317 

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Tags added: kernel-key

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [ 5281.179615]  [<03ff805df114>] xfs_log_force+0x44/0x100 [xfs]
  [ 5281.179640]  [<03ff805ec668>] xfsaild+0x170/0x798 [xfs]
  [ 

[Kernel-packages] [Bug 1645521] Re: [Feature] ISH (Intel Sensor Hub) support

[Tim Gardner]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Robert Hooker (sarvatt)
   Status: Fix Committed

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

Title:
  [Feature] ISH (Intel Sensor Hub) support

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Integrete ISH kernel driver and ISH driver should provoide following 
interface to user
  (1) Batch ModeGet the hardware batch buffer size/count,Set the batch 
timeout value
  (2) Wakeup/non-wakeupchecking if one sensor is wakeup instance or 
non-wakeup instance.For wakeup instance, when batch buffer is full or wait 
timeout, system must be woken up and receive batched sensor events.
  (3) Timestamp  expose the sensor event timestamp to user space for sync
  (4) physical sensors-support exposing following physical 
sensors:Accelerometer,Gyroscope,Magnetic,Field,Pressure,Light,Proximity
  (5) Advanced sensorsupport exposing following advanced sensors:
  Gravity,Linear Acceleration,Rotation Vector,Orientation,Game 
Rotation,Geomagentic Rotation,Step Detector,Step Counter,Terminal,Significant 
motion,Wakeup Gesture,Glance Gesture,Tilt,PanZoon,Lift and Look
  (6)multiple sensor instance support
  (7)private command support  support set/get path for private command set 
and response get, because some advanced sensor needs different special command 
to work properly.
  (8)User defined sensor support--- exposing non-pre-defined sensors.
  Because customer may add a new sensor in firmware, and hope sensor driver can 
expose it as a unknown sensor automatically, then application can use it 
directly without any code change.

  HW: Broxton-p

  Upstream Schedule:
  Basic Sensor Driver: 4.9
  Advanced Sensor Driver: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645521/+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 1676918] Re: blackscreen when trying to resume from suspend

[Daniel Holz]

Got a blackscreen with Kernel 4.11. Unfortunately kern.log and syslog
don't have any entries about it.

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

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

Title:
  blackscreen when trying to resume from suspend

Status in gnome-power-manager package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1677622] Re: missing ramdisks in latest amd64 kernel snap

[Federico Gimenez]

The oroblem happens on an amd64 ubuntu-core system, no apport-collect in
there, please let me know how can I get the required logs on that
system.

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

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

Title:
  missing ramdisks in latest amd64 kernel snap

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While running the snapd suite using the amd64 kernel snap from the
  beta channel (rev 59) we got this error running [1]:

  2017-03-30 09:36:41 Error preparing 
linode:ubuntu-core-16-64:tests/main/snap-auto-mount : 
  -
  [ ... ]
  Create a ramdisk with the testrootorg-store.account-key assertion
  + mkfs.vfat /dev/ram0
  /dev/ram0: No such file or directory
  mkfs.fat 3.0.28 (2015-05-16)

  There are no /dev/ram* files on the ubuntu-core system, not sure if
  this is intended and we should adapt to it. It was created with:

  $ sudo /snap/bin/ubuntu-image --image-size 3G -c beta -O . ./models
  /pc-amd64.model

  and, once logged to the ubuntu-core system, the version:

  $ $ cat /proc/version_signature
  Ubuntu 4.4.0-67.88-generic 4.4.49

  Thanks,

  [1] https://github.com/snapcore/snapd/blob/master/tests/main/snap-
  auto-mount/task.yaml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677622/+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 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

[Huân Đoàn Ngọc]

** Also affects: linux (Arch Linux)
   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/1584407

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20150930/dswload-210)

Status in linux package in Ubuntu:
  Expired
Status in linux package in Arch Linux:
  New

Bug description:
  [ 0.016192] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20150930/dswload-210)
  [ 0.016195] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20150930/psobject-227)
  [ 0.016222] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20150930/tbxfload-193)
  [ 0.021348] ACPI Error: 1 table load failures, 7 successful 
(20150930/tbxfload-214)

  
  I have noticed this ACPI error persisting in my syslog and dmesg. Based on 
what I have learnt from  ACPI, acpitool -w and lspci, I think the error is 
related to Namespaces provided in the DDST on \_SB_.PCI0.XHC_.RHUB.HS11, which 
I think concerns the Root → System bus tree → PCI bus  → USB controller: Intel 
Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) in my system. I 
have not found what .RHUB.HS11 refers too. I have tried changing my UEFI USB 
settings but to no avail. Appreciate help to fix this bug. 

  I reported it as a question
  https://answers.launchpad.net/ubuntu/+question/293489 and to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553690.
  https://launchpad.net/~penalvch advice me to make this ubuntu-bug
  report.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ uname -r
  4.4.0-22-generic

  MB Bios: ASUS z170m-plus version 0704

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sunbear1604   1905 F pulseaudio
   /dev/snd/controlC0:  sunbear1604   1905 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 07:48:53 2016
  HibernationDevice: RESUME=UUID=c1eef599-9978-461e-a399-a04370b6ae59
  InstallationDate: Installed on 2016-05-01 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=69a55da3-4a70-4239-8e7e-2430ceac525d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0704
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0704:bd02/18/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520

[Carl Mueller]

Fix not showing in 4.4.0-71 either. Just FYI in case it was intended.

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

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  My processor does not appear to be utilizing and idling states deeper
  than C3.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carl   2446 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 13 08:57:06 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88
  InstallationDate: Installed on 2017-03-09 (3 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IwConfig:
   lono wireless extensions.
   
   wlp2s0no wireless extensions.
  MachineType: Dell Inc. Precision 5520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed 
root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0X41RR
  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:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1645521] Re: [Feature] ISH (Intel Sensor Hub) support

[Robert Hooker]

** Information type changed from Proprietary to Public

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Robert Hooker (sarvatt)

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

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

Title:
  [Feature] ISH (Intel Sensor Hub) support

Status in intel:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Integrete ISH kernel driver and ISH driver should provoide following 
interface to user
  (1) Batch ModeGet the hardware batch buffer size/count,Set the batch 
timeout value
  (2) Wakeup/non-wakeupchecking if one sensor is wakeup instance or 
non-wakeup instance.For wakeup instance, when batch buffer is full or wait 
timeout, system must be woken up and receive batched sensor events.
  (3) Timestamp  expose the sensor event timestamp to user space for sync
  (4) physical sensors-support exposing following physical 
sensors:Accelerometer,Gyroscope,Magnetic,Field,Pressure,Light,Proximity
  (5) Advanced sensorsupport exposing following advanced sensors:
  Gravity,Linear Acceleration,Rotation Vector,Orientation,Game 
Rotation,Geomagentic Rotation,Step Detector,Step Counter,Terminal,Significant 
motion,Wakeup Gesture,Glance Gesture,Tilt,PanZoon,Lift and Look
  (6)multiple sensor instance support
  (7)private command support  support set/get path for private command set 
and response get, because some advanced sensor needs different special command 
to work properly.
  (8)User defined sensor support--- exposing non-pre-defined sensors.
  Because customer may add a new sensor in firmware, and hope sensor driver can 
expose it as a unknown sensor automatically, then application can use it 
directly without any code change.

  HW: Broxton-p

  Upstream Schedule:
  Basic Sensor Driver: 4.9
  Advanced Sensor Driver: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1645521/+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 1677297] Re: [Zesty] rename msm_emac to qcom_emac

[Timur Tabi]

Yes, the REP has the Atheros 8033, which uses the same driver.

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

Title:
  [Zesty] rename msm_emac to qcom_emac

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  We landed a patch to support msm_emac module in initrd for amberwing 
platforms. But the upstream driver has since been renamed to qcom_emac. This 
module is needed in d-i's initrd so that these nics can be used to d-i install 
the system. The driver already exists in the zesty kernel under 
drivers/net/ethernet/qualcomm/emac/

  Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add
  qcom_emac to initrd, and change the module name to qcom_emac.

  [Test Case]
  D-I install zesty on amberwing platform and notice that DI does not recognize 
the onboard two port nic.

  [Regression Potential]
  At present this driver applies only to amberwing systems, any regression will 
be isolated to amberwing platforms. The over all risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677297/+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 1677622] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1677622

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

Title:
  missing ramdisks in latest amd64 kernel snap

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While running the snapd suite using the amd64 kernel snap from the
  beta channel (rev 59) we got this error running [1]:

  2017-03-30 09:36:41 Error preparing 
linode:ubuntu-core-16-64:tests/main/snap-auto-mount : 
  -
  [ ... ]
  Create a ramdisk with the testrootorg-store.account-key assertion
  + mkfs.vfat /dev/ram0
  /dev/ram0: No such file or directory
  mkfs.fat 3.0.28 (2015-05-16)

  There are no /dev/ram* files on the ubuntu-core system, not sure if
  this is intended and we should adapt to it. It was created with:

  $ sudo /snap/bin/ubuntu-image --image-size 3G -c beta -O . ./models
  /pc-amd64.model

  and, once logged to the ubuntu-core system, the version:

  $ $ cat /proc/version_signature
  Ubuntu 4.4.0-67.88-generic 4.4.49

  Thanks,

  [1] https://github.com/snapcore/snapd/blob/master/tests/main/snap-
  auto-mount/task.yaml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677622/+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 1677611] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was peacefully typed comment in firefox when it suddenly freezes. In
  process list it become 'Z' state.

  My kernel log displayed this (and I think this is a kernel bug):

  
  Mar 30 16:27:20 x220 kernel: [17792.860827] [ cut here 
]
  Mar 30 16:27:20 x220 kernel: [17792.861119] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!
  Mar 30 16:27:20 x220 kernel: [17792.861594] invalid opcode:  [#2] SMP
  Mar 30 16:27:20 x220 kernel: [17792.861839] Modules linked in: ebtable_filter 
ebtables ip6table_filter ip6_tables ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 
xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter xt_conntrack nf_nat   nf_conntrack br_netfilter 
bridge stp llc aufs binfmt_misc snd_usb_audio snd_usbmidi_lib snd_hwdep 
snd_rawmidi snd_seq_device snd_pcm snd_timer uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 iwldvm 
mac80211 intel_rapl   x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc thinkpad_acpi nvram snd soundcore aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf iwlwifi 
input_leds joydev serio_rawcfg80211 lpc_ich
  Mar 30 16:27:20 x220 kernel: [17792.865910]  shpchp mei_me mei mac_hid cuse 
ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc sunrpc ppdev lp parport ip_tables x_tables 
autofs4 uas usb_storage btrfs raid10 raid456  async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear wacom hid_generic usbhid hid i915 i2c_algo_bit e1000e psmouse 
drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops sdhci_pci ptp 
libahci drm sdhci pps_core   wmi fjes video
  Mar 30 16:27:20 x220 kernel: [17792.868607] CPU: 0 PID: 3469 Comm: Socket 
Thread Tainted: G UD 4.10.0-14-generic #16-Ubuntu
  Mar 30 16:27:20 x220 kernel: [17792.869146] Hardware name: LENOVO 
4298R86/4298R86, BIOS 8DET56WW (1.26 ) 12/01/2011
  Mar 30 16:27:20 x220 kernel: [17792.869584] task: 91084c995a00 
task.stack: a24d42a1c000
  Mar 30 16:27:20 x220 kernel: [17792.869936] RIP: 
0010:__migration_entry_wait+0x16a/0x180
  Mar 30 16:27:20 x220 kernel: [17792.870244] RSP: 0018:a24d42a1fd68 
EFLAGS: 00010246
  Mar 30 16:27:20 x220 kernel: [17792.870544] RAX: 0017c0048078 RBX: 
e7428673c9f0 RCX: e7428673c9f0
  Mar 30 16:27:20 x220 kernel: [17792.870933] RDX: 0001 RSI: 
9107dcf279d0 RDI: e742845c4e80
  Mar 30 16:27:20 x220 kernel: [17792.871319] RBP: a24d42a1fd80 R08: 
91084c816c80 R09: 91084c816c80
  Mar 30 16:27:20 x220 kernel: [17792.871706] R10: 7f0f9a900290 R11: 
7f0f9ac37750 R12: e742845c4e80
  Mar 30 16:27:20 x220 kernel: [17792.872094] R13: 3e11713a R14: 
a24d42a1fe30 R15: 9107eb2d00c8
  Mar 30 16:27:20 x220 kernel: [17792.872481] FS:  7f0f840fb700() 
GS:91085e20() knlGS:
  Mar 30 16:27:20 x220 kernel: [17792.872918] CS:  0010 DS:  ES:  CR0: 
80050033
  Mar 30 16:27:20 x220 kernel: [17792.873231] CR2: 7f2adeb02fe0 CR3: 
0001ab122000 CR4: 000406f0
  Mar 30 16:27:20 x220 kernel: [17792.873623] Call Trace:
  Mar 30 16:27:20 x220 kernel: [17792.873775]  migration_entry_wait+0x74/0x80
  Mar 30 16:27:20 x220 kernel: [17792.874020]  do_swap_page+0x5b3/0x770
  Mar 30 16:27:20 x220 kernel: [17792.874233]  handle_mm_fault+0x873/0x1360
  Mar 30 16:27:20 x220 kernel: [17792.874467]  __do_page_fault+0x23e/0x4e0
  Mar 30 16:27:20 x220 kernel: [17792.874705]  do_page_fault+0x22/0x30
  Mar 30 16:27:20 x220 kernel: [17792.874922]  page_fault+0x28/0x30
  Mar 30 16:27:20 x220 kernel: [17792.875133] RIP: 0033:0x7f0f8b27c5ce
  Mar 30 16:27:20 x220 kernel: [17792.875352] RSP: 002b:7f0f840fa858 
EFLAGS: 00010206
  Mar 30 16:27:20 x220 kernel: [17792.875660] RAX:  RBX: 
7f0f7ded4d58 RCX: 7f0f63208000
  Mar 30 16:27:20 x220 kernel: [17792.876061] RDX:  RSI: 
7f0f0353a7c8 RDI: 7f0eb98ec0a8
  Mar 30 16:27:20 x220 kernel: [17792.876503] RBP: 0001 R08: 
0011 R09: 7f0f9a900290
  Mar 30 16:27:20 x220 kernel: [17792.876932] R10: 7f0f9a900290 R11: 
7f0f9ac37750 R12: 7f0f7ded4d00
  Mar 30 16:27:20 x220 kernel: [17792.877364] R13: 7f0f079630a0 R14: 
0001 R15: 

[Kernel-packages] [Bug 1677622] [NEW] missing ramdisks in latest amd64 kernel snap

[Federico Gimenez]

Public bug reported:

While running the snapd suite using the amd64 kernel snap from the beta
channel (rev 59) we got this error running [1]:

2017-03-30 09:36:41 Error preparing 
linode:ubuntu-core-16-64:tests/main/snap-auto-mount : 
-
[ ... ]
Create a ramdisk with the testrootorg-store.account-key assertion
+ mkfs.vfat /dev/ram0
/dev/ram0: No such file or directory
mkfs.fat 3.0.28 (2015-05-16)

There are no /dev/ram* files on the ubuntu-core system, not sure if this
is intended and we should adapt to it. It was created with:

$ sudo /snap/bin/ubuntu-image --image-size 3G -c beta -O . ./models/pc-
amd64.model

and, once logged to the ubuntu-core system, the version:

$ $ cat /proc/version_signature
Ubuntu 4.4.0-67.88-generic 4.4.49

Thanks,

[1] https://github.com/snapcore/snapd/blob/master/tests/main/snap-auto-
mount/task.yaml

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1677622

Title:
  missing ramdisks in latest amd64 kernel snap

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While running the snapd suite using the amd64 kernel snap from the
  beta channel (rev 59) we got this error running [1]:

  2017-03-30 09:36:41 Error preparing 
linode:ubuntu-core-16-64:tests/main/snap-auto-mount : 
  -
  [ ... ]
  Create a ramdisk with the testrootorg-store.account-key assertion
  + mkfs.vfat /dev/ram0
  /dev/ram0: No such file or directory
  mkfs.fat 3.0.28 (2015-05-16)

  There are no /dev/ram* files on the ubuntu-core system, not sure if
  this is intended and we should adapt to it. It was created with:

  $ sudo /snap/bin/ubuntu-image --image-size 3G -c beta -O . ./models
  /pc-amd64.model

  and, once logged to the ubuntu-core system, the version:

  $ $ cat /proc/version_signature
  Ubuntu 4.4.0-67.88-generic 4.4.49

  Thanks,

  [1] https://github.com/snapcore/snapd/blob/master/tests/main/snap-
  auto-mount/task.yaml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677622/+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 1677297] RE: Zesty use qcom_emac instead of msm_emac.

[Manoj Iyer]

> It's not unrelated. That is the actusl phy on the SDP.

and the same for REPs? our target cert platform?

> 
> From: Manoj Iyer [manoj.i...@canonical.com]
> Sent: Wednesday, March 29, 2017 10:11 PM
> To: Timur Tabi
> Cc: Manoj Iyer; Andrew Cloke; David Douglas; 1677...@bugs.launchpad.net
> Subject: Re: Zesty use qcom_emac instead of msm_emac.
>
> That is hard to SRU, we don't want to be adding unrelated modules to DI.
>
> With at803x loaded
> ==
> ubuntu@ubuntu:~$ uname -a
> Linux ubuntu 4.10.0-10-generic #13~ubunturc2+build.1-Ubuntu SMP Tue Feb 28
> 23:33:09 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux
> ubuntu@ubuntu:~$
> ubuntu@ubuntu:~$ lsmod | grep at803x
> at803x
> ubuntu@ubuntu:~$ lsmod | grep qcom
> qcom_emac  40960  0
> ubuntu@ubuntu:~$
>
> eth0  Link encap:Ethernet  HWaddr 8c:fd:f0:06:90:cd
>   inet addr:10.228.66.102  Bcast:10.228.66.255  Mask:255.255.255.0
>
> So clearly as a side effect of loading at803x qcom_emac is able to get an
> IP address. But I am afraid this is not something we can justify as an
> SRU.
>
>
> On Wed, 29 Mar 2017, Timur Tabi wrote:
>
>> Assuming that you did back-port enough, then you should try loading
>> at803x.ko first.  Technically, there is an erratum with that PHY that the
>> driver resolves, although I've never seen it make a difference until today.
>>
>> On 03/29/2017 04:50 PM, Manoj Iyer wrote:
>>> Timur,
>>>
>>> Based on https://bugs.launchpad.net/bandera/ubuntu-17.04/+bug/1657261 yes
>>> this was backported from 4.11 to 4.10 and commited to zesty and to xenial.
>>>
>>> On Wed, 29 Mar 2017, Timur Tabi wrote:
>>>
 Did you back-port driver from 4.11?

 On 03/29/2017 03:55 PM, Manoj Iyer wrote:
>
> I have a public bug to track the qcom_emac replacement for msm_emac. This
> is currently blocked because qcom_emac that is in Zesty is unable to get
> DHCP leases. Needs a fix from qti to the driver before we can sru the
> change. It is my understanding that once we sru the required patches we
> can request for a DI respin in zesty to pick up the updated kernel.
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677297
>
> --
> 
> Manoj Iyer
> Ubuntu/Canonical
> ARM Servers - Cloud
> 


>>>
>>> --
>>> 
>>> Manoj Iyer
>>> Ubuntu/Canonical
>>> ARM Servers - Cloud
>>> 
>>
>>
>
> --
> 
> Manoj Iyer
> Ubuntu/Canonical
> ARM Servers - Cloud
> 
>
>

--

Manoj Iyer
Ubuntu/Canonical
ARM Servers - Cloud


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

Title:
  [Zesty] rename msm_emac to qcom_emac

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  We landed a patch to support msm_emac module in initrd for amberwing 
platforms. But the upstream driver has since been renamed to qcom_emac. This 
module is needed in d-i's initrd so that these nics can be used to d-i install 
the system. The driver already exists in the zesty kernel under 
drivers/net/ethernet/qualcomm/emac/

  Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add
  qcom_emac to initrd, and change the module name to qcom_emac.

  [Test Case]
  D-I install zesty on amberwing platform and notice that DI does not recognize 
the onboard two port nic.

  [Regression Potential]
  At present this driver applies only to amberwing systems, any regression will 
be isolated to amberwing platforms. The over all risk of regression is low.

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

Re: [Kernel-packages] [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

[js1]

Just happened on 4.10.5-041005-generic #201703220931.  Did not
experience with 4.10.1.

[  685.335137] irq 17: nobody cared (try booting with the "irqpoll" option)
[  685.335145] CPU: 3 PID: 0 Comm: swapper/3 Not tainted
4.10.5-041005-generic #201703220931
[  685.335146] Hardware name:  /DP35DP, BIOS
DPP3510J.86A.0572.2009.0715.2346 07/15/2009
[  685.335146] Call Trace:
[  685.335149]  
[  685.335155]  dump_stack+0x63/0x81
[  685.335157]  __report_bad_irq+0x35/0xc0
[  685.335158]  note_interrupt+0x234/0x270
[  685.335160]  handle_irq_event_percpu+0x54/0x80
[  685.335161]  handle_irq_event+0x3b/0x60
[  685.335162]  handle_fasteoi_irq+0x8f/0x140
[  685.335165]  handle_irq+0x1a/0x30
[  685.335168]  do_IRQ+0x46/0xd0
[  685.335170]  common_interrupt+0x89/0x89
[  685.335172] RIP: 0010:mwait_idle+0x66/0x160
[  685.335173] RSP: 0018:ab09006a3e80 EFLAGS: 0246 ORIG_RAX:
ff1e
[  685.335174] RAX:  RBX: 9ac866bfc080 RCX: 
[  685.335175] RDX:  RSI:  RDI: 
[  685.335176] RBP: ab09006a3e98 R08: 0100 R09: 
[  685.335177] R10:  R11:  R12: 0003
[  685.335177] R13: 9ac866bfc080 R14:  R15: 
[  685.335178]  
[  685.335181]  arch_cpu_idle+0xf/0x20
[  685.335182]  default_idle_call+0x23/0x30
[  685.335184]  do_idle+0x16f/0x200
[  685.335185]  cpu_startup_entry+0x71/0x80
[  685.335188]  start_secondary+0x154/0x190
[  685.335189]  start_cpu+0x14/0x14
[  685.335190] handlers:
[  685.335193] [] usb_hcd_irq
[  685.335195] [] usb_hcd_irq
[  685.335198] [] ata_bmdma_interrupt
[  685.335199] Disabling IRQ #17

On Tue, Feb 14, 2017 at 2:16 AM, Jiann-Ming Su  wrote:
> Just happened with a 4.8 kernel:
>
> [ 1317.106797] irq 17: nobody cared (try booting with the "irqpoll" option)
> [ 1317.106804] CPU: 3 PID: 0 Comm: swapper/3 Not tainted
> 4.8.17-040817-generic #201701090438
> [ 1317.106805] Hardware name:  /DP35DP, BIOS
> DPP3510J.86A.0572.2009.0715.2346 07/15/2009
> [ 1317.106807]  0086 3d3abaf3984afb2f 8e3f2bd83e78
> b5413362
> [ 1317.106810]  8e3f1f391c00 8e3f1f391cb4 8e3f2bd83ea8
> b50e24f5
> [ 1317.106812]  8e3f1f391c00  b5f58dc0
> 00e1
> [ 1317.106814] Call Trace:
> [ 1317.106816][] dump_stack+0x63/0x81
> [ 1317.106825]  [] __report_bad_irq+0x35/0xc0
> [ 1317.106827]  [] note_interrupt+0x243/0x290
> [ 1317.106829]  [] handle_irq_event_percpu+0x54/0x80
> [ 1317.106830]  [] handle_irq_event+0x3e/0x60
> [ 1317.106832]  [] handle_fasteoi_irq+0x9f/0x150
> [ 1317.106834]  [] handle_irq+0x1a/0x30
> [ 1317.106836]  [] do_IRQ+0x4b/0xd0
> [ 1317.106839]  [] common_interrupt+0x82/0x82
> [ 1317.106839][] ? mwait_idle+0x78/0x170
> [ 1317.106843]  [] arch_cpu_idle+0xf/0x20
> [ 1317.106845]  [] default_idle_call+0x2a/0x40
> [ 1317.106846]  [] cpu_startup_entry+0x2ec/0x350
> [ 1317.106848]  [] start_secondary+0x151/0x190
> [ 1317.106849] handlers:
> [ 1317.106853] [] usb_hcd_irq
> [ 1317.106854] [] usb_hcd_irq
> [ 1317.106857] [] ata_bmdma_interrupt
> [ 1317.106859] Disabling IRQ #17
>
> On Sun, Feb 5, 2017 at 11:41 AM, Jiann-Ming Su  wrote:
>> Seems to be happening more frequently on 4.4 kernels.  Just happened
>> again on 4.4.0-57.  I'm also running without the nvidia proprietary
>> drivers, just nouveau.
>>
>> [  476.598833] irq 17: nobody cared (try booting with the "irqpoll" option)
>> [  476.598843] CPU: 1 PID: 0 Comm: swapper/1 Not tainted
>> 4.4.0-57-generic #78-Ubuntu
>> [  476.598845] Hardware name:  /DP35DP, BIOS
>> DPP3510J.86A.0572.2009.0715.2346 07/15/2009
>> [  476.598847]  0086 bc9f5848ed8acd71 88012bc83e60
>> 813f6f33
>> [  476.598851]  8800354c9600 8800354c96d4 88012bc83e88
>> 810ddd03
>> [  476.598855]  8800354c9600  0011
>> 88012bc83ec0
>> [  476.598858] Call Trace:
>> [  476.598861][] dump_stack+0x63/0x90
>> [  476.598874]  [] __report_bad_irq+0x33/0xc0
>> [  476.598877]  [] note_interrupt+0x247/0x290
>> [  476.598880]  [] handle_irq_event_percpu+0x167/0x1d0
>> [  476.59]  [] handle_irq_event+0x3e/0x60
>> [  476.598890]  [] handle_fasteoi_irq+0x99/0x150
>> [  476.598894]  [] handle_irq+0x1d/0x30
>> [  476.598897]  [] do_IRQ+0x4b/0xd0
>> [  476.598901]  [] common_interrupt+0x82/0x82
>> [  476.598902][] ? mwait_idle+0x76/0x180
>> [  476.598906]  [] arch_cpu_idle+0xf/0x20
>> [  476.598909]  [] default_idle_call+0x2a/0x40
>> [  476.598911]  [] cpu_startup_entry+0x2f1/0x350
>> [  476.598914]  [] start_secondary+0x154/0x190
>> [  476.598916] handlers:
>> [  476.598920] [] usb_hcd_irq
>> [  476.598922] [] usb_hcd_irq
>> [  476.598925] [] ata_bmdma_interrupt
>> [  476.598926] Disabling IRQ #17
>>
>> On Wed, Nov 9, 2016 at 3:18 AM, Christopher M. 

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[Daniel Drake]

Chris and I don't have experience with the G752 series but looking at
one of the dumps from above:

I: Bus=0003 Vendor=0b05 Product=1837 Version=0110
N: Name="ASASTeK COMPUTER INC. ROG MacroKey"
P: Phys=usb-:00:14.0-8/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/0003:0B05:1837.0004/input/input7
U: Uniq=
H: Handlers=sysrq kbd event7 leds
B: PROP=0
B: EV=120013
B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
B: MSC=10
B: LED=1f

The patches you linked to add support for this ID 0B05:1837 so I think
the function key issue is now solved, as soon as you are able to
build/run such a kernel.

No ideas about the touchpad issue. I would next check if there are
interrupts registered against that device. Another thing to try is
making sure that the intel pin control driver being used on this
platform is built into the kernel, not a module.

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 

[Kernel-packages] [Bug 1677611] [NEW] kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[George Shuklin]

Public bug reported:

I was peacefully typed comment in firefox when it suddenly freezes. In
process list it become 'Z' state.

My kernel log displayed this (and I think this is a kernel bug):


Mar 30 16:27:20 x220 kernel: [17792.860827] [ cut here ]
Mar 30 16:27:20 x220 kernel: [17792.861119] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!
Mar 30 16:27:20 x220 kernel: [17792.861594] invalid opcode:  [#2] SMP
Mar 30 16:27:20 x220 kernel: [17792.861839] Modules linked in: ebtable_filter 
ebtables ip6table_filter ip6_tables ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 
xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter xt_conntrack nf_nat   nf_conntrack br_netfilter 
bridge stp llc aufs binfmt_misc snd_usb_audio snd_usbmidi_lib snd_hwdep 
snd_rawmidi snd_seq_device snd_pcm snd_timer uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media arc4 iwldvm 
mac80211 intel_rapl   x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc thinkpad_acpi nvram snd soundcore aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf iwlwifi 
input_leds joydev serio_rawcfg80211 lpc_ich
Mar 30 16:27:20 x220 kernel: [17792.865910]  shpchp mei_me mei mac_hid cuse 
ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc sunrpc ppdev lp parport ip_tables x_tables 
autofs4 uas usb_storage btrfs raid10 raid456  async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear wacom hid_generic usbhid hid i915 i2c_algo_bit e1000e psmouse 
drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops sdhci_pci ptp 
libahci drm sdhci pps_core   wmi fjes video
Mar 30 16:27:20 x220 kernel: [17792.868607] CPU: 0 PID: 3469 Comm: Socket 
Thread Tainted: G UD 4.10.0-14-generic #16-Ubuntu
Mar 30 16:27:20 x220 kernel: [17792.869146] Hardware name: LENOVO 
4298R86/4298R86, BIOS 8DET56WW (1.26 ) 12/01/2011
Mar 30 16:27:20 x220 kernel: [17792.869584] task: 91084c995a00 task.stack: 
a24d42a1c000
Mar 30 16:27:20 x220 kernel: [17792.869936] RIP: 
0010:__migration_entry_wait+0x16a/0x180
Mar 30 16:27:20 x220 kernel: [17792.870244] RSP: 0018:a24d42a1fd68 EFLAGS: 
00010246
Mar 30 16:27:20 x220 kernel: [17792.870544] RAX: 0017c0048078 RBX: 
e7428673c9f0 RCX: e7428673c9f0
Mar 30 16:27:20 x220 kernel: [17792.870933] RDX: 0001 RSI: 
9107dcf279d0 RDI: e742845c4e80
Mar 30 16:27:20 x220 kernel: [17792.871319] RBP: a24d42a1fd80 R08: 
91084c816c80 R09: 91084c816c80
Mar 30 16:27:20 x220 kernel: [17792.871706] R10: 7f0f9a900290 R11: 
7f0f9ac37750 R12: e742845c4e80
Mar 30 16:27:20 x220 kernel: [17792.872094] R13: 3e11713a R14: 
a24d42a1fe30 R15: 9107eb2d00c8
Mar 30 16:27:20 x220 kernel: [17792.872481] FS:  7f0f840fb700() 
GS:91085e20() knlGS:
Mar 30 16:27:20 x220 kernel: [17792.872918] CS:  0010 DS:  ES:  CR0: 
80050033
Mar 30 16:27:20 x220 kernel: [17792.873231] CR2: 7f2adeb02fe0 CR3: 
0001ab122000 CR4: 000406f0
Mar 30 16:27:20 x220 kernel: [17792.873623] Call Trace:
Mar 30 16:27:20 x220 kernel: [17792.873775]  migration_entry_wait+0x74/0x80
Mar 30 16:27:20 x220 kernel: [17792.874020]  do_swap_page+0x5b3/0x770
Mar 30 16:27:20 x220 kernel: [17792.874233]  handle_mm_fault+0x873/0x1360
Mar 30 16:27:20 x220 kernel: [17792.874467]  __do_page_fault+0x23e/0x4e0
Mar 30 16:27:20 x220 kernel: [17792.874705]  do_page_fault+0x22/0x30
Mar 30 16:27:20 x220 kernel: [17792.874922]  page_fault+0x28/0x30
Mar 30 16:27:20 x220 kernel: [17792.875133] RIP: 0033:0x7f0f8b27c5ce
Mar 30 16:27:20 x220 kernel: [17792.875352] RSP: 002b:7f0f840fa858 EFLAGS: 
00010206
Mar 30 16:27:20 x220 kernel: [17792.875660] RAX:  RBX: 
7f0f7ded4d58 RCX: 7f0f63208000
Mar 30 16:27:20 x220 kernel: [17792.876061] RDX:  RSI: 
7f0f0353a7c8 RDI: 7f0eb98ec0a8
Mar 30 16:27:20 x220 kernel: [17792.876503] RBP: 0001 R08: 
0011 R09: 7f0f9a900290
Mar 30 16:27:20 x220 kernel: [17792.876932] R10: 7f0f9a900290 R11: 
7f0f9ac37750 R12: 7f0f7ded4d00
Mar 30 16:27:20 x220 kernel: [17792.877364] R13: 7f0f079630a0 R14: 
0001 R15: 7f0f7ded4d00
Mar 30 16:27:20 x220 kernel: [17792.877769] Code: ff ff ff 4c 89 e7 e8 86 a2 f8 
ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 
d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 1c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 
1b eb
Mar 30 16:27:20 x220 kernel: [17792.878901] RIP: 
__migration_entry_wait+0x16a/0x180 RSP: a24d42a1fd68
Mar 30 16:27:20 x220 kernel: [17792.879374] ---[ end trace 13a363fde0dac0fd ]---

ProblemType: Bug

[Kernel-packages] [Bug 1677600] [NEW] Xenial update to v4.4.58 stable release

[Tim Gardner]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.4.58 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.4.58 stable release shall be
applied:

net/openvswitch: Set the ipv6 source tunnel key address attribute correctly
net: bcmgenet: Do not suspend PHY if Wake-on-LAN is enabled
net: properly release sk_frag.page
amd-xgbe: Fix jumbo MTU processing on newer hardware
net: unix: properly re-increment inflight counter of GC discarded candidates
net/mlx5: Increase number of max QPs in default profile
net/mlx5e: Count LRO packets correctly
net: bcmgenet: remove bcmgenet_internal_phy_setup()
ipv4: provide stronger user input validation in nl_fib_input()
socket, bpf: fix sk_filter use after free in sk_clone_lock
tcp: initialize icsk_ack.lrcvtime at session start time
Input: elan_i2c - add ASUS EeeBook X205TA special touchpad fw
Input: i8042 - add noloop quirk for Dell Embedded Box PC 3000
Input: iforce - validate number of endpoints before using them
Input: ims-pcu - validate number of endpoints before using them
Input: hanwang - validate number of endpoints before using them
Input: yealink - validate number of endpoints before using them
Input: cm109 - validate number of endpoints before using them
Input: kbtab - validate number of endpoints before using them
Input: sur40 - validate number of endpoints before using them
ALSA: seq: Fix racy cell insertions during snd_seq_pool_done()
ALSA: ctxfi: Fix the incorrect check of dma_set_mask() call
ALSA: hda - Adding a group of pin definition to fix headset problem
USB: serial: option: add Quectel UC15, UC20, EC21, and EC25 modems
USB: serial: qcserial: add Dell DW5811e
ACM gadget: fix endianness in notifications
usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval
usb-core: Add LINEAR_FRAME_INTR_BINTERVAL USB quirk
USB: uss720: fix NULL-deref at probe
USB: lvtest: fix NULL-deref at probe
USB: idmouse: fix NULL-deref at probe
USB: wusbcore: fix NULL-deref at probe
usb: musb: cppi41: don't check early-TX-interrupt for Isoch transfer
usb: hub: Fix crash after failure to read BOS descriptor
uwb: i1480-dfu: fix NULL-deref at probe
uwb: hwa-rc: fix NULL-deref at probe
mmc: ushc: fix NULL-deref at probe
iio: adc: ti_am335x_adc: fix fifo overrun recovery
iio: hid-sensor-trigger: Change get poll value function order to avoid sensor 
properties losing after resume from S3
parport: fix attempt to write duplicate procfiles
ext4: mark inode dirty after converting inline directory
mmc: sdhci: Do not disable interrupts while waiting for clock
xen/acpi: upload PM state from init-domain to Xen
iommu/vt-d: Fix NULL pointer dereference in device_to_iommu
ARM: at91: pm: cpu_idle: switch DDR to power-down mode
ARM: dts: at91: sama5d2: add dma properties to UART nodes
cpufreq: Restore policy min/max limits on CPU online
raid10: increment write counter after bio is split
libceph: don't set weight to IN when OSD is destroyed
xfs: don't allow di_size with high bit set
xfs: fix up xfs_swap_extent_forks inline extent handling
nl80211: fix dumpit error path RTNL deadlocks
USB: usbtmc: add missing endpoint sanity check
xfs: clear _XBF_PAGES from buffers when readahead page
igb: add i211 to i210 PHY workaround
vfio/spapr: Postpone allocation of userspace version of TCE table
block: allow WRITE_SAME commands with the SG_IO ioctl
fbcon: Fix vc attr at deinit
crypto: algif_hash - avoid zero-sized array
Linux 4.4.58

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.4.58 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[aljosa]

I have been informed that there are people (Chris Chiu and Daniel Drake)
working on ASUS ROG models, and their patches are already slated to be
released with kernel 4.12:

https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/log/?h=for-4.12/asus

Unfortunately I'm not able to apply those patches by myself. It would be
great if some of you Linux people affected by "ASUS G752VS - Touchpad
and Fn keys" problem can test mentioned patches and enter in contact
with Chris and Daniel.

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: 

[Kernel-packages] [Bug 1670634] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From jac...@de.ibm.com 2017-03-30 08:50 EDT---
New Kernel, new hang ...

?  961.242228! INFO: task kworker/1:1:38 blocked for more than 120 seconds.
?  961.242235!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.242236! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.242480! INFO: task xfsaild/dm-11:1742 blocked for more than 120 seconds.
?  961.242481!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.242482! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.242933! INFO: task rs:main Q:Reg:2043 blocked for more than 120 seconds.
?  961.242934!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.242935! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.243407! INFO: task cpuplugd:2355 blocked for more than 120 seconds.
?  961.243409!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.243410! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.243544! INFO: task irqbalance:2447 blocked for more than 120 seconds.
?  961.243546!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.243546! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.243617! INFO: task kworker/0:2H:3385 blocked for more than 120 seconds.
?  961.243618!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.243619! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.243911! INFO: task kworker/0:1H:6035 blocked for more than 120 seconds.
?  961.243912!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.243913! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.244405! INFO: task kworker/0:2:22440 blocked for more than 120 seconds.
?  961.244406!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.244407! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.244543! INFO: task kworker/0:4:22938 blocked for more than 120 seconds.
?  961.244545!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.244545! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
?  961.245404! INFO: task dpkg:24617 blocked for more than 120 seconds.
?  961.245405!   Not tainted 4.4.0-71-generic #92-Ubuntu
?  961.245406! "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.

And the dump:

KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-71-generic
DUMPFILE: mclint_20170330_kernel_4_4_0-71_without_openafs.dump
CPUS: 1
DATE: Thu Mar 30 12:14:27 2017
UPTIME: 00:24:42
LOAD AVERAGE: 14.32, 12.51, 7.23
TASKS: 407
NODENAME: mclint
RELEASE: 4.4.0-71-generic
VERSION: #92-Ubuntu SMP Fri Mar 24 13:03:47 UTC 2017
MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
PANIC: ""
PID: 0
COMMAND: "swapper/0"
TASK: bad528  [THREAD_INFO: b78000]
CPU: 0
STATE: TASK_RUNNING
INFO: no panic task found

The dump is already uploaded to Box

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: 

[Kernel-packages] [Bug 1677589] [NEW] Zesty update to v4.10.7 stable release

[Tim Gardner]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.10.7 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.10.7 stable release shall be
applied:

net/openvswitch: Set the ipv6 source tunnel key address attribute correctly
net: bcmgenet: Do not suspend PHY if Wake-on-LAN is enabled
net: properly release sk_frag.page
amd-xgbe: Fix jumbo MTU processing on newer hardware
openvswitch: Add missing case OVS_TUNNEL_KEY_ATTR_PAD
net: unix: properly re-increment inflight counter of GC discarded candidates
qmi_wwan: add Dell DW5811e
net: vrf: Reset rt6i_idev in local dst after put
net/mlx5: Add missing entries for set/query rate limit commands
net/mlx5e: Use the proper UAPI values when offloading TC vlan actions
net/mlx5: Increase number of max QPs in default profile
net/mlx5e: Count GSO packets correctly
net/mlx5e: Count LRO packets correctly
ipv6: make sure to initialize sockc.tsflags before first use
net: bcmgenet: remove bcmgenet_internal_phy_setup()
ipv4: provide stronger user input validation in nl_fib_input()
socket, bpf: fix sk_filter use after free in sk_clone_lock
genetlink: fix counting regression on ctrl_dumpfamily()
tcp: initialize icsk_ack.lrcvtime at session start time
amd-xgbe: Fix the ECC-related bit position definitions
net: solve a NAPI race
HID: sony: Fix input device leak when connecting a DS4 twice using USB/BT
Input: ALPS - fix V8+ protocol handling (73 03 28)
Input: ALPS - fix trackstick button handling on V8 devices
Input: elan_i2c - add ASUS EeeBook X205TA special touchpad fw
Input: i8042 - add noloop quirk for Dell Embedded Box PC 3000
Input: iforce - validate number of endpoints before using them
Input: ims-pcu - validate number of endpoints before using them
Input: hanwang - validate number of endpoints before using them
Input: yealink - validate number of endpoints before using them
Input: cm109 - validate number of endpoints before using them
Input: kbtab - validate number of endpoints before using them
Input: sur40 - validate number of endpoints before using them
ALSA: seq: Fix racy cell insertions during snd_seq_pool_done()
ALSA: ctxfi: Fix the incorrect check of dma_set_mask() call
ALSA: hda - Adding a group of pin definition to fix headset problem
USB: serial: option: add Quectel UC15, UC20, EC21, and EC25 modems
USB: serial: qcserial: add Dell DW5811e
ACM gadget: fix endianness in notifications
usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval
dvb-usb-firmware: don't do DMA on stack
usb-core: Add LINEAR_FRAME_INTR_BINTERVAL USB quirk
USB: uss720: fix NULL-deref at probe
USB: lvtest: fix NULL-deref at probe
USB: idmouse: fix NULL-deref at probe
USB: wusbcore: fix NULL-deref at probe
usb: musb: cppi41: don't check early-TX-interrupt for Isoch transfer
usb: hub: Fix crash after failure to read BOS descriptor
USB: usbtmc: add missing endpoint sanity check
USB: usbtmc: fix probe error path
uwb: i1480-dfu: fix NULL-deref at probe
uwb: hwa-rc: fix NULL-deref at probe
mmc: ushc: fix NULL-deref at probe
nl80211: fix dumpit error path RTNL deadlocks
mmc: core: Fix access to HS400-ES devices
iio: adc: ti_am335x_adc: fix fifo overrun recovery
iio: sw-device: Fix config group initialization
iio: hid-sensor-trigger: Change get poll value function order to avoid sensor 
properties losing after resume from S3
iio: magnetometer: ak8974: remove incorrect __exit markups
mei: fix deadlock on mei reset
mei: don't wait for os version message reply
parport: fix attempt to write duplicate procfiles
ppdev: fix registering same device name
ext4: mark inode dirty after converting inline directory
powerpc/64s: Fix idle wakeup potential to clobber registers
audit: fix auditd/kernel connection state tracking
mmc: sdhci-of-at91: Support external regulators
mmc: sdhci-of-arasan: fix incorrect timeout clock
mmc: sdhci: Do not disable interrupts while waiting for clock
mmc: sdhci-pci: Do not disable interrupts in sdhci_intel_set_power
hwrng: amd - Revert managed API changes
hwrng: geode - Revert managed API changes
clk: sunxi-ng: sun6i: Fix enable bit offset for hdmi-ddc module clock
clk: sunxi-ng: mp: Adjust parent rate for pre-dividers
mwifiex: pcie: don't leak DMA buffers when removing
ath10k: fix incorrect wlan_mac_base in qca6174_regs
crypto: ccp - Assign DMA commands to the channel's CCP
fscrypt: remove broken support for detecting keyring key revocation
vfio: Rework group release notifier warning
xen/acpi: upload PM state from init-domain to Xen
iommu/vt-d: Fix NULL pointer dereference in 

[Kernel-packages] [Bug 1591804] Re: [Feature] Purley: Memory Protection Keys

[Leann Ogasawara]

** Changed in: intel
   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/1591804

Title:
  [Feature] Purley: Memory Protection Keys

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Memory Protection Keys for Userspace (PKU aka PKEYs) is a Skylake-SP server 
feature that provides a mechanism for enforcing page-based protections, but 
without requiring modification of the page tables when an application changes 
protection domains.  It works by dedicating 4 previously ignored bits in each 
page table entry to a "protection key", giving 16 possible keys.
  There is also a new user-accessible register (PKRU) with two separate bits 
(Access Disable and Write Disable) for each key.Being a CPU register, PKRU is 
inherently thread-local,potentially giving each thread a different set of 
protectionsfrom every other thread.
  There are two new instructions (RDPKRU/WRPKRU) for reading and writing to the 
new register.  The feature is only available in 64-bit mode, even though there 
is theoretically space in the PAE PTEs.  These permissions are enforced on data 
access only and have no effect on instruction fetches.

  HW: Purley

  Upstream status:
  v4.6 kernel implement basic and execute-only support
  v4.9 kernel will have new interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1591804/+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 1677579] Missing required logs.

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1677579

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

Title:
  CVE-2017-6353

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Commit dfcb9f4f99f1e9a49e43398a7bfbf56927544af1 needs to be backported
  in order to really fix what commit 2dcab5984841 upstream was supposed
  to fix.

  Commit 2dcab5984841 was backported to Xenial as part of the 4.4.y
  stable update.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677579/+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 1677579] Re: CVE-2017-6353

[Thadeu Lima de Souza Cascardo]

Trusty and Yakkety will be affected was we backport upstream commit
2dcab5984841.

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

Title:
  CVE-2017-6353

Status in linux package in Ubuntu:
  New

Bug description:
  Commit dfcb9f4f99f1e9a49e43398a7bfbf56927544af1 needs to be backported
  in order to really fix what commit 2dcab5984841 upstream was supposed
  to fix.

  Commit 2dcab5984841 was backported to Xenial as part of the 4.4.y
  stable update.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677579/+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 1677579] [NEW] CVE-2017-6353

[Thadeu Lima de Souza Cascardo]

Public bug reported:

Commit dfcb9f4f99f1e9a49e43398a7bfbf56927544af1 needs to be backported
in order to really fix what commit 2dcab5984841 upstream was supposed to
fix.

Commit 2dcab5984841 was backported to Xenial as part of the 4.4.y stable
update.

Cascardo.

** 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/1677579

Title:
  CVE-2017-6353

Status in linux package in Ubuntu:
  New

Bug description:
  Commit dfcb9f4f99f1e9a49e43398a7bfbf56927544af1 needs to be backported
  in order to really fix what commit 2dcab5984841 upstream was supposed
  to fix.

  Commit 2dcab5984841 was backported to Xenial as part of the 4.4.y
  stable update.

  Cascardo.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677579/+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 1677575] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Thunderbolt hotplug causes system hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a problem similar to the bug #1599476, my system freezes when I
  unplug my thunderbolt port if it is connected during startup.

  What I have tested so far : 
  * If the thunderbolt is plugged at startup and I unplug it -> System freeze
  * If the thunderbolt is not plugged at startup, I can plug it and unplug it 
fine. 

  What I expect to happen : 
  Being able to unplug my thunderbolt without the system freezing. 

  I updated my BIOS and the firmware of the dock : 
  13:47 troche@serenity ~ % sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
  1.2.19
  12/22/2016

  This was working fine in Ubuntu 16.04, and it is not working since my update 
to Ubuntu 16.10.
  13:47 troche@serenity ~ % lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  My computer is a Dell Precision 5510 laptop with a dock WD15
  Thunderbolt.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-41-generic 4.8.0-41.44
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   troche 2945 F...m pulseaudio
   /dev/snd/controlC0:  troche 2945 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 30 13:41:26 2017
  HibernationDevice: RESUME=UUID=65e0fb0a-8046-4428-bb89-53d36638d70a
  InstallationDate: Installed on 2016-08-24 (218 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Precision 5510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=7510dd66-3e56-446f-b39c-71724a228d07 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-03-27 (3 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677575/+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 1677575] [NEW] Thunderbolt hotplug causes system hang

[Thibault Roche]

Public bug reported:

I have a problem similar to the bug #1599476, my system freezes when I
unplug my thunderbolt port if it is connected during startup.

What I have tested so far : 
* If the thunderbolt is plugged at startup and I unplug it -> System freeze
* If the thunderbolt is not plugged at startup, I can plug it and unplug it 
fine. 

What I expect to happen : 
Being able to unplug my thunderbolt without the system freezing. 

I updated my BIOS and the firmware of the dock : 
13:47 troche@serenity ~ % sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
1.2.19
12/22/2016

This was working fine in Ubuntu 16.04, and it is not working since my update to 
Ubuntu 16.10.
13:47 troche@serenity ~ % lsb_release -rd
Description:Ubuntu 16.10
Release:16.10

My computer is a Dell Precision 5510 laptop with a dock WD15
Thunderbolt.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-41-generic 4.8.0-41.44
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   troche 2945 F...m pulseaudio
 /dev/snd/controlC0:  troche 2945 F pulseaudio
CurrentDesktop: Unity
Date: Thu Mar 30 13:41:26 2017
HibernationDevice: RESUME=UUID=65e0fb0a-8046-4428-bb89-53d36638d70a
InstallationDate: Installed on 2016-08-24 (218 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Precision 5510
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=7510dd66-3e56-446f-b39c-71724a228d07 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-41-generic N/A
 linux-backports-modules-4.8.0-41-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2017-03-27 (3 days ago)
dmi.bios.date: 12/22/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.19
dmi.board.name: 0N8J4R
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug third-party-packages yakkety

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

Title:
  Thunderbolt hotplug causes system hang

Status in linux package in Ubuntu:
  New

Bug description:
  I have a problem similar to the bug #1599476, my system freezes when I
  unplug my thunderbolt port if it is connected during startup.

  What I have tested so far : 
  * If the thunderbolt is plugged at startup and I unplug it -> System freeze
  * If the thunderbolt is not plugged at startup, I can plug it and unplug it 
fine. 

  What I expect to happen : 
  Being able to unplug my thunderbolt without the system freezing. 

  I updated my BIOS and the firmware of the dock : 
  13:47 troche@serenity ~ % sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
  1.2.19
  12/22/2016

  This was working fine in Ubuntu 16.04, and it is not working since my update 
to Ubuntu 16.10.
  13:47 troche@serenity ~ % lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  My computer is a Dell Precision 5510 laptop with a dock WD15
  Thunderbolt.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-41-generic 4.8.0-41.44
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   troche 2945 F...m pulseaudio
   /dev/snd/controlC0:  troche 2945 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 30 13:41:26 2017
  HibernationDevice: RESUME=UUID=65e0fb0a-8046-4428-bb89-53d36638d70a
  InstallationDate: Installed on 2016-08-24 (218 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Precision 5510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic 
root=UUID=7510dd66-3e56-446f-b39c-71724a228d07 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-03-27 (3 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.19
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  

[Kernel-packages] [Bug 1072234] Re: 050d:0017 Bluetooth mouse randomly disconnects

[Aleksey]

Same for me with Microsoft Sculpt Comfort mouse on different machines
with Ubuntu 16.04/10. Mouse keeps disconnecting every few minutes and
then after about 20 seconds reconnects again. No visible issue in logs,
just formal info about reconnection.

** Changed in: bluez (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  050d:0017 Bluetooth mouse randomly disconnects

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Quantal, my Belkin bluetooth mouse disconnects
  sporadically from my computer. Sometimes this will happen several
  times a day, at other times it will stay connected for almost the
  entire day without a problem.

  After the connection is dropped, Bluetooth seems to become
  unresponsive. Generally unplugging and replugging the USB adapter is
  necessary to return it to a usable state.

  It was extremely reliable under Precise.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: bluetooth 4.101-0ubuntu6
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sat Oct 27 23:58:59 2012
  InstallationDate: Installed on 2012-03-08 (233 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=62a1305b-ef07-4168-8292-c82e0718a496 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (7 days ago)
  dmi.bios.date: 07/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-V EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd07/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:19:0E:0A:2A:A1  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:458652 acl:26915 sco:0 events:74 errors:0
TX bytes:1125 acl:19 sco:0 commands:29 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1072234/+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 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds

[Aleksey]

Same for me with Microsoft Sculpt Comfort mouse on different machines
with Ubuntu 16.04/10. Mouse keeps disconnection every few minutes and
the reconnects again. No visible issue in logs, just info about
reconnection.

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

Title:
  Bluetooth mouse disconnects and reconnects every few seconds

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth mouse (Genius Traveller 9005BT) that I have been
  using without problems with Ubuntu for over a year. Since a few weeks
  ago, however, it started disconnecting and reconnected from the
  computer. The symptoms are like this:

  1. The mouse works, and the bluetooth icon on the computer is visible (in 
gnome-shell's top bar)
  2. The mouse stops working, but the bluetooth icon is still visible. This 
state lasts between 1 and 10 seconds.
  3. The bluetooth icon vanishes. This can last for half a second if I keep 
trying to use the mouse, to forever I I leave the mouse alone
  4. The bluetooth icon reappears and the mouse starts working again. This 
state last from 2-3 seconds if I don't move the mouse, to seemingly forever if 
I continuously move the mouse

  This seems to occur only after a suspend/resume cycle, and rebooting
  the computer fixes the issue.

  The only thing I see in syslog is this when the mouse reconnects:
  Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 
0005:0458:0139.002F: unknown main item tag 0x0
  Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as 
/devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59
  Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 
0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] 
on e8:2a:ea:8b:a5:5f

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr 11 09:49:37 2015
  InstallationDate: Installed on 2015-01-23 (77 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: E8:2A:EA:8B:A5:5F  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0
TX bytes:29044 acl:238 sco:0 commands:218 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1442896/+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 1651454] Re: [Lenovo Thinkpad T460p] Ultra Dock external displays not detected after suspend/resume cycle

[Donjan Rodic]

OK, I'm on 4.8.0-45 now and it's working well again.
Will close this for now.

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1651454

Title:
  [Lenovo Thinkpad T460p] Ultra Dock external displays not detected
  after suspend/resume cycle

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The bug is identical to the expired
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 where a
  new report was requested.

  This time around with a fresh install of 16.10 amd64 on a Thinkpad
  T460p and a Lenovo Ultra Dock with two external monitors.

  The setup does work when freshly booting with the laptop on the dock. 
Suspending undocked, docking, resuming doesn't light up the external monitors. 
Neither does just docking awake.
  The relevant error messages seem to be these:

  Dec 20 13:21:50 talas kernel: [265391.482117] 
[drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage 
retries, give up
  Dec 20 13:21:50 talas kernel: [265391.498583] [drm:intel_wait_ddi_buf_idle 
[i915]] *ERROR* Timeout waiting for DDI BUF D idle bit

  Other relevant bug reports might be:
  https://bugzilla.redhat.com/show_bug.cgi?id=1316877
  https://bbs.archlinux.org/viewtopic.php?id=209791

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  donjan 2341 F pulseaudio
   /dev/snd/pcmC1D0p:   donjan 2341 F...m pulseaudio
   /dev/snd/controlC1:  donjan 2341 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Dec 20 15:36:08 2016
  InstallationDate: Installed on 2016-10-25 (56 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20FXS0Y200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic 
root=UUID=104820cc-7d87-46d1-a1aa-e650ff221603 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET71W (2.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS0Y200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FXS0Y200:pvrThinkPadT460p:rvnLENOVO:rn20FXS0Y200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FXS0Y200
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651454/+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 219057] Re: Bluetooth does not coexist with WiFi

[praveen kannan]

I have also same problem when wireless connection is switched on
Bluetooth disconnects immediately. I can't reconnect until wifi is
disconnected.

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

Title:
  Bluetooth does not coexist with WiFi

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On my system bluetooth and wifi are unusable together. I have a built-
  in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi
  transfers slow to a halt whenever there is BT traffic.

  For example, if I play a music file from another machine through the
  network using a BT headset, only the first few seconds of the file
  will play until the player runs out of buffered data. No further data
  is downloaded. Web pages also do not download, and I even lose
  connection to AP from time to time.

  At the same time, it looks like AFH is trying to work. If I monitor
  the value returned by 'hcitool afh', it changes. But this seems to
  have little effect on connection quality.

  Is this a problem with my hardware, or the AFH implementation? Is
  there a way to force bluetooth to not use the channels in use by WiFi?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+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 1188459] Re: Updating of Atheros firmware for ath9k_htc

[Bug Watch Updater]

** Changed in: debian
   Status: Confirmed => Fix Released

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

Title:
  Updating of Atheros firmware for ath9k_htc

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in Debian:
  Fix Released

Bug description:
  The current linux-firmware package for Precise and above contains non-
  free firmware in a package meant to contain free firmware. Recently,
  the htc_7010.fw and htc_9721.fw firmwares were updated by Atheros and
  re-released under a free software license. More information at
  https://www.fsf.org/news/ryf-ce.rtification-thinkpenguin-usb-with-
  atheros-chip.

  Recent firmware files can be obtained from http://jxself.org/ath9k-
  htc/version-1.3.2/ or from the source at https://github.com/qca/open-
  ath9k-htc-firmware

  Please consider updating these two firmware files in a package update
  for supported Ubuntu versions when possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1188459/+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 1660832] Re: unix domain socket cross permission check failing with nested namespaces

[Stefan Bader]

Not fixed because we had to revert the commits due to various
regressions.

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Released => Triaged

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  unix domain socket cross permission check failing with nested
  namespaces

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in apparmor source package in Yakkety:
  Confirmed
Status in linux source package in Yakkety:
  Triaged
Status in apparmor source package in Zesty:
  Confirmed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When using nested namespaces policy within the nested namespace is trying 
  
  to cross validate with policy outside of the namespace that is not
  
  visible to it. This results the access being denied and with no way to
  
  add a rule to policy that would allow it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1660832/+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 1664912] Re: linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-xenial 4.4.0-63.84~14.04.2

[Stefan Bader]

Unfortunately also "SAUCE: apparmor: fix link auditing failure due to,
uninitialized var" got reverted in the big revert for bug 1666897. So
not really fixed in Yakkety and Xenial based kernels right now.

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Released => Triaged

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

** Changed in: linux-lts-xenial (Ubuntu Trusty)
   Status: Fix Released => Triaged

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

Title:
  linux-lts-xenial 4.4.0-63.84~14.04.2 ADT test failure with linux-lts-
  xenial 4.4.0-63.84~14.04.2

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux-lts-xenial source package in Xenial:
  Invalid
Status in linux source package in Yakkety:
  Triaged
Status in linux-lts-xenial source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in linux-lts-xenial source package in Zesty:
  Invalid

Bug description:
  Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux-lts-xenial/20170214_051856_a19a2@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664912/+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 1638996] Re: apparmor's raw_data file in securityfs is sometimes truncated

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor's raw_data file in securityfs is sometimes truncated

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  Hi,

  It looks like sometimes apparmor's securityfs output is sometimes
  truncated,

  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 ls -al
  total 0
  drwxr-xr-x  3 root root 0 Nov  3 16:45 .
  drwxr-xr-x 13 root root 0 Nov  3 16:44 ..
  -r--r--r--  1 root root 0 Nov  3 16:45 attach
  -r--r--r--  1 root root 0 Nov  3 16:45 mode
  -r--r--r--  1 root root 0 Nov  3 16:45 name
  drwxr-xr-x  3 root root 0 Nov  3 16:45 profiles
  -r--r--r--  1 root root 0 Nov  3 16:45 raw_abi
  -r--r--r--  1 root root 46234 Nov  3 16:45 raw_data
  -r--r--r--  1 root root 0 Nov  3 16:45 raw_hash
  -r--r--r--  1 root root 0 Nov  3 16:45 sha1
  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 cat raw_data > /tmp/out
  
root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1#
 ls -al /tmp/out 
  -rw-r--r-- 1 root root 4009 Nov  3 16:55 /tmp/out

  and

  2016-11-03 10:58:01 tych0 jjohansen: hi, http://paste.ubuntu.com/23421551/
  2016-11-03 10:58:18 tych0 it looks like fstat is lying to me about the size 
of the policy
  2016-11-03 10:59:20 @jjohansen  tych0: hrmm interesting, can you zip up the 
/tmp/out file so I can see it looks like a complete policy file?
  2016-11-03 11:00:03 @jjohansen  something is definitely not right there. hrmmm
  2016-11-03 11:00:26 @jjohansen  the size is set by the input buffer size
  2016-11-03 11:00:28 tych0 jjohansen: http://files.tycho.ws/tmp/out
  2016-11-03 11:00:36 tych0 yeah, i assume
  2016-11-03 11:01:15 @jjohansen  my guess is something is messing up in the 
seq_file walk of the policy
  2016-11-03 11:02:38 @jjohansen  tych0: yep the file is truncated, can you 
open a bug and I will start looking for it
  2016-11-03 11:03:14 tych0 jjohansen: sure, just on linux?
  2016-11-03 11:03:35 @jjohansen  tych0: yeah for now, just linux
  2016-11-03 11:03:43 @jjohansen  we can add others if needed later
  2016-11-03 11:03:44 tych0 jjohansen: FWIW, somehow it seems racy, becasue 
sometimes it works and sometimes it doesn't

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638996/+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 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor_parser hangs indefinitely when called by multiple threads

Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug surfaced when starting ~50 LXC container with LXD in parallel
  multiple times:

  # Create the containers
  for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done

  # Exectute this loop multiple times until you observe errors.
  for c in c foo{1..50}; do lxc restart $c & done

  After this you can

  ps aux | grep apparmor

  and you should see output similar to:

  root 19774  0.0  0.0  12524  1116 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19775  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19776  0.0  0.0  13592  3224 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19778  0.0  0.0  13592  3384 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19780  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19782  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19783  0.0  0.0  13592  3388 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19784  0.0  0.0  13592  3252 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19794  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
  root 19795  0.0  0.0  13592  3256 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25

  apparmor_parser remains stuck even after all LXC/LXD commands have
  exited.

  dmesg output yields lines like:

  [41902.815174] audit: type=1400 audit(1480191089.678:43):
  apparmor="STATUS" operation="profile_load" profile="unconfined" name
  ="lxd-foo30_" pid=12545 comm="apparmor_parser"

  and cat /proc/12545/stack shows:

  [] aa_remove_profiles+0x88/0x270
  21:19   brauner  [] profile_remove+0x144/0x2e0
  21:19   brauner  [] __vfs_write+0x18/0x40
  21:19   brauner  [] vfs_write+0xb8/0x1b0
  21:19   brauner  [] SyS_write+0x55/0xc0
  21:19   brauner  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  21:19   brauner  [] 0x

  This looks like a potential kernel bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1645037/+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 1660836] Re: apparmor auditing denied access of special apparmor .null fi\ le

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor  auditing denied access of special apparmor .null fi\ le

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When an fd is disallowed from being inherited during exec, instead of 
  
  closed it is duped to a special apparmor/.null file. This prevents the
  
  fd from being reused by another file in case the application expects  
  
  the original file on a give fd (eg stdin/stdout etc). This results in 
  
  a denial message like 
  
  [32375.561535] audit: type=1400 audit(1478825963.441:358): apparmor="DENIED" 
op\
  eration="file_inherit" namespace="root//lxd-t_" 
profile="/sbin/dhc\
  lient" name="/dev/pts/1" pid=16795 comm="dhclient" requested_mask="wr" 
denied_m\
  ask="wr" fsuid=165536 ouid=165536 
  

  
  Further access to the fd is resultin in the rather useless denial message 
  
  of
  
  [32375.566820] audit: type=1400 audit(1478825963.445:359): apparmor="DENIED" 
op\
  eration="file_perm" namespace="root//lxd-t_" 
profile="/sbin/dhclie\
  nt" name="/apparmor/.null" pid=16795 comm="dhclient" requested_mask="w" 
denied_\
  mask="w" fsuid=165536 ouid=0  
  

  
  since we have the original denial, the noisy and useless .null based  
  
  denials can be skipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660836/+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 1660834] Re: apparmor label leak when new label is unused

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor label leak when new label is unused

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When a new label is created, it is created with a proxy in a circular 
  
  ref count that is broken by replacement. However if the label is not  
  
  used it will never be replaced and the circular ref count will never  
  
  be broken resulting in a leak.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660834/+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 1658219] Re: flock not mediated by 'k'

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  flock not mediated by 'k'

Status in AppArmor:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  $ cat ./apparmor.profile 
  #include 

  profile test {
#include 

/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,

  }

  $ sudo apparmor_parser -r ./apparmor.profile

  $ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
  yes

  $ ls -l /tmp/test.lock 
  -rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock

  The flock command uses flock(LOCK_EX) and I expected it to be blocked
  due to the lack of 'k'.

  apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
  kernel on amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+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 1656121] Re: unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt from a unshared mount namespace

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  unexpected errno=13 and disconnected path when trying to open
  /proc/1/ns/mnt from a unshared mount namespace

Status in AppArmor:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  This bug is based on a discussion with jjohansen on IRC.

  While working on a feature for snapd
  (https://github.com/snapcore/snapd/pull/2624) we came across an
  unexpected EACCES that only seems to happen when apparmor is in the
  loop.

  The kernel log shows something interesting. The full log is available
  here: http://paste.ubuntu.com/23789099/

  Jan 12 23:16:43 autopkgtest kernel: [  498.616822] audit: type=1400
  audit(1484259403.009:67): apparmor="ALLOWED" operation="open"
  info="Failed name lookup - disconnected path" error=-13 profile="snap
  .test-snapd-tools.cmd//null-/usr/bin/snap//null-/usr/lib/snapd/snap-
  confine" name="" pid=25299 comm="snap-confine" requested_mask="r"
  denied_mask="r" fsuid=0 ouid=0

  The code that triggers this is reproduced below (also visible here
  https://github.com/snapcore/snapd/pull/2624/files)

  +void sc_reassociate_with_pid1_mount_ns()
   +{
   +int init_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +int self_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +
   +debug("checking if the current process shares mount namespace"
   +  "with the init process");
   +
   +init_mnt_fd = open("/proc/1/ns/mnt",
   +   O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH);
   +if (init_mnt_fd < 0) {
   +die("cannot open mount namespace of the init process (O_PATH)");
   +}
   +self_mnt_fd = open("/proc/self/ns/mnt",
   +   O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH);
   +if (self_mnt_fd < 0) {
   +die("cannot open mount namespace of the current process 
(O_PATH)");
   +}
   +char init_buf[128], self_buf[128];
   +memset(init_buf, 0, sizeof init_buf);
   +if (readlinkat(init_mnt_fd, "", init_buf, sizeof init_buf) < 0) {
   +die("cannot perform readlinkat() on the mount namespace file "
   +"descriptor of the init process");
   +}
   +memset(self_buf, 0, sizeof self_buf);
   +if (readlinkat(self_mnt_fd, "", self_buf, sizeof self_buf) < 0) {
   +die("cannot perform readlinkat() on the mount namespace file "
   +"descriptor of the current process");
   +}
   +if (memcmp(init_buf, self_buf, sizeof init_buf) != 0) {
   +debug("the current process does not share mount namespace with "
   +  "the init process, re-association required");
   +// NOTE: we cannot use O_NOFOLLOW here because that file will 
always be a
   +// symbolic link. We actually want to open it this way.
   +int init_mnt_fd_real
   +__attribute__ ((cleanup(sc_cleanup_close))) = -1;
   +init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY | O_CLOEXEC);
   +if (init_mnt_fd_real < 0) {
   +die("cannot open mount namespace of the init process");
   +}
   +if (setns(init_mnt_fd_real, CLONE_NEWNS) < 0) {
   +die("cannot re-associate the mount namespace with the 
init process");
   +}
   +} else {
   +debug("re-associating is not required");
   +}
   +}

  The specific part that causes the error is:

   +  init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY |
  O_CLOEXEC);

  The call to open returns -1 and errno set to 13 (EACCES) despite using
  attach_disconnected.

  The code in question is executed from a seguid root executable that
  runs under a complain-mode profile (it is started from a process that
  is already confined with such a profile). All of the profiles are
  using attach_disconnected.

  I can reproduce this issue each time by running:

  spread -debug -v qemu:ubuntu-16.04-64:tests/regression/lp-1644439

  Against the code in this pull request:

  https://github.com/snapcore/snapd/pull/2624

  Which is git://github.com/zyga/snapd in the "reassociate-fix" branch

  Appropriate qemu images can be made using instructions from:

  https://github.com/zyga/spread-qemu-images

  I'm also happy to try any test kernels as I can easily run those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1656121/+subscriptions

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

[Kernel-packages] [Bug 1660833] Re: apparmor reference count bug in label_merge_insert()

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor reference count bug in label_merge_insert()

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  @new does not have a reference taken locally and should not have its  
  
  reference put locally either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660833/+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 1660840] Re: apparmor oops in bind_mnt when dev_path lookup fails

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor oops in bind_mnt when dev_path lookup fails

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Bind mounts can oops when devname lookup fails because the devname is 
  
  unintialized and used in auditing the denial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660840/+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 1660842] Re: apparmor not checking error if security_pin_fs() fails

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor not checking error if security_pin_fs() fails

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  The error condition of security_pin_fs() was not being checked which
  will result can result in an oops or use after free, due to the fs pin
  count not being incremented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660842/+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 1660845] Re: apparmor reference count leak when securityfs_setup_d_inode\ () fails

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor reference count leak when securityfs_setup_d_inode\ () fails

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  apparmor is leaking the parent ns ref count, by directly returning the
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660845/+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 1660849] Re: apparmor refcount leak of profile namespace when removing profiles

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  apparmor refcount leak of profile namespace when removing profiles

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  When doing profile removal, the parent ns of the profiles is taken,
  but the reference isn't being put, resulting in the ns never being
  freed even after it is removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660849/+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 1661030] Re: regession tests failing after stackprofile test is run

[Stefan Bader]

** Changed in: linux (Ubuntu Yakkety)
   Status: Fix Released => Triaged

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

Title:
  regession tests failing after stackprofile test is run

Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Triaged
Status in apparmor source package in Yakkety:
  Fix Committed
Status in linux source package in Yakkety:
  Triaged
Status in apparmor source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Incomplete

Bug description:
  from source, I'm running the tests and the makefile fails at the end
  with:

  running stackprofile
  Makefile:303: recipe for target 'tests' failed
  make: *** [tests] Error 1

  No idea why that is happening. It's breaking on our kernel team
  regression tests runs, so can this be investigated?  The source was
  fetched using "apt-get source apparmor".

  A full run is below:

  king@ubuntu:~/apparmor-2.10.95/tests/regression/apparmor$ sudo make
  USE_SYSTEM=1 tests

  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)
  (ioperm)
  (iopl)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12503 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12537 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12803 Segmentation fault  (core dumped) $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12833 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12869 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12905 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  /home/king/apparmor-2.10.95/tests/regression/apparmor/prologue.inc: line 219: 
12941 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ
  Fatal Error (environ): Unable to run test sub-executable

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root

  running ptrace
 using ptrace v6 tests ...

  running pwrite

  running query_label
  Alert: query_label passed. Test 'QUERY file (all base perms #1)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #1)
  Alert: query_label passed. Test 'QUERY file (all base perms #2)' was marked 
as expected pass but known problem (xpass)
  xpass: QUERY file (all base perms #2)

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap
  mkswap: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.
  swapon: /tmp/sdtest.21272-20356-eRXvtR/swapfile: insecure permissions 0644, 
0600 suggested.

  running sd_flags

  running setattr

  running symlink

  running syscall

  running tcp

  running unix_fd_server

  running