Bug is still ailve. Reproduce every time I'm copying files to usb hdd.
Ubuntu 24.04 LTS Gnome Desktop
uname -a
Linux 6.8.0-39-generic #39-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 5 21:49:14 UTC
2024 x86_64 x86_64 x86_64 GNU/Linux
dmesq:
[14692.691038] xhci_hcd :0d:00.0: WARN Event TRB for slot
Same issue on my Ubuntu Budgie with asus ux433f:
$ uname -a
Linux 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64
x86_64 x86_64 GNU/Linux
Wi-fi and bluetooth aren't work together and Wi-Fi is suddenly
disconnected :(
dmesg shows:
"...
[2.179463] iwlwifi :00:14.3: loa
ah, here is actually an issue:
the kernel 6.9.x have the fix (this?
https://lore.kernel.org/lkml/20240123113246.75539-1-mstro...@opensource.cirrus.com/T/)
so the sound there is working.
but kernel 6.8.0-xx is much better. the video driver works, the energy
consumption is 4 times less.
jus
The solution for me was:
1) install mainline
```
udo add-apt-repository ppa:cappelikan/ppa
sudo apt update && sudo apt upgrade -y
sudo apt install -y mainline
```
kernel for sound 6.9.12
2) isntall sound driver over systems (remove the system ones)
```
sudo rm -r /lib/firmware/intel/sof-ipc4-
Public bug reported:
This is a request for a backport of the following upstream patch from
4.18:
"bcache: stop bcache device when backing device is offline"
https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee
Field engineering uses bcache quite extensively and it wo
Setting to 'Confirmed' as the issue was fixed upstream and this is a
backport request.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- bcache device is accessible even if a backing device is not (writeback mode)
+ [4.15] bcache device is accessible even
Just reproduced it on my env (where things used to work) after updating
from MAAS 2.5.0~rc2 to 2.5.2.
https://paste.ubuntu.com/p/CY834ZGnvS/
[ 15.458594] VFS: Cannot open root device
"squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bion"; or
unknown-block(0,0): error -6
tree /var/l
echo -n
'BOOT_IMAGE=http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/boot-kernel
nomodeset ro
root=squash:http://10.10.101.2:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs
ip=maas-vhost6:BOOTIF ip6=off overlayroot=tmpfs
overlayroot_cfgdisk=disabled cc:{'datasource_l
The kernel code path mentioned in #55 is only executed if there is no
"early userspace init" - in other words, if there is no /init on initrd:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/init/main.c?id=Ubuntu-4.15.0-47.50#n1087
/*
* check if th
I cannot reproduce the same with a xenial (GA kernel) image with 2048
MiB of RAM allocated to a VM.
So it seems to me that this is a kernel issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Found something interesting.
Bionic + 2048 MiB of RAM (bad):
[1.520243] Unpacking initramfs...
[ 14.712821] Initramfs unpacking failed: broken padding
[ 14.723088] Freeing initrd memory: 56636K
Bionic + 2049 MiB of RAM (good):
[0.752624] Unpacking initramfs...
[5.572407] Freeing
Tested bionic-hwe - the issue does not occur with 2048 MiB.
The closest issue filed upstream I found is this:
https://bugzilla.kernel.org/show_bug.cgi?id=199845
** Bug watch added: Linux Kernel Bug Tracker #199845
https://bugzilla.kernel.org/show_bug.cgi?id=199845
--
You received this bug no
** Changed in: qemu (Ubuntu)
Status: Confirmed => 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/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes t
tar -czvf boot-resources-20190419-115735-amd64-generic-bionic.tar.gz
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/
boot-resources/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/
boot-resources/s
The bionic/ga files from #63 need to be placed into both dirs:
1) /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-18.04/bionic/daily
2) /var/lib/maas/boot-resources/current/ubuntu/amd64/generic/bionic/daily
The sha256 of the *initrd file* that triggers the issue is
69ca457a119fe309d315972ca
Tried using direct kernel boot with QEMU and couldn't reproduce it:
sha256sum
/mnt/libvirt-images/boot-resources-20190419-115735/snapshot-20190419-115735/ubuntu/amd64/generic/bionic/daily/boot-initrd
69ca457a119fe309d315972ca2756a17bd9bc55bc98f2bea5542566a7f41b08f
/mnt/libvirt-images/boot-resou
Recently hit that on Focal due to the fact that quotas were enabled by
LXD.
This renders the system completely unresponsive if you use btrfs as a
rootfs with btrfs-transaction or btrfs-cleaner kernel threads hogging a
100% of 1 CPU core.
Booting using a live USB, disabling quotas and temporarily
** Tags added: champagne
--
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/1838151
Title:
Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing
wide band speech support.
Sandor,
Not on the VRF usage side but there is a feature in MAAS 2.6 to have a
better way to work in multi-homed environments (for bionic+ machines):
https://docs.maas.io/2.6/en/intro-new
"Networking - Multiple default gateways"
It relies on "routing policy database" (RPDB) functionality
https:/
** Also 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/1728256
Title:
Memory corruption in Windows 10 guest / amd64
S
Dup:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728256
https://bugs.launchpad.net/qemu/+bug/1728256/comments/11
This affects other guests like W2k12r2 and Windows 10 as well.
** Tags added: cpe-onsite
--
You received this bug notification because you are a member of Kernel
Packages,
Got similar behavior with windows server 2012r2 VMs.
Environment:
uname -a
Linux ubuntu-q87 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ii linux-image-4.13.0-36-generic
4.13.0-36.40~16.04.1 am
It's not caused by WiFi card. As I understand, this error is produced by
AMD Ryzen2200 processor. I have the same problem too.
--
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/1758545
Title:
nvidia-xconfig -generated xorg.conf looked like this
https://paste.ubuntu.com/p/4hRVzHmbJV/
--
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/1785964
Title:
Unable to unlock the desktop ses
Had this with nvidia graphics drivers after installing and then removing
proprietary drivers downloaded from nvidia website. I could not log in
at all at first boot.
If you see nvidia modules loaded, make sure that you select an xorg
session on the login screen (not wayland) if you this control pr
Public bug reported:
I ran into a problem with the console argument handling on a physical
system with a BMC (Dell R610) and also reproduced the same behavior on a
QEMU/KVM VM with multiple serial ports.
The kernel documentation notes that the last entry will
https://www.kernel.org/doc/Documenta
** Description changed:
I ran into a problem with the console argument handling on a physical
system with a BMC (Dell R610) and also reproduced the same behavior on a
QEMU/KVM VM with multiple serial ports.
- The kernel documentation notes that the last entry will
+ The kernel documentat
apport information
** Tags added: apport-collected uec-images
** Description changed:
I ran into a problem with the console argument handling on a physical
system with a BMC (Dell R610) and also reproduced the same behavior on a
QEMU/KVM VM with multiple serial ports.
The kernel docum
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219759/+files/ProcEnviron.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/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219763/+files/WifiSyslog.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/bug
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219758/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
The information above is from a VM with a reproducer.
** 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/1807140
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219760/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219756/+files/Lspci.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/1807140
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219755/+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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219762/+files/UdevDb.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/1807140
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219757/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1807140/+attachment/5219761/+files/ProcModules.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/b
I have the same issue on the Razer Blade 2017 - the kernel log is
flooded with messages.
Disabling PCIe Active State Power Management helps:
GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
pcie_aspm=off"
Tested that on 4.11.0-041100rc8-generic.
** Attachment added: "dmesg_pcie_asp
Public bug reported:
The kernel log is constantly filled with the following:
236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
[ 236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected,
type=Data Link Layer, id=00e5(Transmitter ID)
[ 236.912553] pcieport
This is most likely a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173
--
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/1687714
Title:
Unless pcie_aspm is disabled
Hi Joseph,
Not a regression. I installed Zesty while it was in beta on this machine
and an issue was there already.
Tried 4.8 on a live usb - had that issue as well.
This is a relatively new hw so 4.4 kernel was not possible to boot
properly.
--
You received this bug notification because you a
Reproduced on 4.8-36-generic (the log has rotated due to the volume of
messages so the kernel version message is not there).
** Attachment added: "pcie_aspm_4.8.0-36-generic.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714/+attachment/4871082/+files/pcie_aspm_4.8.0-36-generic.
Reproduced on 4.8-36-generic (the log has rotated due to the volume of
messages so the kernel version message is not there).
** Attachment added: "pcie_aspm_4.8.0-36-generic.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714/+attachment/4871081/+files/pcie_aspm_4.8.0-36-generic.
Joseph,
I did (the log rotated so you don't see the version number):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714/+attachment/4870948/+files/dmesg_pcie_aspm_rc8.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Kalle,
The chip firmware was a guess based upon somebody else's feedback:
http://lists.infradead.org/pipermail/ath10k/2016-January/006714.html
It might not be true at all and I have done some investigation after
creating this bug report a month ago.
My notes from back then:
- iperf tcp vs udp p
Thanks Joseph! I will try it out.
--
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/1670041
Title:
Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
1535)
Status in
Hi, just a quick update: I have not forgotten about trying out the new
kernel. I am currently geographically far away from the access point
that I used for testing and it is hard to find 802.11ac Wi-Fi in the
wild.
I will provide the test results once I get to the right environment.
--
You recei
Eudald, I am sure. Tested multiple times.
# edit /etc/default/grub
sudo update-grub
sudo shutdown -r now
and you should be good.
https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.txt
pcie_aspm= [PCIE] Forcibly enable or disable PCIe Active State
Power
There is a scenario where a real rootfs is located on a bcache device,
however, for that we need to register a bcache device at the initrd
stage which already happens now. Then we'd locate a file system on it
and do pivot_root and so on.
The bcache naming, I believe, is not guaranteed at this poin
There's also Intel 9260 coming up (wave 2):
https://wikidevi.com/wiki/Intel_Dual_Band_Wireless-AC_9260_(9260NGW)
Judging by this https://communities.intel.com/message/506847#506847 it's
only available for OEMs as of now so maybe those will go into
circulation soon for regular folks.
Meanwhile, I
So, going back to question in #60, the Dell link just says to get the
latest stuff from kvalo's firmware repo.
If you are on 17.10 like myself then you already have it and it doesn't
help with the original problem:
➜ ~ apt policy linux-firmware
linux-firmware:
Installed: 1.169
Candidate: 1.
** Tags added: cpe-onsite
--
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/1729145
Title:
/dev/bcache/by-uuid links not created after reboot
Status in linux package in Ubuntu:
Triaged
S
Marcos,
#68
Regardless of fastboot on/off I get the same behavior without
pcie_aspm=off
➜ ~ uname -r
4.13.0-16-generic
--
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/1521173
Title:
A
I reviewed this once again:
1. persistent /dev/bcache - not possible or needed due to how kernel
enumeration works
2. our userspace handles /dev/by-dname/ properly so we just need
CACHED_UUID given to us during coldplug in some way to properly create
/dev/bcache/by-uuid/ symlinks and consequent
So, the kernel fix could look like this:
* instead of just failing with "device already registered"
* the kernel would emit another uevent with CACHED_UUID which would be
processed another time to set up a symlink
It seems like this approach with "synthetic uevents" may be used for
other purpose
We do run udevd at the initramfs stage in init-top and stop it in init-
bottom:
➜ scripts git:(ubuntu/xenial-updates) ✗ grep -RiP udev
init-bottom/udev:# Stop udevd, we'll miss a few events while we run init, but
we catch up
init-bottom/udev:udevadm control --exit
init-top/udev:SYSTEMD_LOG_LEVE
After booting with break=bottom kernel parameter I can see that symlinks
are in fact present at the initramfs stage.
They are gone afterwards post pivot_root & systemd start (the bcache dir
isn't even present while it was there)
ubuntu@maas-xenial4:~$ ls /dev/disk/
by-dname by-id by-label by-p
Just in case also checked with this rule that creates links at /dev
/dev/disk/by-uuid /dev/bcache/by-uuid https://paste.ubuntu.com/26081756/
They are all there originally (see the screenshot).
But not there afterwards. So it's not just a problem with a different
path.
https://paste.ubuntu.com/26
Ryan,
As discussed in IRC, I tweaked locations for testing in #11 and added
all paths in #14.
Looks like after `mount -n -o move /dev ${rootmnt}/dev` ${rootmnt}/dev
has the proper content (see the bcache rule as well)
https://paste.ubuntu.com/26082611/
== before ==
lrwxrwxrwx113
/de
Looks like masking systemd-udevd removes this behavior. Need to figure
out where it actually clears everything out.
ubuntu@maas-xenial4:~$ sudo systemctl mask systemd-udevd
11:32 PM Created symlink from /etc/systemd/system/systemd-udevd.service to
/dev/null.
# reboot
ubuntu@maas-xenial4:~$ ls /
John,
Interfaces of a host carry enough information to be used to make routing
decisions - that's the core idea of host and router-side VRF
implementations. Network spaces as of now do not help you to solve
routing problems in any way unless you have one big L2 network and
"routing" is done withou
Public bug reported:
окт 06 13:49:20 blade kernel: asynchronous wait on fence
i915:gnome-shell[2505]/1:42b timed out
окт 06 13:49:21 blade kernel: [drm] GPU HANG: ecode 9:0:0x96dbccee, in
qtdemux0:sink [5106], reason: Hang on rcs0, action: reset
окт 06 13:49:21 blade kernel: [drm] GPU hangs can
Haven't noticed that issue on previous kernels although I was mostly
using NVIDIA GPU not integrated intel GPU as in this case.
I will try to reproduce this on 4.14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
Haven't noticed that issue on previous kernels although I was mostly
using NVIDIA GPU not integrated intel GPU as in this case.
I will try to reproduce this on 4.14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
Public bug reported:
Problem description:
* a host is multi-homed if it has multiple network interfaces with L3
addresses configured (physical or virtual interfaces, natural to
OpenStack regardless of IPv4/IPv6 and IPv6 in general);
* if all hosts that need to participate in L3 communication are
For Ubuntu kernel this is a backport request.
--
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/1737428
Title:
VRF support to solve routing problems associated with multi-homing
Status in
** Description changed:
Problem description:
* a host is multi-homed if it has multiple network interfaces with L3
addresses configured (physical or virtual interfaces, natural to
OpenStack regardless of IPv4/IPv6 and IPv6 in general);
* if all hosts that need to participate in L3
** Description changed:
Problem description:
* a host is multi-homed if it has multiple network interfaces with L3
addresses configured (physical or virtual interfaces, natural to
OpenStack regardless of IPv4/IPv6 and IPv6 in general);
+
+ (see 3.3.4 Local Multihoming
+ https://tools.
ubuntu-fan clearly triggers the problem.
Clean machine, no bridges after Juju installs ubuntu-fan and networking
still works as bridges were not created yet => no ifup/down executions:
root@maas-xenial3:/home/ubuntu# ifdown -a ; ifup -a
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expressio
Before and after ifdown -> ifup with fan:
http://paste.ubuntu.com/26169937/
After purging:
http://paste.ubuntu.com/26169950/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
This is reproducible on a machine with a single NIC:
https://paste.ubuntu.com/26170595/
** Summary changed:
- bridge activaction error: bridge activation failed | unconfigured interfaces
cause ifup failures
+ /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured
interfaces
Tested that on a "broken" environment (after a reboot with a broken
package):
root@maas-xenial3:~# apt install ubuntu-fan
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
ubuntu-fan
1 upgraded, 0 newly instal
*** This bug is a duplicate of bug 1737640 ***
https://bugs.launchpad.net/bugs/1737640
** This bug has been marked a duplicate of bug 1737640
/usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured
interfaces cause ifup failures
--
You received this bug notification bec
Andres,
I'm not going to be at the sprint but the problems described need a
proper solution in MAAS and Juju at least from the end host perspective.
Similar to how VLANs are supported natively in MAAS & Juju, L3
virtualization technologies like VRF should be as well. I hope the
information I will
I can confirm this behavior on 4.13 -> 4.15rc4 with Intel 9260NGW.
3b:00.0 Network controller: Intel Corporation Device 2526 (rev 29)
Subsystem: Intel Corporation Device 0014
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at dd20 (64-bit, non-prefetchable) [si
Tested 9260NGW with different kernels (-33 for 4.13, -34 for 4.14 and
4.15):
1) 4.13.0-21.24 + iwlwifi-9260-th-b0-jf-b0-33.ucode: could not connect
to any network, "Unhandled alg: 0x707"
wlp59s0: associated
and then immediately
deauthenticating from ...
see https://paste.ubuntu.com/26234416/
One additional detail. Even on 4.15 "Unhandled alg" can be reproduced
occasionally after disconnecting and reconnecting the adapter to an STA:
дек 22 22:12:45 blade kernel: iwlwifi :3b:00.0: Unhandled alg: 0x707
дек 22 22:12:45 blade kernel: iwlwifi :3b:00.0: Unhandled alg: 0x707
дек 22 22
Public bug reported:
I wanted to test a snap application called clementine and opened up
preferences after it was launched and playing music. After clicking on
something my whole system hanged.
Regardless of the app, I decided to lookup how something like that could
manage to "kill" the whole sys
Just to clarify on UUIDs - there are 3 types of UUIDs in question:
1. cache set UUIDs (upstream docs mention that multiple cache devices per cache
set are not supported but a configuration with M:N as in
: has been taken into account)
2. cache device superblock UUIDs;
3. backing device superbloc
Joseph,
No luck on 4.12.0-041200rc4-generic, unfortunately:
https://paste.ubuntu.com/24826561/
--
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/1670041
Title:
Poor performance of Atheros
Got a repro on 4.13.0-041300rc7 with the debug mask above set.
** Attachment added: "ath10k-repro3.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+attachment/4942967/+files/ath10k-repro3.log
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "ath10k-repro4.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+attachment/4943912/+files/ath10k-repro4.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
I don't have a special wireless off/on button on my keyboard but I'm
assuming rfkill will do (soft kill switch).
The issue does not get triggered by the following loop (I may leave it
for several hours to get a better picture and modify to wait more
intelligently):
➜ ~ while test 1 ; do rfkill
I did get a lot of corrected PCIe errors previously which is why I set
pcie_aspm=off (otherwise it flooded my kernel log instantly)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687714
https://launchpadlibrarian.net/318000853/dmesg_pcie_aspm_rc8.log
I need to think of a good test for oth
This is the most heavily loaded configuration I use with this device and
I don't have issues with either an NVMe SSD or GPU. No hardware-related
issues with any USB devices (data goes through PCIe in the end).
➜ ~ lspci -v -t
-[:00]-+-00.0 Intel Corporation Device 5910
+-01.0
4.13 without modifications:
http://paste.ubuntu.com/25499163/
scp (cubic)
➜ /tmp scp testfile srv:/tmp
testfile
I will try 2 things:
1. re-seat the card
2. get a card from a different manufacturer and test.
It might be a buggy slot in the motherboard and if the problem persists
with a new card I will know for sure that the slot is defective.
--
You received this bug notification because you are a member
Sorry, I should have mentioned that before: in the original test I also
had a device plugged in via usb type-c (thunderbolt 3) - that device had
an ethernet interface which you can see in the logs. It's another
problem that I need to debug because type-c hot-plug of that device
worked once but succ
Gathering more evidence in support of a faulty motherboard theory.
At some point I got this (system wasn't under heavy load - just a
browser opened + remote video playback):
https://gist.github.com/dshcherb/06f4e4a0260b6d5313df1594d959849a#file-
nvme-failure-razer-dmesg-log-L2073
сен 10 22:23:3
Eric,
I should have tried cubic in the previous (#46) test - quite an
interesting result: http://paste.ubuntu.com/25200234/ (6 tests cubic &
bbr)
lspci | grep QCA
3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network
Adapter (rev 32)
With cubic cwnd grows quite quickly
SRU request thread:
https://lists.ubuntu.com/archives/kernel-team/2017-July/086054.html
--
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/1705493
Title:
[4.4][backport] Multiple partitions
Tested the patched kernel - the results are consistent now across laptop
-> server, server -> laptop tests for both TCP and UDP.
➜ ~ uname -a
Linux blade 4.10.0-20-generic #22~lp1670041 SMP Fri May 5 18:23:15 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
4 tests:
1) laptop -> server via AP (TCP);
2)
Hi,
Guys, it should be there for both the Yakkety kernel and linux-generic-
hwe-16.04:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=7570ffb5145abf4413421c154077bc31abad1264
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
yakkety.git/commit/?id=5e0bc558603351c8ce573913ba64b169082
Sorry about the confusion: the commits are tagged with -53 and I
mentioned -52 in the apt output.
--
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/1679823
Title:
bond0: Invalid MTU 9000 re
** Description changed:
+ Update (2017-05-20):
+ Kalle Valo suggested a hack which increased client -> AP TCP performance - so
it does not look like a firmware issue as I thought originally, rather an
ath10k driver issue:
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
Public bug reported:
I experience a very poor 802.11ac performance of a QCA6174 Wireless card
(Killer Wireless 1535).
This is a dev version of Zesty with a recently released 4.10 kernel:
uname -r
4.10.0-9-generic
dpkg -l linux-firmware | grep ii
ii linux-firmware 1.163all Fir
Just to rule out the case of bad compatibility between the STA on the
router (Quantenna QSR1000 chipset, QT3840BC SoC in case of my RT-87U)
and the client WNIC I also checked with a different STA.
So the second router's 802.11ac hardware is Compex_WLE900VX Qualcomm
Atheros QCA9880 (V2) which uses
** Description changed:
- I experience a very poor 802.11ac performance of a QCA6174 Wireless card
- (Killer Wireless 1535).
+ Update: added some forensics in the paste (a long read):
+ http://paste.ubuntu.com/24118478/
+
+ TL;DR with a bit of intuition:
+ We need a new firmware-5.bin from Qualco
Confirmed *NFA364xp.bin and qca61x4_2_2.bin usage by Windows. linux-
firmware's version is definitely not up-to-date for this card as it
refers to NFA324i (see the paste link).
** Attachment added: ".inf file parsed by Windows"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/+atta
1 - 100 of 153 matches
Mail list logo
