Still reproducible with 6.5.0-26-generic
kdump won't generate any dump or send anything over ssh.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048951
Title:
Kernel Oops -
Still reproducible with 6.5.0-25-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048951
Title:
Kernel Oops - kernel NULL pointer dereference
** Summary changed:
- NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic
(linux-image-generic-hwe-22.04)
+ Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec,
profile_transition) with linux-image-6.5.0-18-generic
(linux-image-generic-hwe-22.04)
I can confirm that booting with "apparmor=0" added to kernel command line works
around the issue.
This host runs lxd containers, so from the security standpoint running it
without apparmor is not acceptable. However this proves there is an apparmor
bug.
--
You received this bug notification
** Package changed: linux-meta-hwe-6.5 (Ubuntu) => linux-hwe-6.5
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048951
Title:
NUC12WSHi7 hangs few minutes after boot
** Attachment added: "Screenshot 2024-02-16 at 13.42.06.png"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746725/+files/Screenshot%202024-02-16%20at%2013.42.06.png
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "Screenshot 2024-02-16 at 13.43.11.png"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746726/+files/Screenshot%202024-02-16%20at%2013.43.11.png
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "Screenshot 2024-02-16 at 13.39.07.png"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746724/+files/Screenshot%202024-02-16%20at%2013.39.07.png
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "Screenshot 2024-02-16 at 13.35.42.png"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746723/+files/Screenshot%202024-02-16%20at%2013.35.42.png
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "Screenshot 2024-02-16 at 13.32.35.png"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746722/+files/Screenshot%202024-02-16%20at%2013.32.35.png
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "Screenshot 2024-02-16 at 13.29.01.png"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5746721/+files/Screenshot%202024-02-16%20at%2013.29.01.png
--
You received this bug notification because you are a member of Kernel
Packages,
I was able to disable mode switch and record a video with the kernel attempting
to output the oops.
It seems to be an issue with apparmor.
The text I manually recovered from the video:
---
BUG: kernel NULL pointer dereference, address: 0008
#PF: supervisor read access in kernel mode
Still reproducible with 6.5.0-18-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048951
Title:
NUC12WSHi7 hangs few minutes after boot with linux-
Still reproducible with linux-image-6.5.0-15-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048951
Title:
NUC12WSHi7 hangs few minutes after boot with linux-
I was able to find one single line that syslog server was able to catch:
[ 353.589347] BUG: kernel NULL pointer dereference, address: 0008
I guess it doesn't give a lot of information...
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738249/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
** Attachment added: "lsb_release.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738250/+files/lsb_release.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
** Attachment added: "dmidecode.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738246/+files/dmidecode.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738247/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+attachment/5738248/+files/lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
Public bug reported:
Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few
minutes after the boot.
I can't find anything in the journal for the previous boot it just ends without
any error. Remote syslog server does not receive any error log from this host.
I've tried
I can still see the same error in dmesg on 4.10.0-041000rc4-generic
#201701152031, but it won't post it constantly as it was on 4.4. It is
logged just once at boot time.
** Attachment added: "dmesg-4.10-rc4.txt"
Public bug reported:
I observe lots of i915 warnings in dmesg after the upgrade from 14.04 to 16.04.
My current kernel is 4.4.0-59-generic.
Warnings are:
[ 1078.547129] [ cut here ]
[ 1078.547372] WARNING: CPU: 0 PID: 273 at
** Also affects: rsyslog (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/1373070
Title:
full fix for disconnected path (paths)
I'm affected by this bug too at Trusty + Vivid HWE
# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
# uname -a
Linux amanda 3.19.0-42-generic #48~14.04.1-Ubuntu SMP Fri Dec 18 10:25:23 UTC
2015 i686 i686 i686 GNU/Linux
# dpkg -l | grep linux-image-generic
ii
Just FYI:
The bug, which Ubuntu cannot fix for 7 (SEVEN!!!) years, was fixed in Fedora in
1.5 months: https://bugzilla.redhat.com/show_bug.cgi?id=1141525
** Bug watch added: Red Hat Bugzilla #1141525
https://bugzilla.redhat.com/show_bug.cgi?id=1141525
--
You received this bug notification
It seems that issue is gone with this fix.
1. Installed the package from trusty-proposed
# LANG=C apt-cache policy rsyslog
rsyslog:
Installed: 7.4.4-1ubuntu2.6
Candidate: 7.4.4-1ubuntu2.6
Version table:
*** 7.4.4-1ubuntu2.6 0
400 http://archive.ubuntu.com/ubuntu/
Also if you read comments of other Ubuntu _developers_, they are rather
confident that the bug is in Utopic HWE for Trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1425398
As I said before, I don't use Vivid, I use Trusty which is stated to be
supported until 2019!
The bug is against trusty, please don't close it as fixed in an non-LTS
release
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
John,
I'm using Ubuntu Trusty with Utopic HWE, so my apparmor is from Trusty.
I didn't install anything from backports or Utopic by hand to not mess package
system and LTS state of distribution.
But somehow the system does not behave like trusty.
Note that I've updated this system from 12.04 w/
First of all, Trusty kernel worked somehow differently. It didn't
complain for /dev/log.
Yes, my /etc/apparmor.d/usr.sbin.rsyslogd does not have 'r' for /dev/log:
/dev/log wl,
So does it mean that the rsyslog profile has to be patched for trusty?
Or at least some kind of
I can confirm that the audit message is gone from /var/log/syslog after
I got back to the original 3.13.0-46 Ubuntu 14.04.2 kernel.
** Summary changed:
- Apparmor uses rsyslogd profile for different processes
+ Apparmor uses rsyslogd profile for different processes - utopic HWE
** Also affects:
Are you serios? This bug is confirmed in 12.04 and 13.04. It can't be
invalid!
--
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/207473
Title:
Screen brightness double level changes on
33 matches
Mail list logo
