public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Magnus Lindholm <linmag7@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: qla1280 driver for qlogic-1040 on alpha
Date: Fri, 25 Oct 2024 16:00:45 -0400	[thread overview]
Message-ID: <yq15xpgdl6j.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CA+=Fv5QXiwWd+v9vHo89X_H94+P5OsT_0MEs_8dRAYJawWpy1w@mail.gmail.com> (Magnus Lindholm's message of "Sat, 19 Oct 2024 19:37:08 +0200")


Hi Magnus!

> I've been running linux on alpha (alphaserver es40) for a while, using
> a qlogic-1040 scsi controller. A few weeks ago I added more RAM to the
> es40, but as soon as I got above 2GB RAM I started seeing file system
> corruptions on the drive attached to the qlogic controller.

The qla1280 driver has been used extensively on 64-bit platforms.

Is your isp1040 original to the ES40? My Alphas used 53c8xx series
controllers if I remember correctly. And with the ES40 being fairly
recent (21264), I would have thought it would have used a slightly more
modern controller than a 1040.

> The nvram flag "enable_64bit_addressing" on the qlogic board is not
> checked nor set by the driver.

That would be a good place to start. Maybe if you could dump the NVRAM
contents and validate if that is set by the 1040 firmware? I'm afraid I
don't have a databook. But the 1040 was current right around the time
the industry transitioned from 32 to 64-bit so it could very well be
broken.

If you can establish whether that flag is unset on your controller,
we could use that as a heuristic for configuring DMA.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2024-10-25 20:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 17:37 qla1280 driver for qlogic-1040 on alpha Magnus Lindholm
2024-10-25 20:00 ` Martin K. Petersen [this message]
2024-10-25 20:48   ` Magnus Lindholm
2024-10-27 23:05     ` Magnus Lindholm
2024-10-29  2:18       ` Martin K. Petersen
2024-10-29  6:51         ` Magnus Lindholm
2024-10-30  1:02         ` Maciej W. Rozycki
2024-10-30  7:52           ` Magnus Lindholm
2024-10-30  9:25             ` Thomas Bogendoerfer
2024-10-30 11:50               ` Magnus Lindholm
2024-10-31  7:37                 ` Maciej W. Rozycki
2024-10-31 10:35                   ` Magnus Lindholm
2024-10-31 17:30                     ` Maciej W. Rozycki
2024-10-31 22:19                       ` Magnus Lindholm
2024-11-01  2:36                         ` Maciej W. Rozycki
2024-11-04  7:41                       ` Christoph Hellwig
2024-11-04 20:49                         ` Magnus Lindholm
2024-11-04 21:52                           ` Maciej W. Rozycki
2024-11-05  1:40                             ` Martin K. Petersen
2024-11-05  8:34                               ` Thomas Bogendoerfer
2024-11-05 11:17                                 ` Magnus Lindholm
2024-11-05 18:16                                 ` Maciej W. Rozycki
2024-11-05 19:24                                   ` Magnus Lindholm
2024-11-12 13:52                                     ` Thomas Bogendoerfer
2024-11-15 23:39                                       ` Magnus Lindholm
2024-11-25 19:55                                         ` Maciej W. Rozycki
2024-11-26 21:33                                           ` Magnus Lindholm
2025-01-27 16:30                                             ` Magnus Lindholm
2025-04-04 21:35                                               ` Magnus Lindholm
2024-11-05 19:56                                   ` Martin K. Petersen
2024-11-05 21:06                                     ` Magnus Lindholm
2024-11-05 21:33                                     ` Thomas Bogendoerfer
2024-11-09 18:28                                       ` Magnus Lindholm
2024-11-10 15:59                                         ` Maciej W. Rozycki
2024-11-10 17:41                                           ` Magnus Lindholm
2024-11-04 21:54                         ` Maciej W. Rozycki

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=yq15xpgdl6j.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=linmag7@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox