linux-kernel - Re: Nvidia SATA - Seagate SATA Drives

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] [day] [month] [year] [list]

Date:	Wed, 10 Oct 2007 08:50:28 -0700
From:	Jim Gifford <maillist@...55.com>
To:	Robert Hancock <hancockr@...w.ca>
CC:	Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Nvidia SATA - Seagate SATA Drives

Robert Hancock wrote:
> Jim Gifford wrote:
>> Robert Hancock wrote:
>>> Jim Gifford wrote:
>>>> Here's the situation. I have a MSI KN8Neo-f motherboard with a 
>>>> Seagate Barracuda 250 GB SATA drive. I have replaced this drive 
>>>> three times in the last two weeks due to it failing. Now the only 
>>>> thing in common is the use of a 2.6.22.9 kernel I built from 
>>>> scratch, before that I was using 2.6.19 kernel but working on doing 
>>>> some upgrades for the CLFS project and tried a 2.6.22.9.  I will 
>>>> explain the situation and including the links I used for fix the 
>>>> issues.
>>>>
>>>> It boots up and instantly has a problem detecting so I have to add 
>>>> irqpoll to my bootup line. {Reference 
>>>> http://my.opera.com/snowburn/blog/index.dml/tag/failed%20to%20set%20xfermode} 
>>>> Then I get the adma issue, so I add sata_nv.adma=0 to my bootup 
>>>> line.{Reference 
>>>> http://www.ussg.iu.edu/hypermail/linux/kernel/0706.1/1424.html}
>>>>
>>>> Now after a few times of booting the drive completely fails. So is 
>>>> the nv_sata drive the cause?? Based on what I have done yes, and 
>>>> the reason I can say that is because I took another one of those 
>>>> drives and the same computer loaded Windows(forgive me for using 
>>>> this word!!!) on it and it worked perfectly.
>>>
>>> You'll have to be more specific about "completely fails".. Also, it 
>>> would be useful to get the dmesg output from dmesg directly and not 
>>> from syslog, as the entries posted under the second link you gave 
>>> were missing some critical information (it seems that syslog can do 
>>> this in some cases..) In particular the line showing what command 
>>> failed would be useful.
>> It never gets into the system at all, just locks up. The hard drive 
>> starts clicking and eventually doesn't get recognized by BIOS.
>
> That doesn't sound like a kernel problem if it's not even recognized 
> by the BIOS, there's nothing the kernel should be able to do that 
> could cause that. Sounds more like a hardware issue. If the drive has 
> been replaced before then it could be a power supply or temperature 
> problem?
I thought that also, just tried a new power supply, same problem. I can 
recreate this problem within minutes with a new drive. Got 2 more drives 
left in this batch. Temperature is in the low range of the specs.
-
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/