** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags adde
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1766052
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This should fix it:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091890.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/1766052
Title:
Incorrect blacklist of bcm2835_wdt
Public bug reported:
Without bcm2835_wdt loaded, Raspberry Pi systems cannot reboot or shut
down. This needs to be removed from the automatic blacklist generated by
the kernel build that ends up in /lib/modprobe.d/blacklist_linux_$(uname
-r).conf
** Affects: linux (Ubuntu)
Importance: Undeci
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launch
[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.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu Bionic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
[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.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
--- Comment From dnban...@us.ibm.com 2018-04-21 23:43 EDT---
The kernel mentioned in #114 was a quick, rough attempt to force one instance
of free_work/del_work pending at a time.
With that, the machine still seems to be up.
root@boslcp3:~# uptime
22:21:50 up 3:41, 2 users, load averag
--- Comment From dnban...@us.ibm.com 2018-04-21 23:33 EDT---
Continuing from the description at #84...
This is going to be long post. I debated putting it as as
attachment but placing it in the main body will probably
help in searching in the future.
==
Yeah, so I doubt it's a whitespace fix in the rxrpc driver. However, a
diff between the configs on v415-rc2 and v415-rc3 has lots of
differences, the most interesting being this one:
$ diff -u config-4.15.0-041500rc2-generic config-4.15.0-041500rc3-generic
/* ... snip ... */
@@ -5675,9 +5677,9 @@
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-te
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.15.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-te
Hi Joseph,
No luck... Still not working.
Updated via UKUU. I have attached the screenshot showing the kernel version
plus the list of input devices.
Cheers,
Dave
PS why doesn't the wiki suggest using UKUU to install upstream kernels? So
much easier to do.
dave@dave-laptop:~$ cat /proc/bus/inp
--- Comment From dnban...@us.ibm.com 2018-04-21 21:30 EDT---
I gave a test kernel to Chanh to try out on boslcp3, based on the observations
from the crash.(it has taken a while ...) - just a quick initial attempt.
I will soon be posting the analysis. Meanwhile, boslcp3 still seems to
be u
--- Comment From chngu...@us.ibm.com 2018-04-21 20:09 EDT---
Dwip provided a new kernel and we start test on 3 guests.
root@boslcp3:~# date
Sat Apr 21 19:00:07 CDT 2018
root@boslcp3:~# uptime
19:00:09 up 20 min, 3 users, load average: 0.01, 0.42, 0.48
root@boslcp3:~# uname -a
Linux boslcp
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow se
--- Comment From dougm...@us.ibm.com 2018-04-21 19:17 EDT---
We need to see the console messages *before* things go wrong. Please capture
the SOL console output from boot until this happens.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-21 17:04
EDT---
** Attachment added: "sol console log"
https://bugs.launchpad.net/bugs/1762844/+attachment/5125257/+files/boslcp3.0421.txt
--
You received this bug notification because you are a member of Kernel
Package
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow se
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
**
--- Comment From kla...@br.ibm.com 2018-04-21 18:55 EDT---
(In reply to comment #80)
> (In reply to comment #79)
> > Machine still seems to be up... will check if I can observe anything
> > interesting ...
>
> System just crashes it now. The vmcore is at /var/crash/201804181042
Can we retr
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-master-bug:
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+
+ backports: bug 1766028
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-master-bug:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects: kernel-sru-workflow
Imp
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1765232
Title:
Kernel 4.15.0-15 breaks Dell PowerEdge 12th
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
--
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/1765498
Title:
linux-kvm: 4.15.0-100
Sorry Kai-Heng Feng but I'm already using Ubuntu 18 since the beginning
of this month. Fortunately, the problem was fixed or never existed in
the new version.
Thank you for your help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-21 17:04
EDT---
** Attachment added: "sol console log"
https://bugs.launchpad.net/bugs/1762844/+attachment/5125224/+files/boslcp3.0421.txt
--
You received this bug notification because you are a member of Kernel
Package
--- Comment From chngu...@us.ibm.com 2018-04-21 17:02 EDT---
Not sure what is going on. The SOL console print out all of these messages...
rcu_sched self-detected stall on CPU
[20705.652053] 95-: (1 GPs behind) idle=c72/2/0 softirq=179/180 fqs=2586003
[20705.652101] (t=5172329 jiffie
** Description changed:
+ SRU Justification
+
+ Impact: Since 4.15.0-15 some machines have been failing to boot due to
+ IO hangs. This is caused by patches applied for LP #1759723, which
+ assigned managed interrupt vectors and reply queues for all possible
+ CPUs, not just present CPUs. Some dr
The kernel from post #12 also works without issue for me 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/1765232
Title:
Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers
Statu
Thanks for testing, I'll get those reverts sent to the list.
--
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/1765232
Title:
Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers
Status
I cannot run the affected (production) system using a broken kernel, and it
will lockup after boot within seconds.
If necessary, I can provide additional information or testing upon request.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notificati
Seth, thanks for the guidance, that did it. Looks like the kernel from
#12 works without issue. Glad you were able to identify the commits that
did it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Make sure you got linux-image-unsigned, linux-modules, *and* linux-
modules-extra. linux-modules-extra has the hpsa driver.
--
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/1765232
Title:
--- Comment From jos...@br.ibm.com 2018-04-21 15:29 EDT---
Ah, forget it, it's in 4.15.0-15.16 not 4.15.0-16. Anyway, you can revert it if
required.
Thank you
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
--- Comment From jos...@br.ibm.com 2018-04-21 15:14 EDT---
Hi Seth,
Just another point is that it's related
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765232) to kernel
4.15.0-15 but as per comment #11 these patches were applied in
4.15.0-16.
--
You received this bug notifica
--- Comment From jos...@br.ibm.com 2018-04-21 14:38 EDT---
Hello Seth,
Without those patches CPU hoplug doesn't work but the issue related on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765232 looks more
urgent yet. I agree to revert it if necessary.
Thanks
--
You received thi
I tried both these kernels, and unfortunately they are both still
leading to hangs on my HP ProLiant (from bug #1765105).
That being said I've not installed an out-of-tree kernel on Ubuntu
before, I assume it's just installing linux-image and linux-modules? I
just want to verify that I'm not messi
While booting (ALT+F1) following message are shown:
[0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update
microcode to version 0xb2 (or later)
[0.00] ACPI BIOS Error (bug): Failure looking up [\SP.PCIO.XHC.RHUB.HS11],
AE_NOT_FOUND (20180105/dswload-211)
[0.00] ACP
--- Comment From dougm...@us.ibm.com 2018-04-21 14:26 EDT---
I have ltc-boston1 setup with Ubuntu kernel 4.15.0-15, but there is no SAN
connected to the QLE2742. I see no problem there right now. I have reserve the
system for this bug until Monday evening.
--
You received this bug notif
Ubuntu MATE-18.04 - daily build - 21.04.2018 - Kernel
4.16.3-041603.201804190730 (via ukuu)
Additional Drivers - NVIDIA Corporation: GM107 [GeForce GTX 750 Ti]
- Using NVIDIA binary driver-version 340.106 from ndivia-340 (proprietary)
Same issue, hibernate works, resume from hibernate - error!
C
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1765998
and then change the status of the bug to 'Confirmed'.
If, due to the nature
--- Comment From kla...@br.ibm.com 2018-04-21 09:21 EDT---
Should we go back to the stock Ubuntu kernel in an attempt to identify if bug
167104 is a result of the custom kernel or the newest PNOR?
--- Comment From prad...@us.ibm.com 2018-04-21 13:17 EDT---
(In reply to comment #10
** Description changed:
I've spent the last few days tracking down an issue where an attempt to
shutdown an LXD container after several hours of host uptime on Ubuntu
Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
spinning on one CPU core and all subsequent container s
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Fix Committed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug is for
Ubuntu MATE-18.04 - daily build - 21.04.2018 - Uname: Linux
4.15.0.15-generic x86_64
Additional Drivers - NVIDIA Corporation: GM107 [GeForce GTX 750 Ti]
- Using NVIDIA binary driver-version 340.106 from ndivia-340 (proprietary)
Same issue. Hibernate works (sudo pm-hibernate), but Resume from
Hib
Hi Joseph,
So far I haven't seen it again, so it may have been a one time glitch.
cheers
Tom
On 20-04-18 20:26, Joseph Salisbury wrote:
> Do you have a way to reproduce this bug, or was it a one time event?
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Tags added
Kernel 3d7682af228fd78dc46bc: Black screen.
--
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/1761751
Title:
Black screen on 18.04 + AMD RX460
Status in linux package in Ubuntu:
In Progr
The cause of the issue is already understood, and the machine currently isn't
running an unmodified kernel for debugging reasons. Apport logs won't help here.
Contact me if you need specific information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this b
Ubuntu MATE-18.04 - daily build - 21.04.2018 - Uname: Linux
4.15.0.15-generic x86_64
Additional Drivers - NVIDIA Corporation: GM107 [GeForce GTX 750 Ti]
- Using NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested)
Same issue. Hibernate works (sudo pm-hibernate), but Resume from
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-18-generic (not installed)
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
AptOrdering:
linux-headers-4.15.0-18-gener
Public bug reported:
I'm running into an issue on Ubuntu Bionic (but not Xenial) where
shortly after boot, under heavy load from many LXD containers starting
at once, access to the btrfs filesystem that the containers are on
deadlocks.
The issue is quite hard to reproduce on other systems, quite
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1765980
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
[Impact]
HiSilicon HNS NIC names are truncated in /proc/interrupts, making it difficult
for an admin to associate activity among adapters in the system.
[Test Case]
$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
Without the fix:
enahisic2i0-tx0
enahisic2i0-tx1
Public bug reported:
I've spent the last few days tracking down an issue where an attempt to
shutdown an LXD container after several hours of host uptime on Ubuntu
Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
spinning on one CPU core and all subsequent container start/stop
o
And now here's another test build with the upstream fixes. Note that the
last patch needed too much backporting to do in short order, and I had
to include one additional prerequisite:
http://people.canonical.com/~sforshee/lp1765232/linux-4.15.0-18.19+lp1765232v201804211053/
Please test the kernel
Here's a test kernel with the reverts, please let us know ASAP whether
or not this fixes the issue.
http://people.canonical.com/~sforshee/lp1765232/linux-4.15.0-18.19+lp1765232v201804211006/
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
I think the patches from this bug are causing a problem. See LP:
#1765232 for details.
I've identified a number of upstream fixes for these patches, listed on
that bug. We are days out from release though, and the last of them
(d3056812e7df "genirq/affinity: Spread irq vectors among present CPUs a
I've been investigating, and I strongly suspect these commits for bug
1759723 are to blame.
f0aff9ccc834 genirq/affinity: assign vectors to all possible CPUs
9403a13fd07e blk-mq: simplify queue mapping & schedule with each possisble CPU
As far as I can tell there are 8 other fixes we'd need to
4.15.0-12 had the same problem, please see #1756455 [1] (which is
absolutely the same as this one).
I have also tried all mainline kernels from 4.15.3 up to 4.17rc1, and
here are the results:
* all mainline kernels in branch 4.15 do NOT have any issues
* starting with mainline 4.16.0 it is imposs
Hello.
Today, I noticed the same entries in a log files such as
'/var/log/syslog' and via dmesg(1) on 16.04 LTS Release (i386/x86_32
arch) with v4.4.0-120-generic (4.4.117) Linux kernel. The one thing,
that is different is 'use_ibrs' value. In my case it's:
[~]$ sudo dmesg
[ 464.877859] use_ibrs
--- Comment From chngu...@us.ibm.com 2018-04-20 16:48 EDT---
Boslcp3 is back with the new kernel from #94.
root@boslcp3:~# cat /proc/cmdline
root=UUID=bab108a0-d0a6-4609-87f1-6e33d0ad633c ro splash quiet
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M
I w
I'd suggest prioritizing testing of the v4.15.17 mainline kernel as this
is the latest update bionic has incorporated. If that is broken then try
v4.15.18 to see if there's a fix there, otherwise it points to some
Ubuntu-specific changes or backports.
--
You received this bug notification because
--- Comment From dougm...@us.ibm.com 2018-04-21 08:45 EDT---
The latest logs show a panic in process_one_work() on CPU 145, some sort of
NULL pointer fault, followed by 2 CPUs (22, 125) getting a "Bad interrupt in
KVM entry/exit code, sig: 6" panic (possibly in response to the panic IPI).
Hello, the problem exists since several versions.
This is a new installation from the daily-live 20180418.
I installed
linux-image-4.17.0-041700rc1-generic_4.17.0-041700rc1.201804152230_amd64.deb
but the problem is the same.
When I run "sudo pm-hibernate" the power LED flashes quickly, the screen
@zebul666
The wl kernel module seems not to honor the crda setting. It doesn't connect to
high channels at all.
See https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1574196
Nevertheless, Ubuntu still doesn't set the regulatory domain automatically.
I'm using 17.10.
--
You received this bug
Same problem here, maybe it doesn't respect the crda settings provided by
Ubuntu?
https://packages.ubuntu.com/artful/crda
--
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/1574196
Title:
C
77 matches
Mail list logo
