From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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:10:51 +0200 [thread overview]
Message-ID: <426003AB.3060904@shadowconnect.com> (raw)
In-Reply-To: <1113587286.11114.30.camel@localhost.localdomain>
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?
Best regards,
Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)
Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany
Phone: +49 82 82/99 51-0
Fax: +49 82 82/99 51-11
E-Mail: Markus.Lidel@shadowconnect.com
URL: http://www.shadowconnect.com
next prev parent reply other threads:[~2005-04-15 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 16:03 Adaptec 2010S i2o + x86_64 doesn't work 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 [this message]
2005-04-15 18:16 ` Arjan van de Ven
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=426003AB.3060904@shadowconnect.com \
--to=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 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.