linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cengiz Günay" <cgunay@emory.edu>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Tejun Heo <tj@kernel.org>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: sata_nv times out for BD-ROM iHOS104-08
Date: Fri, 22 Jan 2010 09:11:18 -0500	[thread overview]
Message-ID: <d2d378041001220611ieb9d715of8d727f8f93ca9f@mail.gmail.com> (raw)
In-Reply-To: <51f3faa71001191859l3c323a8ev6b7c0cced2c59e92@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]

Hello, Tejun & Robert,

On Tue, Jan 19, 2010 at 9:59 PM, Robert Hancock <hancockrwd@gmail.com> wrote:
>>> 2009/12/24 Tejun Heo <tj@kernel.org>:
>> Hmm.... it worked?  Does kernel parameter sata_nv.adma_enabled=0 make
>> any difference?  Can you please attach boot log with the kernel
>> parameter specified?
>
> Think you meant maybe sata_nv.swncq=0 instead - this is an MCP51
> controller so it doesn't support ADMA. I don't imagine SWNCQ would
> make any difference with an ATAPI device, but wouldn't hurt to try.

Thanks for following this up. I tried both of your suggested kernel
parameters (attached). Neither solved my problem, but also it looks
like I couldn't turn off the SWNCQ mode. Even though I set it to zero,
sata_nv still shows that it uses it. Although the order of my devices
changed, so I assume it did something.

I hope this helps shed some light! I will also try the kernel patch --
not sure if that is suited for the problem I'm having?

-Cengiz



-- 
Cengiz Gunay
--
Postdoctoral Fellow
Prinz Lab, Dept. of Biology, Emory University
1510 Clifton Rd., Room 2172, Atlanta, GA 30322, U.S.A.
cgunay@emory.edu  cengique@users.sf.net         cengique@yahoo.com
Lab: +1-404-727-9381    Home/Cell: +1-678-559-8694
http://userwww.service.emory.edu/~cgunay
ICQ# 21104923, cengique@{jabber.org,Skype}
--

[-- Attachment #2: dmesg-sata_nv-adma_disabled.log --]
[-- Type: text/x-log, Size: 4224 bytes --]

 BIOS-e820: 000000007fef3000 - 000000007ff00000 (ACPI data)
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32 root=/dev/mapper/nvidia_ceebaiib1 ro single sata_nv.adma_enabled=0
Memory: 2052264k/2096064k available (2319k kernel code, 42132k reserved, 912k data, 404k init, 1186760k highmem)
      .data : 0xc1243e41 - 0xc1328128   ( 912 kB)
libata version 3.00 loaded.
sata_nv 0000:00:0e.0: version 3.5
sata_nv 0000:00:0e.0: PCI INT A -> Link[APSI] -> GSI 21 (level, low) -> IRQ 21
sata_nv 0000:00:0e.0: Using SWNCQ mode
sata_nv 0000:00:0e.0: setting latency timer to 64
scsi0 : sata_nv
scsi1 : sata_nv
ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xd400 irq 21
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xd408 irq 21
sata_nv 0000:00:0f.0: PCI INT A -> Link[APSJ] -> GSI 20 (level, low) -> IRQ 20
sata_nv 0000:00:0f.0: Using SWNCQ mode
sata_nv 0000:00:0f.0: setting latency timer to 64
scsi2 : sata_nv
scsi3 : sata_nv
ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xe800 irq 20
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xe808 irq 20
ata3: SATA link down (SStatus 0 SControl 300)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7
ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-7: ST3250620AS, 3.AAC, max UDMA/133
ata2.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATAPI: ATAPI   iHOS104, WL08, max UDMA/100
ata4.00: configured for UDMA/100
ata4.00: qc timeout (cmd 0xa0)
ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/100
ata4.00: qc timeout (cmd 0xa0)
ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
ata4: limiting SATA link speed to 1.5 Gbps
ata4.00: limiting speed to UDMA/100:PIO3
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/100
ata4.00: qc timeout (cmd 0xa0)
ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
ata4.00: disabled
ata4: hard resetting link
ata4: nv: skipping hardreset on occupied port
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4: EH complete
sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
PM: Adding info for No Bus:sda
 sda:
sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
PM: Adding info for No Bus:sdb
 sdb:
PM: Adding info for No Bus:sdc
PM: Adding info for No Bus:sdd
sd 5:0:0:0: [sdg] 3981312 512-byte logical blocks: (2.03 GB/1.89 GiB)
PM: Adding info for No Bus:sde
PM: Adding info for No Bus:sdf
sd 5:0:0:0: [sdg] Write Protect is off
sd 5:0:0:0: [sdg] Mode Sense: 43 00 00 00
sd 5:0:0:0: [sdg] Assuming drive cache: write through
PM: Adding info for No Bus:sdg
sd 4:0:0:0: [sdc] Attached SCSI removable disk
sd 4:0:0:1: [sdd] Attached SCSI removable disk
sd 4:0:0:2: [sde] Attached SCSI removable disk
sd 4:0:0:3: [sdf] Attached SCSI removable disk
sd 5:0:0:0: [sdg] Assuming drive cache: write through
 sdg: sdg1
PM: Adding info for No Bus:sdg1
sd 5:0:0:0: [sdg] Assuming drive cache: write through
sd 5:0:0:0: [sdg] Attached SCSI removable disk
 sda1 sda2 sda3 < unknown partition table
sd 1:0:0:0: [sdb] Attached SCSI disk
PM: Adding info for No Bus:sda1
PM: Adding info for No Bus:sda2
PM: Adding info for No Bus:sda3
sd 0:0:0:0: [sda] Attached SCSI disk
EXT3-fs: mounted filesystem with writeback data mode.
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { AbortedCommand }
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { AbortedCommand }
EXT3-fs: mounted filesystem with writeback data mode.

[-- Attachment #3: dmesg-sata_nv-swncq-disabled.log --]
[-- Type: text/x-log, Size: 4193 bytes --]

 BIOS-e820: 000000007fef3000 - 000000007ff00000 (ACPI data)
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32 root=/dev/mapper/nvidia_ceebaiib1 ro single sata_nv.swncq=0
Memory: 2052264k/2096064k available (2319k kernel code, 42132k reserved, 912k data, 404k init, 1186760k highmem)
      .data : 0xc1243e41 - 0xc1328128   ( 912 kB)
libata version 3.00 loaded.
sata_nv 0000:00:0e.0: version 3.5
sata_nv 0000:00:0e.0: PCI INT A -> Link[APSI] -> GSI 21 (level, low) -> IRQ 21
sata_nv 0000:00:0e.0: Using SWNCQ mode
sata_nv 0000:00:0e.0: setting latency timer to 64
scsi1 : sata_nv
scsi2 : sata_nv
ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xd400 irq 21
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xd408 irq 21
sata_nv 0000:00:0f.0: PCI INT A -> Link[APSJ] -> GSI 20 (level, low) -> IRQ 20
sata_nv 0000:00:0f.0: Using SWNCQ mode
sata_nv 0000:00:0f.0: setting latency timer to 64
scsi3 : sata_nv
scsi4 : sata_nv
ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xe800 irq 20
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xe808 irq 20
ata3: SATA link down (SStatus 0 SControl 300)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-7: SAMSUNG SP2504C, VT100-41, max UDMA7
ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-7: ST3250620AS, 3.AAC, max UDMA/133
ata2.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATAPI: ATAPI   iHOS104, WL08, max UDMA/100
ata4.00: configured for UDMA/100
sd 1:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
PM: Adding info for No Bus:sda
 sda:
sd 2:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
PM: Adding info for No Bus:sdb
 sdb:
PM: Adding info for No Bus:sdc
PM: Adding info for No Bus:sdd
 sda1 sda2 sda3 <
PM: Adding info for No Bus:sde
PM: Adding info for No Bus:sdf
sd 0:0:0:0: [sdc] Attached SCSI removable disk
sd 0:0:0:1: [sdd] Attached SCSI removable disk
sd 0:0:0:2: [sde] Attached SCSI removable disk
sd 0:0:0:3: [sdf] Attached SCSI removable disk
PM: Adding info for No Bus:sda1
PM: Adding info for No Bus:sda2
PM: Adding info for No Bus:sda3
sd 1:0:0:0: [sda] Attached SCSI disk
sd 2:0:0:0: [sdb] Attached SCSI disk
ata4.00: qc timeout (cmd 0xa0)
ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/100
sd 5:0:0:0: [sdg] 3981312 512-byte logical blocks: (2.03 GB/1.89 GiB)
sd 5:0:0:0: [sdg] Write Protect is off
sd 5:0:0:0: [sdg] Mode Sense: 43 00 00 00
sd 5:0:0:0: [sdg] Assuming drive cache: write through
PM: Adding info for No Bus:sdg
sd 5:0:0:0: [sdg] Assuming drive cache: write through
 sdg: sdg1
PM: Adding info for No Bus:sdg1
sd 5:0:0:0: [sdg] Assuming drive cache: write through
sd 5:0:0:0: [sdg] Attached SCSI removable disk
ata4.00: qc timeout (cmd 0xa0)
ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
ata4: limiting SATA link speed to 1.5 Gbps
ata4.00: limiting speed to UDMA/100:PIO3
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/100
ata4.00: qc timeout (cmd 0xa0)
ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
ata4.00: disabled
ata4: hard resetting link
ata4: nv: skipping hardreset on occupied port
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4: EH complete
EXT3-fs: mounted filesystem with writeback data mode.
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { AbortedCommand }
hda: task_no_data_intr: status=0x41 { DriveReady Error }
hda: task_no_data_intr: error=0x04 { AbortedCommand }
EXT3-fs: mounted filesystem with writeback data mode.

  reply	other threads:[~2010-01-22 14:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 16:07 sata_nv times out for BD-ROM iHOS104-08 Cengiz Gunay
2009-12-23  7:38 ` Tejun Heo
     [not found]   ` <d2d378040912232302u4b550dap687fcadced237935@mail.gmail.com>
2009-12-24  7:25     ` Tejun Heo
2010-01-16 21:34       ` Cengiz Günay
2010-01-17 15:28         ` Ozan Çağlayan
2010-01-19  9:05           ` Tejun Heo
2010-01-19  9:34             ` Ozan Çağlayan
2010-01-20  2:13         ` Tejun Heo
2010-01-20  2:59           ` Robert Hancock
2010-01-22 14:11             ` Cengiz Günay [this message]
2010-01-23  3:45               ` Tejun Heo
2010-01-23 21:39                 ` Cengiz Günay
     [not found]                   ` <4B67A149.10406@kernel.org>
2010-02-17 16:14                     ` Cengiz Günay
2010-02-18  1:50                       ` Tejun Heo
2010-02-20 19:11                         ` Cengiz Günay
2010-02-21  1:01                           ` Tejun Heo
2010-02-21 21:28                             ` Cengiz Günay
2010-02-23  2:38                               ` Tejun Heo
2010-02-28 17:24                                 ` Cengiz Günay
2010-03-02 11:48                                   ` Tejun Heo
2010-03-08 19:17                                     ` Cengiz Günay
2010-03-08 23:46                                       ` Robert Hancock
2010-03-09  1:21                                       ` Tejun Heo
2010-03-09  5:18                                         ` Cengiz Günay
2010-05-25 19:34                                           ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2010-01-17  4:54 Gregory Moyer
2010-01-21  3:15 Gregory Moyer
2010-06-03 17:40 Gregory Moyer

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=d2d378041001220611ieb9d715of8d727f8f93ca9f@mail.gmail.com \
    --to=cgunay@emory.edu \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).