The meta-packages have been rolled back and the fix is in progress of
being applied and 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/1779961
Title:
Boot delays with
Public bug reported:
We (Canonical CPC) are seeing an issue with today's build of the bionic
minimal cloud images. Boot stops at "Starting Initial cloud-init job
(metadata service crawler)..." for nearly 5 minutes (booting on
scalingstack and locally with kvm) this is with a new kernel, but
The package in proposed fixed the issue for me too.
--
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/1757008
Title:
bcmwl-kernel-source: bcmwl kernel module failed to build [error:
ignore comment 3, i retested it, with kernel
Linux deepthought 4.17.0-041700rc3-generic #201804300800 SMP Mon Apr 30
08:03:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
and the bug clearly still exists. My apologies.
317 root 20 0 172284 130324 3280 R 81.2 3.3 6:30.80
** Attachment added: "Screenshot at 2018-05-05 11-17-38.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+attachment/5134287/+files/Screenshot%20at%202018-05-05%2011-17-38.png
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete =>
It seems the kernel version
Linux deepthought 4.17.0-041700rc3-generic #201804300800 SMP Mon Apr 30
08:03:00 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
solves the issue, normal cpu usage with bluetooth turned on and device
connected, as identified in the below screenshots.
** Attachment added:
I can confirm, using said screenshot, i turned off bluetooth in my bios,
and as top shows in the below screenshot the bug seems resolved, so the
bug is confirmed.
** Attachment added: "Screenshot at 2018-04-29 08-57-39.png"
Public bug reported:
I can confirm the following bug in kernel version 4.15 in bionic,
https://bugzilla.kernel.org/show_bug.cgi?id=199035
I have thus booted into 4.13, and temporarily worked around the bug. If
you need any further information please tell me.
** Affects: linux (Ubuntu)
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-29.32-generic 4.13.13
Uname: Linux 4.13.0-29-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a
Can confirm, happens on my machine also with 4.13.0-25 and higher.
Symptoms are exactly the same as described above
Failure happens with all possible ways to hibernate: from GUI, console with
pm-hibernate or closing the lid
--
You received this bug notification because you are a member of
It already uses gtk3. It builds in this complicated way where it can use
either gtk3 or gtk2 at runtime, but presumably you can just stop
building the gtk2 support in.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in
2,8 cubic
iperf3 -c dest
Connecting to host dest, port 5201
[ 4] local src port 49522 connected to dest port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 6.17 MBytes 51.7 Mbits/sec6 91.9 KBytes
[ 4] 1.00-2.00 sec 8.34 MBytes 70.0
4.13-rc2 + tcp_output.c
- limit = max(2 * skb->truesize, sk->sk_pacing_rate >> 10);
+ limit = max(2 * skb->truesize, sk->sk_pacing_rate >> 7);
w/ cubic
% iperf3 -c dest
Connecting to host dest, port 5201
[ 4] local src port 47742 connected to dest port 5201
[ ID] Interval
Hi Eric,
This compares Cubic with BBR with 4.13-rc2 (which has a few new commits
to bbr.c):
wlan0: mtu 1500 qdisc mq state UP mode
DORMANT group default qlen 1000
$ cat /proc/sys/net/ipv4/tcp_congestion_control
cubic
$ iperf3 -c
Connecting to host , port 5201
Eric,
Is this patch the basis for a more permanent and general fix (it seems
not specific to ath10k)?
Thanks!
The patch produces a marked improvement with TCP from the local QCA6174
client to AP/remote.
4.12.0 (UDP; no patch)
% iperf3 -u -b 1000M -c remote
Connecting to host remote, port 5201
Thanks for the quick reply. Unfortunately this does not change anything
(also did a reboot to be sure).
--
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/1657553
Title:
Laptop stick and
Sorry, I should have specified this more clearly.
The trackpad works flawlessly, but the trackpoint is way too sensitive
rendering it unusable.
Changes in the (Linux Mint) mouse settings dialog show no effect.
BTW: The trackpoint worked great when booting from the Mint live cd,
which could
)]
⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=13 [slave pointer (2)]
Let me know if any other information is needed.
Thanks and best regards,
Philip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
And the build from -proposed fixes the other machine as well, thanks.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Kamal's build resolves the problem on one of our machines, I'll test the
other one once the package is in proposed.
--
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/1566726
Title:
System
Probably relevant: https://lkml.org/lkml/2016/3/9/590
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1566726
Title:
System freeze after update to 3.16.0-69-generic [NULL
Public bug reported:
So far I've seen this happen on 2 systems today. On one only X froze, the other
one panicked.
Booting into 3.16.0-67 is the workaround for now
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Date: Wed Apr 6
Thank you so much!
2016-02-04 1:54 GMT+06:00 Seth Arnold <1541...@bugs.launchpad.net>:
> Your filesystem is full; nothing will work well until you've freed some
> space. I suggest running:
>
> sudo apt-get clean
>
> Then use apt-get purge to remove some old linux packages. Be sure to
> leave at
Public bug reported:
The firmware crashed during regular wifi traffic and failed to restart
the card afterwards.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-5-generic 4.3.0-5.16
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
Public bug reported:
Happened during a LTS testupgrade from trusty to xenial
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-5-generic 4.3.0-5.16
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic x86_64
ApportVersion:
I still had this very same bug on an Asus f555l, I managed to get it
working with package bcmwl-kernel-source_6.30.223.248+bdcom-
0ubuntu1_amd64.deb which is not the one from the repos. I do not
understand if the bug is going to be actually fixed or what.
--
You received this bug notification
I am experiencing a same/similar issue on a Dell XPS13 Developer Edition
9333 and have seen it with linux-image-3.16.3-031603-generic (mainline)
linux-image-3.16.0-24-generic and linux-image-extra-3.16.0-23-generic. I
have attempted to test it with linux-image-3.18.0-031800rc2-generic but
it will
Public bug reported:
setup:
* amd fx8320
* nvdia graphic card
* 16gb ram
*ubuntu 14.10 beta
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic (not installed)
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
(In reply to comment #122)
I also get a mirrored output on VGA, however I could not extend to that
adapter. (it seems to be a hardware mirror, I only see one external display,
DP2, in XrandR...)
Same here. Switching to one external DP display now works like a charm.
Gets identified as DP2 in
(In reply to comment #125)
(In reply to comment #115)
I tried applying the two patches which you posted on intel-gfx[1], ported to
3.13.
[1] http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/33737
Using a T540p and an Ultradock, connected to a Dell U2410 via a
(In reply to comment #128)
(In reply to comment #124)
There seems to be still a problem enumerating the devices connected to the
DP hub
We currently do not support MST (multistream) DP branch devices. If it works
for multiple monitors, great, but it's more or less by accident.
Thank you
(In reply to comment #131)
(In reply to comment #129)
It seems the hang is resolved with the dock firmware update (2.17) provided
by Lenovo. As far as I am concerned I think this bug can be closed.
From the kernel perspective it's fixed when we don't freeze the machine even
when a dock
(In reply to comment #118)
Just installed the firmware update. Now dock shows firmware version 2.17.
Firmware update utility required Intel display-driver installed on my
Windows 8.1 installation, otherwise it was unable to update to detect the
DP-hub.
It also required a least one display
(In reply to comment #117)
That is beta firmware.
The Lenovo guy in there said final firmware would likely be released next
week.
And I asked for a bootable CD update, and other people did so as well.
The Lenovo guy in there said he'd pass on the request for a bootable CD
update.
Just
Just to add that I also have this bug in Kubuntu 13.10 and had it in
Ubuntu 13.04 on the same hardware previously.
Machine is a Dell Optiplex 755
My kernel is currently 3.11.0-13-generic 64 bit.
lspci -vv
00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI
Controller (rev
Public bug reported:
Fresh install of Mythbuntu 12.04.3 LTS.
from cli, ran 'sudo apt-get install -y gcc rar tar gzip
linux-headers-3.8.0-32-generic build-essential cvs libncurses5-dev unzip'
Error caused during the completion of this command.
Contents of
i have to revoke my previous statement: the bridge only makes the bug to
appear less frequent.
--
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/1197078
Title:
mininet created devices are
I am able to reproduce this bug with both kernel versions
Linux fgcn-of-4 3.11.0-5-generic #11-Ubuntu SMP Fri Sep 6 19:01:31 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
Linux fgcn-of-3 3.11.0-031100-generic #201309021735 SMP Mon Sep 2 21:36:21 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
i am using the
one small (and maybe weird) addition to my last post:
Whenever a system is configured with a bridge, the error seems NOT to occur. In
our lab we have 4 systems, two with configured bridges and two without. Only
the systems without bridges behave erroneous.
If, after a reboot, a bridge is added
Public bug reported:
Broadcom proprietary driver failed to install.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion:
I'm experiencing the same issue with Ralink RT5390, also using rt2800pci
(running Arch Linux with kernel 3.9.9, though).
As previously noted, changing the MAC address was working in previous
kernel versions. Currently only addresses very similar to the default
address can be set.
I fetched the
201 - 242 of 242 matches
Mail list logo