[Kernel-packages] [Bug 2055121] Re: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canon
is this the expected behavior from ubuntu when we do bios reset to default and clear NVRAM ??? ** Information type changed from Public to Private -- 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/2055121 Title: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing Status in linux package in Ubuntu: New Bug description: Description: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing in dmesg. Version-Release ubuntu 22.04.3, 24.04.4 Steps to Reproduce: 1. BIOS (Reset default and clear NVRAM) 2. install ubuntu 22.04.3 / 24.04.4 3. Post OS installation reboot the system and check LC logs warning messgae will be displayed. 4. Check dmesg for logs like : Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing. Note: This warning and dmesg logs will be showed only when you deafault bios and clear NVRAM. not seen warning message without clearing BIOS NVRAM. Is this the behavaviour is expected when install os after clearing BIOS NVRAM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055121/+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 2055121] Re: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canon
LifeCycle controller logs --- UEFI0074-The Secure Boot policy has been modified since the last time the system was started. Detailed Description: The system BIOS logs this message after detecting a change in Secure Boot policy settings. Such a change may result from user configuration or a system BIOS update. Changes to the following settings trigger this message: 1) Secure Boot (Enable/Disable) 2) Secure Boot Policy (Standard/Custom) 3) Platform Key 4) Key Exchange Keys 5) Authorized Signature Database (db) 6) Forbidden Signature Database (dbx). Recommended Action:Review the Secure Boot policy settings in System Setup > System BIOS > Security Settings page. If policy changes were expected, no action is necessary. Otherwise, modify the Secure Boot policy settings as needed. Dmesg logs -- root@ubuntu:~# dmesg |grep -i secure [0.00] secureboot: Secure boot disabled [0.012309] secureboot: Secure boot disabled [ 10.251237] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' [ 10.258614] (2017): 242ade75ac4a15e50d50c84b0d45ff3eae707a03' [ 10.266502] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (ESM 2018): 365188c1d374d6b07c3c8f240f8ef722433d6a8b' [ 10.273814] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2019): c0746fd6c5da3ae827864651ad66ae47fe24b3e8' [ 10.280706] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v1): a8d54bbb3825cfb94fa13c9f8a594a195c107b8d' [ 10.288123] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v2): 4cf046892d6fd3c9a5b03f98d845f90851dc6a8c' [ 10.295040] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (2021 v3): 100437bb6de6e469b581e61cd66bce3ef4ed53af' [ 10.301685] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing (Ubuntu Core 2019): c1d57b8f6b743f23ee41f4f7ee292f06eecadfb9' [ 10.485916] integrity: Loaded X.509 cert 'VMware, Inc.: VMware Secure Boot Signing: 04597f3e1ffb240bba0ff0f05d5eb05f3e15f6d7' [ 10.522527] blacklist: Revoked X.509 cert 'Debian Secure Boot Signer: 00a7468def' -- 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/2055121 Title: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing Status in linux package in Ubuntu: New Bug description: Description: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing in dmesg. Version-Release ubuntu 22.04.3, 24.04.4 Steps to Reproduce: 1. BIOS (Reset default and clear NVRAM) 2. install ubuntu 22.04.3 / 24.04.4 3. Post OS installation reboot the system and check LC logs warning messgae will be displayed. 4. Check dmesg for logs like : Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing. Note: This warning and dmesg logs will be showed only when you deafault bios and clear NVRAM. not seen warning message without clearing BIOS NVRAM. Is this the behavaviour is expected when install os after clearing BIOS NVRAM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055121/+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 2055121] [NEW] [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Can
Private bug reported: Description: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing in dmesg. Version-Release ubuntu 22.04.3, 24.04.4 Steps to Reproduce: 1. BIOS (Reset default and clear NVRAM) 2. install ubuntu 22.04.3 / 24.04.4 3. Post OS installation reboot the system and check LC logs warning messgae will be displayed. 4. Check dmesg for logs like : Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing. Note: This warning and dmesg logs will be showed only when you deafault bios and clear NVRAM. not seen warning message without clearing BIOS NVRAM. Is this the behavaviour is expected when install os after clearing BIOS NVRAM? ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055121 Title: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing Status in linux package in Ubuntu: New Bug description: Description: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot policy has been modified since the last time the system was started." logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing in dmesg. Version-Release ubuntu 22.04.3, 24.04.4 Steps to Reproduce: 1. BIOS (Reset default and clear NVRAM) 2. install ubuntu 22.04.3 / 24.04.4 3. Post OS installation reboot the system and check LC logs warning messgae will be displayed. 4. Check dmesg for logs like : Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing. Note: This warning and dmesg logs will be showed only when you deafault bios and clear NVRAM. not seen warning message without clearing BIOS NVRAM. Is this the behavaviour is expected when install os after clearing BIOS NVRAM? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055121/+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 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Hi Michael,
There were actually 2 issues reported in this bug
1.duplicate dax id devices
2.CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y
1st issue is got resolved, and 2nd issue you have mentioned in Bugzilla
is no longer disabled.
To reconfigure dax-devices we have to make offline/disable online memory
every time manually?
--
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/2028158
Title:
[SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set
to flat mode. Duplicate device_dax ids were created and hence probing
is failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax
to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax
to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",---> Converted from devdax - system-ram
"online_memblocks":32,
"total_memblocks":32,
"movable":true
},
{
"chardev":"dax5.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax2.0",
[Kernel-packages] [Bug 2028158] [NEW] Observed device_dax related probe errors in dmesg when HBM CPU is set to flat mode and creating duplicate device_dax ids and hence probe is failing.
Private bug reported:
Description of problem:
Observed device_dax related probe error when HBM CPU is set to flat
mode. and creating duplicate device_dax ids and hence probe is failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Demmy/duplicate devices should not create.
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should be
only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",---> Converted from devdax - system-ram
"online_memblocks":32,
"total_memblocks":32,
"movable":true
},
{
"chardev":"dax5.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram", ---> Converted from devdax - system-ram
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i dax
[ 12.748880] device_dax dax2.0: mapping0: 0x208000-0x307fff could not
reserve range
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748901] device_dax dax3.0: mapping0: 0x508000-0x607fff could not
reserve range
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
[ 812.677056] device_dax dax4.0: mapping0: 0x208000-0x307fff could not
reserve range
[ 812.677070] device_dax: probe of dax4.0 failed with error -16
[ 821.092762] device_dax dax5.0: mapping0: 0x508000-0x607fff could not
reserve range
[ 821.092774] device_dax: probe of dax5.0 failed with error -16
** Affects: linux (Ubuntu)
Importance: Undecided
[Kernel-packages] [Bug 2006080] [NEW] [Ubuntu-22.04] Installing Ubuntu 22.04 from PXE server does not change the boot order
Private bug reported: I am seeing a somewhat surprising behavior regarding device boot order after installing Ubuntu 22.04 from PXE server. In most setups with PXE as the 1st boot device in BIOS UEFI Boot Settings, installing OSes such as RHEL, SLES from PXE server or virtual CD-ROM (using ISO image) on a selected hard drive would result in a device boot order change after a successful OS install and server reboot. After the server reboots, we typically see the HDD/SSD (with the newly installed active partition) take the place of the PXE device as the 1st boot device in BIOS UEFI Boot Settings, and the system would boot directly to the OS bypassing PXE boot (assuming no manual intervention) since the PXE device is now 2nd in the boot order. In addition to RHEL and SLES, I also see this behavior after installing Ubuntu versions (such as 20.04) from virtual CD-ROM and PXE server except for Ubuntu 22.04 installation from our PXE server. Somehow the PXE device remains the 1st boot device after installing Ubuntu 22.04 from our PXE server. In that particular case, the system would eventually boots to Ubuntu 22.04 from the hard drive after it boots to the PXE menu and timed out. So I don’t quite understand why the boot order doesn’t change (for Ubuntu 22.04 PXE install) compared with all the other OS versions and installation methods. Even installing Ubuntu 22.04 using ISO image on virtual CD- ROM would change the 1st boot device from PXE to disk. Could you shed some light on this behavior? Steps to repro: 1. Install 22.04 from PXE server 2. Reboot the system Actual: Installing Ubuntu 22.04 from PXE server does not change the boot order automatically. PXE device remains the 1st boot device after installing Ubuntu 22.04 from our PXE server. Expectation: After installing Ubuntu 22.04 from PXE server, After the server reboots system would boot directly to the OS bypassing PXE boot (assuming no manual intervention). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/2006080 Title: [Ubuntu-22.04] Installing Ubuntu 22.04 from PXE server does not change the boot order Status in linux package in Ubuntu: New Bug description: I am seeing a somewhat surprising behavior regarding device boot order after installing Ubuntu 22.04 from PXE server. In most setups with PXE as the 1st boot device in BIOS UEFI Boot Settings, installing OSes such as RHEL, SLES from PXE server or virtual CD-ROM (using ISO image) on a selected hard drive would result in a device boot order change after a successful OS install and server reboot. After the server reboots, we typically see the HDD/SSD (with the newly installed active partition) take the place of the PXE device as the 1st boot device in BIOS UEFI Boot Settings, and the system would boot directly to the OS bypassing PXE boot (assuming no manual intervention) since the PXE device is now 2nd in the boot order. In addition to RHEL and SLES, I also see this behavior after installing Ubuntu versions (such as 20.04) from virtual CD-ROM and PXE server except for Ubuntu 22.04 installation from our PXE server. Somehow the PXE device remains the 1st boot device after installing Ubuntu 22.04 from our PXE server. In that particular case, the system would eventually boots to Ubuntu 22.04 from the hard drive after it boots to the PXE menu and timed out. So I don’t quite understand why the boot order doesn’t change (for Ubuntu 22.04 PXE install) compared with all the other OS versions and installation methods. Even installing Ubuntu 22.04 using ISO image on virtual CD-ROM would change the 1st boot device from PXE to disk. Could you shed some light on this behavior? Steps to repro: 1. Install 22.04 from PXE server 2. Reboot the system Actual: Installing Ubuntu 22.04 from PXE server does not change the boot order automatically. PXE device remains the 1st boot device after installing Ubuntu 22.04 from our PXE server. Expectation: After installing Ubuntu 22.04 from PXE server, After the server reboots system would boot directly to the OS bypassing PXE boot (assuming no manual intervention). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006080/+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 1999883] [NEW] [DELL EMC Ubuntu-22.04 BUG] When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more
Private bug reported: It is seen on Intel based DELL EMC system under development that when we select system profile as "Performance Per Watt (DAPC)" using BIOS setting, then install Ubuntu-22.04 and boot into OS then check the bootup time. How reproducible: Always Steps to Reproduce: 1. Install Ubuntu-22.04 on Intel based DELL EMC system under development with latest firmware 2. set system profile as "Performance Per Watt (DAPC)" from BIOS setting 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "SOS report" https://bugs.launchpad.net/bugs/1999883/+attachment/5635892/+files/sosreport-MW01219-boottime-2022-12-16-djbofzn.tar.xz ** Information type changed from Public to Private -- 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/1999883 Title: [DELL EMC Ubuntu-22.04 BUG] When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more Status in linux package in Ubuntu: New Bug description: It is seen on Intel based DELL EMC system under development that when we select system profile as "Performance Per Watt (DAPC)" using BIOS setting, then install Ubuntu-22.04 and boot into OS then check the bootup time. How reproducible: Always Steps to Reproduce: 1. Install Ubuntu-22.04 on Intel based DELL EMC system under development with latest firmware 2. set system profile as "Performance Per Watt (DAPC)" from BIOS setting 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999883/+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 1981554] Re: [Ubuntu-22.04] Video mode is not working with the external monitor
Hi Michael, I have tried daily build https://cdimage.ubuntu.com/ubuntu- server/jammy/daily-live/ and the issue is got resolved with 22.04.1 daily build. -- 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/1981554 Title: [Ubuntu-22.04] Video mode is not working with the external monitor Status in linux package in Ubuntu: Incomplete Bug description: Description: The SUT Dell EMC Poweredge R440 can not display video mode with external monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC virtual console. Steps to Reproduce: 1. Connect External monitor to SUT using VGA cable. 2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console. 3. Start to install the OS and click "Try or Install Ubuntu server". 4. The SUT can not display video mode with monitor when OS boots. Expected Results: Video mode should work properly when OS boots with external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+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 1981554] Re: [Ubuntu-22.04] Video mode is not working with the external monitor
Hi Found following upstream patch - https://github.com/torvalds/linux/commit/40ce1121c1d76daf9048a86e36c83e469281b9fd which seems related to the issue. i have Applied this patch and and tested issue is fixed. -- 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/1981554 Title: [Ubuntu-22.04] Video mode is not working with the external monitor Status in linux package in Ubuntu: Incomplete Bug description: Description: The SUT Dell EMC Poweredge R440 can not display video mode with external monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC virtual console. Steps to Reproduce: 1. Connect External monitor to SUT using VGA cable. 2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console. 3. Start to install the OS and click "Try or Install Ubuntu server". 4. The SUT can not display video mode with monitor when OS boots. Expected Results: Video mode should work properly when OS boots with external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+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 1981554] Re: [Ubuntu-22.04] Video mode is not working with the external monitor
Hello Mr.Jeff Lane, I have collected the logs and attached as Ubuntu Kernel Bot (ubuntu-kernel-bot) suggested using command apport-collect 1981554 ** Attachment added: "apport.linux.c1ywpzcg.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+attachment/5606281/+files/apport.linux.c1ywpzcg.apport -- 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/1981554 Title: [Ubuntu-22.04] Video mode is not working with the external monitor Status in linux package in Ubuntu: Incomplete Bug description: Description: The SUT Dell EMC Poweredge R440 can not display video mode with external monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC virtual console. Steps to Reproduce: 1. Connect External monitor to SUT using VGA cable. 2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console. 3. Start to install the OS and click "Try or Install Ubuntu server". 4. The SUT can not display video mode with monitor when OS boots. Expected Results: Video mode should work properly when OS boots with external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+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 1981554] Re: [Ubuntu-22.04] Video mode is not working with the external monitor
- I have installed GUI and checked the default display resolution was 1280*1024@75Hz---> While booting and afterbooting external display not showing anything. - Changed to display resolution 1152*864@75Hz ---> while booting not able to see content on display but Afterboot able to see content in external disaplay. - if "nomodeset" kernel parameter is passed issue is not reproducible. Workaround: - If we install GUI based ubuntu and after OS boot done change display resolution to the 1152*864@75Hz we can able to see content on external display. -- 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/1981554 Title: [Ubuntu-22.04] Video mode is not working with the external monitor Status in linux package in Ubuntu: Incomplete Bug description: Description: The SUT Dell EMC Poweredge R440 can not display video mode with external monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC virtual console. Steps to Reproduce: 1. Connect External monitor to SUT using VGA cable. 2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console. 3. Start to install the OS and click "Try or Install Ubuntu server". 4. The SUT can not display video mode with monitor when OS boots. Expected Results: Video mode should work properly when OS boots with external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+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 1981554] [NEW] [Ubuntu-22.04] Video mode is not working with the external monitor
Private bug reported: Description: The SUT Dell EMC Poweredge R440 can not display video mode with external monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC virtual console. Steps to Reproduce: 1. Connect External monitor to SUT using VGA cable. 2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console. 3. Start to install the OS and click "Try or Install Ubuntu server". 4. The SUT can not display video mode with monitor when OS boots. Expected Results: Video mode should work properly when OS boots with external monitor. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/1981554 Title: [Ubuntu-22.04] Video mode is not working with the external monitor Status in linux package in Ubuntu: New Bug description: Description: The SUT Dell EMC Poweredge R440 can not display video mode with external monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC virtual console. Steps to Reproduce: 1. Connect External monitor to SUT using VGA cable. 2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console. 3. Start to install the OS and click "Try or Install Ubuntu server". 4. The SUT can not display video mode with monitor when OS boots. Expected Results: Video mode should work properly when OS boots with external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+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
