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

2005-07-28 Thread Mark Burton

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 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 localhost kernel: eth1: Transmit timeout, status 0c 
0005 c07f media 00.
Jul  3 14:31:13 localhost kernel: eth1: Tx queue start entry 1160  
dirty entry 1156.
Jul  3 14:31:13 localhost kernel: eth1:  Tx descriptor 0 is 0008a03c. 
(queue head)


I have no TPM (as far as I can find)

Hence I dont think this is the same problem, but it's manifestation is 
identical.


I was using a realtec card, using the 8139too driver, hence I first 
suspected that. As a test, I have an even older 3com509B, using that 
gives exactly the same results (though it doens't seem to be kind 
enough to output anything to /var/log/debug, so all you get are the 
"server not responding" messages under heavy NFS load.

lsmod however, shows both modules loaded

I'm running debian, and recently got a recent kernel image
/proc/version gives:
Linux version 2.6.11-1-386 ([EMAIL PROTECTED]) (gcc version 3.3.6 
(Debian 1:3.3.6-6)) #1 Mon Jun 20 20:53:17 MDT 2005


Im not a kernel expert at all, any help sorting this problem would be 
appreciated, but Its only worth fixing if it's a general problem -- 
if' I'm on my own, I'll fix it with a band-aid :-)


Cheers

Mark.


-
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/


-
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/


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

2005-07-28 Thread Mark Burton

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 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 localhost kernel: eth1: Transmit timeout, status 0c 
0005 c07f media 00.
Jul  3 14:31:13 localhost kernel: eth1: Tx queue start entry 1160  
dirty entry 1156.
Jul  3 14:31:13 localhost kernel: eth1:  Tx descriptor 0 is 0008a03c. 
(queue head)


I have no TPM (as far as I can find)

Hence I dont think this is the same problem, but it's manifestation is 
identical.


I was using a realtec card, using the 8139too driver, hence I first 
suspected that. As a test, I have an even older 3com509B, using that 
gives exactly the same results (though it doens't seem to be kind 
enough to output anything to /var/log/debug, so all you get are the 
server not responding messages under heavy NFS load.

lsmod however, shows both modules loaded

I'm running debian, and recently got a recent kernel image
/proc/version gives:
Linux version 2.6.11-1-386 ([EMAIL PROTECTED]) (gcc version 3.3.6 
(Debian 1:3.3.6-6)) #1 Mon Jun 20 20:53:17 MDT 2005


Im not a kernel expert at all, any help sorting this problem would be 
appreciated, but Its only worth fixing if it's a general problem -- 
if' I'm on my own, I'll fix it with a band-aid :-)


Cheers

Mark.


-
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/


-
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/


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

2005-07-25 Thread Mark Burton



[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! :-)))



  - /proc/interrupt


more /proc/interrupts
   CPU0
  0: 473349IO-APIC-edge  timer
  1: 10IO-APIC-edge  i8042
  2:  0  XT-PIC  cascade
  5:  1IO-APIC-edge  soundblaster
  7:  2IO-APIC-edge  parport0
  9:   8152IO-APIC-edge  aic7xxx
 10:  19988IO-APIC-edge  eth0
 11:577IO-APIC-edge  ohci_hcd, ohci_hcd, ohci_hcd, 
ohci_hcd, eth1

 12:101IO-APIC-edge  i8042
 14:  51421IO-APIC-edge  ide0
NMI:  0
LOC: 473350
ERR:  0
MIS:  0


  - mptable


I'm running a single (old) processor, and I dont have mptable 
installed I can't even find a package for it, am I missing 
something? Sorry!



  - 8259A.pl


perl 8259A.pl
irq 0: 00, edge
irq 1: 00, edge
irq 2: 00, edge
irq 3: 00, edge
irq 4: 00, edge
irq 5: 00, edge
irq 6: 00, edge
irq 7: 00, edge
irq 8: 0a, edge
irq 9: 0a, level
irq 10: 0a, edge
irq 11: 0a, level
irq 12: 0a, edge
irq 13: 0a, edge
irq 14: 0a, edge
irq 15: 0a, edge



  - lspci -vvv


:00:00.0 Non-VGA unclassified device: Intel Corp. 82378ZB/IB, 
82379AB (SIO, SIO.A) PCI to ISA Bridge (rev 88)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium 
>TAbort- SERR- 
Latency: 0

:00:01.0 IDE interface: Silicon Image, Inc. (formerly CMD 
Technology Inc) PCI0646 (rev 01) (prog-if 8a [Master SecP PriP])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
>TAbort- SERR- 
Latency: 64 (500ns min, 1000ns max)
Interrupt: pin A routed to IRQ 14
Region 0: I/O ports at 
Region 1: I/O ports at 
Region 2: I/O ports at 
Region 3: I/O ports at 
Region 4: I/O ports at fc00 [size=16]

:00:02.0 SCSI storage controller: Adaptec AIC-7880U
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
>TAbort- SERR- Latency: 248 (2000ns min, 2000ns max), Cache Line Size: 0x08 
(32 bytes)

Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at f800 [disabled] [size=256]
Region 1: Memory at ffbfc000 (32-bit, non-prefetchable) 
[size=4K]


:00:0b.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2064W 
[Millennium] (rev 01) (prog-if 00 [VGA])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping+ SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
>TAbort- SERR- 
Interrupt: pin A routed to IRQ 11
Region 0: Memory at a000 (32-bit, non-prefetchable) 
[size=16K]

Region 1: Memory at a080 (32-bit, prefetchable) [size=8M]
Expansion ROM at d000 [disabled] [size=64K]

:00:0d.0 USB Controller: Lucent Microelectronics USS-344S USB 
Controller (rev 11) (prog-if 10 [OHCI])

Subsystem: Lucent Microelectronics USS-344S USB Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium 
>TAbort- SERR- 
Latency: 248 (750ns min, 21500ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ffbec000 (32-bit, non-prefetchable) 
[size=4K]

Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=1 PME-

:00:0d.1 USB Controller: Lucent Microelectronics USS-344S USB 
Controller (rev 11) (prog-if 10 [OHCI])

Subsystem: Lucent Microelectronics USS-344S USB Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium 
>TAbort- SERR- 
Latency: 248 (750ns min, 21500ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ffbdc000 (32-bit, non-prefetchable) 
[size=4K]

Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=1 PME-

:00:0d.2 USB Controller: Lucent Microelectronics USS-344S USB 
Controller (rev 11) (prog-if 10 [OHCI])

Subsystem: Lucent Microelectronics USS-344S USB Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- 

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

2005-07-25 Thread Mark Burton



[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! :-)))



  - /proc/interrupt


more /proc/interrupts
   CPU0
  0: 473349IO-APIC-edge  timer
  1: 10IO-APIC-edge  i8042
  2:  0  XT-PIC  cascade
  5:  1IO-APIC-edge  soundblaster
  7:  2IO-APIC-edge  parport0
  9:   8152IO-APIC-edge  aic7xxx
 10:  19988IO-APIC-edge  eth0
 11:577IO-APIC-edge  ohci_hcd, ohci_hcd, ohci_hcd, 
ohci_hcd, eth1

 12:101IO-APIC-edge  i8042
 14:  51421IO-APIC-edge  ide0
NMI:  0
LOC: 473350
ERR:  0
MIS:  0


  - mptable


I'm running a single (old) processor, and I dont have mptable 
installed I can't even find a package for it, am I missing 
something? Sorry!



  - 8259A.pl


perl 8259A.pl
irq 0: 00, edge
irq 1: 00, edge
irq 2: 00, edge
irq 3: 00, edge
irq 4: 00, edge
irq 5: 00, edge
irq 6: 00, edge
irq 7: 00, edge
irq 8: 0a, edge
irq 9: 0a, level
irq 10: 0a, edge
irq 11: 0a, level
irq 12: 0a, edge
irq 13: 0a, edge
irq 14: 0a, edge
irq 15: 0a, edge



  - lspci -vvv


:00:00.0 Non-VGA unclassified device: Intel Corp. 82378ZB/IB, 
82379AB (SIO, SIO.A) PCI to ISA Bridge (rev 88)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium 
TAbort- TAbort- MAbort- SERR- PERR-

Latency: 0

:00:01.0 IDE interface: Silicon Image, Inc. (formerly CMD 
Technology Inc) PCI0646 (rev 01) (prog-if 8a [Master SecP PriP])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
TAbort- TAbort- MAbort- SERR- PERR-

Latency: 64 (500ns min, 1000ns max)
Interrupt: pin A routed to IRQ 14
Region 0: I/O ports at ignored
Region 1: I/O ports at ignored
Region 2: I/O ports at ignored
Region 3: I/O ports at ignored
Region 4: I/O ports at fc00 [size=16]

:00:02.0 SCSI storage controller: Adaptec AIC-7880U
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
TAbort- TAbort- MAbort- SERR- PERR-
Latency: 248 (2000ns min, 2000ns max), Cache Line Size: 0x08 
(32 bytes)

Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at f800 [disabled] [size=256]
Region 1: Memory at ffbfc000 (32-bit, non-prefetchable) 
[size=4K]


:00:0b.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2064W 
[Millennium] (rev 01) (prog-if 00 [VGA])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping+ SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
TAbort- TAbort- MAbort- SERR- PERR-

Interrupt: pin A routed to IRQ 11
Region 0: Memory at a000 (32-bit, non-prefetchable) 
[size=16K]

Region 1: Memory at a080 (32-bit, prefetchable) [size=8M]
Expansion ROM at d000 [disabled] [size=64K]

:00:0d.0 USB Controller: Lucent Microelectronics USS-344S USB 
Controller (rev 11) (prog-if 10 [OHCI])

Subsystem: Lucent Microelectronics USS-344S USB Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium 
TAbort- TAbort- MAbort- SERR- PERR-

Latency: 248 (750ns min, 21500ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ffbec000 (32-bit, non-prefetchable) 
[size=4K]

Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=1 PME-

:00:0d.1 USB Controller: Lucent Microelectronics USS-344S USB 
Controller (rev 11) (prog-if 10 [OHCI])

Subsystem: Lucent Microelectronics USS-344S USB Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium 
TAbort- TAbort- MAbort- SERR- PERR-

Latency: 248 (750ns min, 21500ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ffbdc000 (32-bit, non-prefetchable) 
[size=4K]

Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
PME(D0-,D1+,D2+,D3hot+,D3cold-)

Status: D0 PME-Enable- DSel=0 DScale=1 PME-

:00:0d.2 USB Controller: Lucent Microelectronics USS-344S USB 
Controller (rev 11) (prog-if 10 [OHCI])


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

2005-07-23 Thread OGAWA Hirofumi
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/messages along the
> lines of:
> Jul  3 14:31:13 localhost kernel: eth1: Transmit timeout, status 0c
> 0005 c07f media 00.
> Jul  3 14:31:13 localhost kernel: eth1: Tx queue start entry 1160
> dirty entry 1156.
> Jul  3 14:31:13 localhost kernel: eth1:  Tx descriptor 0 is
> 0008a03c. (queue head)

Probably it's the miss config of PIC. Can you post more info?

  - /proc/interrupt
  - mptable
  - 8259A.pl
  - lspci -vvv
-- 
OGAWA Hirofumi <[EMAIL PROTECTED]>
-
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/


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

2005-07-23 Thread OGAWA Hirofumi
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/messages along the
 lines of:
 Jul  3 14:31:13 localhost kernel: eth1: Transmit timeout, status 0c
 0005 c07f media 00.
 Jul  3 14:31:13 localhost kernel: eth1: Tx queue start entry 1160
 dirty entry 1156.
 Jul  3 14:31:13 localhost kernel: eth1:  Tx descriptor 0 is
 0008a03c. (queue head)

Probably it's the miss config of PIC. Can you post more info?

  - /proc/interrupt
  - mptable
  - 8259A.pl
  - lspci -vvv
-- 
OGAWA Hirofumi [EMAIL PROTECTED]
-
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/


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

2005-07-19 Thread Mark Burton

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 localhost kernel: eth1: Transmit timeout, status 0c 
0005 c07f media 00.
Jul  3 14:31:13 localhost kernel: eth1: Tx queue start entry 1160  
dirty entry 1156.
Jul  3 14:31:13 localhost kernel: eth1:  Tx descriptor 0 is 0008a03c. 
(queue head)


I have no TPM (as far as I can find)

Hence I dont think this is the same problem, but it's manifestation is 
identical.


I was using a realtec card, using the 8139too driver, hence I first 
suspected that. As a test, I have an even older 3com509B, using that 
gives exactly the same results (though it doens't seem to be kind 
enough to output anything to /var/log/debug, so all you get are the 
"server not responding" messages under heavy NFS load.

lsmod however, shows both modules loaded

I'm running debian, and recently got a recent kernel image
/proc/version gives:
Linux version 2.6.11-1-386 ([EMAIL PROTECTED]) (gcc version 3.3.6 (Debian 
1:3.3.6-6)) #1 Mon Jun 20 20:53:17 MDT 2005


Im not a kernel expert at all, any help sorting this problem would be 
appreciated, but Its only worth fixing if it's a general problem -- if' 
I'm on my own, I'll fix it with a band-aid :-)


Cheers

Mark.


-
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/


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

2005-07-19 Thread Mark Burton

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 localhost kernel: eth1: Transmit timeout, status 0c 
0005 c07f media 00.
Jul  3 14:31:13 localhost kernel: eth1: Tx queue start entry 1160  
dirty entry 1156.
Jul  3 14:31:13 localhost kernel: eth1:  Tx descriptor 0 is 0008a03c. 
(queue head)


I have no TPM (as far as I can find)

Hence I dont think this is the same problem, but it's manifestation is 
identical.


I was using a realtec card, using the 8139too driver, hence I first 
suspected that. As a test, I have an even older 3com509B, using that 
gives exactly the same results (though it doens't seem to be kind 
enough to output anything to /var/log/debug, so all you get are the 
server not responding messages under heavy NFS load.

lsmod however, shows both modules loaded

I'm running debian, and recently got a recent kernel image
/proc/version gives:
Linux version 2.6.11-1-386 ([EMAIL PROTECTED]) (gcc version 3.3.6 (Debian 
1:3.3.6-6)) #1 Mon Jun 20 20:53:17 MDT 2005


Im not a kernel expert at all, any help sorting this problem would be 
appreciated, but Its only worth fixing if it's a general problem -- if' 
I'm on my own, I'll fix it with a band-aid :-)


Cheers

Mark.


-
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/