Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@lisas.de>
To: Andreas Mohr <andi@lisas.de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christian Gmeiner <christian.gmeiner@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: libata / IDE cs5536: 80c cable detect issue (and worse?)
Date: Thu, 18 Jul 2013 20:25:41 +0200	[thread overview]
Message-ID: <20130718182541.GA30707@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <20130718181355.GA31889@rhlx01.hs-esslingen.de>

Hi,

forgot to mention that I had already added a libata.force=40c boot
after my 80c config issue discovery
which did successfully cause the "limiting to UDMA/33 due to 40c foo" dmesg
yet where there's now initial but strong confirmation via reports
that the resulting UDMA/33 limit did NOT manage to fix corruption issues,
thus it's more strongly likely that the "bound to ill-suited pata_amd driver"
(due to incorrectly configuring speeds, or due to not configuring speeds
at all due to possibly BIOS not providing emulation of PCI register accesses
to Geode bus, which would be properly supported by pata_cs5536 OTOH)
thing is the actual reason and might fix it (fingers crossed).

Thanks,

Andreas Mohr

  reply	other threads:[~2013-07-18 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 18:13 libata / IDE cs5536: 80c cable detect issue (and worse?) Andreas Mohr
2013-07-18 18:25 ` Andreas Mohr [this message]
2013-07-19 10:40   ` Bartlomiej Zolnierkiewicz
2013-07-19 12:26     ` Andreas Mohr
2013-07-19 14:30       ` Bartlomiej Zolnierkiewicz
2013-07-19 16:45         ` Andreas Mohr
2013-08-06 15:47           ` Bartlomiej Zolnierkiewicz

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=20130718182541.GA30707@rhlx01.hs-esslingen.de \
    --to=andi@lisas.de \
    --cc=bzolnier@gmail.com \
    --cc=christian.gmeiner@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    /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