[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-19 Thread Mauricio Faria de Oliveira
Hi Daniel,

That's great news.

I had in mind to ask for testing w/ 5.3 HWE if 5.4 worked, 
glad you gone ahead and could confirm it works too.

I'll be looking at the logs to try to identify any patch
that's missing and/or broken.

cheers,
Mauricio

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-18 Thread Daniel Axtens
The 5.3.0 HWE kernel also works, which means we now have a good
workaround while we debug things.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-18 Thread Daniel Axtens
Hi Mauricio,

5.4.0-14 works for me, dmesg attached.

I'll see if an HWE kernel supplied in the bionic repositories also
works, maybe we can use that in the mean time so we don't fall any
further behind on kernel updates while we debug this.

Regards,
Daniel

** Attachment added: "dmesg-5.4.0-14-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329404/+files/dmesg-5.4.0-14-generic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-18 Thread Mauricio Faria de Oliveira
Oh, sadly -89 doesn't work either; ok.

Yup, bisecting to find the specific issue/commit would be nice, to get a
better pointer.

On the quick path front, if you still have the time for another test,
could you please try the 5.4 kernel on Focal?

It should install/boot fine on Bionic, done that myself recently --
something along the lines of:

$ echo 'deb http://archive.ubuntu.com/ubuntu focal main restricted' | sudo tee 
/etc/apt/sources.list.d/focal.list
$ sudo apt update
$ sudo apt install linux-{image,modules}-5.4.0-9-generic # check that only the 
kernel packages are installed / come from Focal.
$ sudo rm /etc/apt/sources.list.d/focal.list

cheers,
Mauricio

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-18 Thread Daniel Axtens
Ah, I was just about to tell you that I have just tried master-next at
a59858e18bc8996f8c96d307a33e504b079dc541 ! I think that is the same sha
that ended up being tagged as -89, so I think it provides us with the
same information.

Sadly -89 also doesn't seem to work; dmesg attached.

I don't know anything about the qla2xxx driver, so I was planning to
confirm that the problem was introduced by the set of qla2xxx changes
that went into -73 and then bisect them. But, if you have any insight or
specific knowledge that would suggest a better path, I'm very happy to
give that a go.

Regards,
Daniel

** Attachment added: "dmesg-89"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329273/+files/dmesg-89

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-18 Thread Mauricio Faria de Oliveira
Hi Daniel,

The build from master-next is no longer needed -- it's been just cut to
4.15.0-89 currently in bionic-proposed.

Can you give that a try instead?

It has all fixes previously in master-next, and nothing new remains in
qla2xxx.

$ git log --oneline Ubuntu-4.15.0-89.89..origin/master-next -- 
drivers/scsi/qla2xxx/
$ 

cheers,
Mauricio

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-17 Thread Daniel Axtens
Hi Mauricio,

Thanks for the prompt answer! After a lot of messing around to get a
remote console, I can finally test. It looks like -88 doesn't work. I'm
attaching a dmesg from -88 and -72. I will build and test master-next
next.

Regards,
Daniel

** Attachment added: "dmesg from -88"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329132/+files/dmesg-88

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-17 Thread Daniel Axtens
** Attachment added: "dmesg from -72"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5329133/+files/dmesg-72

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-14 Thread Mauricio Faria de Oliveira
Hi Daniel, hope you're doing well!

Thanks for reporting this regression. I worked a bit with qla2xxx back
in IBM LTC, so I can try to help.

There are indeed a few 'stable' fixes for qla2xxx between 4.15.0-72 and -73 
(none on -74).
Well, apparently not so stable. 
And none of their upstream commit IDs are marked in Fixes commits on mainline, 
sadly; so no immediate indicators of the culprit.

There are more fixes in Ubuntu-4.15.0-88.88 (yes) currently in bionic-proposed.
And a few more fixes in master-next (just in git, not yet released.)

So,
1) Could you please try the kernel packages from bionic-proposed first ?
2) And if doesn't help, build the packages from master-next ? (or I can give 
you test packages)

Hopefully either may help. Otherwise, we can check more recent kernel
versions.

Thanks,
Mauricio

$ git log --oneline Ubuntu-4.15.0-72.81..Ubuntu-4.15.0-73.82  -- 
drivers/scsi/qla2xxx/
8fe9110fefd8 scsi: qla2xxx: Fix port speed display on chip reset
0b693aca8824 scsi: qla2xxx: Fix deadlock between ATIO and HW lock
51313cd70fe2 scsi: qla2xxx: Terminate Plogi/PRLI if WWN is 0
18dd3502aa79 scsi: qla2xxx: Fix dropped srb resource.
4af79e867720 scsi: qla2xxx: Defer chip reset until target mode is enabled
c41bc5e5c6bb scsi: qla2xxx: Fix iIDMA error
c0579128d7b8 scsi: qla2xxx: stop timer in shutdown path
3bf89d9345a5 scsi: qla2xxx: Initialized mailbox to prevent driver load failure
725ec645a843 scsi: qla2xxx: fixup incorrect usage of host_byte
7616c2489f28 scsi: qla2xxx: fix a potential NULL pointer dereference

$ git log --oneline Ubuntu-4.15.0-73.82..Ubuntu-4.15.0-74.84  -- 
drivers/scsi/qla2xxx/
$

$ git log --oneline Ubuntu-4.15.0-73.82..Ubuntu-4.15.0-88.88-- 
drivers/scsi/qla2xxx/
1803d2ecfe61 scsi: qla2xxx: Send Notify ACK after N2N PLOGI
c531496eb731 scsi: qla2xxx: Fix PLOGI payload and ELS IOCB dump length
374f839d0f64 scsi: qla2xxx: Drop superfluous INIT_WORK of del_work
3e74574ced98 scsi: qla2xxx: Don't call qlt_async_event twice
8c30c08b2648 nvme_fc: add module to ops template to allow module references
1c20b1a30c12 scsi: qla2xxx: Change discovery state before PLOGI
175f007da89a scsi: qla2xxx: Fix message indicating vectors used by driver
1221bd3c290f scsi: qla2xxx: Always check the qla2x00_wait_for_hba_online() 
return value
87237677ef42 scsi: qla2xxx: Fix qla24xx_process_bidir_cmd()
1bc7062548ad scsi: qla2xxx: Fix session lookup in qlt_abort_work()
6f8b7559c514 scsi: qla2xxx: Fix DMA unmap leak
437b5663a092 scsi: qla2xxx: Fix driver unload hang
09cca2e026e4 scsi: qla2xxx: deadlock by configfs_depend_item

$ git log --oneline Ubuntu-4.15.0-88.88..origin/master-next-- 
drivers/scsi/qla2xxx/
c135532d2507 scsi: qla2xxx: Fix error handling in qlt_alloc_qfull_cmd()
5c3b3f0e5131 scsi: qla2xxx: Avoid that qlt_send_resp_ctio() corrupts memory
7455f405f8bd scsi: qla2xxx: Fix a format specifier
8bb67105d5cb scsi: qla2xxx: Unregister chrdev if module initialization fails
3d381f9bd4e8 scsi: qla2xxx: fix rports not being mark as lost in sync fabric 
scan
e02de738c644 scsi: qla2xxx: Fix qla2x00_request_irqs() for MSI


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863044] Re: qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

2020-02-12 Thread Daniel Axtens
** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+attachment/5327820/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863044

Title:
  qla2xxx no longer detects LUNs with 4.15.0-74+ on IBM BladeCenter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863044/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs