All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Christian <christiand59@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Date: Mon, 19 Mar 2007 08:09:24 -0400	[thread overview]
Message-ID: <45FE7D74.6090503@garzik.org> (raw)
In-Reply-To: <200703190808.00746.christiand59@web.de>

Christian wrote:
> On Monday 19 March 2007 03:48:14 you wrote:
>> Christian wrote:
>>> On Sunday 18 March 2007 06:43:09 you wrote:
>>>> Christian wrote:
>>>>>> This does indeed look like a drive side issue to me (the controller is
>>>>>> reporting CPBs with response flags 2 which as far as I can tell
>>>>>> indicates it's still waiting for the drive to complete the request).
>>>>> I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA
>>>>> support made it in the -mm kernel (maybe around 2.6.19-mm? or even
>>>>> earlyer). I'm seeing this problem excessively since I upgraded to
>>>>> 2.6.21-rc3-mm1. I think something got broken recently...
>>>> Can you post the result of "hdparm -I /dev/sdX"?
>>> Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT
>>>
>>> user@ubuntu:~$ sudo hdparm -I /dev/sda
>>>
>>> /dev/sda:
>>>
>>> ATA device, with non-removable media
>>>         Model Number:       SAMSUNG HD401LJ
>>>         Serial Number:      S0HVJ1FL900207
>>>         Firmware Revision:  ZZ100-15
>>> Standards:
>>>         Used: ATA/ATAPI-7 T13 1532D revision 4a
>>>         Supported: 7 6 5 4
>>> Configuration:
>>>         Logical         max     current
>>>         cylinders       16383   16383
>>>         heads           16      16
>>>         sectors/track   63      63
>>>         --
>>>         CHS current addressable sectors:   16514064
>>>         LBA    user addressable sectors:  268435455
>>>         LBA48  user addressable sectors:  781422768
>>>         device size with M = 1024*1024:      381554 MBytes
>>>         device size with M = 1000*1000:      400088 MBytes (400 GB)
>> That's a fairly recent drive.  Does the problem go away if you downgrade
>> the kernel?
> 
> Yes, for me the problem was introduced recently. I have moved around terabytes 
> (sic!) on my discs with older kernels and I never got errors.

I may have missed the answer to this before, but:  does the problem go 
away if you disable preempt?

	Jeff




  parent reply	other threads:[~2007-03-19 12:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.wBi/iM3CKSfrll7UnPHTbU0scEQ@ifi.uio.no>
2007-03-16 13:56 ` [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ Robert Hancock
2007-03-16 14:44   ` Christian
2007-03-18  5:43     ` Tejun Heo
2007-03-18 20:31       ` Christian
2007-03-19  2:48         ` Tejun Heo
2007-03-19  7:08           ` Christian
2007-03-19  7:39             ` Tejun Heo
2007-03-21 14:34               ` Christian
2007-03-21 16:35                 ` Tejun Heo
2007-03-19 12:09             ` Jeff Garzik [this message]
2007-03-20  9:41               ` Max Kellermann
2007-03-19 12:21         ` Pablo Sebastian Greco
2007-03-16 11:20 Max Kellermann
2007-03-16 14:34 ` Christian

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=45FE7D74.6090503@garzik.org \
    --to=jeff@garzik.org \
    --cc=christiand59@web.de \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.