From: Andi Kleen <ak@suse.de>
To: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM
Date: Wed, 14 Nov 2007 13:17:35 +0100 [thread overview]
Message-ID: <200711141317.35746.ak@suse.de> (raw)
In-Reply-To: <198606.73895.qm@web52608.mail.re2.yahoo.com>
On Wednesday 14 November 2007 12:55, Srihari Vijayaraghavan wrote:
> [Sorry to reply to my own email thread]
>
> Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au> wrote:
> ...
>
> > No problems. Here's the log of unworking kernel with IOMMU turned on.
> > Basically it goes on reseting the SATA ports throwing many errors (none
> > are present in 2.6.23 or on 2.6.24-rc with mem=3500M) for many minutes at
> > which point I do a power reset :-(.
> >
> > Also the log of the working kernel with IOMMU but with mem=3500M is also
> > attached for the record. It's basically the same above kernel just with
> > the added parameter.
>
> Gentlemen,
>
> This changeset has introduced a regression in 2.6.24-rc, such that my
> machine boots no more:
Hmm, you got an AHCI controller that does not do 64bit DMA masks?
Or do you have CONFIG_IOMMU_DEBUG enabled?
Anyways, not being able to deal with merged SG lists must be some
driver or hardware bug. I would stick some printks into gart_map_sg()
and try to find out where the failing DMA is initiatiated and then
split it into multiple IO submissions at the caller level.
-Andi
next prev parent reply other threads:[~2007-11-14 12:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 11:55 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM Srihari Vijayaraghavan
2007-11-14 12:17 ` Andi Kleen [this message]
2007-11-14 16:43 ` Thomas Gleixner
2007-11-14 16:46 ` Andi Kleen
2007-11-19 22:47 ` Srihari Vijayaraghavan
2007-11-20 1:03 ` Tejun Heo
2007-11-20 15:34 ` Thomas Gleixner
2007-11-20 15:44 ` Andi Kleen
2007-11-20 18:29 ` Thomas Gleixner
2007-11-20 18:43 ` Andi Kleen
2007-11-20 16:36 ` 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM II Andi Kleen
2007-11-20 19:07 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2007-11-08 22:41 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM Srihari Vijayaraghavan
2007-11-09 4:00 ` Tejun Heo
2007-11-12 10:56 ` Srihari Vijayaraghavan
2007-11-13 0:06 ` Srihari Vijayaraghavan
2007-11-13 3:08 ` Tejun Heo
2007-11-13 11:17 ` Srihari Vijayaraghavan
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=200711141317.35746.ak@suse.de \
--to=ak@suse.de \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sriharivijayaraghavan@yahoo.com.au \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).