On Thu, Feb 02, 2006 at 03:39:10PM +0300, Vladimir B. Savkin wrote:
> 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.
>
For the record - without irqbalance the box is stable.
~
:wq
With best regards,
Vladimir Savkin.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
