From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: akpm@osdl.org, torvalds@osdl.org,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
Jon Smirl <jonsmirl@yahoo.com>
Subject: Re: [BK PATCHES] 2.6.x libata update
Date: Sun, 15 Feb 2004 10:18:39 +0200 [thread overview]
Message-ID: <1076833119.27648.15.camel@nosferatu.lan> (raw)
In-Reply-To: <402E85EE.70801@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
On Sat, 2004-02-14 at 22:32, Jeff Garzik wrote:
> Martin Schlemmer wrote:
> > Yep, it still breaks it. I get a dma timeout on heavy disk access,
> > and then things start to freeze (or do not start at all). Seems
> > Jon is hitting the same issue with -bk4.
>
> Thanks for re-verifying. The buggy patch is now reverted upstream, and
> I'll be looking into another way to fix the "too many interrupts on
> ICH5" problem.
>
Stupid question - its not maybe fixed in later revisions of the
controller (also those this breaks)? I never had the heavy interrupts
problem some seems to have ...
--
# cat /proc/interrupts
CPU0 CPU1
0: 64547502 64536877 IO-APIC-edge timer
2: 0 0 XT-PIC cascade
8: 6702 945 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
14: 244 142 IO-APIC-edge ide0
15: 35 62 IO-APIC-edge ide1
169: 1287568 1399519 IO-APIC-level libata, uhci_hcd, eth0
177: 746886 747222 IO-APIC-level Intel ICH5
185: 5637855 5624744 IO-APIC-level uhci_hcd, uhci_hcd, nvidia
193: 0 0 IO-APIC-level uhci_hcd
201: 0 0 IO-APIC-level ehci_hcd
NMI: 0 0
LOC: 129049693 129049832
ERR: 0
MIS: 0
--
(yes, with the patch it happens without nvidia as well)
--
Bus 0, device 31, function 1:
IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 2).
IRQ 169.
I/O at 0xfc00 [0xfc0f].
Non-prefetchable 32 bit memory at 0x40000000 [0x400003ff].
Bus 0, device 31, function 2:
IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 2).
IRQ 169.
I/O at 0xefe0 [0xefe7].
I/O at 0xefac [0xefaf].
I/O at 0xefa0 [0xefa7].
I/O at 0xefa8 [0xefab].
I/O at 0xef90 [0xef9f].
--
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-15 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 18:43 [BK PATCHES] 2.6.x libata update Jeff Garzik
2004-02-13 19:28 ` Martin Schlemmer
2004-02-13 21:03 ` Jeff Garzik
2004-02-14 18:29 ` Martin Schlemmer
2004-02-14 20:32 ` Jeff Garzik
2004-02-15 8:18 ` Martin Schlemmer [this message]
2004-02-15 15:17 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2004-02-15 16:07 Jon Smirl
2004-02-15 16:11 Jon Smirl
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=1076833119.27648.15.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=jonsmirl@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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