linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Hasselmann <hhasselm@web.de>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, Shane.Huang@amd.com
Subject: Re: Gigabyte GA-MA69VM-S2 can't do 64bit DMA
Date: Wed, 16 Sep 2009 11:19:46 +0200	[thread overview]
Message-ID: <4AB0ADB2.8090009@web.de> (raw)
In-Reply-To: <4AAFE66D.8050807@gmail.com>

Tejun Heo schrieb:
> Holger Hasselmann wrote:
>   
>> Hello Tejun,
>>
>> I want let you know, that the following laptop would need to be included
>> in the list of the 32bit DMA boards.
>>
>> First I have used the snapshot 2.6.31-git and was not able to boot until
>> I reversed the patch 58a09b38cfcd700b796ea07ae3d2e0efbb28b561.
>>
>> I have tried it with the snapshot 2.6.31-git2 and was not able to boot.
>>
>> I have checked the latest bios (1.10c) for this laptop and it did not
>> worked.
>>
>> I will attache the dmidecoder output (don't know if this helps).
>>     
>
> Can you please verify the attached patch fixes the problem?  This should
> apply cleanly to 2.6.31.
>
> Thanks.
>
>   
I have tried the attached patch on a clean 2.6.31 source and it is working.

dmesg is showing the following:

libata version 3.00 loaded.
ahci 0000:00:12.0: version 3.0
ahci 0000:00:12.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
ahci 0000:00:12.0: ASUS M2A-VM: BIOS too old, forcing 32bit DMA, update BIOS
ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pmp pio slum part

Will try it later on the latest git, I think the dmesg should identify 
the Board correct then and.

Thanks,
Holger


  reply	other threads:[~2009-09-16  9:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 17:50 Gigabyte GA-MA69VM-S2 can't do 64bit DMA Holger Hasselmann
2009-09-15 19:09 ` Tejun Heo
2009-09-16  9:19   ` Holger Hasselmann [this message]
2009-09-16 10:49     ` Tejun Heo
2009-09-17 22:12       ` Holger Hasselmann
2009-09-18  0:43         ` Tejun Heo
2009-09-18  1:17           ` Huang, Shane
2009-09-18  8:09             ` Tejun Heo

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=4AB0ADB2.8090009@web.de \
    --to=hhasselm@web.de \
    --cc=Shane.Huang@amd.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).