focal/linux-azure: Enable missing config options
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-azure (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| Focal |
Fix Released
|
Medium
|
Tim Gardner | ||
Bug Description
SRU Justification
[Impact]
focal/linux-azure is missing a number of config options compared to impish/linux-azure. This kernel is also missing 2 patches that significantly impact network performance.
From Microsoft:
We tested this kernel. The P0P1 test cases are finished. Below are we found. P2 test cases are still running. I will update you when they are finished.
1. From dmesg, we can see following lines. Could you check why it has these messages and if the messages impact the system?
[ 3.341802] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[ 3.346056] unable to read xattr id index table
2. The kernel hasn't backport Michael's SRIOV performance improvement patches. The network performance is not expected.
Here are the patches:
https:/
https:/
3. It is failed to create raid 0 using below command.
# mdadm --create /dev/md0 --level 0 --raid-devices 16 /dev/sd[
mdadm: Defaulting to version 1.2 metadata
mdadm: RUN_ARRAY failed: Invalid argument
From dmesg, it has following lines:
[ 235.830712] md: personality for level 0 is not loaded!
[ 235.830733] md: md0 stopped.
I see many raid related configuration is not set. Could you check the raid related and other configuration?
# cat /boot/config-
CONFIG_RAID_ATTRS=m
# CONFIG_
# CONFIG_SCSI_AACRAID is not set
# CONFIG_
# CONFIG_
CONFIG_
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_DM_RAID is not set
CONFIG_
CONFIG_
CONFIG_RAID6_PQ=m
CONFIG_
[Test Case]
Microsoft tested
[Where things could go wrong]
There should be little chance of regression given that these are config options.
| affects: | linux (Ubuntu) → linux-azure (Ubuntu) |
| Changed in linux-azure (Ubuntu): | |
| assignee: | nobody → Tim Gardner (timg-tpi) |
| importance: | Undecided → Medium |
| tags: | added: bot-stop-nagging |
| Changed in linux-azure (Ubuntu): | |
| status: | New → Fix Released |
| assignee: | Tim Gardner (timg-tpi) → nobody |
| Changed in linux-azure (Ubuntu Focal): | |
| assignee: | nobody → Tim Gardner (timg-tpi) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| description: | updated |
| Changed in linux-azure (Ubuntu Focal): | |
| status: | In Progress → Fix Committed |
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote | #1 |
| tags: | added: verification-needed-focal |
| tags: |
added: verification-done-focal removed: verification-needed-focal |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in linux-azure (Ubuntu Focal): | |
| status: | Fix Committed → Fix Released |
This bug is awaiting verification that the linux-azure/
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/