FYI, I'm using an XPS 15 9560, from this page:
https://wiki.archlinux.org/index.php/Dell_XPS_13_(9360)#Wireless
It says:
"The Killer 1535 Wirless Adapter is functional and the ath10k firmware is
included in recent linux kernel versions. The connection speed reported by iw
is limited to 1-6Mbits
I also can confirm, sound is not working on hammerhead.
Digging around a bit I did notice that the soundcard is being recognized at
least, so maybe it's a config problem?
I also seen that alsa is not starting the audio mixer..
This is my first attempt at porting so I hope the info I just provide
I just tried this on a ubuntu cloud 18.04.3 VM and it works. Could this
get foreported to the 4.15.x kernels as well?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1811819
Title:
pl
Both of those, B and D, are confirmed to work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1811819
Title:
please include the kernel module VXLAN
Status in linux-kvm package in Ub
I have the same with the headset that was initially reported - the
Sennheiser HD 4.50 BTNC. A2DP works perfectly.
--
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/1878194
Title:
[Sennheise
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
I can confirm that Michael's solution also fixed it for me. I didn't
have the 19.10 config to hand so I extracted default.pa from the .deb
from 19.10 as found here
https://launchpad.net/ubuntu/bionic/amd64/p
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
@Michael unfortunately, the fix did not persist for me through a reboot
either.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
ht
Public bug reported:
I have a customer running a cluster of servers on Ubuntu 16.04.1, kernel
4.15.0-43-generic. Two of the nodes on separate occasions experienced
kernel OOPS on Dec 21st and Dec 26th with similar call trace messaging:
Dec 21 10:18:27.200 node1 kernel: [1179506.273413] BUG: unabl
Thanks for the recommendation. Thought the same but wanted to be sure
that would be recommended POA for this. Will forward to customer and
work with them.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
They are running Intel Xeon Gold 5120 CPU so will recommend that as
well, thanks.
--
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/1859099
Title:
BUG: unable to handle kernel paging reques
Just curious on an update of when this should be available in the apt
repositories? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1811819
Title:
please include the kernel mo
Public bug reported:
To use kube-router as part of a kubernetes install, it requires kernel
module CONFIG_NETFILTER_XT_SET build it makes use of the 'set' module in
iptables.
Otherwise, since this kernel module is not built as a module nor
included in the kernel itself, iptables complains:
root@
We are also seeing this running trusty with the HWE kernel (i.e. 4.4) in
which we have upgraded to the upstream i40e drivers.
When we started using i40e 2.0.26 we found that we needed to add
pre-up sleep 15
for bond0 and this seems to work all the time.
However, when using i40e 2.3.6 or 2.4.6 w
Dear Mr. Salisbury,
I can't believe it's been 12 days since I filed this report. Seems like it was
just yesterday. And in fact it's just today I found your missives. Shame on me!
I'm having a bad case of battle fatigue with this issue. I'm deploying like
TODAY. Do I live with errors? Do I compi
Just though of something. reinstalled a system from daily build yesterday.
So here's the deal: I'l try to see if it's fixed as of yesterday
But it will take me some hours to re-con zoneminder to trigger the bug.
-jeff
On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury
wrote:
Hey! This bug may be fixed.As best I recall I did a fresh install from nightly
build about 3 days ago, but had not installed zoneminder so no op to tickle the
bug.
Today I did an upgrade and a dist-upgrade, then loaded zoneminder, started
pulling data over renesas port, so far no dmesg errors, I
No, premature. Bug still exists. I'll try your kernel at the next sitting.
-Jeff
On Tuesday, May 29, 2018, 1:11:03 PM PDT, Joseph Salisbury
wrote:
I built a patched test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1773704
Can you test this ke
Public bug reported:
A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.
183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
184 pdev->device == 0x0014)
185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
186 if (pdev->vendor == PCI_V
Don't see the point in adding log files for a simple and obvious typo,
but before code was added for this fix I believe I did generate before
and after logs under bug ID #1710548. In any case I'm running kernels in
which I've fixed the typo.
Status changed to confirmed.
** Changed in: linux (Ubu
To clarify your comment #1, I could install linux-kvm-xenial now to get
the modules, but your work will eventually add them to the default
kernel used by Ubuntu Minimal Cloud images?
Thanks in advance
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
ubuntu@deva-controller0:~$ uname -a
Linux deva-controller0 4.15.0-1022-kvm #22+ipset.0 SMP Mon Sep 24 15:12:21 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@deva-controller0:~$ cd /boot
ubuntu@deva-controller0:/boot$ grep SET config-4.15.0-1022-kvm
CONFIG_ARCH_HAS_SET_MEMORY=y
CONFIG_CPUSETS=y
Hmm, having resigned to building my own kernels for the foreseeable
future, I DL'd the source tree for bionic and took a peek at xhci-pci.c
It looks like someone has tried to incorporate the patch of interest. I
find:
if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
pdev->devic
Yeah it's a typo.
--
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/1710548
Title:
Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech
C920 Webcam/Zoneminder/Startech
St
Hi,
It looks like someone attempted a fix, but it was beset by a typo. I fixed the
typo and compiled the kernel and the issue was resolved. I detailed the typo in
the original thread. Can you run this up the flagpole for me? I don't know how
to get in touch with the devs.
Thank you,
-Jeff
O
I downloaded the three files you mentioned and tried to install them
using 'dpkg -i *.deb' as root. Two of the pkgs installed OK but the
kernel proper did not, giving error:
Selecting previously unselected package
linux-image-unsigned-4.15.0-22-generic.
dpkg: regarding
linux-image-unsigned-4.1
The typo is still present in 4.15.0-29.31
--
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/1773704
Title:
Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
in Bionic 1
The underlying bug is also described in bug ID #1737629, but I think
that report was prior to the typo ie: before the "fix" with the typo was
added.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
I wasn't able to test the kernel you provided, dpkg -i complained of
conflicting packages. I suspect because the kernel was down-rev relative to the
running kernel. But I don't reslly know, I'm relatively new to compilling and
installing kernels.
However, I was able to compile and install my ow
Thank you Joseph, sorry I couldn't try your test kernel but I've just
been chasing my tail trying to figure out why I can install some kernels
and not others.
My email is mysterylectric...@yahoo.com
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Ooops. I can see that point. The Startech card I'm using claims to be
based on the uPD720202: perhaps it has two if them. I'd say that the
uPD720202 needs the XHCI_TRUST_TX_LENGTH quirk as well.
-Jeff
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
has the same issue.
my env is:
centos7.5 + BCM57800,
i am using openshift + vxlan, when a vxlan packet is sent to the node,
node is restarted automatically.
I also test the latest kernel (4.18.12), which still have the same
issue.
i also tried to disable tso/gso/gro/tx-udp_tnl-segmentation/rx-
^I agree with John that this must be related to both Bluetooth and Wifi
on at the same time. I don't have an RJ45-USBC dongle to confirm however
Im able to see an increase in how often the shuddering occurs when using
a 5GHz band wifi vs a 2.4GHz.
I was suggested to update the BIOS by another thre
Yep, I’ll have it tested.
Jeffrey Hugo
Senior Engineer
Qualcomm Datacenter Technologies, Inc.
1-303-247-5002
From: Manoj Iyer [mailto:manoj.i...@canonical.com]
Sent: Wednesday, May 10, 2017 10:00 PM
To: Jeff Hugo ; 1689...@bugs.launchpad.net
Cc: Joseph Chang
Subject: [Bug #1689886] Please test
Hmm, that looks like it should work. I wonder why it didn’t seem to go
well for me. I’ll give it another shot.
Jeffrey Hugo
Senior Engineer
Qualcomm Datacenter Technologies, Inc.
1-303-247-5002
From: Manoj Iyer [mailto:manoj.i...@canonical.com]
Sent: Thursday, May 11, 2017 11:21 AM
To: Jeff
: B81.01410.0013
Jeffrey Hugo
Senior Engineer
Qualcomm Datacenter Technologies, Inc.
1-303-247-5002
From: Jeff Hugo
Sent: Thursday, May 11, 2017 11:42 AM
To: 'Manoj Iyer'
Cc: Joseph Chang ; 1689...@bugs.launchpad.net
Subject: RE: [Bug #1689886] Please test this kernel and report resul
to install the correct kernel,
and leaves the system in a non-bootable state.
Jeffrey Hugo
Senior Engineer
Qualcomm Datacenter Technologies, Inc.
1-303-247-5002
From: Manoj Iyer [mailto:manoj.i...@canonical.com]
Sent: Thursday, May 11, 2017 10:16 AM
To: Joseph Chang
Cc: Jeff Hugo ; 1689
Just FYI, it will likely take me a few days to get to this.
Jeffrey Hugo
Senior Engineer
Qualcomm Datacenter Technologies, Inc.
1-303-247-5002
From: Manoj Iyer [mailto:manoj.i...@canonical.com]
Sent: Thursday, May 11, 2017 9:23 PM
To: Jeff Hugo ; 1688...@bugs.launchpad.net
Cc: Nate Watterson
nt=10005msec, maxt=10005msec
Disk stats (read/write):
nvme0n1: ios=255788/0, merge=0/0, ticks=1246388/0, in_queue=1246788,
util=99.05%
Jeffrey Hugo
Senior Engineer
Qualcomm Datacenter Technologies, Inc.
1-303-247-5002
From: Manoj Iyer [mailto:manoj.i...@canonical.com]
Sent: Thursday, May 11, 201
Public bug reported:
Hi Everyone,
I'm working on Ubuntu 18.04, x86_64, fully patched. The kernel is
5.4.0-48-generic.
Dmesg shows a few messages for a Sonix Technology USB Camera. The camera
is somewhat popular on Amazon. The camera is
https://www.amazon.com/gp/product/B086WVDKH7.
Here are the
Hello, I can confirm this is a kernel bug which manifests on the Lenovo
IdeaPad 3 15IIL05.
Attached is a tarball from the Fedora "Problem Reporting" tool which
includes the dmesg and other system data. I realize this isn't a Fedora
bug tracker but this is a kernel bug and there doesn't seem to be
Public bug reported:
Hi Everyone,
Just a heads up here... I'm working on Zorin OS 15.3, which is based on
Ubuntu Bionic.
I upgrade from the linux-image-5.4.0-53-generic kernel to the linux-
image-5.4.0-54-generic kernel. After the upgrade to the 5.4.0-54 kernel
sound stopped working. Settings sh
Validated the test kernel in the PPA by installing it onto a QDF2400
device running 16.04.3
Used JTAG to trigger multiple concurrent errors, and observed that all
errors were parsed, instead of just the first one:
root@ubuntu:/home/ubuntu# cat /sys/kernel/debug/tracing/trace
# tracer: nop
#
#
** Summary changed:
- Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in 16.04?
Logitech C920 Webcam/Zoneminder/Startech
+ Renesas / NEC - µPD720202 needs XHCI_TRUST_TX_LENGTH quirk? Logitech C920
Webcam/Zoneminder/Startech
--
You received this bug notification because you
Bug still exists in 4.15 kernel/Bionc Beaver
** Description changed:
- In trying to build a zoneminder server, I think I stumbled on a kernel
- bug. It seems to have snuck in sometime between 16.04 desktop promoted
- to server, and 17.04 server promoted to desktop.
+ Building zoneminder server.
** Description changed:
Building zoneminder server. I think I stumbled on a kernel bug.
The suggestion is that the popular Renesas / NEC - µPD720202 may need
"quirk" in the kernel.
-
Wiped the drive.
Loaded 17.04 Server
Now getting 100's of messages in DMESG complaining of thous
Shouldn't the -116 kernel be blacklisted? On a fresh install I'm still
seeing the -116 update available.
--
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/1750937
Title:
4.4.0-116 Kernel up
How would the average person know to (or know how to) avoid this
problem, before it happens?
Is there something in the -116 kernel that's so great, and time
sensitive that it's worth putting folks through the huge inconvenience
of tracking down the root cause and booting into a previous kernel?
-
ElasticSearch doens't log anything itself. There's just this in
journalctl -xe
-- Unit elasticsearch.service has begun starting up.
Jan 24 18:34:26 logness systemd[1]: Started Elasticsearch.
-- Subject: Unit elasticsearch.service has finished start-up
-- Defined-By: systemd
-- Support: http://list
Curious as to when this fix will propagate into mainline. Haven't looked
into it very deeply, but it seems that kernel/"ubuntu base" updates
trounce the fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
> #15 says problem went away but is on Kernel 4.4 and Kerne 4.8
> where message was "hacked" to not display. With kernels 4.9, 4.10,
> etc...
That's not the first time the kernel folks have done that. They do it in
the crypto subsystem to hide messages that folks would want to see and
fix, like th
Public bug reported:
My machine (XPS 13 9360) won't go into suspend properly after upgrading
from linux-image-4.13.0-17-generic to linux-image-4.13.0-19-generic.
This affects both suspend through lid close and "systemctl suspend".
Screen goes off, power led remains lit. Then after some time the s
itecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: jeffrey1963 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
+ InstallationDate: Installed on 2017-10-
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationD
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: In
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
Installati
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Install
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Install
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationD
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationD
3.0-17 resolved the issue.
---
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bd
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
Installati
0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Installed o
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Install
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
Insta
e.
---
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f
ersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Install
e
becoming responsive again.
Booting back into 4.13.0-17 resolved the issue.
---
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
Dist
sInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Installed on 2017-10-18 (56 days ago)
InstallationMedi
itecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Installed on 2017-10-
---
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe
COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Installed on 2017-10-18 (56 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardv
PID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Installed on 2017-10-18 (56 days ago)
InstallationMedia: Ubuntu 17.10 &
reen comes back on, is stuck and lets me wait for a few before
becoming responsive again.
Booting back into 4.13.0-17 resolved the issue.
---
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: je
me the
screen comes back on, is stuck and lets me wait for a few before
becoming responsive again.
Booting back into 4.13.0-17 resolved the issue.
---
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: je
:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=0253ffe9-bdbf-4825-b583-e8055f7bffe5
InstallationDate: Installed on 2017-10-18 (56 days ago)
InstallationMedia:
ts me wait for a few before
becoming responsive again.
Booting back into 4.13.0-17 resolved the issue.
---
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeffrey1963 F pulseaudio
C
Kernel verified.
Jeffrey Hugo
Senior Engineer
Qualcomm Datacenter Technologies, Inc.
1-303-247-5002
From: Manoj Iyer [mailto:manoj.i...@canonical.com]
Sent: Monday, June 19, 2017 11:42 AM
To: Jeff Hugo
Cc: 1698...@bugs.launchpad.net; Timur Tabi ; Tyler
Baicar
Subject: could you please help
Sorry for the delays. The nvme fio test didn't stress the system enough
with this build, so I setup two systems with a direct wired, back to
back, high performance network link and ran iperf. With the client in
pass through, and the server in passthough/nonpassthrough, the data rate
was slightly
Validated.
Reported against FW 1.5. Validated against FW 2.0
Test:
sudo apt-get install kexec-tools
sudo kexec -l -d /boot/vmlinuz- --initrd=/boot/initrd.img-
--reuse-cmd
sudo kexec -e
wait up to 10 minutes for the new kernel to boot
System will crash at userspace boot without this fix.
--
Validated
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
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/1709123
Title:
[SRU][Zesty] [QDF2400] pl011 E4
Validated.
root@ubuntu:/home/ubuntu/andy/ibmtss930/utils# ./reg.sh -1
init tpm done
Initialize Regression Test Keys
Create a platform primary storage key
INFO:
Create a storage key under the primary key
INFO:
Create an unrestricted RSA signing key under the primary key
INFO:
Create an unrestr
Public bug reported:
In trying to build a zoneminder server, I think I stumbled on a kernel
bug. It seems to have snuck in sometime between 16.04 desktop promoted
to server, and 17.04 server promoted to desktop.
The suggestion is that the very popular Nec/Renasas 27xxx2 may need
"quirk" in the k
Placeholder for attachment
** Attachment added: "dmesg.4.13.0rc4"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+attachment/4933122/+files/dmesg.4.13.0rc4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thank you, Joseph!
I did test upstream at v4.13-rcr4 as you suggested. Same complaints. I
tried v4.13-rcr4 "lowlatency" as well, same complaints.
What seems strange to me is that I don't think I was getting these
complaints under 16.04 LTS Desktop with Studio (ie
lowlatency)/LAMP/ZoneMinder overl
Post script: these warnings do not crash or otherwise interfere with
system operation. ZoneMinder, in particular, `seems to function just
fine.
It's just...annoying and it seems the fix should be simple. Either this
chipset needs quirk, or not.
Does that sound crazy?
--
You received this bug n
Will sit, and think, and talk to you soon.
--
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/1710548
Title:
Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
Logitech
Dear Kai-Heng Feng,
Sure enough you fixed it. No complaints now.
I'd be very curious to look over the source code changes to improve my
linux-fu.
But that's secondary.
For now I hope an administrator can mark up my bug report to ensure that
the changes you have made get propagated.
Thank you v
Placeholder for DMESG attachment after the fix incorporated by Kai-Heng
Feng in
http://people.canonical.com/~khfeng/linux-
image-4.13.0-rc5+_4.13.0-rc5+-2_amd64.deb
Note well the kernel complaints such as:
[96415.044917] handle_tx_event: 516 callbacks suppressed
[96415.044924] xhci_hcd :0c:
Placeholder for DMESG attachment after the fix, sorry: file extension
collision.
** Attachment added: "postfix.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710548/+attachment/4934482/+files/postfix.txt
--
You received this bug notification because you are a member of Kernel
Pac
** Tags added: kernel-bug-exists-upstream
--
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/1710548
Title:
Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
Logitech C
** 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/1710548
Title:
Nec/Renasas 27xxx2 May also need Quirk in 17.04, no pro
Title and post edited to reflect actual chipset name Renesas / NEC -
µPD720202 not 27xxx2 as initially and mistakenly reported.
Do not duplicate as new bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Summary changed:
- Nec/Renasas 27xxx2 May also need Quirk in 17.04, no problem in 16.04?
Logitech C920 Webcam/Zoneminder/Startech
+ Renesas / NEC - µPD720202 May also need Quirk in 17.04, no problem in 16.04?
Logitech C920 Webcam/Zoneminder/Startech
** Description changed:
In trying to
Sorry for the delay, had to wait for another issue to be debugged before
I could take over the hardware again. I enabled -proposed and performed
an apt-get update and fix is working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
May have spoken too soon, found server went into a kernel panic after I
got back from lunch. There's some complaints about the controller so I
am going to try the 4.4.47 kernel again to be sure it's not the
hardware.
Is there anything that needs to be ran besides "apt-get update" after
enabling pr
Got it working 2nd try, enabling -proposed in Xenial resolved the 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/bugs/1661131
Title:
kernel crash when NVMe drive inserted in one slot
Not sure if it changes things... ASUS released an update for the AMI
UEFI on the Z170M-E DE board. Its now version 2202, dated 02/15/2017.
The issue is still present.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** 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/1655437
Title:
16.04 fails to boot with kernel 4.4.0-22-generic
Status in linux package in Ub
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1655437/+attachment/4802609/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
1 - 100 of 256 matches
Mail list logo
