[Kernel-packages] [Bug 2048951] Re: 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)
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 - 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) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: 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)
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 (apparmor_bprm_creds_for_exec, profile_transition) with linux- image-6.5.0-18-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: 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)
** 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) -- 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 (apparmor_bprm_creds_for_exec, profile_transition) with linux- image-6.5.0-18-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-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 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 (apparmor_bprm_creds_for_exec, profile_transition) with linux- image-6.5.0-18-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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 with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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, 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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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, 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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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, 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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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, 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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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, 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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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, 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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
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 #PF: error_code(0x) - not-present page P?D 0 P4D 0 Ooops: [#1] PREEMPT SMP WDPTI ... Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? do_user_addr_fault+0x31d/0x6b0 ? exc_page_fault+0x83/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? find_attach+0x11a/0x5e0 ? d_namespace_path_constprop.0+0xa3/0x310 profile_transition+0x5e0/0x910 apparmor_bprm_creds_for_exec+0x3b9/0xc00 security_bprm_creds_for_exec+0x2e/0x50 bprm_execve.part.0+0x12f/0x250 bprm_execve+0x5d/0xa0 do_execveat_common.isra.0+0x1a9/0x260 __x64_sys_execve+0x87/0x60 do_syscall_64+0x58/0x?0 ? syscall_exit_to_user_mode+0x37/0x60 ? do_syscall_64+0x67/0x90 entry_SYSCALL_64_after_hwframe+0x6r/0xd8 --- I will also attach screenshots from the video -- 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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
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 subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
** 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. https://bugs.launchpad.net/bugs/2048951 Title: NUC12WSHi7 hangs few minutes after boot with linux- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] [NEW] NUC12WSHi7 hangs few minutes after boot with linux-image-6.5.0-14-generic (linux-image-generic-hwe-22.04)
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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. ** Affects: linux-meta-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- 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- image-6.5.0-14-generic (linux-image-generic-hwe-22.04) Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: 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 running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656539] Re: Lots of i915 warnings in the log
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656539/+attachment/4806704/+files/dmesg-4.10-rc4.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/1656539 Title: Lots of i915 warnings in the log Status in linux package in Ubuntu: Incomplete Bug description: 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 /build/linux-5Vy7q8/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12169 intel_atomic_check+0x307/0x6d0 [i915]() [ 1078.547388] WARN_ON(!connector_state->crtc) ... [ 1078.591137] [ cut here ] [ 1078.591377] WARNING: CPU: 0 PID: 273 at /build/linux-5Vy7q8/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 intel_modeset_check_state+0x556/0x910 [i915]() [ 1078.591394] encoder's enabled state mismatch (expected 0, found 1) ... I have the following video controller: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 янв 14 08:17 seq crw-rw 1 root audio 116, 33 янв 14 08:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Jan 14 08:30:26 2017 InstallationDate: Installed on 2012-08-28 (1599 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Evo Technologies, Inc. ECOPC N.1A/LE PciMultimedia: ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/hostname-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-28 (139 days ago) dmi.bios.date: 05/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: JT94510H.86A.0045.2010.0519.1750 dmi.board.name: D945GSEJT dmi.board.vendor: Intel Corporation dmi.board.version: AAE57850-407 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrJT94510H.86A.0045.2010.0519.1750:bd05/19/2010:svnEvoTechnologies,Inc.:pnECOPCN.1A/LE:pvr:rvnIntelCorporation:rnD945GSEJT:rvrAAE57850-407:cvn:ct3:cvr: dmi.product.name: ECOPC N.1A/LE dmi.sys.vendor: Evo Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1656539] [NEW] Lots of i915 warnings in the log
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 /build/linux-5Vy7q8/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12169 intel_atomic_check+0x307/0x6d0 [i915]() [ 1078.547388] WARN_ON(!connector_state->crtc) ... [ 1078.591137] [ cut here ] [ 1078.591377] WARNING: CPU: 0 PID: 273 at /build/linux-5Vy7q8/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 intel_modeset_check_state+0x556/0x910 [i915]() [ 1078.591394] encoder's enabled state mismatch (expected 0, found 1) ... I have the following video controller: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 янв 14 08:17 seq crw-rw 1 root audio 116, 33 янв 14 08:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Jan 14 08:30:26 2017 InstallationDate: Installed on 2012-08-28 (1599 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Evo Technologies, Inc. ECOPC N.1A/LE PciMultimedia: ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=/dev/mapper/hostname-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-28 (139 days ago) dmi.bios.date: 05/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: JT94510H.86A.0045.2010.0519.1750 dmi.board.name: D945GSEJT dmi.board.vendor: Intel Corporation dmi.board.version: AAE57850-407 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrJT94510H.86A.0045.2010.0519.1750:bd05/19/2010:svnEvoTechnologies,Inc.:pnECOPCN.1A/LE:pvr:rvnIntelCorporation:rnD945GSEJT:rvrAAE57850-407:cvn:ct3:cvr: dmi.product.name: ECOPC N.1A/LE dmi.sys.vendor: Evo Technologies, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 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/1656539 Title: Lots of i915 warnings in the log Status in linux package in Ubuntu: New Bug description: 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 /build/linux-5Vy7q8/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12169 intel_atomic_check+0x307/0x6d0 [i915]() [ 1078.547388] WARN_ON(!connector_state->crtc) ... [ 1078.591137] [ cut here ] [ 1078.591377] WARNING: CPU: 0 PID: 273 at /build/linux-5Vy7q8/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 intel_modeset_check_state+0x556/0x910 [i915]() [ 1078.591394] encoder's enabled state mismatch (expected 0, found 1) ... I have the following video controller: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 янв 14 08:17 seq crw-rw 1 root audio 116, 33 янв 14 08:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4
[Kernel-packages] [Bug 1373070] Re: full fix for disconnected path (paths)
** 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) Status in cups package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in rsyslog package in Ubuntu: New Bug description: With the apparmor 3 RC1 upload, there is an incomplete bug fix for disconnected paths. This bug is to track that work. This denial may be related: Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is related to bug 1375410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1373070] Re: 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 linux-image-generic 3.13.0.74.80 i386 Generic Linux kernel image ii linux-image-generic-lts-vivid 3.19.0.42.27 i386 Generic Linux kernel image # dpkg -l | grep -e rsyslog -e apparmor ii apparmor2.8.95~2430-0ubuntu5.3 i386 User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.3 all Profiles for AppArmor Security policies ... ii rsyslog 7.4.4-1ubuntu2.6 i386 reliable system and kernel logging daemon # grep 'audit:' /var/log/syslog | grep DENIED Dec 26 09:39:48 amanda kernel: [11627.614510] audit: type=1400 audit(145988.687:54): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=20376 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 -- 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) Status in cups package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in rsyslog package in Ubuntu: New Bug description: With the apparmor 3 RC1 upload, there is an incomplete bug fix for disconnected paths. This bug is to track that work. This denial may be related: Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is related to bug 1375410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 207473] Re: Screen brightness double level changes on Dell laptops
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 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 Dell laptops Status in Linux: Fix Released Status in hal package in Ubuntu: Invalid Status in kde-guidance package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in hal source package in Hardy: Invalid Status in kde-guidance source package in Hardy: Fix Released Status in linux source package in Hardy: Invalid Bug description: Binary package hint: gnome-power-manager I have a fresh installation of Hardy with the latest updates installed on a Dell Inspiron 6400 laptop. The brightness settings (Fn+Up/Down) work although they seem to skip a level each time. '/proc/acpi/video/VID/LCD/brightness' tells me that it supports brightness levels 12, 24, 36, 48, 60, 72, 84 and 100. Without gnome- power-manager running pressing Fn+Up will transition up into each level and back down again smoothly. When gnome-power-manager is running increasing the brightness from 12 I can only get levels 36, 60, 84 and 100. Decreasing the levels from 100 I only get 72, 48, 24 and 12. Running gnome-power-manager with the verbose option shows that when I press the brightness-up button once it is recorded twice. I ran gnome-power-manager in a debugger thinking it was a timing issue and it still happened. I have included the output from pressing the brightness-up button (Fn+Up) once below. This only happens when gnome-power-manager is running and did not happen using Feisty. I have looked at the code and I cannot see why the button event is triggered twice, I don't have any experience of the code but if you can give me any ideas of where to start I can try to look into this myself. Thanks! [hal_device_condition_cb] gpm-button.c:391 (00:11:48): condition=ButtonPressed, details=brightness-up [emit_button_pressed] gpm-button.c:335 (00:11:48): emitting button-pressed : brightness-up [button_pressed_cb] gpm-manager.c:999 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-srv-screensaver.c:167 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-backlight.c:563 (00:11:48):Button press event type=brightness-up [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (00:11:48): GetBrightness returned level: 0 [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:155 (00:11:48): Setting 1 of 7 [gpm_brightness_lcd_up] gpm-brightness-lcd.c:362 (00:11:48): emitting brightness-changed (14) [brightness_changed_cb] gpm-backlight.c:755 (00:11:48):Need to display backlight feedback value 14 [gpm_feedback_display_value] gpm-feedback-widget.c:144 (00:11:48): Displaying 0.14 on feedback widget [gpm_refcount_add] gpm-refcount.c:100 (00:11:48): refcount now: 1 [gpm_refcount_add] gpm-refcount.c:101 (00:11:48): non zero, so sending REFCOUNT_ADDED [brightness_changed_cb] gpm-backlight.c:759 (00:11:48):emitting brightness-changed : 14 [button_pressed_cb] gpm-info.c:698 (00:11:48): Button press event type=brightness-up [hal_device_condition_cb] gpm-button.c:391 (00:11:48): condition=ButtonPressed, details=brightness-up [emit_button_pressed] gpm-button.c:335 (00:11:48): emitting button-pressed : brightness-up [button_pressed_cb] gpm-manager.c:999 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-srv-screensaver.c:167 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-backlight.c:563 (00:11:48):Button press event type=brightness-up [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (00:11:48): GetBrightness returned level: 1 [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:155 (00:11:48): Setting 2 of 7 [gpm_brightness_lcd_up] gpm-brightness-lcd.c:362 (00:11:48): emitting brightness-changed (28) [brightness_changed_cb] gpm-backlight.c:755 (00:11:48):Need to display backlight feedback value 28 [gpm_feedback_display_value] gpm-feedback-widget.c:144 (00:11:48): Displaying 0.28 on feedback widget [gpm_refcount_add] gpm-refcount.c:100 (00:11:48): refcount now: 2 [gpm_refcount_add] gpm-refcount.c:101 (00:11:48): non zero, so sending REFCOUNT_ADDED [brightness_changed_cb] gpm-backlight.c:759 (00:11:48):emitting brightness-changed : 28 [button_pressed_cb] gpm-info.c:698 (00:11:48): Button press event type=brightness-up [gpm_refcount_auto_decrement] gpm-refcount.c:77 (00:11:50):
[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
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/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 7.4.4-1ubuntu2.5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 7.4.4-1ubuntu2.3 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.4.4-1ubuntu2 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 2. commented out the workaround /dev/log rwl, from /etc/apparmor.d/local/usr.sbin.rsyslogd 3. Rebooted to the latest Utopic HWE kernel # uname -a Linux emma 3.16.0-37-generic #51~14.04.1-Ubuntu SMP Wed May 6 15:23:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 4. The issue is gone: # dmesg | grep DENIED # -- 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 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: In Progress Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Fix Committed Bug description: [rsyslog impact] This bug prevents rsyslog from receiving all events from other services on trusty when the utopic-hwe (and newer) kernels are used. The rsyslog SRU adds an additional permission (read access to /dev/log) to the rsyslog apparmor policy to allow this to work. [rsyslog test case] (1) Ensure the rsyslog apparmor policy is set to enforce; it should show up listed in the XX profiles are in enforce mode. section reported by sudo aa-status (if it's disabled, do sudo aa-enforce rsyslogd). (2) Install the utopic or newer hwe enablement stack reboot into the kernel. Using the logger(1) utility should generate log messages (e.g. logger foo) that are recorded in syslog; with this bug, they will be blocked (grep DENIED /var/log/syslog). [rsyslog regression potential] The only change to rsyslog in the SRU is a slight loosening of the rsyslog apparmor policy. The risk of an introduced regression is small. [rsyslog addition info] The qa-regression-testing script is useful for verifying that rsyslog is still functioning properly (http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-rsyslog.py) [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii
[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
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 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Invalid Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Triaged Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
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 linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Invalid Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Triaged Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
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/ Trusty HWE to 14.04 with do-release-upgrade few months ago. $ LANG=C apt-cache policy apparmor apparmor-profiles apparmor-utils apparmor: Installed: 2.8.95~2430-0ubuntu5.1 Candidate: 2.8.95~2430-0ubuntu5.1 Version table: *** 2.8.95~2430-0ubuntu5.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages apparmor-profiles: Installed: 2.8.95~2430-0ubuntu5.1 Candidate: 2.8.95~2430-0ubuntu5.1 Version table: *** 2.8.95~2430-0ubuntu5.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages apparmor-utils: Installed: 2.8.95~2430-0ubuntu5.1 Candidate: 2.8.95~2430-0ubuntu5.1 Version table: *** 2.8.95~2430-0ubuntu5.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- 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 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: New Status in linux-lts-utopic package in Ubuntu: New Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
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 Utopic HWE release notes has to be updated? I've updated /etc/apparmor.d/local/usr.sbin.rsyslogd and can confirm that message is gone with Utopic kernel. -- 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 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: New Status in linux-lts-utopic package in Ubuntu: New Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes
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: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New -- 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 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: New Status in linux-lts-utopic package in Ubuntu: New Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 207473] Re: Screen brightness double level changes on Dell laptops
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 Dell laptops Status in The Linux Kernel: Fix Released Status in “hal” package in Ubuntu: Invalid Status in “kde-guidance” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “hal” source package in Hardy: Invalid Status in “kde-guidance” source package in Hardy: Fix Released Status in “linux” source package in Hardy: Invalid Bug description: Binary package hint: gnome-power-manager I have a fresh installation of Hardy with the latest updates installed on a Dell Inspiron 6400 laptop. The brightness settings (Fn+Up/Down) work although they seem to skip a level each time. '/proc/acpi/video/VID/LCD/brightness' tells me that it supports brightness levels 12, 24, 36, 48, 60, 72, 84 and 100. Without gnome- power-manager running pressing Fn+Up will transition up into each level and back down again smoothly. When gnome-power-manager is running increasing the brightness from 12 I can only get levels 36, 60, 84 and 100. Decreasing the levels from 100 I only get 72, 48, 24 and 12. Running gnome-power-manager with the verbose option shows that when I press the brightness-up button once it is recorded twice. I ran gnome-power-manager in a debugger thinking it was a timing issue and it still happened. I have included the output from pressing the brightness-up button (Fn+Up) once below. This only happens when gnome-power-manager is running and did not happen using Feisty. I have looked at the code and I cannot see why the button event is triggered twice, I don't have any experience of the code but if you can give me any ideas of where to start I can try to look into this myself. Thanks! [hal_device_condition_cb] gpm-button.c:391 (00:11:48): condition=ButtonPressed, details=brightness-up [emit_button_pressed] gpm-button.c:335 (00:11:48): emitting button-pressed : brightness-up [button_pressed_cb] gpm-manager.c:999 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-srv-screensaver.c:167 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-backlight.c:563 (00:11:48):Button press event type=brightness-up [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (00:11:48): GetBrightness returned level: 0 [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:155 (00:11:48): Setting 1 of 7 [gpm_brightness_lcd_up] gpm-brightness-lcd.c:362 (00:11:48): emitting brightness-changed (14) [brightness_changed_cb] gpm-backlight.c:755 (00:11:48):Need to display backlight feedback value 14 [gpm_feedback_display_value] gpm-feedback-widget.c:144 (00:11:48): Displaying 0.14 on feedback widget [gpm_refcount_add] gpm-refcount.c:100 (00:11:48): refcount now: 1 [gpm_refcount_add] gpm-refcount.c:101 (00:11:48): non zero, so sending REFCOUNT_ADDED [brightness_changed_cb] gpm-backlight.c:759 (00:11:48):emitting brightness-changed : 14 [button_pressed_cb] gpm-info.c:698 (00:11:48): Button press event type=brightness-up [hal_device_condition_cb] gpm-button.c:391 (00:11:48): condition=ButtonPressed, details=brightness-up [emit_button_pressed] gpm-button.c:335 (00:11:48): emitting button-pressed : brightness-up [button_pressed_cb] gpm-manager.c:999 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-srv-screensaver.c:167 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-backlight.c:563 (00:11:48):Button press event type=brightness-up [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (00:11:48): GetBrightness returned level: 1 [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:155 (00:11:48): Setting 2 of 7 [gpm_brightness_lcd_up] gpm-brightness-lcd.c:362 (00:11:48): emitting brightness-changed (28) [brightness_changed_cb] gpm-backlight.c:755 (00:11:48):Need to display backlight feedback value 28 [gpm_feedback_display_value] gpm-feedback-widget.c:144 (00:11:48): Displaying 0.28 on feedback widget [gpm_refcount_add] gpm-refcount.c:100 (00:11:48): refcount now: 2 [gpm_refcount_add] gpm-refcount.c:101 (00:11:48): non zero, so sending REFCOUNT_ADDED [brightness_changed_cb] gpm-backlight.c:759 (00:11:48):emitting brightness-changed : 28 [button_pressed_cb] gpm-info.c:698 (00:11:48): Button press event type=brightness-up [gpm_refcount_auto_decrement] gpm-refcount.c:77 (00:11:50):refcount now: 1 [gpm_refcount_auto_decrement] gpm-refcount.c:74 (00:11:50):zero, so sending REFCOUNT_ZERO [gpm_feedback_close_window]
