mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Heikki Orsila <shd@zakalwe.fi>
Cc: "Vladimir B. Savkin" <master@sectorb.msk.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: Still broken sata (VIA) on Asus A8V (kernel 2.6.14+) with irqbalance
Date: Sat, 29 Jul 2006 05:08:09 +0100	[thread overview]
Message-ID: <1154146089.10955.109.camel@bastov.localdomain> (raw)
In-Reply-To: <20060728200250.GA12840@zakalwe.fi>

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

cat DMESG | grep -i fixup
PCI: VIA IRQ fixup for 0000:00:0f.1, from 255 to 0
PCI: VIA IRQ fixup for 0000:00:10.0, from 11 to 3
PCI: VIA IRQ fixup for 0000:00:10.1, from 11 to 3
PCI: VIA IRQ fixup for 0000:00:10.2, from 10 to 3

with IO-APIC working , you could try patches to not "VIA IRQ quirk
fixup", but could not be the main problem. 

I have a very experimental patch
http://lkml.org/lkml/2006/7/28/99


Which you can just apply and make bzImage, install and reboot  , don't
need to recompile all over again.


On Fri, 2006-07-28 at 23:02 +0300, Heikki Orsila wrote:
> On Fri, Jul 28, 2006 at 04:12:15PM +0400, Vladimir B. Savkin wrote:
> > Hello! 
> > Here goes my first report on the issue.
> > 
> > On Wed, Feb 01, 2006 at 07:28:00PM +0300, Vladimir B. Savkin wrote:
> > > My system based on Asus A8V (VIA chipset) works fine with 2.6.13.3,
> > > but after upgrading (kernels 2.6.14.7 and 2.6.15.1 tried) it
> > > gaves error messages some minutes after boot.
> > > 
> > > The messages are as following:
> > >   ata2: command 0xXX timeout, stat 0x50 host_stat 0x4
> > > where XX gets different values from time to time, 0x25 mostly.
> > > I/O to this controller halts after that.
> > > 
> > > Attached are boot dmesg log and lspci output.
> > > 
> > 
> > I just checked - the problem persists with 2.6.17.7
> 
> This is ASUS K8V SE Deluxe on amd64 with SiI 3114 SATA controller. I 
> upgraded from Ubuntu 6.06 kernel 2.6.15-23 to vanilla 2.6.17.4 and got 
> following errors shortly after the boot:
> 
> Jul 26 00:35:39 cheradenine kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
> Jul 26 00:35:39 cheradenine kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
> Jul 26 00:35:39 cheradenine kernel: ata1: error=0x04 { DriveStatusError }
> 
> Linux cheradenine 2.6.17.4 #2 SMP Wed Jul 19 16:33:24 EEST 2006 x86_64 GNU/Linux
>  
> Gnu C                  4.0.3
> Gnu make               3.81beta4
> binutils               2.16.91
> util-linux             2.12r
> mount                  2.12r
> module-init-tools      3.2.2
> e2fsprogs              1.38
> jfsutils               1.1.8
> reiserfsprogs          3.6.19
> reiser4progs           1.0.5
> xfsprogs               2.7.7
> PPP                    2.4.4b1
> Linux C Library        2.3.6
> Dynamic linker (ldd)   2.3.6
> Procps                 3.2.6
> Net-tools              1.60
> Console-tools          0.2.3
> Sh-utils               5.93
> udev                   079
> Modules Loaded         
> 
> > libata version 1.20 loaded.
> > sata_via 0000:00:0f.0: version 1.1
> > ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 16
> > sata_via 0000:00:0f.0: routed to hard irq line 10
> > ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xB802 bmdma 0xA800 irq 16
> > ata2: SATA max UDMA/133 cmd 0xB400 ctl 0xB002 bmdma 0xA808 irq 16
> > ata1: SATA link down (SStatus 0)
> > scsi0 : sata_via
> 
> Mine is "sata_sil 0000:00:0d.0: version 0.9".
> 
> 0000:00:0d.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02)
> 
> If these are symptoms of the same bug, it is not sata_via specific.
> 
> Heikki Orsila
> heikki.orsila@iki.fi
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-- 
Sérgio M.B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]

  reply	other threads:[~2006-07-29  4:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 16:28 Broken sata (VIA) on Asus A8V (kernel 2.6.14+) Vladimir B. Savkin
2006-02-01 23:08 ` Tejun Heo
2006-02-01 23:19   ` Vladimir B. Savkin
2006-02-01 23:35     ` Tejun Heo
2006-02-02 11:44       ` Vladimir B. Savkin
2006-02-02 11:50         ` Tejun Heo
2006-02-02 12:39           ` Vladimir B. Savkin
2006-02-02 20:36             ` Vladimir B. Savkin
2006-07-28 12:12 ` Still broken sata (VIA) on Asus A8V (kernel 2.6.14+) with irqbalance Vladimir B. Savkin
2006-07-28 20:02   ` Heikki Orsila
2006-07-29  4:08     ` Sergio Monteiro Basto [this message]
2006-07-30 10:48       ` Heikki Orsila
2006-09-06 18:06         ` Sergio Monteiro Basto
2006-09-07  0:24           ` Vladimir B. Savkin
2006-10-17 15:17 Dyson
2006-10-18 14:26 ` Sergio Monteiro Basto
2006-10-18 17:12   ` Dyson
2006-10-18 18:05     ` Sergio Monteiro Basto
2006-10-20 12:30       ` Dyson

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=1154146089.10955.109.camel@bastov.localdomain \
    --to=sergio@sergiomb.no-ip.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=master@sectorb.msk.ru \
    --cc=shd@zakalwe.fi \
    /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

all inboxes | Powered by JetHome®