lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46EAD526.1040601@pvv.org>
Date:	Fri, 14 Sep 2007 20:38:30 +0200
From:	Jon Ivar Rykkelid <jonry@....org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Tejun Heo <htejun@...il.com>, Prakash Punnoor <prakash@...noor.de>,
	linux-kernel@...r.kernel.org, Robert Hancock <hancockr@...w.ca>
Subject: Re: sata_nv issues with MCP51 SATA controller

Jeff Garzik wrote:
> Jon Ivar Rykkelid wrote:
>
>> I'm going to test another (identical) motherboard this evening to 
>> establish whether it could be a HW-issue.
>
> Not just motherboard.  It is more likely to be a cable, drive or PSU 
> problem.

>> It is NOT the PSU, nor is it cables, as all the drives work well 
>> using the same cables + PSU (in the same box) if I connect them to my 
>> other two controllers (in that same box).
>
>
> It's sometimes the combination that matters most.  You cannot really 
> make that determination yet.
>

Whatever.
(Though I must confess, that in spite of my Master degree in Electrical 
Engineering and extensive HW experience, I can not for the life of me 
understand how you can find it more likely to be cables (that work fine 
with other controllers), disks (that also work fine with other 
controllers) or the power-supply (that also works fine with exactly the 
same things connected to it) rather than the motherboard's 
SATA-controller (that is the item that actually is reported to fail in 
the first place). - Sure, I'm well aware that sometimes the combination 
of HW matters, but to my experience we're normally not talking about 
"dumb" stuff like cables and PSU if that is the issue.)

Anyway, I have just changed to the other (identical) motherboard, and 
things are running just fine at the moment...
I'll let you know if they start acting up (as they did before). If not I 
guess the fault was with the motherboard and not the driver - Guess 
we'll know pretty soon...

Thanks for all your effort, gents, let's hope it all works now!

BR
Jon Ivar

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ