PCI Master Aborts effect multiple subsystems?

Hi, I am trying to do a small amount of work on the wcfxo device driver (or an fxo card), which is part of zapatel, which is used by asterisk, the linux open source PBX (hence cross post). question 1: Are PCI Master Aborts delivered to all subsystems, if they are, do I need to "fix" ALL the dr

Re: tx queue start entry x dirty entry y (was 8139too PCI IRQ issues)

For reference, Thanks to Ogawa Hirofumi, the solution was to use noapic on the boot line, as my machine is too old to handle APIC well. Cheers Mark. On 19 Jul 2005, at 18:00, Mark Burton wrote: Hi, I'm getting similar results to Nick Warne, in that when my ethernet is stressed at all

Re: tx queue start entry x dirty entry y (was 8139too PCI IRQ issues)

MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 32, Cache Line Size: 0x08 (32 bytes) -- On 23 Jul 2005, at 21:11, OGAWA Hirofumi wrote: Mark Burton <[EMAIL PROTECTED]> writes: Hi, I'm getting similar results to Nick Warne, in that when my ethernet is stre

tx queue start entry x dirty entry y (was 8139too PCI IRQ issues)

Hi, I'm getting similar results to Nick Warne, in that when my ethernet is stressed at all (for instance by NFS), I end up with nfs: server. not responding, still trying nfs: server OK With a realtec card, I get errors in /var/spool/messages along the lines of: Jul 3 14:31:13 localho