All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Rune Torgersen <runet@innovsys.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Libata state machine error in 2.6.18.1
Date: Mon, 14 May 2007 12:38:55 -0400	[thread overview]
Message-ID: <4648909F.7020809@garzik.org> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B02E898EB@ismail.innsys.innovsys.com>

Rune Torgersen wrote:
> Hi
> We're running 2.6.18 on an inhouse devloped embeded board.
> CPU is a Freescale 8280, and we have a SIL3124 controller talking to a
> Hitachi 320GB (Hitachi HDT725032VLA360) disk.
> 
> Once in a while we get the following error while formatiing the drive:
> 
> ata2: illegal qc_active transition (00000002->00000008)
> ata2.00: exception Emask 0x2 SAct 0x2 SErr 0x0 action 0x2 frozen
> ata2.00: tag 1 cmd 0x61 Emask 0x2 stat 0x50 err 0x0 (HSM violation)
> ata2: soft resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
> ata2.00: revalidation failed (errno=-5)
> ata2: failed to recover some devices, retrying in 5 secs
> ata2: hard resetting port
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: configured for UDMA/100
> ata2: EH complete

What are the results from 2.6.22-rc1?

You're running an ancient kernel that has seen a great many bug fixes 
since 2.6.18.

	Jeff




      reply	other threads:[~2007-05-14 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 15:59 Libata state machine error in 2.6.18.1 Rune Torgersen
2007-05-14 16:38 ` Jeff Garzik [this message]

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=4648909F.7020809@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=runet@innovsys.com \
    /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.