[Kernel-packages] [Bug 2012060] Re: Crash doesn't open kdumps on Jammy with HWE kernel

[Roman Bolshakov]

The issue is still present for 6.2 kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2012060

Title:
  Crash doesn't open kdumps on Jammy with HWE kernel

Status in crash package in Ubuntu:
  New

Bug description:
  Hi!

  I'm running Ubuntu with HWE kernel 5.19.0-35-generic. The kernel
  contains slab struct changes [1] that break crash 8.0.0. The issue has
  been fixed [3] in commit 14f8c460473c ("memory: Handle struct slab
  changes on Linux 5.17-rc1 and later"). The fix is available in crash
  8.0.1 and above.

  If you wish I can send a merge request to jammy-devel with this single
  patch but for now it seems that Ubuntu's process with regards to this
  package is just bump it to the newer version from debian.

  Please advice how to proceed. For now I just build the latest version
  of crash and I can open kdumps from Jammy with HWE using it.

  1. https://lwn.net/Articles/881039/
  2. https://bugzilla.redhat.com/show_bug.cgi?id=2041702
  3. 
https://github.com/crash-utility/crash/commit/14f8c460473c8613553b5defd174ca2af812ddcb

  $ lsb_release -rd
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  $ apt-cache policy crash
  crash:
Installed: 8.0.0-1ubuntu1
Candidate: 8.0.0-1ubuntu1
Version table:
   *** 8.0.0-1ubuntu1 500
  500 http://th.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2012060/+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 2012060] [NEW] Crash doesn't open kdumps on Jammy with HWE kernel

[Roman Bolshakov]

Public bug reported:

Hi!

I'm running Ubuntu with HWE kernel 5.19.0-35-generic. The kernel
contains slab struct changes [1] that break crash 8.0.0. The issue has
been fixed [3] in commit 14f8c460473c ("memory: Handle struct slab
changes on Linux 5.17-rc1 and later"). The fix is available in crash
8.0.1 and above.

If you wish I can send a merge request to jammy-devel with this single
patch but for now it seems that Ubuntu's process with regards to this
package is just bump it to the newer version from debian.

Please advice how to proceed. For now I just build the latest version of
crash and I can open kdumps from Jammy with HWE using it.

1. https://lwn.net/Articles/881039/
2. https://bugzilla.redhat.com/show_bug.cgi?id=2041702
3. 
https://github.com/crash-utility/crash/commit/14f8c460473c8613553b5defd174ca2af812ddcb

$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04

$ apt-cache policy crash
crash:
  Installed: 8.0.0-1ubuntu1
  Candidate: 8.0.0-1ubuntu1
  Version table:
 *** 8.0.0-1ubuntu1 500
500 http://th.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

** Affects: crash (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2012060

Title:
  Crash doesn't open kdumps on Jammy with HWE kernel

Status in crash package in Ubuntu:
  New

Bug description:
  Hi!

  I'm running Ubuntu with HWE kernel 5.19.0-35-generic. The kernel
  contains slab struct changes [1] that break crash 8.0.0. The issue has
  been fixed [3] in commit 14f8c460473c ("memory: Handle struct slab
  changes on Linux 5.17-rc1 and later"). The fix is available in crash
  8.0.1 and above.

  If you wish I can send a merge request to jammy-devel with this single
  patch but for now it seems that Ubuntu's process with regards to this
  package is just bump it to the newer version from debian.

  Please advice how to proceed. For now I just build the latest version
  of crash and I can open kdumps from Jammy with HWE using it.

  1. https://lwn.net/Articles/881039/
  2. https://bugzilla.redhat.com/show_bug.cgi?id=2041702
  3. 
https://github.com/crash-utility/crash/commit/14f8c460473c8613553b5defd174ca2af812ddcb

  $ lsb_release -rd
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  $ apt-cache policy crash
  crash:
Installed: 8.0.0-1ubuntu1
Candidate: 8.0.0-1ubuntu1
Version table:
   *** 8.0.0-1ubuntu1 500
  500 http://th.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2012060/+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 1924588] Re: P2P mode doesn't work in qla2xxx

[Roman Bolshakov]

It should be fixed in 5.4.0-74.83:
  https://launchpad.net/ubuntu/+source/linux/5.4.0-74.83

By pulling upstream v5.4.114 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926493):
Revert "scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure"
Revert "scsi: qla2xxx: Fix stuck login session using prli_pend_timer"
scsi: qla2xxx: Dual FCP-NVMe target port support
scsi: qla2xxx: Fix device connect issues in P2P configuration
scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure
scsi: qla2xxx: Add a shadow variable to hold disc_state history of fcport


** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1924588

Title:
  P2P mode doesn't work in  qla2xxx

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Link to a patch series to the stable:
  https://www.spinics.net/lists/stable/msg458515.html

  QLogic FC adapters don't work in direct mode on focal (at least
  QLE2692, and QLE2694, QLE2742 are affected):

  [  266.821659] qla2xxx [:05:00.0]-3874:3: ELS_DCMD PLOGI sent, hdl=1a, 
loopid=0, to port_id 02 from port_id 01
  [  266.822926] qla2xxx [:05:00.0]-583f:3: ELS IOCB Done -Driver ELS logo 
error hdl=1a comp_status=0x0 error subcode 1=0x0 error subcode 2=0x0 
total_byte=0x74
  [  266.822933] qla2xxx [:05:00.0]-3872:3: ELS_DCMD ELS done rc 0 hdl=1a, 
portid=02 21:00:34:80:0d:74:14:d2
  [  266.822937] qla2xxx [:05:00.0]-2918:3: qla_handle_els_plogi_done 1764 
21:00:34:80:0d:74:14:d2 post PRLI
  [  266.822965] qla2xxx [:05:00.0]-291b:3: Async-prli - 
21:00:34:80:0d:74:14:d2 hdl=0, loopid=0 portid=02 retries=29 nvme.
  [  266.823008] qla2xxx [:05:00.0]-5837:3: Async-prli failed - 
21:00:34:80:0d:74:14:d2 hdl=1b portid=02 comp=31 iop0=18 iop1=b.
  [  266.823011] qla2xxx [:05:00.0]-2929:3: qla2x00_async_prli_sp_done 
21:00:34:80:0d:74:14:d2 res 0
  [  266.823014] qla2xxx [:05:00.0]-2918:3: qla24xx_handle_prli_done_event 
1934 21:00:34:80:0d:74:14:d2 post NVMe prli
  [  266.823019] qla2xxx [:05:00.0]-e801:3: Scheduling sess 
a438982b for deletion 21:00:34:80:0d:74:14:d2
  [  266.823031] qla2xxx [:05:00.0]-290a:3: qlt_unreg_sess sess 
a438982b for deletion 21:00:34:80:0d:74:14:d2
  [  266.823039] qla2xxx [:05:00.0]-f884:3: qlt_free_session_done: se_sess 
 / sess a438982b from port 21:00:34:80:0d:74:14:d2 
loop_id 0x00 s_id 00:00:02 logout 1 keep 0 els_logo 0
  [  266.823043] qla2xxx [:05:00.0]-f886:3: qlt_free_session_done: waiting 
for sess a438982b logout
  [  266.823066] qla2xxx [:05:00.0]-2870:3: Async-logout - hdl=0 loop-id=0 
portid=02 21:00:34:80:0d:74:14:d2.
  [  266.823087] qla2xxx [:05:00.0]-5836:3: Async-logout complete - 
21:00:34:80:0d:74:14:d2 hdl=1c portid=02 iop0=0.
  [  266.823093] qla2xxx [:05:00.0]-f893:3: qlt_logo_completion_handler: 
se_sess  / sess a438982b from port 
21:00:34:80:0d:74:14:d2 loop_id 0x00 s_id 00:00:02 LOGO failed: 0x0
  [  266.928413] qla2xxx [:05:00.0]-f887:3: qlt_free_session_done: sess 
a438982b logout completed
  [  266.931754] qla2xxx [:05:00.0]-f89a:3: se_sess  / sess 
a438982b port 21:00:34:80:0d:74:14:d2 is gone, no own PLOGI pending 
(ref=-1)

  The snippet above shows that qla2xxx is trying to send NVMe PRLI
  instead of FCP PRLI to FCP target and link connection doesn't succeed.

  The same bug exists in linux-stable since 5.4.69. P2P worked until
  5.4.69 but issue_lip was broken and link was not recovered after
  issue_lip.

  We have triaged the issue and found a way to fix it by backporting and
  properly merging upstream patches and will send a series to linux-
  stable shortly. (https://www.spinics.net/lists/stable/msg458515.html)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-71-generic 5.4.0-71.79
  ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
  Uname: Linux 5.4.0-71-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-71-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: skip
  Date: Thu Apr 15 15:43:55 2021
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU