This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1672344
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
I also have to say that the system where I experienced this error is not
with me anymore.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1415880
Title:
14e4:4365 bcmwl-kernel source:
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_09-44-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
Huang YangWen: can you attach result of those command:
ls -l /sys/bus/acpi/devices/
sudo lspci -vvnn
I wonder what the differences between motherboards are. I suspect Gigabyte has
something other boards don't have.
--
You received this bug notification because you are a member of Kernel
@anthony ... technically that would be me ... practically the gadget
will never update the firmware files (the firmware files as well as the
dtb are usually in a dead-lock with the kernel version)
i'm waiting for a solution for this from the core team before we can
move on ... your best bet is to
@ying-chun the kernel snap only upgrades the kerne, modules and files in
/lib/firmware ...
the gadget snap only updates the gadget.yaml, snap.yaml and files not in
/boot (i.e. it excludes all bootloader bits by default). until there is
a solution for potential unbootable systems this will not
Default Comment by Bridge
** Attachment added: "crash_7.1.7-1_ppc64el.deb"
https://bugs.launchpad.net/bugs/1672361/+attachment/4836960/+files/crash_7.1.7-1_ppc64el.deb
** Changed in: ubuntu
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
** Package changed: ubuntu =>
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/onibi__3.13.0-113.160~precise1__2017-03-13_13-19-00/results-index.html
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Kernel
Packages, which
m4.10xl also looks good:
[7399124.202570] lp1497428: module verification failed: signature and/or
required key missing - tainting kernel
[7399124.223762] pageblock_nr_pages 0x200
[7399124.226007] node 0 zone 0 info:
[7399124.227849] node 0 zone 0 provided page pfn 0xfff valid 1 present 1
Public bug reported:
Test: test_152_sysctl_disables_apparmor_unpriv_userns failed on
4.4.0-1008.17 - aws
This issue can't be found on 4.4.0-67.88 generic kernel for aws.
There was once a similar bug for this, please refer to bug 1636461
FAIL: test_152_sysctl_disables_apparmor_unpriv_userns
You have been subscribed to a public bug:
Please cherry pick
Upstream commit 651c824ffe2fd7eb8e416dbf4ff5c9a1da6ef7c6
commit 24a696228c56fd4354d29abe05b206373e0c8bfb
** Affects: crash (Ubuntu)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_10-50-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
** Description changed:
Test: test_152_sysctl_disables_apparmor_unpriv_userns failed on
4.4.0-1008.17 - aws
This issue can't be found on 4.4.0-67.88 generic kernel for aws.
- There was once a bug for this, please refer to bug 1636461
+ There was once a similar bug for this, please refer
I just installed the latest upstream kernel but since I cannot reproduce
this issue manually I need some time (1-5 days) of full testing in order
to update this bug report.
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Public bug reported:
This shouldn't be needed anymore, and it wasn't really effective anyway
due to the way the kernel selftests are being invoked.
** Affects: linux (Ubuntu)
Importance: Low
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Changed in: linux (Ubuntu)
** Tags added: regression-testing-passed
--
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/1671232
Title:
linux: 3.13.0-113.160 -proposed tracker
Status in Kernel SRU Workflow:
In
You have been subscribed to a public bug:
I use a very low and laptop with a built in rtl8723b wifi card. I always
used the driver from lwfinger on github and that one worked well.
But now Ubuntu comes with a driver for this card but that does not work on
normal boot.
Strange thing is this
** Changed in: kernel-sru-workflow/regression-testing
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/1671232
Title:
linux: 3.13.0-113.160
Public bug reported:
Testing failed on:
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/b/bcmwl/20170310_122529_bc576@/log.gz
** Affects: bcmwl (Ubuntu)
Importance: Undecided
Status: New
** Tags:
https://bugs.lttng.org/issues/1091
end of sudo lttng-sessiond -vvv shows that we have a vmalloc failure:
DEBUG1 - 14:25:37.954060 [10037/10081]: Woken up but nothing in the UST command
queue (in thread_dispatch_ust_registration() at main.c:1891)
DEBUG1 - 14:25:37.954072 [10037/10082]: Got the
** 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/1672198
Title:
RTL8723b Kernel driver not loading on normal boot.
Status in linux package in
Please include the stable release updates released this weekend
(v4.10.2). The following Hyper-V commits were included:
hyperv.h : commit ec6f27bd19e0f9142c71d293d4c3b381348550b7 : Drivers: hv:
vmbus: Fix a rescind handling bug
channel.c : commit ec6f27bd19e0f9142c71d293d4c3b381348550b7 :
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/onibi__3.13.0-113.160~precise1__2017-03-13_14-27-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/onibi__3.13.0-113.160~precise1__2017-03-13_14-04-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/onibi__3.13.0-113.160~precise1__2017-03-13_13-42-00/results-index.html
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
--
You received this bug
--- Comment From jac...@de.ibm.com 2017-03-13 09:57 EDT---
Next iteration: I was able to make OpenAFS for the proposed kernel fixed and so
I was able to start the next pdebuild job and again I run into a hang
scenario:
Mar 13 14:30:32 mclint multipathd[881]: mpatha: sda - tur
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1672397/+attachment/4837019/+files/make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1672397
Title:
bcmwl
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1672198
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
I was experimenting similar behaviour using kernel 4.6.0 x86_64 (linux
mint + cinnamon).
After upgrading to 4.8.0-040800-generic x86_64 seems fine now.
Regards
Luis F. Heckler
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
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/1672439
Title:
No C-State Deeper than C3
~$ sudo powertop (Idle Stats tab)
Package | Core|CPU 0 CPU 4
POLL0.0%| POLL0.0%| POLL0.0%0.0 ms 0.0%
0.0 ms
C1 0.8%| C1 0.3%| C1 0.3%0.2 ms 0.4%
0.6 ms
C2
Because I do not have access to the machine running Ubuntu now i ran
apport from my machine which is identical and has the identical problem
with RTL8723 just it runs Linux Mint. As you can see I tried various
Kernel up to 4.9 and the problem is the same with any kernel.
--
You received this bug
Installed:
intel-microcode_3.20161104.1~deb8u1~bpo7+1_amd6
--
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
~$ dmesg |grep idle
[0.00] clocksource: refined-jiffies: mask: 0x max_cycles:
0x, max_idle_ns: 7645519600211568 ns
[0.00] clocksource: hpet: mask: 0x max_cycles: 0x,
max_idle_ns: 79635855245 ns
[0.044934] process: using mwait in idle threads
[
Let me know what other information I could supply.
--
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
** Also affects: makedumpfile (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857051
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
Public bug reported:
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
apport information
** Tags added: apport-collected serena
** Description changed:
I use a very low and laptop with a built in rtl8723b wifi card. I always
used the driver from lwfinger on github and that one worked well.
But now Ubuntu comes with a driver for this card but that does
cat /sys/module/intel_idle/parameters/max_cstate
~$ cat /sys/module/intel_idle/parameters/max_cstate
9
--
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
~$ sudo i7z
sudo i7z
i7z DEBUG: i7z version: svn-r93-(27-MAY-2013)
i7z DEBUG: Found Intel Processor
i7z DEBUG:Stepping 9
i7z DEBUG:Model e
i7z DEBUG:Family 6
i7z DEBUG:Processor Type 0
i7z DEBUG:Extended Model 9
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Unknown
Hi Colin,
As you indicated it seems that an actual allocation problem occurred on:
syscall table list zmalloc: Cannot allocate memory (in syscall_table_list() at
syscall.c:291)
>From the code:
/*
tests ran: 7, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-67.88-lowlatency/gonzo__4.4.0-67.88__2017-03-13_14-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.
I confirm the same crash bug in Kernel versions:
4.4.0-66-generic
4.4.0-64-generic
4.4.0-21-generic
I could not test with latest upstream kernel because I needed ZFS (I
looked into building it for latest upstream, but found no reasonable
path).
I can also confirm the crash is related to a drive
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_08-42-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
Why the patch was dropped in the version 4.8.0.41.52 of linux-image-gerneric?
Does 4.8.0.41.52 corresponds to tag Ubuntu-4.8.0-41.44 ? If so, why the numbers
don't match ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
CPU is Ryzen 1700x
However lm-sensor is not working properly.
--
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/1671360
Title:
System doesn't boot properly on AMD Ryzen / Gigabyte
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_09-00-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
Works find with Ubuntu 16.04 + 4.10.1-041001-generic
The kernel is downloaded from Ubuntu website
motherboard ASUS PRIME B350-PLUS.
** Attachment added: "Screenshot from 2017-03-13 16-53-20.png"
** Changed in: hwe-next
Status: Confirmed => Invalid
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Thanks Kai-Heng.
Done (and attached.)
Many thanks,
A
On 13/03/17 15:56, Kai-Heng Feng wrote:
> We need some information from ACPI then.
>
> Please install acpica-tools and run acpidump,
>
> $ sudo apt install acpica-tools
> $ sudo acpidump > acpi-dump
>
> Attach acpi-dump file.
>
**
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_09-23-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
** Changed in: kernel-sru-workflow/automated-testing
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/1671232
Title:
linux: 3.13.0-113.160
Public bug reported:
happened during the post trigger install part
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-108-generic 3.13.0-108.155
ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic i686
ApportVersion:
Hi.
I tried to
"snap refresh pi3 --channel=edge"
"snap refresh pi2-kernel --channel=edge"
The rainbow square is still appeared. Is this the correct way to upgrade
gadgets and put the firmwares onto the system?
# snap info pi3
name: pi3
summary: "Raspberry Pi 3 support package"
** Tags removed: need-duplicate-check
--
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/1672318
Title:
package linux-image-extra-3.13.0-108-generic 3.13.0-108.155 failed to
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/1672318
Title:
package
I think I'm making wrong assumption? It seems to me that refresh gadget snaps
won't upgrade the files in the system.
Upgrading kernel snap does change the kernel/uboot.env stuff. But not for
gadgets right? Seems we need to regenerate an edge image for testing this?
--
You received this bug
Verified with the older 4.8.0-38 kernel, docker.io version
1.12.1-0ubuntu15 and 1.12.6-0ubuntu1~16.10.1 will both fail without the
-extra package as well.
So just like xnon mentioned above, we will need to add the missing
driver to the main kernel package.
--
You received this bug notification
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/gonzo__3.13.0-113.160~precise1__2017-03-13_08-22-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
Hi, here a video of the problem...
** Attachment added: "Demonstration"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663637/+attachment/4836850/+files/radeon_flickering.mp4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Looks like this has been corrected, from a recent c4.8xl launch:
--
[0.00] Linux version 3.13.0-71-generic (buildd@lgw01-09) (gcc version
4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015
(Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29)
[0.00] Command line:
** Description changed:
After starting `btrfs scrub start /` `dmesg` contains
```
[Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds.
[ +0,09] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu
[ +0,05] "echo 0 >
We received the hardware back and have started testing all blockers
again. The latest test of the above mentioned PPA did not yield positive
results:
"Unable to find PowerPC CPU definition"
$ apt-cache policy qemu-system-ppc
qemu-system-ppc:
Installed: 1:2.5+dfsg-5ubuntu10.10
Candidate:
Hi Colin,
Please take a look at the following patch
https://lists.lttng.org/pipermail/lttng-dev/2017-March/026959.html
Could you report to us if it fixes your issue?
Please note that s390 is not supported/tested by LTTng-modules.
You probably encountered this bug since no syscalls tracepoints
same, very annoying
Thinkpad T440, with Linux Mint 18.1 Cinnamon (based on Ubuntu 16.04) and
a Logitech K380 bluetooth keyboard
lsb_release -rd
Description:Linux Mint 18.1 Serena
Release:18.1
uname -a
Linux xochiquetzal 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017
Public bug reported:
i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even in
this case when i try to install my nividia graphic cards driver, it
never boots again after installation.
my graphic card: nvidia 950m
** Affects: linux (Ubuntu)
Importance: Undecided
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1672563
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
This is a BIOS issue can you please attach dmidecode of your platform, I'd like
to know more detailed platform and bios information.
Also please add the while dmesg and cat /proc/iomem
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Thanks Jonathan, I'll get around to that first thing tomorrow morning.
Much appreciated.
--
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/1671063
Title:
ubuntu_lttng_smoke_test failed on
Dear All,
I had exactly the same situation of post #23. Coming from Kubuntu 16.04, bought
a new system Ryzen 1800x+GA-AB350 Gaming 3.
First boot, using the "old" SSD worked fine, so I decided to upgrade to version
16.10. The procedure goes well, but after the reboot got plenty of error
message
It did start as I had to use kernel 4.8 in order to get my multimedia
keys and suspend to ram working on that machine. With Kernel 4.4 I had
to compile the the driver from lwfinger in order to use wifi.
I will test kernel 4.11 tomorrow and report.
--
You received this bug notification because
Just to be sure I installed qemu-system-ppc version 1:2.6.1+dfsg-
0ubuntu5.3 from yakkety-updates and the tests pass.
--
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/1656112
Title:
Power
--- Comment From thiag...@br.ibm.com 2017-03-13 14:27 EDT---
Hello Canonical,
Let me provide a status update:
To fix this bug it's necessary to fix several issues with lifetime of
structures in the block subsystem, as well as a number of related race
conditions. A number of patches need
** 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/1672198
Title:
RTL8723b Kernel driver not loading on normal boot.
Thanks for the report. Given that the kernel version is larger than
4.4.0-48, it should be skipping the line that resets the expected value
to 0; it looks like the version comparison is falling back to the string
version when handling the abi portion of the version (likely due to
python-apt not
Could this be just a kernel issue? I had Flyme installed on my Pro 5 for
a couple a days and I did not reflashed the whole system, just restored
it with TWRP and yes, Android Flyme latest stable had suddenly an issue
with a noise and distortion when using a Bluetooth. Then I realised that
I have
Public bug reported:
The br_netfilter module processes packets traveling through its bridge,
and while processing each skb it places a special fake dst onto the skb.
When the skb leaves the bridge, it removes the fake dst and places a
real dst onto it. However, it uses a hook to do this, and
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_01-34-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've tried manually copy the binary blobs into /boot and the rainbow
square disappeared. And when the power is not enough it displayed a
"lightning" icon. So if we rebuild an image based on the gadget in edge
channel we should be able to fix the problem.
--
You received this bug notification
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1664809
Title:
[0bda:0328] Card reader failed after S3
Gerardus,
Can you make a Zesty LiveUSB and test if this issue happens?
I just grabbed a Killer 1535 and seems like the issue does not happen on
Zesty.
I'd like to make sure this issue is solved in 4.10, so I can bisect and
backport needed patch.
--
You received this bug notification because
** Tags added: kernel-da-key kernel-hyper-v
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: Tim Gardner (timg-tpi) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_01-55-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.13.0-113.160~precise1-generic/alkaid__3.13.0-113.160~precise1__2017-03-14_02-15-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is the bluetooth a USB device?
At least it's not listed in your USB devices.
--
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/1671854
Title:
Bluetooth not enabling
Status in linux
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
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 resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11
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 resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/ppc64el/l/linux/20170311_003703_69a51@/log.gz
Error building some of the tests, likely because of generating position
independent executables by default:
Public bug reported:
QDF2400 platforms require an erratum workaround to avoid a memory
corruption issue. This was fixed upstream in the following commit:
commit 90922a2d03d84de36bf8a9979d62580102f31a92
Author: Shanker Donthineni
Date: Tue Mar 7 08:20:38 2017 -0600
@Robert ... sure, let me clarify the events.
1. I had Ubuntu 16.04 LTS for some time already running on my system.
2. I bought AMD Ryzen 1800 + Gigabyte AB350 Gaming 3 and I took the SSD from
the old system and pushed it into the new one
3. Everything worked fine, except I had to install NVIDIA
@Maciej : I think you missunderstood ... both Gigabyte (mine) and Asus
boards (Huang`s) work fine with 16.04 LTS ... what you need to do .. is
ask Huang to try his luck with 16.10 :) or 17.04
So, Huang, can you make 2 DVD`s .. one with 16.10 and another with 17.04
(or 2 bootable flashes) and just
Does the bug go away if you boot back into the prior kernel version?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed
Public bug reported:
The zesty kernel has a backport of the MSI/PCIe passthrough changes for
arm64. This changeset introduced a bug that can cause a build failure
with certain configurations. Though it doesn't impact the Ubuntu config,
it could creep up again if we change our config. I reproduced
This is a simple patch for perf and a clean cherry pick from upstream.
I'm going ahead and applying it.
** 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
--- Comment From thiag...@br.ibm.com 2017-03-13 15:22 EDT---
Small update:
The following commit is not actually necessary. It fixes code which is
not present in v4.4:
e17354961bb5 zram_drv: update for backing dev info changes
--
You received this bug notification because you are a
1 - 100 of 140 matches
Mail list logo