From: Jens Axboe <jens.axboe@oracle.com>
To: Marco Gatti <marco@pianoinflames.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Robert Hancock <hancockr@shaw.ca>,
Andrew Morton <akpm@linux-foundation.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Greg KH <greg@kroah.com>, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@elte.hu>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Bug: get EXT3-fs error Allocating block in system zone
Date: Sun, 9 Dec 2007 21:04:40 +0100 [thread overview]
Message-ID: <20071209200440.GC13382@kernel.dk> (raw)
In-Reply-To: <475C48EE.8020701@pianoinflames.de>
On Sun, Dec 09 2007, Marco Gatti wrote:
> Jens Axboe schrieb:
> >
> >Was just thinking that, this should do the trick. If this works, then we
> >can look at whether this is a hardware or iommu or block bouncing
> >(unlikely, would affect more people) bug.
> >
> >diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
> >index 4688dbf..cad3cbc 100644
> >--- a/drivers/ata/ahci.c
> >+++ b/drivers/ata/ahci.c
> >@@ -623,6 +623,9 @@ static void ahci_save_initial_config(struct pci_dev
> >*pdev,
> > hpriv->saved_cap = cap = readl(mmio + HOST_CAP);
> > hpriv->saved_port_map = port_map = readl(mmio + HOST_PORTS_IMPL);
> >
> >+ hpriv->saved_cap &= ~HOST_CAP_64;
> >+ cap &= ~HOST_CAP_64;
> >+
> > /* some chips have errata preventing 64bit use */
> > if ((cap & HOST_CAP_64) && (hpriv->flags & AHCI_HFLAG_32BIT_ONLY)) {
> > dev_printk(KERN_INFO, &pdev->dev,
> >
>
> Hello Jens,
> Thanks for help. I just applied the patch. Unfortunately it doesn't work.
Can you try and additionally boot with iommu=off as a boot parameter?
--
Jens Axboe
next prev parent reply other threads:[~2007-12-09 20:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Fg53DJSEh/kZhf/uRCv9FYZsaSQ@ifi.uio.no>
[not found] ` <fa.nPzIjJ2SchPb1LOa/dRWb/WyEZU@ifi.uio.no>
[not found] ` <fa.LkmHGN+Fx6H930bfeCDU6pGdBKM@ifi.uio.no>
[not found] ` <fa.oSqMiIX7WubypXrhZGaRKU5wNGU@ifi.uio.no>
[not found] ` <fa.0pc9/nNmTq+eWIU9rADRn0xYGdI@ifi.uio.no>
[not found] ` <fa.hqM73i24f6G31R5F3sKL8+3H8Ww@ifi.uio.no>
[not found] ` <475C2C02.70001@shaw.ca>
2007-12-09 18:59 ` Bug: get EXT3-fs error Allocating block in system zone Linus Torvalds
2007-12-09 19:09 ` Jens Axboe
2007-12-09 19:58 ` Marco Gatti
2007-12-09 20:04 ` Jens Axboe [this message]
[not found] ` <475C536B.5070409@pianoinflames.de>
2007-12-09 21:01 ` Jens Axboe
2007-12-10 18:01 ` Marco Gatti
2007-12-10 18:08 ` Jens Axboe
2007-12-10 18:11 ` Linus Torvalds
2007-12-10 23:59 ` Robert Hancock
2008-01-31 18:46 ` Marco Gatti
2007-12-18 8:36 ` Marco Gatti
2007-12-10 16:38 ` Mark Lord
2007-12-10 17:47 ` Marco Gatti
2007-12-19 21:25 ` Marco Gatti
2007-12-19 21:27 ` Alan Cox
[not found] <4755BEA1.4090604@pianoinflames.de>
[not found] ` <20071206162500.1f76a234.akpm@linux-foundation.org>
[not found] ` <alpine.LFD.0.9999.0712061631510.13796@woody.linux-foundation.org>
[not found] ` <475B0AD7.10500@pianoinflames.de>
[not found] ` <alpine.LFD.0.9999.0712081644560.12046@woody.linux-foundation.org>
[not found] ` <475C1F06.4080508@pianoinflames.de>
2007-12-09 18:56 ` Linus Torvalds
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=20071209200440.GC13382@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=marco@pianoinflames.de \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).