LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: lepalom@wol.es
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Sata_via problems in a Vintage2-AE1
Date: Fri, 09 Feb 2007 04:46:39 -0500	[thread overview]
Message-ID: <45CC42FF.5030507@gmail.com> (raw)
In-Reply-To: <200702090010.06897.lepalom@wol.es>

Leopold Palomo Avellaneda wrote:
> Dear people,
> 
> I have a barebone Asus Vintage2-AE1 [1]. This box has a mobo Asus A8V-MQ. The 
> board has:
> - the Socket 939 for AMD Athlon 64FX/Athlon 64.
> - North Bridge: VIA K8M800  
> - South Bridge: VIA VT8251
> - VIA Graphics Integrated
> - IDE 2 x UltraDMA 133
> - 4 x Serial ATA
> ...
> 
> I'm using the bios version 0206. The 0210 doesn't show me the vga card, so I 
> don't have graphics mode. I think that is a buggy bios.
> 
> The bios is configured with vt8251 in AHCI mode and bios boot up activated, so 
> the hd is recognized in the beginning. I don't have any raid, only one hd. 
> The hd is a Maxtor 6V250F0.
> 
> I'm using a debian etch but the i386 version. The only way that I can use the 
> hd is using a 2.6.16 standard kernel with the modifications explained in this 
> page [2]. Basically you have to use their ahci.c and sata_via.c. The 
> modifications are small from the original code from Mr Jeff Garzik.
> 
> I have tried to use the 2.6.18 and 2.6.20rc6 and the result is the same. The  
> kernel boots, but when arrives at the ata3, 
> 
> scsi2 : ahci
> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata3.00: qc timeout (cmd 0xec)
> ata3.00: failed to IDENTIFY (I/O error, err_mask=0x104)
> .... repeated some times ...
> scsi3 : ahci
> ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> scsi4 : ahci
> ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> scsi5 : ahci
> ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> Done.
> Begin: Mounting root file system... ...
> Begin: Running /scripts/local-top
> ide0: I/O resource 0x3F6-0x3F6 not free.
> ide0: ports already in use, skipping probe.
> ide1: I/O resource 0x376-0x376 not free.
> ide1: ports already in use, skipping probe.
> Done.
> Begin: Waiting for root file system ...

It might be VIA IRQ quirk problem.

1. Does giving 'irqpoll' parameter to kernel make any difference?

2. Can you give a shot at 2.6.20?

-- 
tejun

  reply	other threads:[~2007-02-09  9:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 23:10 Leopold Palomo Avellaneda
2007-02-09  9:46 ` Tejun Heo [this message]
2007-02-09 17:13   ` Leopold Palomo Avellaneda
2007-02-09 20:09     ` Leopold Palomo Avellaneda
2007-02-10 14:45       ` Tejun Heo
2007-02-10 17:05         ` Leopold Palomo Avellaneda
2007-02-12  9:11         ` Jean Delvare
2007-02-12  9:47           ` Tejun Heo
2007-02-12 10:57           ` Leopold Palomo-Avellaneda
2007-02-12 16:23           ` Leopold Palomo-Avellaneda
2007-02-13 11:20             ` Jean Delvare
2007-02-13 16:11               ` Leopold Palomo-Avellaneda
2007-02-13 16:19                 ` Jean Delvare
2007-02-15 11:23                   ` Sata_via problems in a Vintage2-AE1: Resume Leopold Palomo-Avellaneda
2007-02-21 11:42                     ` Tejun Heo
2007-02-21 15:56                       ` Leopold Palomo-Avellaneda

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=45CC42FF.5030507@gmail.com \
    --to=htejun@gmail.com \
    --cc=lepalom@wol.es \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Sata_via problems in a Vintage2-AE1' \
    /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

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).