All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Heflin <rheflin@atipa.com>
To: Emmanuel Fleury <emmanuel.fleury@labri.fr>
Cc: linux-ide@vger.kernel.org
Subject: Re: Issues with sata_nv and 2 disks under 2.6.16 and 2.6.17-rc2
Date: Wed, 26 Apr 2006 09:05:46 -0500	[thread overview]
Message-ID: <444F7E3A.5070109@atipa.com> (raw)
In-Reply-To: <444F7490.3030800@labri.fr>

Emmanuel Fleury wrote:
> Hi,
> 
> Roger Heflin wrote:
>>> ata1: command 0xc8 timeout, stat 0x50 host_stat 0x24
>>> ata1: status=0x50 { DriveReady SeekComplete }
>>> sda: Current: sense key: No Sense
>>>     Additional sense: No additional sense information
>>> Info fld=0x3481ff
>>> ata2: command 0xc8 timeout, stat 0x50 host_stat 0x24
>>> ata2: status=0x50 { DriveReady SeekComplete }
>>> sdb: Current: sense key: No Sense
>>>     Additional sense: No additional sense information
>>> Info fld=0x166ff
>>> ata1: command 0xc8 timeout, stat 0x50 host_stat 0x24
>>> ata1: status=0x50 { DriveReady SeekComplete }
>>> sda: Current: sense key: No Sense
>>>     Additional sense: No additional sense information
>>> Info fld=0x3482ff
>>> ata2: command 0xc8 timeout, stat 0x50 host_stat 0x24
>>> ata2: status=0x50 { DriveReady SeekComplete }
>>> sdb: Current: sense key: No Sense
>>>     Additional sense: No additional sense information
>>> Info fld=0x167ff
>>> ata1: command 0xca timeout, stat 0x50 host_stat 0x24
>>> ata1: status=0x50 { DriveReady SeekComplete }
> 
> Can you try to set the following config options as module:
> 
> Device Drivers  --->
>   SCSI device support  --->
>     SCSI low-level drivers  --->
>       AHCI SATA support
> 
> And
> 
> Device Drivers  --->
>   SCSI device support  --->
>     SCSI low-level drivers  --->
>       NVIDIA SATA support
>

Both are already build as modules, so the failure was with
them as modules.   I used the default type of config setup
from FC5 kernels which loves to build everything as
modules, since FC5 gets annoyed with things being build it.

                             Roger

  reply	other threads:[~2006-04-26 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 17:02 Issues with sata_nv and 2 disks under 2.6.16 and 2.6.17-rc2 Roger Heflin
2006-04-26 13:16 ` Roger Heflin
2006-04-26 13:24   ` Emmanuel Fleury
2006-04-26 14:05     ` Roger Heflin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-26 14:28 Fortier,Vincent [Montreal]
2006-04-26 14:28 ` Fortier,Vincent [Montreal]
2006-04-26 14:42 ` Roger Heflin
2006-04-26 14:46 Fortier,Vincent [Montreal]
2006-04-26 14:46 ` Fortier,Vincent [Montreal]
2006-04-26 14:52 ` Roger Heflin

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=444F7E3A.5070109@atipa.com \
    --to=rheflin@atipa.com \
    --cc=emmanuel.fleury@labri.fr \
    --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 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.