All of lore.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Thierry Vignaud <tvignaud@mandriva.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: libata PATA status for VIA 8237
Date: Wed, 24 Oct 2007 16:33:40 +0200	[thread overview]
Message-ID: <20071024143340.GA8895@DervishD> (raw)
In-Reply-To: <m2k5pche63.fsf@vador.mandriva.com>

    Hi Thierry :)

 * Thierry Vignaud <tvignaud@mandriva.com> dixit:
> DervishD <lkml@dervishd.net> writes:
> > I'm thinking about switching fully to libata in the near future
> > (currently I'm using CONFIG_IDE for all my PATA drives, both hard disks
> > and DVD recorder), and I was wondering if PATA support for VIA8237 was
> > full or not. For what I've googled, it seems that it is usable both for
> > PATA and for SATA, but I want to be sure.
> > 
> > If I'm asking here is because I have SATA support for my VIA chipset
> > enabled in the kernel (CONFIG_SATA_VIA), but I'm getting these messages:
> > 
> >     sata_via 0000:00:0c.0: version 2.0
> >     sata_via 0000:00:0c.0: routed to hard irq line 10
> >     ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE0A bmdma 0xFA00 irq 10
> >     ata2: SATA max UDMA/133 cmd 0xFD00 ctl 0xFD0A bmdma 0xFA08 irq 10
> >     scsi0 : sata_via
> >     ata1: SATA link down (SStatus 0 SControl 310)
> > >>  ATA: abnormal status 0x7F on port 0xFE07
> >     scsi1 : sata_via
> >     ata2: SATA link down (SStatus 0 SControl 310)
> > >>  ATA: abnormal status 0x7F on port 0xFD07
> >     sata_via 0000:00:0f.0: routed to hard irq line 11
> >     ata3: SATA max UDMA/133 cmd 0xF900 ctl 0xF802 bmdma 0xF500 irq 11
> >     ata4: SATA max UDMA/133 cmd 0xF700 ctl 0xF602 bmdma 0xF508 irq 11
> >     scsi2 : sata_via
> >     ata3: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
> > >>  ATA: abnormal status 0x7F on port 0xF907
> >     scsi3 : sata_via
> >     ata4: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
> > >>  ATA: abnormal status 0x7F on port 0xF707
> 
> I saw those too from times to times on boot with a VIA VT6421 with no
> consequences.
> So I would say they're non important (but who know for real until you
> test with real disk attached?)

I think I can manage to get a SATA disk to make tests, but the problem
is that I won't be able to make destructive (destroying the data, I
mean, not the hardware XD) tests on it :((

Merci :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
We are waiting for 13 Feb 2009 23:31:30 +0000 ...

      reply	other threads:[~2007-10-24 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  9:56 libata PATA status for VIA 8237 DervishD
2007-10-24 12:48 ` Thierry Vignaud
2007-10-24 14:33   ` DervishD [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=20071024143340.GA8895@DervishD \
    --to=lkml@dervishd.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tvignaud@mandriva.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.