mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kenneth topp <caught@prodigy.net>
To: linux-kernel@vger.kernel.org
Cc: Tejun Heo <htejun@gmail.com>
Subject: Re: Broken sata (VIA) on Asus A8V (kernel 2.6.14+)
Date: Wed, 1 Feb 2006 21:58:23 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0602012105110.30257@static> (raw)


I'm pretty close to finding irqbalance to be the reason for my similar 
timeouts.  still narrowing down with git bisect, but it's the only 
substantial thing left, which is the smp_affinity fix..

it's a 2.6.14.7 and ~2.6.15-rc4 change.

my timeouts don't occur immediately either.  So what do I look for when 
IRQ get misrouted?  Would it be a driver/device issue?  It seems like I 
have to go back to the point my kernel went MSI and patch it, then bisect 
all over again..

  As well as the ata timeouts leading to permanently D stated pdflushs, the 
other symptom I see is my usb mouse/keyboard occationally types really 
slowly, like 2400bps slow.


the patch that made this issue appear for me:

--- a/arch/i386/kernel/io_apic.c
+++ b/arch/i386/kernel/io_apic.c
@@ -1937,7 +1937,7 @@ static void ack_edge_ioapic_vector(unsig
{
int irq = vector_to_irq(vector);
- move_irq(vector);
+ move_native_irq(vector);
ack_edge_ioapic_irq(irq);
}
@@ -1952,7 +1952,7 @@ static void end_level_ioapic_vector (uns
{
int irq = vector_to_irq(vector);
- move_irq(vector);
+ move_native_irq(vector);
end_level_ioapic_irq(irq);
}

-

-my /proc/interrupts
   0:       3487    1817855    IO-APIC-edge  timer
   1:          0         60    IO-APIC-edge  i8042
   8:          0          1    IO-APIC-edge  rtc
   9:          0          0   IO-APIC-level  acpi
  14:        534     177341    IO-APIC-edge  ide0
  15:         96      64627    IO-APIC-edge  ide1
169:         16       9846   IO-APIC-level  libata
177:        877     643023   IO-APIC-level  libata, eth0, 
radeon@pci:0000:01:00.0
185:       1146     532391   IO-APIC-level  eth1
193:         16       8392   IO-APIC-level  eth2
201:        173     104730   IO-APIC-level  VIA8237
209:        177     103680   IO-APIC-level  uhci_hcd:usb1, uhci_hcd:usb2, 
uhci_hcd:usb3, ehci_hcd:usb4


Kenneth Topp


------

Vladimir B. Savkin wrote:
> On Thu, Feb 02, 2006 at 08:08:07AM +0900, Tejun Heo wrote:
>
>>Vladimir B. Savkin wrote:
>>
>>>Hello!
>>>
>>>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.
>>>
>>
>>How reproducible is the problem?  With how much certainty can you say
>>the problem is introduced by newer kernels?  e.g. If the problem occurs
>>most of the time with 2.5.15.1 but it stops happending after switching
>>back to 2.6.13.3, you can be pretty sure.
>
>
> Highly reproducible: months vs. minutes of uptime.
>
>

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?

-- 
tejun

             reply	other threads:[~2006-02-02  2:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  2:58 kenneth topp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-01 16:28 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

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=Pine.LNX.4.64.0602012105110.30257@static \
    --to=caught@prodigy.net \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome