92efe6f666
Add kernel 5.10.74 debian packaging. The kernel we are building starts as source code from the Yocto Project kernel found at (https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/about/?h=v5.10/standard/base). To facilitate the creation of a Debian package of this kernel we start by making a copy of the 5.10 Debian Bullseye 'debian' folder taken from (http://snapshot.debian.org/package/linux/5.10.28-1/) and apply customization via the meta-data patches in debian/deb_patches dir. In this way we can review and incorporate changes the Debian community makes to their kernel's 'debian' folder over time. Since there are StarlingX specific patches to the kernel not suitable to send for merging in linux-yocto we apply these here as defined in scope and order in the contained debian/patches/series file. Verification: As we are only getting the Debian work bootstrapped there is quite a few restrictions as far as what can be tested. - I have compared it to the kernel 5.10.74 being used with stx centos: - the linux-yocto source code is same; - all the StarlingX specific patches are same; - the .config of Starlingx centos kernel 5.10.74 is taken to Starlingx debian, coexists and overrides the default debian kenrel configs, and only below changes are done for it: - remove some CONFIGs not set by Starlingx centos kernel code intentionally, such as CONFIG_CC_CAN_LINK; - remove some CONFIGs special for Starlingx centos kernel code such as: CONFIG_CC_VERSION_TEXT; - keep the CONFIGs related with signature aligned with debian release, because the security feature is still in development. - 28 debs are built successfully. Build kernel image into rootfs and initramfs. Build the LAT ustart image from them. - Use qemu to boot the ustart image, and the installer installs the rootfs successfully. The final debian system with this new kernel boot up successfully and run some simple commands successfully. Story: 2009221 Task: 43290 Signed-off-by: Li Zhou <li.zhou@windriver.com> Change-Id: I2f98fcc3f929e3e006d30210d559913a10a77ac2
42 lines
1.6 KiB
Diff
42 lines
1.6 KiB
Diff
From 2a32d5bc7e385fbf40f22cc413354e17a24d4de9 Mon Sep 17 00:00:00 2001
|
|
From: Jiping Ma <jiping.ma2@windriver.com>
|
|
Date: Sun, 10 Oct 2021 18:56:26 -0700
|
|
Subject: [PATCH] scsi: smartpqi: Enable sas_address sysfs for SATA device
|
|
type.
|
|
|
|
We met the issue DM complains that it can't find the disk specified
|
|
in the deployment config file after we updated the Linux kernel to 5.10.
|
|
The error is "failed to find disk for path /dev/disk/by-path/
|
|
pci-0000:3b:00.0-sas-0x31402ec001d92983-lun-0"
|
|
|
|
This happens because device type SATA is excluded from being
|
|
processed with the function pqi_is_device_with_sas_address.
|
|
which causes all SATA type disk drives to appear the same, having
|
|
zeroes in the lun name. /dev/disk/by-path/
|
|
pci-0000:3b:00.0-sas-0x0000000000000000-lun-0
|
|
|
|
We can add type SA_DEVICE_TYPE_SATA to class device_with_sas_address,
|
|
since it will also get the sas_address from wwid. and works transparently
|
|
with the old kernel without gaps.
|
|
|
|
Signed-off-by: Jiping Ma <jiping.ma2@windriver.com>
|
|
---
|
|
drivers/scsi/smartpqi/smartpqi_init.c | 1 +
|
|
1 file changed, 1 insertion(+)
|
|
|
|
diff --git a/drivers/scsi/smartpqi/smartpqi_init.c b/drivers/scsi/smartpqi/smartpqi_init.c
|
|
index ecb2af3f43ca..df16e0a27a41 100644
|
|
--- a/drivers/scsi/smartpqi/smartpqi_init.c
|
|
+++ b/drivers/scsi/smartpqi/smartpqi_init.c
|
|
@@ -2101,6 +2101,7 @@ static inline void pqi_mask_device(u8 *scsi3addr)
|
|
static inline bool pqi_is_device_with_sas_address(struct pqi_scsi_dev *device)
|
|
{
|
|
switch (device->device_type) {
|
|
+ case SA_DEVICE_TYPE_SATA:
|
|
case SA_DEVICE_TYPE_SAS:
|
|
case SA_DEVICE_TYPE_EXPANDER_SMP:
|
|
case SA_DEVICE_TYPE_SES:
|
|
--
|
|
2.31.1
|
|
|