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 (for

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

[I'm currently having nasty ISP problems, so I've removed myself from the list for the time-being, as e-mail is struggling to get through to me -- hence the delay in my reply to this, SORRY] Probably it's the miss config of PIC. Can you post more info? Thanks for helping! :-))) - /p

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

Mark Burton <[EMAIL PROTECTED]> writes: > 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/me

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