Date: Thu, 2 Feb 2006 15:39:10 +0300
From: "Vladimir B. Savkin" <master@sectorb.msk.ru>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Broken sata (VIA) on Asus A8V (kernel 2.6.14+)
Message-ID: <20060202123910.GA14328@tentacle.sectorb.msk.ru>
References: <20060201162800.GA32196@tentacle.sectorb.msk.ru> <43E13F57.40808@gmail.com> <20060201231911.GA5463@tentacle.sectorb.msk.ru> <43E145B8.6090404@gmail.com> <20060202114429.GA3035@tentacle.sectorb.msk.ru> <43E1F211.8030507@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <43E1F211.8030507@gmail.com>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1509
Lines: 42

On Thu, Feb 02, 2006 at 08:50:41PM +0900, Tejun Heo wrote:
> Vladimir B. Savkin wrote:
> >On Thu, Feb 02, 2006 at 08:35:20AM +0900, Tejun Heo wrote:
> >
> >>Your BMDMA controller is reporting raised interrupt (0x4) and your drive 
> >>is saying that it's ready for the next command, yet interrupt handler of 
> >>sata_via hasn't run and thus the timeout.  It looks like some kind of 
> >>IRQ routing problem to me although I have no idea how the problem 
> >>doesn't affect the boot process.
> >>
> >>Can you try to boot with boot parameter pci=noacpi?
> >
> >
> >That did not help.
> >
> >And yes, irqbalance is running, as Kenneth suggested.
> >
> 
> Sadly, I'm pretty much ignorant with that part of the kernel.  However, 
> if it's really because interrupts are lost when sent to one of the 
> processors, one of the following should keep the system going while the 
> other cause the problem immediately.
> 
> echo 1 > /proc/irq/your_IRQ_number/smp_affinity
> 
> or...
> 
> echo 2 > /proc/irq/your_IRQ_number/smp_affinity
 
It is certainly not that simple.
Just playing with smp_affinity (with irqbalance stopped) gives no errors.

~
:wq
                                        With best regards, 
                                           Vladimir Savkin. 

-
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/