epic100 in current -ac kernels

epic100 in current -ac kernels

[ARND BERGMANN]

There seems to be some movement in the driver and the latest one
is not working for me (again), so I'm giving a subjective status report
for the versions I have tried lately:

Working epic100 drivers:
 - 2.4.0
 - 2.4.0-ac9

Broken epic100 drivers:
 - 2.4.0-ac4
 - 2.4.1-ac2
 - 2.4.1-ac4

I have not yet looked at the source to find the problem, but the other
kernels between that each seem to contain one of the those versions above.
The symptom is always that after 'ifconfig eth0 up', the system slows down
to the point where I can hardly type on the keyboard and even 'ifconfig
eth0 down' takes serveral seconds (on an Athlon-800)!

The boot message is:
eth0: SMSC EPIC/100 83c170 at 0xd091e000, IRQ 11, 00:e0:29:6c:36:6f.
eth0: MII transceiver #3 control 3000 status 7849.
eth0: Autonegotiation advertising 01e1 link partner 0001.
epic100.c:v1.11 1/7/2001 Written by Donald Becker <becker@scyld.com>
  http://www.scyld.com/network/epic100.html
 (unofficial 2.4.x kernel port, version 1.1.6, January 11, 2001)
PCI: Found IRQ 11 for device 00:0d.0
PCI: The same IRQ used for device 00:04.2
PCI: The same IRQ used for device 00:04.3
PCI: The same IRQ used for device 00:09.0                                                      

The device on 00:04:[23] is a VT82C586B USB and on 00:09:0 an
Ensoniq 5880 AudioPCI (rev 02). I can not change the IRQ settings
right now without physical access to the machine (it is locked).

At least with some broken versions, I also got these messages in
syslog (every 4 seconds):
Feb  7 21:10:06 project kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb  7 21:10:06 project kernel: eth0: Transmit timeout using MII device,
Tx status 000b.
Feb  7 21:10:10 project kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb  7 21:10:10 project kernel: eth0: Transmit timeout using MII device,
Tx status 000b.
Feb  7 21:10:14 project kernel: NETDEV WATCHDOG: eth0: transmit timed out
Feb  7 21:10:14 project kernel: eth0: Transmit timeout using MII device,
Tx status 000b.          
...

The card is acoording to lspci:

00:0d.0 Ethernet controller: Standard Microsystems Corp [SMC] 83C170QF
(rev 08)
        Subsystem: Standard Microsystems Corp [SMC]: Unknown device a020
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2000ns min, 7000ns max)
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 9800 [size=256]
        Region 1: Memory at df800000 (32-bit, non-prefetchable) [size=4K]
        Expansion ROM at <unassigned> [disabled] [size=64K]
        Capabilities: [dc] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1+,D2+,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-


Arnd <><

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: epic100 in current -ac kernels

[Francois Romieu]

ARND BERGMANN <std7652@et.FH-Osnabrueck.DE> écrit :
> There seems to be some movement in the driver and the latest one
> is not working for me (again), so I'm giving a subjective status report
> for the versions I have tried lately:
> 
> Working epic100 drivers:
>  - 2.4.0
>  - 2.4.0-ac9

Could you give a look at ac12 (fine here) ?


-- 
Ueimor <romieu@cogenit.fr>
Cogenit                                  Tél : +33 (0) 1 40 20 08 43
53 rue Sainte Anne                       Fax : +33 (0) 1 40 20 08 45
75002 Paris                              <URL:http://www.cogenit.fr>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: epic100 in current -ac kernels

[ARND BERGMANN]

On Thu, 8 Feb 2001, Francois Romieu wrote:

> > 
> > Working epic100 drivers:
> >  - 2.4.0
> >  - 2.4.0-ac9
> 
> Could you give a look at ac12 (fine here) ?
> 
No, does not work, same problem.

Arnd <><

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: epic100 in current -ac kernels

[Francois Romieu]

ARND BERGMANN <std7652@et.FH-Osnabrueck.DE> écrit :
> On Thu, 8 Feb 2001, Francois Romieu wrote:
> 
> > > 
> > > Working epic100 drivers:
> > >  - 2.4.0
> > >  - 2.4.0-ac9
> > 
> > Could you give a look at ac12 (fine here) ?
> > 
> No, does not work, same problem.

The modifications between ac9 and ac12 come from the new DMA 
mapping. They added a bug for the (already buggy ?) big-endian
machines. I would be surprised that something has *always* been 
missing in the driver and your hardware triggers it*. IMHO the culprit 
is to be found elsewhere.
I'd like to know what it's worth to share an irq with a pio audio card.

-- 
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: epic100 in current -ac kernels

[ARND BERGMANN]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1874 bytes --]

On Fri, 9 Feb 2001, Francois Romieu wrote:

> ARND BERGMANN <std7652@et.FH-Osnabrueck.DE> écrit :
> > On Thu, 8 Feb 2001, Francois Romieu wrote:
> > 
> > > > 
> > > > Working epic100 drivers:
> > > >  - 2.4.0
> > > >  - 2.4.0-ac9
> > > 
> > > Could you give a look at ac12 (fine here) ?
> > > 
> > No, does not work, same problem.
> 
> The modifications between ac9 and ac12 come from the new DMA 
> mapping.
What about 2.4.0-ac5? That had the same problem as -ac12. Did it also have
the new DMA mapping?

> They added a bug for the (already buggy ?) big-endian
> machines. I would be surprised that something has *always* been 
> missing in the driver and your hardware triggers it*. IMHO the culprit 
> is to be found elsewhere.
Yes, I'm pretty sure the problem is not only the epic100 driver, now that
I have done some more investigation. With the broken drivers (I tried
2.4.0-ac12 and 2.4.1-ac5), something generates an enourmous amount of
interrupts as soon as I run 'ifconfig eth0 up'. Within 10 seconds, I got
roughly 950000 interrupts on IRQ11, instead of 30!
After disabling the usb-uhci (I was using the JE driver) in the BIOS
setup, the system reproducibly locked up hard a few seconds after
'ifconfig eth0 up' instead of just getting slow.
Unfortunately, I have no way to also disable the sound card, but at least
it does not make a change if the sound driver is loaded or not.

> I'd like to know what it's worth to share an irq with a pio audio card.
On Monday I can ask the system administrator for the keys so I can open
the machine and put the card into another slot. Right now, USB, sound and
network are hardwired to the same IRQ, that's how the system arrived here.

Arnd <><

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

IRQ (routing ?) problem [was Re: epic100 in current -ac kernels]

[Francois Romieu]

ARND BERGMANN <std7652@et.FH-Osnabrueck.DE> écrit :
[...]
> > > > > Working epic100 drivers:
> > > > >  - 2.4.0
> > > > >  - 2.4.0-ac9
> > > > 
> > > > Could you give a look at ac12 (fine here) ?
> > > > 
> > > No, does not work, same problem.
> > 
> > The modifications between ac9 and ac12 come from the new DMA 
> > mapping.
> What about 2.4.0-ac5? That had the same problem as -ac12. Did it also have
> the new DMA mapping?

Yes. For completness (though irrelevant):
2.4.0-ac2 -> ac6 : DMA mapping + rev9 fixes from Andreas Steinmetz
2.4.0-ac7 -> ac10: Merge becker version 1.11 + pci_enable. No DMA mapping
2.4.0-ac11       : Merge becker version 1.11 + pci_enable + DMA mapping

[...]
> > They added a bug for the (already buggy ?) big-endian
> > machines. I would be surprised that something has *always* been 
> > missing in the driver and your hardware triggers it*. IMHO the culprit 
> > is to be found elsewhere.
> Yes, I'm pretty sure the problem is not only the epic100 driver, now that
> I have done some more investigation. With the broken drivers (I tried
> 2.4.0-ac12 and 2.4.1-ac5), something generates an enourmous amount of
> interrupts as soon as I run 'ifconfig eth0 up'. Within 10 seconds, I got
> roughly 950000 interrupts on IRQ11, instead of 30!
          ^^^^^^
No wonder the system feels sluggish.

> After disabling the usb-uhci (I was using the JE driver) in the BIOS
> setup, the system reproducibly locked up hard a few seconds after
> 'ifconfig eth0 up' instead of just getting slow.

The following informations may help:
- motherboard type
- bios revision
- lspci -x 
- 2.4.2pre3 + whatever recent ac epic100 = ?

-- 
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: IRQ (routing ?) problem [was Re: epic100 in current -ac kernels]

[ARND BERGMANN]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1286 bytes --]

Sorry for the delay, I could not get physical access to the machine
for the last days.

I was able to do some more testing today and found this:
- The problem is not the IRQ /sharing/, after getting rid of all the
  other PCI cards, the problem was still there.
- The only thing that seems to have any effect on the symptoms is the
  presence of the USB driver, either usb-uhci or uhci. I am not using
  USB at all. As described before, the system behaves is either of those
  ways:
   * epic100 driver without DMA mapping (e.g. 2.4.0-ac9): normal operation
   * driver with DMA mapping+USB driver loaded: lots of interrupts -> slow
   * driver with DMA mapping, USB driver not loaded: hang after ~2 seconds
- I sometimes get 'spurious interrupt: IRQ7', even though no device is 
  connected there. Probably not important.

On Sat, 10 Feb 2001, Francois Romieu wrote:

> 
> The following informations may help:
> - motherboard type
Asus A7V, onboard USB hub and Promise ATA/100 chip

> - bios revision
Can't see right now, system was bought in October 2000
I think it was 1.004, but I am not sure.

> - lspci -x 
see attachment, this was when I ripped out sound, tv and scsi

> - 2.4.2pre3 + whatever recent ac epic100 = ?
Still no improvement until latest -ac (2.4.1-ac13)

Arnd <><



[-- Attachment #2: Type: TEXT/PLAIN, Size: 5350 bytes --]

00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
	Subsystem: Asustek Computer, Inc.: Unknown device 8033
	Flags: bus master, medium devsel, latency 0
	Memory at e7000000 (32-bit, prefetchable) [size=16M]
	Capabilities: [a0] AGP version 2.0
	Capabilities: [c0] Power Management version 2
00: 06 11 05 03 06 00 10 22 02 00 00 06 00 00 00 00
10: 08 00 00 e7 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 33 80
30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00

00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8305 (prog-if 00 [Normal decode])
	Flags: bus master, 66Mhz, medium devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	Memory behind bridge: e2800000-e3dfffff
	Prefetchable memory behind bridge: e3f00000-e6ffffff
	Capabilities: [80] Power Management version 2
00: 06 11 05 83 07 00 30 22 00 00 04 06 00 00 01 00
10: 00 00 00 00 00 00 00 00 00 01 01 00 e0 d0 00 00
20: 80 e2 d0 e3 f0 e3 f0 e6 00 00 00 00 00 00 00 00
30: 00 00 00 00 80 00 00 00 00 00 00 00 00 00 08 00

00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 22)
	Subsystem: Asustek Computer, Inc.: Unknown device 8033
	Flags: bus master, stepping, medium devsel, latency 0
00: 06 11 86 06 87 00 10 02 22 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 33 80
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10) (prog-if 8a [Master SecP PriP])
	Flags: bus master, medium devsel, latency 32
	I/O ports at d800 [size=16]
	Capabilities: [c0] Power Management version 2
00: 06 11 71 05 07 00 90 02 10 8a 01 01 00 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d8 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 c0 00 00 00 00 00 00 00 ff 00 00 00

00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10) (prog-if 00 [UHCI])
	Subsystem: Unknown device 0925:1234
	Flags: bus master, medium devsel, latency 32, IRQ 11
	I/O ports at d400 [size=32]
	Capabilities: [80] Power Management version 2
00: 06 11 38 30 17 00 10 02 10 00 03 0c 08 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d4 00 00 00 00 00 00 00 00 00 00 25 09 34 12
30: 00 00 00 00 80 00 00 00 00 00 00 00 0b 04 00 00

00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10) (prog-if 00 [UHCI])
	Subsystem: Unknown device 0925:1234
	Flags: bus master, medium devsel, latency 32, IRQ 11
	I/O ports at d000 [size=32]
	Capabilities: [80] Power Management version 2
00: 06 11 38 30 17 00 10 02 10 00 03 0c 08 20 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d0 00 00 00 00 00 00 00 00 00 00 25 09 34 12
30: 00 00 00 00 80 00 00 00 00 00 00 00 0b 04 00 00

00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
	Flags: medium devsel, IRQ 9
	Capabilities: [68] Power Management version 2
00: 06 11 57 30 00 00 90 02 30 00 00 06 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 68 00 00 00 00 00 00 00 00 00 00 00

00:0c.0 Ethernet controller: Standard Microsystems Corp [SMC] 83C170QF (rev 08)
	Subsystem: Standard Microsystems Corp [SMC]: Unknown device a020
	Flags: bus master, fast devsel, latency 32, IRQ 10
	I/O ports at a400 [size=256]
	Memory at e2000000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=64K]
	Capabilities: [dc] Power Management version 1
00: b8 10 05 00 07 00 90 00 08 00 00 02 00 20 00 00
10: 01 a4 00 00 00 00 00 e2 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 07 01 00 00 b8 10 20 a0
30: 00 00 00 00 dc 00 00 00 00 00 00 00 0a 01 08 1c

00:11.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown device 0d30 (rev 02)
	Subsystem: Promise Technology, Inc.: Unknown device 4d33
	Flags: bus master, medium devsel, latency 32, IRQ 5
	I/O ports at a000 [size=8]
	I/O ports at 9800 [size=4]
	I/O ports at 9400 [size=8]
	I/O ports at 9000 [size=4]
	I/O ports at 8800 [size=64]
	Memory at e1800000 (32-bit, non-prefetchable) [size=128K]
	Expansion ROM at <unassigned> [disabled] [size=64K]
	Capabilities: [58] Power Management version 1
00: 5a 10 30 0d 07 00 10 02 02 00 80 01 00 20 00 00
10: 01 a0 00 00 01 98 00 00 01 94 00 00 01 90 00 00
20: 01 88 00 00 00 00 80 e1 00 00 00 00 5a 10 33 4d
30: 00 00 00 00 58 00 00 00 00 00 00 00 05 01 00 00

01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA])
	Subsystem: Matrox Graphics, Inc.: Unknown device 0378
	Flags: bus master, medium devsel, latency 64, IRQ 10
	Memory at e4000000 (32-bit, prefetchable) [size=32M]
	Memory at e3000000 (32-bit, non-prefetchable) [size=16K]
	Memory at e2800000 (32-bit, non-prefetchable) [size=8M]
	Expansion ROM at e3ff0000 [disabled] [size=64K]
	Capabilities: [dc] Power Management version 2
	Capabilities: [f0] AGP version 2.0
00: 2b 10 25 05 07 00 90 02 04 00 00 03 08 40 00 00
10: 08 00 00 e4 00 00 00 e3 00 00 80 e2 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 2b 10 78 03
30: 00 00 ff e3 dc 00 00 00 00 00 00 00 0a 01 10 20

Re: IRQ (routing ?) problem [was Re: epic100 in current -ac kernels]<

[Arnd Bergmann]

I noticed that there have been updates to epic100 again and just wanted
to note that the problem remains:
2.4.2-ac3 still crashes, but it works fine when I use the epic100.c
from 2.4.0-test9, which was the last working version for me.

Arnd <><

On Thu, 15 Feb 2001, ARND BERGMANN wrote:

> Sorry for the delay, I could not get physical access to the machine
> for the last days.
> 
> I was able to do some more testing today and found this:
> - The problem is not the IRQ /sharing/, after getting rid of all the
>   other PCI cards, the problem was still there.
> - The only thing that seems to have any effect on the symptoms is the
>   presence of the USB driver, either usb-uhci or uhci. I am not using
>   USB at all. As described before, the system behaves is either of those
>   ways:
>    * epic100 driver without DMA mapping (e.g. 2.4.0-ac9): normal operation
>    * driver with DMA mapping+USB driver loaded: lots of interrupts -> slow
>    * driver with DMA mapping, USB driver not loaded: hang after ~2 seconds
> - I sometimes get 'spurious interrupt: IRQ7', even though no device is 
>   connected there. Probably not important.
> 
> On Sat, 10 Feb 2001, Francois Romieu wrote:
> 
> > 
> > The following informations may help:
> > - motherboard type
> Asus A7V, onboard USB hub and Promise ATA/100 chip
> 
> > - bios revision
> Can't see right now, system was bought in October 2000
> I think it was 1.004, but I am not sure.
> 
> > - lspci -x 
> see attachment, this was when I ripped out sound, tv and scsi
> 
> > - 2.4.2pre3 + whatever recent ac epic100 = ?
> Still no improvement until latest -ac (2.4.1-ac13)
> 
> Arnd <><
> 
> 
>