Public bug reported:
This issue was only spotted on Bionic s390x instances.
FAIL: test_140_kernel_modules_not_tainted (__main__.KernelSecurityTest)
kernel modules are not marked with a taint flag (especially 'E' for
TAINT_UNSIGNED_MODULE)
---
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 1751213
and then change the status of the bug to 'Confirmed'.
If, due to the nature
We only yesterday got around to testing. We tried
4.16.0-041600rc2-generic, and the issue persists. I think we can close
this issue, and I'll open a kernel-bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
** Summary changed:
- selftest-setup test in ubuntu_kvm_unit_test will fail on Artful s390x zKVM
+ selftest-setup test in ubuntu_kvm_unit_test will fail on Artful/Bionic s390x
zKVM
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is
4.4.0-116-generic does appear to solve the problem on my Asus Prime
Z270K.
--
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/1745349
Title:
Hard lockup during boot with linux-image-4.4.0-11
** Summary changed:
- intercept test in ubuntu_kvm_unit_test will fail on Artful s390x zKVM
+ intercept test in ubuntu_kvm_unit_test will fail on Artful/Bionic s390x zKVM
** Tags added: bionic
** Description changed:
- Issue spotted on node s2lp6g004 (Artful zVM works fine)
+ Issue spotted on n
--- Comment From heinz-werner_se...@de.ibm.com 2018-02-23 04:02 EDT---
Yes, its recommended to incl. it into Xenial
--
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/1750813
Title:
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
Tried it and lo and behold, I got a crash eventually, although it took
way longer in the regular usage scenario. I am not sure if the TLP
settings are implemented correctly though. On one occasion i7z told m
I've got 4 computers running ubuntu.
2 computers affected, and 2 computers unaffected. The two affected computer are
using btrfs.
--
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/1747597
Ti
Public bug reported:
The ubuntu_bpf_jit test failed on s2lp6g002 with Bionic kernel.
Error message:
modprobe: ERROR: could not insert 'test_bpf': Invalid argument
When you try to insert the module with insmod it shows:
$ sudo insmod /lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko
insmod: ER
--- Comment on attachment From julian.wiedm...@de.ibm.com 2018-02-23 04:31
EDT---
Looks like the patch didn't mirror over properly - once more with feeling...
** Attachment added: "backport to xenial/master-next"
https://bugs.launchpad.net/bugs/1750810/+attachment/5061023/+files/s39
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 1751234
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
This issue can be found on different architectures of the Bionic kernel.
Steps:
1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b
master-next
2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
3. rm -fr autotest/client/tests
4. ln
--- Comment From heinz-werner_se...@de.ibm.com 2018-02-23 04:58 EDT---
I'm not able to test this kernel, but this patch was verified upfront, before
posting..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
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 1751243
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Tags added: bionic
** Summary changed:
- sprs test from kvm-unit-tests will hang on Zesty PowerPC
+ sprs test from kvm-unit-tests will hang on PowerPC
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Correction - 4.4.0-116-generic does not solve the problem.
The server was up for over an hour before hanging. As it doesn't usually
have a console, I can't be certain of the cause of the hang. However, a
subsequent reboot, with a console, involving rebuilding a 10TB RAID 5
array, showed exactly th
Hi, if this is on bionic, you need to wait until 23rd Feb respin is
done, which I guess for you means Monday unfortunately. Since 4.15
landed in bionic now, but d-i was not rebuild correctly in time, thus
there was a missmatch of things temporarily.
--
You received this bug notification because y
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Feb 16 13:45 seq
crw-rw 1 root audio 116, 33 Feb 16 13:45 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Audio
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1679823/+attachment/5061064/+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/1679823
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1679823/+attachment/5061063/+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
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1679823/+attachment/5061061/+files/CRDA.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/1679823
Ti
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1679823/+attachment/5061062/+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/1679823/+attachment/5061068/+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/1679823
I have the same problem with my DELL server. Can't set MTU > 1500 with
current kernel.
--
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 requested, hw
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1679823/+attachment/5061065/+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
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1679823/+attachment/5061069/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1679823/+attachment/5061066/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1679823/+attachment/5061067/+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
--- Comment From pavra...@in.ibm.com 2018-02-23 05:57 EDT---
We have below makedumpfile in bionic-proposed and dump capture works fine.
:~# makedumpfile -v
makedumpfile: version 1.6.3 (released on 29 Jun 2018)
lzo enabled
snappy disabled
--
You received this bug notification because
Sorry, but that version number is not sufficient. It cannot distinguish
between package versions, which might contain patches? When you give a
makedumpfile version, can you use dpkg -s makedumpfile?
Also, I need to know which kernel version you dumped with that. And if
crash could successfully loa
My mistake, it does' work on upstream kernel 4.15, although the ethernet
adapter does break.
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- Comment From sthou...@in.ibm.com 2018-02-23 06:46 EDT---
Any updates?
As part of the bug backlog screening exercise, we are looking for
updates on the bugs that are not witnessing activity for quite sometime.
Please post the latest status on this bug so that it can closed
accordingly.
Public bug reported:
Ubuntu Desktop Bionic up to date
System doesn't boot with an external monitor attached.
There is this message in the journal (full journal attached for this
boot)
fbcon: inteldrmfb (fb0) is primary device
[drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stu
Public bug reported:
linux-image-4.15.0-10-generic doesn't have the firmware that linux-
image-4.13.0-32-generic has. It doesn't have any of the files that are
present in 4.13 in /lib/firmware/4.13.0-32-generic/.
For me, this means i can boot 4.15, but my network wont work because of:
kernel: [
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/1751266
Title:
Missing firmware in linux-imag
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: artful
--
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/1751268
Title:
bionic
> I have the same problem with my DELL server. Can't set MTU > 1500 with
current kernel.
Your hardware is limited, you are not seeing a kernel bug. Your tg3
chip has a "jumbo capable" flag and it seems it not set - meaning your
NIC does not support frames larger than the standard 1500.
/* hardwa
The error messages about the sap-server are not there any longer in Ubuntu
17.10.
Thanks for the fix!
** Changed in: bluez (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubunt
This does not only affect the NVIDIA modules, but seems to affect all
kernel modules built on the system itself. (Meaning all DKMS-built
modules and for example VMWare Workstation/Player modules)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
I keep experiencing this issue, using Ubuntu 17.10, an Intel Core
i3-5005U (with Intel HD 5500). It appears most often when a new
notification comes in (Slack/Spotify) and the lockscreen is visible.
>From dmesg:
[Fri Feb 23 13:51:50 2018] [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
*ERROR* C
Public bug reported:
This bug is for tracking the 4.15.0-11.12 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-developme
This bug was fixed in the package stress-ng - 0.09.17-1
---
stress-ng (0.09.17-1) unstable; urgency=medium
* Makefile: bump version
* Manual: update date
* stress-rawdev: make some functions static
* stress-funcall: fix -Wmissing-declarations warning message
* stress-file-io
** Changed in: kernel-development-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the 4.15.0-11.12 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the as
This bug was fixed in the package debian-installer -
20101020ubuntu451.22
---
debian-installer (20101020ubuntu451.22) xenial; urgency=medium
[ dann frazier ]
* arm64-efi/netboot: Improvements to mini.iso generation:
- Add an EFI System Partition to fix booting from USB stick o
The verification of the Stable Release Update for debian-installer 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 en
The verification of the Stable Release Update for grub2 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 re
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.17
---
grub2 (2.02~beta2-36ubuntu3.17) xenial; urgency=medium
* Signal to zpool that it should emit full names of constituent devices.
(LP: #1527727)
-- Scott Moser Wed, 24 Jan 2018 16:21:35 -0500
** Changed in:
This bug was fixed in the package grub2-signed - 1.66.17
---
grub2-signed (1.66.17) xenial; urgency=medium
* Rebuild against grub2 2.02~beta2-36ubuntu3.17. (LP: #1527727)
-- Scott Moser Thu, 25 Jan 2018 10:05:01 -0500
--
You received this bug notification because you are a mem
Pushed after merge with Debian at my ppa.
sudo add-apt-repository ppa:cascardo/ppa
sudo apt-get update
sudo apt-get install kexec-tools
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs
ok so boot in to old 112 is ok, but not ideal. this also may be
affecting some ethernet/usb connections as well.
--
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 K
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Released
--
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/1736954
Title:
ppc64el: Do not call ibm,os-term on panic
S
Can you add some explanation on how to reproduce this issue, I have no
idea of how the test was run. Thanks!
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you a
** Also affects: linux (Ubuntu Bionic)
Importance: Critical
Status: 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/1749040
Title:
KPTI-enabled kernel fails to boot o
** Summary changed:
- ISST-LTE:PowerNV:Ubuntu1804:Witherspoon:whip: System hung with Kernel panic
-not syncing: Out of memory message when crash is triggered.
+ Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not
syncing: Out of memory message when crash is triggered.
**
On QTI QDF2400 I notice errors from xhci-hcd like:
awrep6 login: [18851.092328] xhci-hcd QCOM8041:02: ERROR: unexpected setup
address command completion code 0x11.
[18851.308402] xhci-hcd QCOM8041:02: ERROR: unexpected setup address command
completion code 0x11.
[18851.530820] usb 5-1.4: device
On Fri, Feb 23, 2018 at 9:24 AM, Manoj Iyer <1749...@bugs.launchpad.net> wrote:
> On QTI QDF2400 I notice errors from xhci-hcd like:
>
> awrep6 login: [18851.092328] xhci-hcd QCOM8041:02: ERROR: unexpected setup
> address command completion code 0x11.
> [18851.308402] xhci-hcd QCOM8041:02: ERROR:
This bug was fixed in the package zfs-linux - 0.7.5-1ubuntu2
---
zfs-linux (0.7.5-1ubuntu2) bionic; urgency=medium
* Bump version and re-upload
-- Colin Ian King Fri, 23 Feb 2018 11:15:17
+
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Fix Released
--
Yo
The newer Ubuntu kernel has the new retpoline Spectre mitigation. In
order to load, your kernel modules will need to be compiled with a
version of gcc that supports retpoline. You can determine if the module
has it with the command "modinfo " and look for the version
magic.
If you are using DKMS
** Changed in: makedumpfile (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1670696
Title:
Typo in error msg when no crashkernel
Closing as won't fix, as it doesn't affect newer versions, and does not
warrant a fix on trusty.
** Changed in: makedumpfile (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ub
Public bug reported:
When kdump-tools is installed, it creates an initrd for the running
kernel. For kernels installed after that, the postinst part will be run
and a initrd will be created as well. However, for kernels that are
already installed, it won't create them.
As an example, when the use
Public bug reported:
This, at least, causes kdump-tools to load only after some timeout. It
could be loaded much earlier.
kdump-tools only requires the network to be online when it's configured
to dump to ssh or nfs, and only when dumping, not when loading.
We should have three services/units he
Barry/Breno,
Could you please reverse mirror
ubuntu-kvm-unit test failed with emulator test on ppc64le
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723914
Thanks
--
Manoj Iyer
Ubuntu/Canonical
ARM Servers - Cloud
--
You receive
Jay Flory, that's important information and sounds like it can lead
those of us affected to a solution. However, my version of gcc is the
default one for 14.04, I do not have a custom version, yet I still have
this problem. Do you know what version of gcc I should install?
--
You received this
Looking at apt logs, it appears my system got a gcc update the day AFTER
the kernel was pushed out. I'll try reinstalling the kernel and see if
that makes a difference.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
You have been subscribed to a public bug:
User reported several nodes lost connectivity in several situations, for
instance during the netboot, in which a flood of arp traffic happens due
to multiple simultaneous boot across the cluster.
No stack trace or message is seen, the device just stop rec
Jay Flory, your information was the key! I removed the -116 kernel and
reinstalled it, and the graphics are fine now. It looks like this was
indeed due to a timing problem between when my system got the gcc update
and the kernel update.
It appears that I'll have to reinstall virtualbox as well.
Yes, I also got the gcc update after the kernel update. With the new
gcc, I could fix the Nvidia kernel module.
Here's how:
# Show the current vermagic string of the kernel module
modinfo nvidia-384 -k 4.4.0-116-generic
# It will probably say:
# vermagic: 4.4.0-116-generic SMP mod_unload mo
Unfortunately I don't currently have a 14.04 installation so I don't
know which versions of gcc are available to you. I am using the package
"gcc-5" from the Xenial (16.04) repositories and it is working. You may
also want to check:
1. "which gcc"
a. Make sure this points to the version of gcc t
Public bug reported:
User reported several nodes lost connectivity in several situations, for
instance during the netboot, in which a flood of arp traffic happens due
to multiple simultaneous boot across the cluster.
No stack trace or message is seen, the device just stop receiving
packets.
In o
hi
I still the same kernel warning .
Regards
** 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/1749744
Title:
kernel
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/1749744
Title:
kernel warning
Status in linux package in Ubuntu:
Confirmed
Bug description:
I get very oft
Public bug reported:
Hello,
dmesg:
[5.630006] platform regulatory.0: Direct firmware load for regulatory.db
failed with error -2
Regards,
--
Cristian
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-10-generic 4.15.0-10.11
ProcVersionSignature: Ubuntu 4.15.0-10.11-g
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Tags added: triage-g
--
You
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
** Also affects: kexec-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: kexec-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** No longer affects: kexec-tools (Ubuntu Artful)
--
You received this bug notification because you are a member of K
As long as you have the updated gcc installed before you install the
kernel, it works 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/1750937
Title:
4.4.0-116 Kernel update on 2/21
That was it Jay Flory! I too had a different version of gcc in my 16.04
installation (an upgrade I got from the ubuntu-toolchain-r ppa, which I
used in order to test something with gcc-7).
I use Timeshift, so I was able to go back to before adding the ppa.
Upgrading normally from that point, while
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?
-
Public bug reported:
Just booting up
ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified:
boot/vmlinuz-4.13.0-32-generic]
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
Annotation: This
The -116 kernel contains protections against the Spectre / Meltdown
exploits. So yeah, it's pretty great.
--
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 u
Just booting up after trying to hibernate doing a:
sudo apt install pm-utils && sudo pm-hibernate
Hibernation did not work, I just booted as normal. My system uses LUKS
encryption & LVM. Hiberation works fine on the same machine in Debian
Jessie.
--
You received this bug notification because yo
** Tags removed: need-duplicate-check
--
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/1751361
Title:
[Gigabyte Technology Co., Ltd. H81M-HD3] hibernate/resume failure
Status in linux pac
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/1751361
Title:
[Gigabyte Technology Co., Ltd.
I took the *-116 kernel a few days ago on my 16.04.3 desktop, got a
mouse freeze after booting, and went back to *-112.
I see from my dpkg.log that version 5.4.0-6ubuntu1~16.04.9 of gcc
installed over a day before the *-116 kernel. I see also from
https://ubuntu.pkgs.org/16.04/ubuntu-updates-main
@cjmather
If you are sure that you have the latest gcc and you are still seeing kernel
panics with the -116 kernel, please file a new bug and report back here what
that bug # is.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
I'm still working on the bisect. It looks like two commits may have
introduced the bug, which is slowing the bisect process.
I found that the following commit causes a kernel trace with rtmsg_ifa
as the EIP:
120645513f55 ("openvswitch: Add eventmask support to CT action.")
Reverting this commit
Hi Xiong,
Can we mark this Fix Released?
--
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/1460900
Title:
[Feature]Code/Data Prioritization (CDP) Enablment
Status in intel:
Incomplete
S
** Changed in: intel
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Expired => Fix Released
--
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/1591808
I had the same problem with my -116 kernel upgrade.
So I am running `gcc version 5.4.1 20160904 (Ubuntu
5.4.1-2ubuntu1~16.04)` but this was already installed it seems - I can't
see in the dpkg.log* files when this was added. I am assuming that this
is a newer version of GCC than is needed, but ho
@glenpike
For Xenial you need gcc-5 5.4.0-6ubuntu1~16.04.9. You can find which version
you have installed via "dpkg -l | grep gcc-5".
--
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
Tim Habigt wrote in #30:
> Yes, I also got the gcc update after the kernel update. With the new
gcc, I could fix the Nvidia kernel module.
> Here's how:
> # Show the current vermagic string of the kernel module
> modinfo nvidia-384 -k 4.4.0-116-generic
> # It will probably say:
> # vermagic: 4.4
For Trusty (14.04) I successfully installed the driver with gcc version
4:4.8.2-1ubuntu6
--
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 update on 2/21 bre
My Trusty (14.04) also shows gcc-4.8 version 4.8.4-2ubuntu1~14.04.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/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (o
My 14.04 machine received the gcc update after the -116 update, just as
others have noted.
I resolved this by booting into -112 then:
sudo apt-get purge linux-headers-4.4.0-116 linux-headers-4.4.0-116-generic
sudo apt-get install linux-generic-lts-xenial
And then rebooted into -116 with everythi
4.15 is now available in Bionic. Marking this Fix Released.
** Information type changed from Proprietary to Public
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Invalid
** Also affects: linux (Ubunt
4.15 is now available in Bionic. Marking this Fix Released.
** Information type changed from Proprietary to Public
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: intel
Marking this Fix Released for Bionic which has a 4.15 based kernel now.
** Information type changed from Private to Public
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: intel
Status: New => Fix Released
** Changed in: linux (Ubuntu Artful)
Status:
John (earthspike), you said your version is
gcc-4.8.real (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4
but when I run gcc --version I get just
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.4) 4.8.4
The version number appears to be the same but instead of gcc-4.8.real I
only see gcc. Is that a significant differenc
1 - 100 of 178 matches
Mail list logo
