I get this every couple of days on our CI - from processes which access
the GPU. nvidia-driver 396.24.02. Here are some dmesg warning from
various failures
[Mon Nov 5 18:43:29 2018] INFO: task kworker/4:2:25281 blocked for more than
120 seconds.
[Mon Nov 5 18:43:29 2018] Tainted: P
BTW: Linux lb-santi 4.4.0-127-generic #153~14.04.1-Ubuntu SMP Sat May 19
14:00:03 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
Sadly not! The slightly older model (also 4k but older rev) worked fine
with the standard install so my intention is to use that (long story but
it has windows only at the moment). Really I wanted the newer 4-core
one running linux but I couldn't justify the time investigating.
--
You received
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 1801865
and then change the status of the bug to 'Confirmed'.
If, due to the
Have you tried kernel parameter `pcie_aspm=off`? There are some PCIe
WiFi modules don't like ASPM L0s.
--
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/1730924
Title:
Wifi does down
** Also affects: stress-ng
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/1801865
Title:
af-alg in ubuntu_stress_smoke_test failed with
I see. There are two "Good" unknown autosuspend USB devices, not sure
which one is my mouse. I can't find it in "Bad" either.
Anyhow, the issue seems resolved currently.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
The af-alg test failed with Trusty Power8, reproduce rate 5/5
06:48:39 DEBUG| [stdout] af-alg STARTING
06:48:39 DEBUG| [stdout] af-alg RETURNED 2
06:48:39 DEBUG| [stdout] af-alg FAILED
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 128 processors online, 128
processors
For sure, please see it attached below.
** Attachment added: "lspci"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730924/+attachment/5209554/+files/lspci
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-prime (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
Pushed https://git.launchpad.net/qa-regression-
testing/commit/?id=2120892f80422c0c8f8002a1589c9d5320da8250 to the
qa-r-t tree, closing that task.
Thanks!
** Changed in: qa-regression-testing
Status: New => Fix Released
--
You received this bug notification because you are a member of
Please attach `sudo lspci -vvnn`.
--
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/1730924
Title:
Wifi does down "crash" in Surface Pro 4
Status in Linux:
Confirmed
Status in linux
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/1801856
Title:
seccomp in
Public bug reported:
Didn't see this on amd64 / i386, but it can be reproduced on power8 and
ARM64
seccomp STARTING
seccomp RETURNED 2
seccomp FAILED
stress-ng: debug: [7528] 8 processors online, 8 processors configured
stress-ng: info: [7528] dispatching hogs: 4 seccomp
stress-ng:
Thanks for all you guys reply!!
And since there are two different suggestion, so I will reply
respectively.
To Cristian,
Yes, the issue I am facing happens after I upgraded from Ubuntu 16.04 to
18.04.
But no, or correctly, I don't know. As I followed what you suggested and
do the test with the
I have Lenovo Ideapad 720s 4k screen, i7-8550U; UHD Graphics 620
(Kabylake GT2) and I am facing the exact same issue in it. The issue is
deep rooted, as I have tried fedora, Mint, etc and there is simply no
escape. But it works perfectly on a windows machine.
Were you able to figure out a
Yeah, it's curious that only the second test triggered a failure. In any
event, I'll fix qa-r-t to expect failure for precise's 3.2 kernel.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Please try this:
Edit /etc/gdm3/custom.conf and uncomment the line:
#WaylandEnable=false
as
WaylandEnable=false
If that works then maybe we can merge this into bug 1798790.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
Adding nomodeset rebuilding initrd and rebooting does not fix it.
The Lenovo ThinkPad W540 has no option to disable the integrated video
card. The internal display is always run by the intel. I have it set to
use the nvidia on external displays because that allows supporting more
displays.
So
@amri,
Could you please report this bug to the GDM developers?;
https://gitlab.gnome.org/GNOME/gdm/issues
** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
Status: Won't Fix => Invalid
** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
Status: Confirmed => Invalid
--
You
Sounds like bug 1797862, if not bug 1796550.
Can you please list the files in /sys/class/leds/ and paste it here?
--
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/1796573
Title:
Keyboard
Maybe merge with bug 1797862?
--
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/1791372
Title:
Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in
Cosmic 18.10, works
Maybe merge with bug 1791372?
** No longer affects: upower (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/1797862
Title:
Cannot turn off keyboard backlight
Status in linux
[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.
Please try updating your system in case bug 1796550 fixed this.
** 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.
https://bugs.launchpad.net/bugs/1800164
[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.
[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.
The patch to suppress stress-ng warnings works as expected, thanks!
** Changed in: ubuntu-kernel-tests
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sounds like bug 1705369 or bug 1798790.
Please try the workarounds mentioned in bug 1705369.
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
** Changed in: ubuntu-kernel-tests
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/1801708
Title:
test_cve_2015_8539_2 failed with 3.2 Precise ESM
Status
** 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:
3.2.0-137.183 - generic
Regression test CMPL, RTB.
Issue to note in amd64:
ubuntu_cts_kernel - manually tested and passed
ubuntu_ecryptfs - passed after re-test
ubuntu_qrt_kernel_panic - test_cve_2015_8539_2 failed on Precise (bug 1801708)
ubuntu_stress_smoke_test - loop / pty test in
nvidia drivers build and install just fine. Starting gdm3 fails to
detect displays, but Xorg does start. Stopping gdm3 and running a bare
Xorg gets working displays. Restarting gdm3 and displays work.
Displays light up fine with lightdm-gtk-greeter and the single Xorg
instance.
If anyone has
After completely removing the nvidia drivers, rebooting, and
reinstalling the nvidia drivers, even the old kernel fails to boot. This
appears to be an nvidia driver issue that shows up because of the gdm3
setup where it runs two different Xorg instances. Under lightdm+gnome
the displays light up
This is a medium CVE, so it's ignored on Precise ESM.
However, one interesting thing is that the same kernel has passed with
the "CVE-2015-8539" test, just not the test_cve_2015_8539_2 test:
22:55:51 DEBUG| Verify CVE-2015-8539 is fixed ... ok
22:55:51 DEBUG| test_cve_2015_8539_2
Probably the FreeBSD is working as Windows, they use the software de-
noise filter when users record sound.
Please test with "pactl load-module module-echo-cancel", then choose
echo-cancelled record device from gnome-sound-setting->input tab. Now
record sth, and play it. Is it better now?
If
** Also affects: caja (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/1801232
Title:
Ubuntu MATE crashes when too many external USB
Also, do you think this might be bug 1723025?
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: xorg-server (Ubuntu)
Looks like same issue as reported in
https://github.com/raspberrypi/linux/issues/2098. We have
CONFIG_MMC_BCM2835=y defined but not in raspberry pi upstream (I'm
looking at
https://github.com/raspberrypi/linux/blob/rpi-4.14.y/arch/arm/configs/bcm2709_defconfig).
Interestingly, both
This may be a regression, please try older kernels like v4.4.
--
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/1801747
Title:
External display not recognized, internal one goes to black
Please attach the dmesg when the issue happens, 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/1798921
Title:
sky2 ethernet card don't work after returning from suspension
** Description changed:
Description:
ndctl testing for AEP:
make --no-print-directory check-TESTS
FAIL: libndctl
FAIL: dsm-fail
PASS: dpa-alloc
PASS: parent-uuid
PASS: multi-pmem
PASS: create.sh
PASS: clear.sh
PASS: pmem-errors.sh
PASS: daxdev-errors.sh
PASS:
The machine seems to have an Intel CPU/GPU from 2009, which makes me
think this might be related somehow to bug 1727356. Can you please try
booting Ubuntu 18.10 as a test?
http://releases.ubuntu.com/18.10/
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
I think you're looking at the wrong line there. The line you want is:
Autosuspend for USB device ...
It sounds like the line for your mouse says "Good", which is actually
bad news. Because it means the kernel is powering down the USB device
for power savings. So a delay is expected.
Make
Can kernel parameter "usbcore.enable_autosuspend=0" workaround the
issue?
--
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/1799064
Title:
Bluetooth (ISSC USB dongle) refuses to power on
** Tags added: multimonitor
--
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/1801747
Title:
External display not recognized, internal one goes to black
Status in linux package in Ubuntu:
The machine is stuck in recovery mode, according to the kernel command
line:
[0.00] Command line:
BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04
-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset
To fix this, you need to reboot and then press Esc as soon as the
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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1799064
Title:
Bluetooth (ISSC USB dongle)
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 nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/174
Title:
Xorg
I'm not sure we should be looking in gdm here.
Tim has mentioned several times that kernel 4.15.0-36-generic works and
kernel 4.15.0-38 fails.
I wonder though, if the Nvidia driver might have just failed to build
for the newer kernels.
** Also affects: linux (Ubuntu)
Importance: Undecided
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
** Summary changed:
- Bluetooth refuses to power on after cosmic upgrade
+ Bluetooth refuses to power on after cosmic upgrade (works in kernel 4.15.0,
but fails in 4.16 onward)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: bluez (Ubuntu)
Status:
** Summary changed:
- Bluetooth mouse sleep after 5 seconds of inactivity
+ Bluetooth mouse sleeps after 5 seconds of inactivity
--
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/1801642
Ok, after another waking from suspend, the issue comes back again.
powertop shows "Bluetooth device interface status" is good. I can't
identify which entry is the mouse, but the only bad USB devices are the
keyboard and touchscreen.
Installing powertop somehow resolve this issue (for now). I'll
Propriétés de la table ACPI
Signature ACPI APIC
Table de descriptionMultiple APIC Description Table
Adresse Mémoire -7A712800h
Longueur de la table188 octets
OEM ID _ASUS_
OEM Table IDNotebook
OEM Revision01072009h
Creator ID AMI
Creator Revision
There is a problem here...
UEFISystème compatible UEFI Microsoft
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI
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 1801668
and then change the status of the bug to 'Confirmed'.
If, due to the
Is the patch described on the following webpage - a patch has arrived on
my system - relevant?
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1797322
It looks like it is not, but I am unsure (and don't fancy doing a load
of testing if it is not).
--
You received this bug
** 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/1801668
Title:
[AEP] ndctl test failed (21/25) and latest
It's an ACPI bug !
I make a bad thing about AMD While trying to correct colour resize
So, on recovery mode... Cleaning remove all files.
I try to install 18.10 on UEFI mode ... crash
I try to install Ub 17.10 UEFI mode Crash
I try to install 16.04.5 UEFI mode crash too
PC says error
The verification of the Stable Release Update for upower has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package upower - 0.99.8-2ubuntu0.1
---
upower (0.99.8-2ubuntu0.1) cosmic; urgency=medium
* debian/patches/git_access_sys.patch:
- Fix upower's keyboard backlight support (lp: #1796550)
-- Sebastien Bacher Thu, 25 Oct 2018 13:31:01
+0200
** Changed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
** 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
I built a test kernel with those two config options enabled and the 40 commits.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1787405
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to
The verification of the Stable Release Update for lxd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Yeah, it looks like it's failing due to that config option:
IOMMU Hardware Support (IOMMU_SUPPORT) [Y/?] y
S390 CCW IOMMU Support (S390_CCW_IOMMU) [Y/n/?] y
S390 AP IOMMU Support (S390_AP_IOMMU) [N/y/?] (NEW) aborted!
Console input/output is redirected. Run 'make oldconfig' to update
Works in 4.15.0, but fails in 4.16.18 and 4.17.19. I don't have time
right now to try earlier point releases (plus this is an infuriatingly
slow system), but hope this helps narrow it down a bit, at least.
A few other observations:
* Unplugging and replugging the dongle, and then restarting
** 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:
The uncommenting #WaylandEnable=false worked a treat for me as with the
previous posters. This is the answer to this problem and needs pinning
to the thread!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in
The mainline builds are all cross-built rather than native
built. Binaries like fixdep etc are used by the build process, and since its a
build on amd64 those binaries are complied for amd64. It is very resource
intensive to build these unsupported kernels native for each architecture.
Also note
** 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:
Hello I am running in to a similar error using the 18.10 cuttlefish with the
usb 3.1 driver.
What kernel has this code change
[ 719.522273] xhci_hcd :02:00.0: Looking for event-dma 000463f2bdf0
trb-start 0004650cbfb0 trb-end 0004650cbfe0 seg-start 0004650cb000
seg-end
--- Comment From cborn...@de.ibm.com 2018-11-05 14:25 EDT---
so I retried on bionic:
# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
1) Happens with both Front mic and Rear mic.
2) No, it still sounds bad.
Something I found is that on FreeBSD is working fine.
--
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/1801540
Behavior is different, Ican't see the image on one or the other display,
system now recognize the second screen but as soon as I switch the
screens keyboard freezes, mouse icon react but no button working, have
to switch off the computer with the on/off button :(
Daniel
--
You received this bug
--- Comment From cborn...@de.ibm.com 2018-11-05 13:57 EDT---
I build the kernel on a different system (not bionic) but yes it built fine.
What config and what compile error do you have?
--
You received this bug notification because you are a member of Kernel
Packages, which is
** 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
-- swm properties --
Dear Christian,
Thank you for telling me where to look for the information you need. Too
many responses tell me what to do not how to do it. I confess - I am a
Linux newbie! But I am a Mentor for Unix and Software Development with over
35 years experience - just not in Linux.
** 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
-- swm properties --
Err: to read is "I can see the image on one or the other display"
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
** 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
-- swm properties --
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
** 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/1801747
Title:
External display not recognized, internal one goes to black
Status in linux
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
** Description changed:
+ == SRU Justification ==
+
+ Description: qdio: reset old sbal_state flags
+
+ Symptom:
+af_iucv socket using HiperSockets may stall.
+ Problem:
+When allocating a new AOB fails, handle_outbound() is
+ still capable of transmitting the selected buffer
+ (just
Thanks for the backports! Were you able to get a kernel to build with
these commits? I applied the 40 commits to a Bionic tree, but it fails
to build.
I'll see if I can figure out why my build failed.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-trusty
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
** 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:
** 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
-- swm properties --
I am unable to boot after waking my laptop from suspend when using v4.19
kernel.
I tried using the recently released v4.19.1 kernel, but I am unable to install
it(dkms apport Error).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Yes the issue did not happen prior to the update to 18.04. But I don't
know if there was a prior kernel in 18.04 where the issue did not occur,
because it's not happening 100% of the time. Still a successful resume
is rare.
I'll give the mainline kernel a try.
--
You received this bug
Hi Cristian. No update/upgrade, straight HDD format + new install of
Ubuntu. I will test the latest kernel.
Thanks for your support
Daniel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ran the Trusty -proposed kernel through some basic tests, looks good.
** 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.
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.19
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.19
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1801743/+attachment/5209386/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 183 matches
Mail list logo
