[Lenovo Ubuntu 24.04 Bug] lpfc driver reports failure message

Bug #2073571 reported by xiaochun Lee
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description:
After installing Ubuntu 24.04 in a SAN disk via "Emulex LPe35000 32Gb 1-Port Fibre Channel Adapter", the lpfc driver show many errors, like:

lpfc 0000:41:00.0: 53: [ 250.627110] 0:(0):0220 FDMI cmd failed FS_RJT Data: x211
lpfc 0000:41:00.0: 0:(0):2754 PRLI failure DID:030E00 Status:x9/x32a00, data: x4 x0 x80000000
lpfc 0000:41:00.0: 25: [ 247.537454] 0:(0):9024 FCP command xa3 failed: x0 SNS x0 x0 Data: x8 xfdc x0 x0 x0
lpfc 0000:27:00.0: 0:(0):2753 PLOGI failure DID:040F00 Status:x3/x103
kernel: rport-13:0-5: blocked FC remote port time out: removing rport

Reproduce Steps:
  1. Install Ubunut 24.04 - can intall successfully
  2. Boot into OS
  3. Check /var/log/syslog

 Expected results:
 No lpfc driver related failures or errors.

 Actual results:
 Many lpfc driver failed messages was recorded.

Configuration:
SR630V3 - Intel EGS
XCC: ESX323N
UEFI:ESE123F
UEFI Setting:Default

os:ubuntu-24.04-live-server-amd64-GA-0426
cpu: Intel(R) Xeon(R) Platinum 8460Y+*2
mem:M321R2GA3BB6-CQKEG*2
Emulex LPe35000 32Gb 1-Port Fibre Channel Adapter fw:  14.2.673.40
Intel Ethernet Server Adapter I350-T4 fw:  1.3450.0
SAN - Lenovo DM7000

Additional info:
  1. Although there're those failures, we can read/write date to SAN disks.
  2. Intel Birch Stream platform has this lpfc driver issues as well.

Revision history for this message
xiaochun Lee (xavier-lee) wrote :

Attach the sosreport file that collected after intallation complete and boot into OS again, and let the OS idle there for one whole night.You can check out that those error message keeping popping out.

Revision history for this message
xiaochun Lee (xavier-lee) wrote (last edit ):

I retrieved two papers related the erros from internet as listed below, just for your reference.

https://access.redhat.com/articles/6268621
https://access.redhat.com/solutions/5736231

description: updated
Revision history for this message
AaronMa (mapengyu) wrote :

@Lee,

Could you try upstream kernel v6.10?
If is reproduced on v6.10, we should file an upstream bug instead.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
xiaochun Lee (xavier-lee) wrote :

Yes, we'll do it!

Revision history for this message
xiaochun Lee (xavier-lee) wrote :

Errors still exist with 6.10 kernel

Jeff Lane  (bladernr)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
AaronMa (mapengyu) wrote :

@xavier

Please file an upstream bug and post here.

Thanks

Revision history for this message
xiaochun Lee (xavier-lee) wrote :

Hi
A new bug was filed in upstream kernel bug at https://bugzilla.kernel.org/show_bug.cgi?id=219128

Revision history for this message
xiaochun Lee (xavier-lee) wrote :

@AaronMa
Through the upstream maintainer's comments at https://bugzilla.kernel.org/show_bug.cgi?id=219128, all that error messages seems are normal behavior, is my understanding right? Would you please have a conclusion on this bug so that we can depend on Ubuntu's claim to handle our own internal bugs.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.