From: matoro <matoro_mailinglist_kernel@matoro.tk>
To: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Sathya Prakash <sathya.prakash@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
PDL-MPT-FUSIONLINUX <MPT-FusionLinux.pdl@broadcom.com>
Subject: Re: [PATCH v3 0/5] Fix mpt3sas driver sparse warnings
Date: Tue, 02 Aug 2022 16:27:33 -0400 [thread overview]
Message-ID: <13f2f53e87ff7b653c46c3da19ea8115@matoro.tk> (raw)
In-Reply-To: <CAK=zhgosaNGejvNq9ANzhuHqwLSxfckfdhLAX_r2y=9DN=oAvA@mail.gmail.com>
Hi folks, sorry for the lateness, unfortunately this is in fact broken
on BE. I use mpt3sas on sparc and my drives fail to come up on 5.19,
bisected to this patchset. Reverting both of the endian-related
commits, b4efbec4c2a75b619fae4e8768be379e88c78687 and
7ab4d2441b952977556672c2fe3f4c2a698cbb37, allows it to boot. However,
after booting, I can't load any modules - everything errors with
"disagrees about version of symbol module_layout". I have completely
wiped out kernel sources, the module tree, and the kernel image,
rebuilding both from scratch with ONLY the revert patch applied, but I
still can't load any modules. Presumably it would work with
CONFIG_MODVERSIONS=n, but these CRC checks are there for a reason and I
can't tell if it has something to do with the revert or not.
$ modprobe --dump-modversions
/lib/modules/5.19.0-gentoo-sparc64/kernel/fs/openpromfs/openpromfs.ko |
grep "module_layout"
0xa6c23707 module_layout
$ grep "module_layout" /usr/src/linux/Module.symvers
0xa6c23707 module_layout vmlinux EXPORT_SYMBOL
If you need real hardware access and do not have any on hand, please
reach out and I can provide temporary access!
Here is the full error on vanilla 5.19:
mpt3sas version 42.100.00.00 loaded
mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem
(32650280 kB)
mpt2sas_cm0: _base_wait_for_doorbell_not_used: failed due to timeout
count(5000), doorbell_reg(18000000)!
mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to
4k
mpt2sas_cm0: MSI-X vectors supported: 1
no of cores: 64, max_msix_vectors: -1
mpt2sas_cm0: 0 1 1
mpt2sas_cm0: pci_alloc_irq_vectors failed (r=-22) !!!
mpt2sas_cm0: High IOPs queues : disabled
mpt2sas0: IO-APIC enabled: IRQ 4
mpt2sas_cm0: iomem(0x0000084100000000), mapped(0x(____ptrval____)),
size(16384)
mpt2sas_cm0: ioport(0x0000085100000000), size(256)
mpt2sas_cm0: doorbell is in use (line=6869)
mpt2sas_cm0: _base_get_ioc_facts: handshake failed (r=-14)
mpt2sas_cm0: failure at
drivers/scsi/mpt3sas/mpt3sas_scsih.c:12336/_scsih_probe()!
mpt2sas_cm1: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem
(32650280 kB)
mpt2sas_cm1: _base_wait_for_doorbell_not_used: failed due to timeout
count(5000), doorbell_reg(18000000)!
mpt2sas_cm1: CurrentHostPageSize is 0: Setting default host page size to
4k
mpt2sas_cm1: MSI-X vectors supported: 1
no of cores: 64, max_msix_vectors: -1
mpt2sas_cm1: 0 1 1
mpt2sas_cm1: pci_alloc_irq_vectors failed (r=-22) !!!
mpt2sas_cm1: High IOPs queues : disabled
mpt2sas1: IO-APIC enabled: IRQ 5
mpt2sas_cm1: iomem(0x0000084120000000), mapped(0x(____ptrval____)),
size(16384)
mpt2sas_cm1: ioport(0x0000085100002000), size(256)
mpt2sas_cm1: doorbell is in use (line=6869)
mpt2sas_cm1: _base_get_ioc_facts: handshake failed (r=-14)
mpt2sas_cm1: failure at
drivers/scsi/mpt3sas/mpt3sas_scsih.c:12336/_scsih_probe()!
-------- Original Message --------
Subject: Re: [PATCH v3 0/5] Fix mpt3sas driver sparse warnings
Date: 2022-03-09 01:35
From: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
On Wed, Mar 9, 2022 at 9:26 AM Martin K. Petersen
<martin.petersen@oracle.com> wrote:
>
>
> Sreekanth,
>
> > This series fix (remove) all sparse warnings generated when compiling
> > the mpt3sas driver. All warnings are related to __iomem access and
> > endianness.
>
> Please review this series and validate the patch 5 modification.
Martin,
This patch set looks good, but before acknowledging this patch set I
just wanted to do some basic testing on a big endian machine.
Currently I don't have a big endian machine, internally I am checking
to get access to big endian machines. Meanwhile if anyone does a basic
testing on any big endian machine then please let me know. I will add
the acknowledgement signature.
Thanks,
Sreekanth
>
> Thanks!
>
> --
> Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-08-02 20:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 23:48 [PATCH v3 0/5] Fix mpt3sas driver sparse warnings Damien Le Moal
2022-03-07 23:48 ` [PATCH v3 1/5] scsi: mpt3sas: fix _ctl_set_task_mid() TaskMID check Damien Le Moal
2022-03-07 23:48 ` [PATCH v3 2/5] scsi: mpt3sas: Fix writel() use Damien Le Moal
2022-03-07 23:48 ` [PATCH v3 3/5] scsi: mpt3sas: fix ioc->base_readl() use Damien Le Moal
2022-03-07 23:48 ` [PATCH v3 4/5] scsi: mpt3sas: fix event callback log_code value handling Damien Le Moal
2022-03-07 23:48 ` [PATCH v3 5/5] scsi: mpt3sas: fix adapter replyPostRegisterIndex declaration Damien Le Moal
2022-03-09 3:56 ` [PATCH v3 0/5] Fix mpt3sas driver sparse warnings Martin K. Petersen
2022-03-09 6:35 ` Sreekanth Reddy
2022-08-02 20:27 ` matoro [this message]
2022-08-02 23:36 ` Damien Le Moal
2022-08-11 19:05 ` matoro
2022-08-11 19:17 ` Damien Le Moal
2022-08-22 17:51 ` matoro
2022-08-22 17:53 ` Damien Le Moal
2022-09-15 15:55 ` matoro
2022-09-16 8:39 ` Damien Le Moal
2022-09-16 13:04 ` Damien Le Moal
2022-04-26 4:25 ` Damien Le Moal
2022-04-26 10:37 ` Martin K. Petersen
2022-04-26 10:44 ` Damien Le Moal
2022-05-03 0:51 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13f2f53e87ff7b653c46c3da19ea8115@matoro.tk \
--to=matoro_mailinglist_kernel@matoro.tk \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.