All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elad Lahav <elahav@uwaterloo.ca>
To: linux-ide@vger.kernel.org
Subject: Kernel 2.6.27: Problems with DVD drive/nVidia MCP51
Date: Fri, 31 Oct 2008 10:02:15 -0400	[thread overview]
Message-ID: <490B0FE7.1020107@uwaterloo.ca> (raw)

After upgrading from 2.6.26.5 to 2.6.27.4, my DVD drive started having problems during 
boot time. Here is the relevant part from dmesg:

ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATAPI: HL-DT-ST DVD+/-RW GSA-T11N, A103, max UDMA/33
ata2.00: applying bridge limits
ata2.00: Drive reports diagnostics failure. This may indicate a drive
ata2.00: fault or invalid emulation. Contact drive vendor for information.
ata2.00: configured for UDMA/33
scsi 0:0:0:0: Direct-Access     ATA      ST3250820AS      3.AD PQ: 0 ANSI: 5
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: cmd a0/00:00:00:24:00/00:00:00:00:00/a0 tag 0 pio 36 in
          cdb 12 00 00 00 24 00 00 00  00 00 00 00 00 00 00 00
          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.00: status: { DRDY }
ata2: hard resetting link
[continue ad inifitum....]

The drive is reported as "HL-DT-ST DVD+/-RW GSA-T11N, A103", connected to an nVidia MCP51 
controller. Googling around, I found similar complaints in the past for other nVidia 
controllers using the sata_nv driver (though I couldn't find anything about the MCP51). I 
tried compiling the version of sata_nv that comes with 2.6.26.5, but that did not solve my 
problems.

I can provide further details if necessary.

--Elad

             reply	other threads:[~2008-10-31 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 14:02 Elad Lahav [this message]
2008-11-11  8:56 ` Kernel 2.6.27: Problems with DVD drive/nVidia MCP51 Tejun Heo
2008-11-11 14:07   ` Elad Lahav

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=490B0FE7.1020107@uwaterloo.ca \
    --to=elahav@uwaterloo.ca \
    --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.