mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Markus Lidel <Markus.Lidel@shadowconnect.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Miquel van Smoorenburg <miquels@cistron.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Adaptec 2010S i2o + x86_64 doesn't work
Date: Fri, 15 Apr 2005 20:16:11 +0200	[thread overview]
Message-ID: <1113588972.6694.78.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <426003AB.3060904@shadowconnect.com>

On Fri, 2005-04-15 at 20:10 +0200, Markus Lidel wrote:
> Hello,
> 
> Alan Cox wrote:
> > On Gwe, 2005-04-15 at 17:15, Miquel van Smoorenburg wrote:
> >>However, I removed 2 GB from the box as Alan sugggested and now the box
> >>comes up just fine with a 64-bit 2.6.11.6 kernel! I've put the 4GB back,
> >>and booted with the kernel "mem=2048" command line option - that also
> >>works, the i2o_block driver sees the adaptec controller just fine.
> >>And I just booted it with "mem=3840M" and that works too.
> >>So the problem appears to be 4 GB memory in 64 bit mode, on this box.
> 
> OK, i never tried it with 4 GB so it really could be a problem...
> 
> > Or the driver is incorrectly handling 64/32bit DMA limit masks which
> > would be my first guess here, and would explain why it works on AMD
> > Athlon64 boxes.
> 
> Hmmm, i only set DMA_32BIT_MASK and don't do anything special on 64-bit 
> systems... Is there anything else to do for correct DMA mapping?


are you sure the HW isn't 31 bit by accident ? 


  reply	other threads:[~2005-04-15 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 16:03 Miquel van Smoorenburg
2005-04-13 17:54 ` Markus Lidel
2005-04-15 14:52 ` Alan Cox
2005-04-15 16:15   ` Miquel van Smoorenburg
2005-04-15 17:48     ` Alan Cox
2005-04-15 18:10       ` Markus Lidel
2005-04-15 18:16         ` Arjan van de Ven [this message]
2005-04-15 18:34           ` Markus Lidel
2005-04-15 20:43           ` Alan Cox

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=1113588972.6694.78.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=Markus.Lidel@shadowconnect.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    /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

all inboxes | Powered by JetHome®