Public bug reported:
Dell Computer Corporation Precision 5510 (CID 201612-25281 and
201612-25287) with pre-installed image.
[Steps To Reproduce]
Enable the proposed pocket, and then update the system by 'sudo apt-get
dist-upgrade'
[Expected Result]
The mic works
[Actual Result]
The mic
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Vivid)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux-lts-xenial (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you
** Tags added: 201612-25281 201612-25287 taipei-lab
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1659598
Title:
[Dell Computer Corporation Precision 5510] mic malfunctions
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+attachment/4809444/+files/kernel.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lshw"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1659621/+attachment/4809443/+files/lshw.txt
** Description changed:
I noticed my Laptop () started to freeze and reboot randomly and
checking the apt logs the date where this started matches a kernel
** Changed in: kexec-tools (Ubuntu)
Milestone: xenial-updates => None
** Summary changed:
- [SRU] [Xenial] Enable ARM64 support in kexec-tools
+ Enable ARM64 support in kexec-tools
** Bug watch added: Debian Bug tracker #791943
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791943
**
tests ran: 64, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-27_03-37-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Just learned that SRU for that would be more ok than I expected, quoting the
SRU policy:
"For Long Term Support releases we regularly want to enable new hardware. Such
changes are appropriate provided that we can ensure not to affect upgrades on
existing hardware."
That said waiting for
I tested with kernel 4.10.041000-rc5-generic from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5/ and I cannot
reproduce the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[IMPACT]
* kexec-tools in Xenial (16.04) currently does not support ARM64
architecture.
* Backport support for ARM64 arch from upstream
https://github.com/horms/kexec-tools
* Majority of the patches are contained in kexec/arch/arm64/ except for
[TESTING ON ARM64 HARDWARE]
$ cat /etc/issue
Ubuntu 16.04.1 LTS \n \l
$ sudo apt-add-repository ppa:manjo/kexec-tools
$ sudo apt update
$ sudo apt install kexec-tools
$ kexec --version
kexec-tools 2.0.10 released 26 January 2017
$ ls /boot
abi-4.7.0-2-generic grub
The above test was that of the kexec-tools package that includes review
comments from dannf.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1659618
Title:
Enable ARM64 support in
Sorry made no difference
Mike
Sent from: YOGA TABLET
Joseph Salisbury wrote:
>You may need to run the following from a terminal:
>
>sudo apt-get install -f
>sudo apt-get clean
>sudo apt-get update
>
>Then re-install the package or updates.
>
>If that does not
Does the bug go away if you boot into the previous kernel version?
** Changed in: linux-lts-vivid (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-lts-vivid (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
**
Does the bug go away if you boot into the previous kernel version?
** Changed in: linux-lts-vivid (Ubuntu)
Status: New => Triaged
** Changed in: linux-lts-vivid (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
**
** Changed in: pulseaudio
Status: Unknown => Confirmed
** Changed in: pulseaudio
Importance: Unknown => Medium
--
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/1438510
Title:
Glad you figured it out, I suspected this had something to do with the
may_create/may_o_create code paths but couldn't wrap my head around it.
Hopefully this will be addressed upstream in the near future.
This change in behavior is surprising though, maybe this should be
documented in
(Hm, dmesg WARN on IOMMU seems to think I need
910170442944e1f8674fd5ddbeeb8ccd1877ea98, but that's unrelated...)
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658255/+attachment/4809482/+files/dmesg.txt
--
You received this bug notification because
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/1659623
Title:
Shutdown/reboot hang on Dell
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/1659621
Title:
Random freezes and reboots
Writing a udev rule to ignore device by ModemManager worked for me:
/etc/udev/rules.d/55-bluetooth-drone-NoModem.rules
KERNEL=="rfcomm*", ATTR{address}=="xx:d3:xx:00:xx:xx",
ENV{ID_MM_DEVICE_IGNORE}="1"
And reloading rules:
sudo udevadm control --reload-rules
So I connect to device as root
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-27_02-22-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The bug is still there if I boot into the previous kernel version
(3.19.0-79.87~14.04.1). However, two weeks ago it did not has this bug
with the previous proposed kernel (3.19.0-79.87~14.04.1).
--
You received this bug notification because you are a member of Kernel
Packages, which is
The bug is still there if I boot into the previous kernel version
(3.19.0-79.87~14.04.1). However, two weeks ago it did not has this bug
with the previous proposed kernel (3.19.0-79.87~14.04.1).
--
You received this bug notification because you are a member of Kernel
Packages, which is
The bug is still there if I boot into the previous kernel version
(3.19.0-80.88~14.04.1). However, two weeks ago it did not has this bug
with the previous proposed kernel (3.19.0-80.88~14.04.1).
--
You received this bug notification because you are a member of Kernel
Packages, which is
4.5 final: Passed (boots up and works ok)
4.6 final: Passed
4.7 final: Passed
4.8-rc1: Passed
4.8.0-26: Failed
@Joseph, all the 4 kernel versions that you wanted me to test, work. My PC
boots up, and Ubuntu can be used as usual.
4.8.0-26 and all the later 4.8.0-xx versions hang at the grub
tests ran: 33, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_06-59-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-26_06-59-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_08-17-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Ben Romer
(bromer)
** Changed in: kernel-sru-workflow/prepare-package-signed
tests ran: 11, failed: 2;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_08-06-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks Manoj! A few comments on your prepared package.
- We need to fix in zesty and yakkety as well as xenial
- Version for xenial should be 1:2.0.10-1ubuntu2.1
- Is arm64_build.patch needed? I know we had to add it to Debian for compat w/
sid's toolchain, but I'm not sure we need it for Ubuntu
Updated changelog to refer to LP: #1659618
new debdiff attached.
** Patch added: "updated debdiff - changelog referring to LP# 1659618"
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+attachment/4809480/+files/updated-debdiff-withLP%23.diff
--
You received this bug
Both kernels behave like any of the kernels from 4.5: no sound on HDMI.
Recapping:
Ubuntu 4.4.0-59: HDMI audio works properly
Mainline 4.4 (any): i915 drm driver does not seem to support Skylake,
HDMI audio not enumerated
All of the below kernels exhibit the same problem: HDMI produces no
** Tags added: kernel-da-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/1659654
Title:
regression in linux-libc-dev in yakkety: C++ style comments are not
allowed in ISO C90
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1659654
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
** 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/1659654
Title:
regression in linux-libc-dev in yakkety: C++ style
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.8 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
Does this bug go away if you boot back into the prior kernel version?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1659621
** Changed in: linux (Ubuntu Yakkety)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Yakkety)
Assignee:
Public bug reported:
klibc is failing to build on arm64 in yakkety because of a change in
unistd.h in linux-libc-dev somewhere between 4.4.0-9136.55 and
4.8.0-36.38:
gcc -Wp,-MD,usr/klibc/syscalls/.SYSCALLS.i.d -nostdinc -iwithprefix include
-I/<>/usr/include/arch/arm64
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1659654
Title:
regression in linux-libc-dev in yakkety: C++ style comments
As a complement to my previous comment: both computers have a
significant amount of RAM (4 and 8 Go respectively) and the swap
partition is shown as not used by the system monitor.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-26_09-40-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Yakkety)
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/1646574
Title:
Mouse cursor invisible or does not move
tests ran: 16, failed: 9;
http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_10-24-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
After much consideration I have finally decided to buy Dell 7566 - a
Skylake 6700hq version (a successor of 7559 model).
I am running Debian testing (Stretch) with kernel 4.8.0.2 with nouveau
driver. After testing it for while I can now confidently say that in
this configuration the 7566 model
tests ran: 33, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-27_01-08-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The attachment "updated debdiff - changelog referring to LP# 1659618"
seems to be a debdiff. The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff. If the attachment isn't a patch, please remove the "patch"
flag from the
So, those patches do not need to be reverted. The actual panic was
likely something other than i915_bpo related.
--
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/1658999
Title:
[Xenial
Oh, and that's not set up by the bootloader, it's in
arch/x86/boot/compressed/eboot.c:
boot_params->secure_boot = get_secure_boot();
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
the proc handler does:
secure_boot_enabled = efi_enabled(EFI_SECURE_BOOT);
this feature flag is set at boot:
#ifdef CONFIG_EFI_SECURE_BOOT_SIG_ENFORCE
if (boot_params.secure_boot == EFI_SECURE_BOOT) {
set_bit(EFI_SECURE_BOOT, );
And that must be doing something wrong, since:
sudo efivar -p -n $(efivar --list | grep SecureBoot)
shows "1"
--
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/1658255
Title:
Kernel not
tests ran: 33, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_23-17-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
And it looks like this is specific to the 4.8 kernel. 4.4 thinks secure
boot is enabled.
--
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/1658255
Title:
Kernel not enforcing module
tests ran: 16, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_23-51-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have reproduced this and can confirm it only affects 4.8 kernels. I
have a Ubuntu 16.04 system with secure boot enabled, and the 4.4 kernels
were enforcing it. Installing and rebooting into the linux-image-
generic-hwe-edge kernel (4.8.0-34.36~16.04.1-generic) and everything
before the kernel
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-27_00-26-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 141, failed: 28;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-27_00-02-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-27_00-27-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-26_23-51-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kexec-tools (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1659618
Title:
Enable ARM64 support in kexec-tools
Trying the fsuid/fsgid workaround, I came across another oddity:
$ id -u
1000
$ id -g
1000
$ unshare -r -U -m /bin/bash
# mount -t tmpfs tmpfs /mnt
# chmod 555 /mnt
# ls -ldn /mnt
dr-xr-xr-x 2 0 0 40 Jan 26 14:15 /mnt
# echo $$
2354
In another terminal:
$ sudo nsenter -G 1000 -S 1000 -t 2354 -m
Thinking more about it, this might be due to the lack of
CAP_DAC_OVERRIDE so I guess I need this too right?
--
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/1659087
Title:
open(2) returns
tests ran: 4, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_23-03-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 18, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-26_22-47-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_22-24-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 18, failed: 2;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_22-25-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
maybe this delimit the issue:
Lenovo 710S (KabyLake i5-7200):
4.7.5 passed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.5/
4.7.6 failed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.6/
4.7.10 failed http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.10/
4.9.6 failed
OK, I got the first kernel (v4.4-wily) validated that it works properly.
I IPL'ed back to the 4.4.0-59 to validate the problem had not suddenly
vanished, still there.
So:
4.4.0-59 bad / has the issue
v4.4-wily working / no issue
Do you still need me to install / test / validate the v4.5-rc1-wily
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-26_22-30-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Why 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/1608236
Title:
Regression: S-video output does not work
Status in linux package in Ubuntu:
Incomplete
Status in linux
101 - 173 of 173 matches
Mail list logo