| 2017-03-14 17:37:47 |
John Lenton |
bug |
|
|
added bug |
| 2017-03-14 17:47:24 |
Joseph Salisbury |
linux (Ubuntu): status |
New |
Triaged |
|
| 2017-03-14 17:47:26 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2017-03-14 17:47:33 |
Joseph Salisbury |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-03-14 17:47:33 |
Joseph Salisbury |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2017-03-14 17:47:39 |
Joseph Salisbury |
linux (Ubuntu Xenial): status |
New |
Triaged |
|
| 2017-03-14 17:47:44 |
Joseph Salisbury |
linux (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-03-14 17:47:48 |
Joseph Salisbury |
tags |
amd64 apport-bug xenial |
amd64 apport-bug kernel-key xenial |
|
| 2017-03-14 20:02:15 |
Michael Hudson-Doyle |
bug |
|
|
added subscriber Michael Hudson-Doyle |
| 2017-03-20 15:34:26 |
Joseph Salisbury |
tags |
amd64 apport-bug kernel-key xenial |
amd64 apport-bug kernel-da-key xenial |
|
| 2017-03-20 16:11:08 |
Joseph Salisbury |
tags |
amd64 apport-bug kernel-da-key xenial |
amd64 apport-bug kernel-key xenial |
|
| 2017-03-21 21:57:43 |
William Grant |
bug |
|
|
added subscriber William Grant |
| 2017-03-28 14:37:03 |
Colin Ian King |
linux (Ubuntu Xenial): assignee |
|
Colin Ian King (colin-king) |
|
| 2017-03-28 14:37:07 |
Colin Ian King |
linux (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2017-04-03 12:21:15 |
John Lenton |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857909 |
|
| 2017-04-18 13:37:00 |
Colin Ian King |
bug watch added |
|
http://bugzilla.kernel.org/195453 |
|
| 2017-04-18 13:37:00 |
Colin Ian King |
bug task added |
|
linux |
|
| 2017-04-18 13:37:30 |
Colin Ian King |
bug watch added |
|
http://bugzilla.kernel.org/195453 |
|
| 2017-04-18 13:38:56 |
Colin Ian King |
bug watch added |
|
http://bugzilla.kernel.org/195453 |
|
| 2017-04-18 13:45:34 |
Stefan Bader |
bug watch added |
|
http://bugzilla.kernel.org/195453 |
|
| 2017-04-24 15:52:08 |
Joseph Salisbury |
tags |
amd64 apport-bug kernel-key xenial |
amd64 apport-bug kernel-da-key xenial |
|
| 2017-05-09 13:53:45 |
Colin Ian King |
linux (Ubuntu Xenial): status |
In Progress |
Incomplete |
|
| 2017-05-11 13:55:10 |
John Lenton |
linux (Ubuntu Xenial): status |
Incomplete |
In Progress |
|
| 2017-05-12 15:00:17 |
Colin Ian King |
description |
This can be reproduced with
https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813
With that, and go 1.8, if you run “make” and then
for i in `seq 99`; do ./a_go; done
you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there.
That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue.
But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated.
If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-64-generic 4.4.0-64.85
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0p: john 2354 F...m pulseaudio
/dev/snd/controlC0: john 2354 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Mar 14 17:17:23 2017
HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf
InstallationDate: Installed on 2014-04-27 (1051 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Latitude E6510
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.4.0-64-generic N/A
linux-backports-modules-4.4.0-64-generic N/A
linux-firmware 1.157.8
SourcePackage: linux
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2:
UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago)
dmi.bios.date: 12/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc. |
== SRU REQUEST XENIAL, YAKKETY, ZESTY ==
Due to two race conditions in check_unsafe_exec(), exec'ing a setuid binary from a threaded program sometimes fails to setuid.
== Fix ==
Sauce patch for Xenial, Yakkety + Zesty:
https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html
This fix re-executes the unsafe check if there is a discrepancy between the expected fs count and the found count during the racy window during thread exec or exit. This re-check occurs very infrequently and saves a lot of addition locking on per thread structures that would make performance of fork/exec/exit prohibitively expensive.
== Test case ==
See the example C code in the patch, https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html
Run the test code as follows: for i in $(seq 1000); do ./a; done
With the patch, no messages are emitted, without the patch, one sees a message:
"Failed, got euid 1000 (expecting 0)"
..which shows the setuid program failed the check_unsafe_exec() because of the race.
== Regression potential ==
breaking existing safe exec semantics.
====================
This can be reproduced with
https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813
With that, and go 1.8, if you run “make” and then
for i in `seq 99`; do ./a_go; done
you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there.
That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue.
But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated.
If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-64-generic 4.4.0-64.85
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0p: john 2354 F...m pulseaudio
/dev/snd/controlC0: john 2354 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Mar 14 17:17:23 2017
HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf
InstallationDate: Installed on 2014-04-27 (1051 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Latitude E6510
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.4.0-64-generic N/A
linux-backports-modules-4.4.0-64-generic N/A
linux-firmware 1.157.8
SourcePackage: linux
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2:
UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago)
dmi.bios.date: 12/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc. |
|
| 2017-05-17 18:06:02 |
Seth Forshee |
linux (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2017-05-18 09:46:41 |
Stefan Bader |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-05-18 09:46:41 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Yakkety) |
|
| 2017-05-18 09:46:41 |
Stefan Bader |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-05-18 09:46:41 |
Stefan Bader |
bug task added |
|
linux (Ubuntu Zesty) |
|
| 2017-05-31 11:03:16 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Zesty): status |
New |
Fix Committed |
|
| 2017-05-31 11:04:32 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Yakkety): status |
New |
Fix Committed |
|
| 2017-05-31 11:16:37 |
Thadeu Lima de Souza Cascardo |
linux (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-05-31 12:33:37 |
Colin Ian King |
linux (Ubuntu Yakkety): assignee |
|
Colin Ian King (colin-king) |
|
| 2017-05-31 12:33:39 |
Colin Ian King |
linux (Ubuntu Zesty): assignee |
|
Colin Ian King (colin-king) |
|
| 2017-05-31 12:33:45 |
Colin Ian King |
linux (Ubuntu Zesty): importance |
Undecided |
High |
|
| 2017-05-31 12:33:48 |
Colin Ian King |
linux (Ubuntu Yakkety): importance |
Undecided |
High |
|
| 2017-06-14 09:09:28 |
Kleber Sacilotto de Souza |
tags |
amd64 apport-bug kernel-da-key xenial |
amd64 apport-bug kernel-da-key verification-needed-xenial xenial |
|
| 2017-06-14 09:10:58 |
Kleber Sacilotto de Souza |
tags |
amd64 apport-bug kernel-da-key verification-needed-xenial xenial |
amd64 apport-bug kernel-da-key verification-needed-xenial verification-needed-yakkety xenial |
|
| 2017-06-14 09:15:59 |
Kleber Sacilotto de Souza |
tags |
amd64 apport-bug kernel-da-key verification-needed-xenial verification-needed-yakkety xenial |
amd64 apport-bug kernel-da-key verification-needed-xenial verification-needed-yakkety verification-needed-zesty xenial |
|
| 2017-06-15 08:11:40 |
Colin Ian King |
linux (Ubuntu): assignee |
|
Colin Ian King (colin-king) |
|
| 2017-06-15 08:31:43 |
Colin Ian King |
tags |
amd64 apport-bug kernel-da-key verification-needed-xenial verification-needed-yakkety verification-needed-zesty xenial |
amd64 apport-bug kernel-da-key verification-done-xenial verification-needed-yakkety verification-needed-zesty xenial |
|
| 2017-06-15 08:36:09 |
Colin Ian King |
tags |
amd64 apport-bug kernel-da-key verification-done-xenial verification-needed-yakkety verification-needed-zesty xenial |
amd64 apport-bug kernel-da-key verification-done-xenial verification-done-yakkety verification-needed-zesty xenial |
|
| 2017-06-15 08:48:36 |
Colin Ian King |
tags |
amd64 apport-bug kernel-da-key verification-done-xenial verification-done-yakkety verification-needed-zesty xenial |
amd64 apport-bug kernel-da-key verification-done-xenial verification-done-yakkety verification-done-zesty xenial |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
linux (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-1000364 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-100363 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-5577 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-7294 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-7374 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-8890 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-9074 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-9075 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-9076 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-9077 |
|
| 2017-06-28 16:34:43 |
Launchpad Janitor |
cve linked |
|
2017-9242 |
|
| 2017-06-28 16:35:34 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-06-28 16:35:43 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-06-29 07:17:58 |
Launchpad Janitor |
linux (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-06-30 17:19:06 |
Launchpad Janitor |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2017-07-02 22:50:24 |
Michael Hudson-Doyle |
bug task added |
|
golang-1.6 (Ubuntu) |
|
| 2017-07-02 22:50:41 |
Michael Hudson-Doyle |
golang-1.6 (Ubuntu): status |
New |
Invalid |
|
| 2017-07-02 22:50:45 |
Michael Hudson-Doyle |
golang-1.6 (Ubuntu Yakkety): status |
New |
Invalid |
|
| 2017-07-02 22:50:48 |
Michael Hudson-Doyle |
golang-1.6 (Ubuntu Zesty): status |
New |
Invalid |
|
| 2017-07-02 22:50:57 |
Michael Hudson-Doyle |
golang-1.6 (Ubuntu Xenial): assignee |
|
Michael Hudson-Doyle (mwhudson) |
|
| 2017-07-02 22:51:01 |
Michael Hudson-Doyle |
golang-1.6 (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-07-02 23:29:58 |
Michael Hudson-Doyle |
description |
== SRU REQUEST XENIAL, YAKKETY, ZESTY ==
Due to two race conditions in check_unsafe_exec(), exec'ing a setuid binary from a threaded program sometimes fails to setuid.
== Fix ==
Sauce patch for Xenial, Yakkety + Zesty:
https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html
This fix re-executes the unsafe check if there is a discrepancy between the expected fs count and the found count during the racy window during thread exec or exit. This re-check occurs very infrequently and saves a lot of addition locking on per thread structures that would make performance of fork/exec/exit prohibitively expensive.
== Test case ==
See the example C code in the patch, https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html
Run the test code as follows: for i in $(seq 1000); do ./a; done
With the patch, no messages are emitted, without the patch, one sees a message:
"Failed, got euid 1000 (expecting 0)"
..which shows the setuid program failed the check_unsafe_exec() because of the race.
== Regression potential ==
breaking existing safe exec semantics.
====================
This can be reproduced with
https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813
With that, and go 1.8, if you run “make” and then
for i in `seq 99`; do ./a_go; done
you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there.
That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue.
But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated.
If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-64-generic 4.4.0-64.85
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0p: john 2354 F...m pulseaudio
/dev/snd/controlC0: john 2354 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Mar 14 17:17:23 2017
HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf
InstallationDate: Installed on 2014-04-27 (1051 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Latitude E6510
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.4.0-64-generic N/A
linux-backports-modules-4.4.0-64-generic N/A
linux-firmware 1.157.8
SourcePackage: linux
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2:
UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago)
dmi.bios.date: 12/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc. |
== SRU template for golang-1.6 ==
[Impact]
The kernel bug reported below means that occasionally (maybe 1 in 1000 times) the snapd -> snap-confine exec that is part of a snap execution fails to take the setuid bit on the snap-confine binary into account which means that the execution fails. This is extremely confusing for the user of the snap who just sees a permission denied error with no explanation.
The kernel bug has been fixed in Xenial+ but not all users of snapd are on xenial+ kernels (they might be on trusty or another distribution entirely).
Backporting this fix will mean that the snapd in the core snap will get the workaround next time it is built and because the snapd in trusty or the other distro will re-exec into the snapd in the core snap before execing snap-confine, users should not see the above behaviour.
[Test case]
This will be a bit tricky as the kernel bug has been fixed. A xenial container on a trusty host/VM should do the trick. The test case from https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 should be sufficient to demonstrate the bug and then, once golang-1.6 has been upgraded from proposed, the fix.
[Regression potential]
If there is a bug in the patch it could cause deadlocks in currently working programs. But the patch is pretty simple and has passed review upstream so I think it should be OK.
== SRU REQUEST XENIAL, YAKKETY, ZESTY ==
Due to two race conditions in check_unsafe_exec(), exec'ing a setuid binary from a threaded program sometimes fails to setuid.
== Fix ==
Sauce patch for Xenial, Yakkety + Zesty:
https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html
This fix re-executes the unsafe check if there is a discrepancy between the expected fs count and the found count during the racy window during thread exec or exit. This re-check occurs very infrequently and saves a lot of addition locking on per thread structures that would make performance of fork/exec/exit prohibitively expensive.
== Test case ==
See the example C code in the patch, https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html
Run the test code as follows: for i in $(seq 1000); do ./a; done
With the patch, no messages are emitted, without the patch, one sees a message:
"Failed, got euid 1000 (expecting 0)"
..which shows the setuid program failed the check_unsafe_exec() because of the race.
== Regression potential ==
breaking existing safe exec semantics.
====================
This can be reproduced with
https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813
With that, and go 1.8, if you run “make” and then
for i in `seq 99`; do ./a_go; done
you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there.
That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue.
But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated.
If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-64-generic 4.4.0-64.85
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0p: john 2354 F...m pulseaudio
/dev/snd/controlC0: john 2354 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Mar 14 17:17:23 2017
HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf
InstallationDate: Installed on 2014-04-27 (1051 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Latitude E6510
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.4.0-64-generic N/A
linux-backports-modules-4.4.0-64-generic N/A
linux-firmware 1.157.8
SourcePackage: linux
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2:
UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago)
dmi.bios.date: 12/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc. |
|
| 2017-07-03 00:11:50 |
Michael Hudson-Doyle |
golang-1.6 (Ubuntu Xenial): status |
New |
In Progress |
|
| 2017-07-10 14:00:33 |
Łukasz Zemczak |
golang-1.6 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-07-10 14:00:38 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-07-10 14:00:42 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2017-07-10 14:00:49 |
Łukasz Zemczak |
tags |
amd64 apport-bug kernel-da-key verification-done-xenial verification-done-yakkety verification-done-zesty xenial |
amd64 apport-bug kernel-da-key verification-done-yakkety verification-done-zesty verification-needed verification-needed-xenial xenial |
|
| 2017-07-14 02:33:48 |
Michael Hudson-Doyle |
tags |
amd64 apport-bug kernel-da-key verification-done-yakkety verification-done-zesty verification-needed verification-needed-xenial xenial |
amd64 apport-bug kernel-da-key verification-done-xenial verification-done-yakkety verification-done-zesty xenial |
|
| 2017-07-17 15:30:28 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-07-17 15:40:32 |
Launchpad Janitor |
golang-1.6 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2021-04-16 03:32:54 |
Bug Watch Updater |
linux: status |
Unknown |
Confirmed |
|
| 2021-04-16 03:32:54 |
Bug Watch Updater |
linux: importance |
Unknown |
High |
|
