From: Michael Madore <mmadore@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.4.4 stability on Lions
Date: Wed, 23 May 2001 16:43:10 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005651@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005642@msgid-missing>
Turns out that my upgrade to C0 processors reset my SCSI controller to 32
bit addressing. I've set it back to 64 bit and now everything seems to be
working ok.
Well, almost everything. I still have the problem with the onboard e100
network adapter. This is the problem where transferring certain files via
nfs causes nfs to die. I don't know if there was ever a resolution to this.
On Tue, May 22, 2001 at 08:34:13PM -0500, Matt_Domsch@Dell.com wrote:
> > The solution to your problem is to
> > alter your SCSI host adapter settings to operate > 4GB. If
> > you can use the
> > SCSI FastUtil the setting to change is found under host
> > adapter settings.
>
> The Linux qla1280 v3.23 driver as distributed in the IA-64 patch *always*
> sets a 64-bit dma_mask if running on a 64-bit processor. The NVRAM bit
> isn't read as the switch anymore.
>
> #if BITS_PER_LONG > 32
> /* Enable 64bit addressing for OS/System combination supporting it */
> /* actual NVRAM bit is: nv->cntr_flags_1.enable_64bit_addressing */
> /* but we will ignore it and use BITS_PER_LONG macro to setup for */
> /* 64 or 32 bit access of host memory in all x86/ia-64/Alpha systems */
> ha->flags.enable_64bit_addressing = 1;
> #else
> ha->flags.enable_64bit_addressing = 0;
> #endif
>
> #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,3,18)
> if (ha->flags.enable_64bit_addressing) {
> printk("[[[ qla1x160: 64 Bit PCI Addressing Enabled ]]]\n");
>
> #if BITS_PER_LONG > 32
> /* Update our PCI device dma_mask for full 64 bit mask */
> //ha->pdev->dma_mask = (pci_dma_t) 0xffffffffffffffffull;
> ha->pdev->dma_mask = 0xffffffffffffffff;
>
> #endif
> }
> #endif
>
> Jes cleaned this up a bit with his patch:
>
> + pci_set_dma_mask(ha->pdev, (dma_addr_t)~0ULL);
>
>
> Thanks,
> Matt
>
>
> --
> Matt Domsch
> Sr. Software Engineer
> Dell Linux Solutions
> www.dell.com/linux
>
>
>
> > -----Original Message-----
> > From: Wiegrefe, Don J [mailto:don.j.wiegrefe@intel.com]
> > Sent: Tuesday, May 22, 2001 5:34 PM
> > To: 'Michael Madore'; Matt_Domsch@exchange.dell.com
> > Cc: linux-ia64@linuxia64.org
> > Subject: RE: [Linux-ia64] 2.4.4 stability on Lions
> >
> >
> > While it is true you should always use the latest BIOS that
> > matches your
> > processor stepping ( in this case 76 ). The solution to your
> > problem is to
> > alter your SCSI host adapter settings to operate > 4GB. If
> > you can use the
> > SCSI FastUtil the setting to change is found under host
> > adapter settings.
> > Hope this helps.
> >
> > Don Wiegrefe
> > Soft Sur/ Lion Hardware/BIOS Support
> >
> > -----Original Message-----
> > From: Michael Madore [mailto:mmadore@turbolinux.com]
> > Sent: Tuesday, May 22, 2001 2:58 PM
> > To: Matt_Domsch@Dell.com
> > Cc: linux-ia64@linuxia64.org
> > Subject: Re: [Linux-ia64] 2.4.4 stability on Lions
> >
> >
> > I just noticed that the machine locked up on me while sitting
> > at the EFI
> > shell prompt. I've downloaded BIOS 76 (latest available on
> > Quad) and I'll
> > see if that makes any difference.
> >
> > On Tue, May 22, 2001 at 04:06:30PM -0500, Matt_Domsch@Dell.com wrote:
> > > > Has anyone seem any instability with the 2.4.4 kernel +
> > > > David's patch on
> > > > Lions? I have been running it successfully on a 2P C0 Big
> > > > Sur with BIOS
> > > > 103. On a 4P C0 Lion with BIOS 73, however, I consistantly
> > > > get lockups
> > > > after a short time. Usually I get a totally black screen.
> > > > I'm going to try
> > > > 2.4.3 and see if I still see the same problem. 2.4.2 seem to
> > > > work fine.
> > >
> > > I had one lockup after about 18 hours of heavy stress
> > copy-and-compare and
> > > NIC traffic last night.
> > > 4P C0, Lion B2 board set, BIOS 80. Black screen, no magic
> > sysrq. I'm
> > > trying to reproduce it now.
> > >
> > > Under normal light loads I haven't seen any issues.
> > >
> > > Thanks,
> > > Matt
> > >
> > > --
> > > Matt Domsch
> > > Sr. Software Engineer
> > > Dell Linux Solutions
> > > www.dell.com/linux
> >
> > --
> > Mike Madore
> > Senior Software Engineer
> > TurboLinux, Inc.
> > (650)228-5203
> >
> > _______________________________________________
> > Linux-IA64 mailing list
> > Linux-IA64@linuxia64.org
> > http://lists.linuxia64.org/lists/listinfo/linux-ia64
> >
> >
> > _______________________________________________
> > Linux-IA64 mailing list
> > Linux-IA64@linuxia64.org
> > http://lists.linuxia64.org/lists/listinfo/linux-ia64
> >
--
Mike Madore
Senior Software Engineer
TurboLinux, Inc.
(650)228-5203
next prev parent reply other threads:[~2001-05-23 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 18:18 [Linux-ia64] 2.4.4 stability on Lions Michael Madore
2001-05-22 19:25 ` McCaffity, Ray
2001-05-22 21:06 ` Matt_Domsch
2001-05-22 21:57 ` Michael Madore
2001-05-22 22:33 ` Wiegrefe, Don J
2001-05-22 22:43 ` Michael Madore
2001-05-23 1:34 ` Matt_Domsch
2001-05-23 16:43 ` Michael Madore [this message]
2001-05-23 18:21 ` David Mosberger
2001-05-23 18:23 ` Michael Madore
2001-05-23 20:06 ` Mallick, Asit K
2001-05-23 20:53 ` Michael Madore
2001-05-23 21:54 ` Robboy, David G
2001-05-23 22:26 ` Michael Madore
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=marc-linux-ia64-105590693005651@msgid-missing \
--to=mmadore@turbolinux.com \
--cc=linux-ia64@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