Re: 2.2.15 with eepro100: eth0: Too much work at interrupt

From: Kamlesh Bans (kbans@corsair.com)
Date: Wed May 17 2000 - 12:57:38 EST


Thanks for the help. I made the following change to eepro100.c (both the
2.2.14/1.18 and 2.2.15/1.20.2.3 versions) plus I modified the version
string (forgetting a newline):

// #define eeprom_delay() inw(ee_addr)
#define eeprom_delay() udelay(100)

Unfortunately, this did not help. Both are built in to the 2.2.15 kernel.

May 8 10:47:28 newton kernel: SCSI device sdg: hdwr sector= 512 bytes.
Sectors= 17689267 [8637 MB] [8.6 GB]
May 8 10:47:28 newton kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
May 8 10:47:28 newton kernel: eepro100.c: $Revision: 1.18 $ 1999/12/29
Modified by Andrey V. Savochkin <saw@msu.ru>
May 8 10:47:28 newton kernel: 1.18kb 2000/05/17 Kamlesh Bans
workaround<4>eth0: Invalid EEPROM checksum 0x0000, check settings before
activating this device!
May 8 10:47:28 newton kernel: eth0: Intel PCI EtherExpress Pro100 at
0xc8808000, 00:00:00:00:00:00, IRQ 11.
May 8 10:47:28 newton kernel: Board assembly 000000-000, Physical
connectors present:
May 8 10:47:28 newton kernel: Primary interface chip None PHY #0.
May 8 10:47:28 newton kernel: General self-test: passed.
May 8 10:47:28 newton kernel: Serial sub-system self-test: passed.
May 8 10:47:28 newton kernel: Internal registers self-test: passed.
May 8 10:47:28 newton kernel: ROM checksum self-test: passed (0x49caa8d6).
May 8 10:47:28 newton kernel: Receiver lock-up workaround activated.
May 8 10:47:28 newton kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
May 8 10:47:28 newton kernel: eepro100.c: $Revision: 1.18 $ 1999/12/29
Modified by Andrey V. Savochkin <saw@msu.ru>
May 8 10:47:28 newton kernel: 1.18kb 2000/05/17 Kamlesh Bans
workaroundPartition check:
May 8 10:47:28 newton kernel: sda: sda1 sda2 sda3 < sda5 sda6 sda7 >

May 8 10:47:28 newton kernel: mdio_read() timed out with val = 08040000.
May 8 10:47:28 newton kernel: eth0: Too much work at interrupt, status=0x2000.
May 8 10:47:28 newton kernel: mdio_read() timed out with val = 08000000.
May 8 10:47:28 newton kernel: eth0: Too much work at interrupt, status=0x2000.
May 8 10:47:28 newton kernel: eth0: Too much work at interrupt, status=0x2000.

May 8 10:37:01 newton kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
May 8 10:37:01 newton kernel: eepro100.c: $Revision: 1.20.2.3 $ 2000/03/02
Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
May 8 10:37:01 newton kernel: 1.20.2.3kb 2000/05/17 Kamlesh Bans
workaround<4>eth0: Invalid EEPROM checksum 0x0000, check settings before
activating this device!
May 8 10:37:01 newton kernel: eth0: Intel PCI EtherExpress Pro100 at
0xc8808000, 00:00:00:00:00:00, IRQ 11.
May 8 10:37:01 newton kernel: Board assembly 000000-000, Physical
connectors present:
May 8 10:37:01 newton kernel: Primary interface chip None PHY #0.
May 8 10:37:01 newton kernel: General self-test: passed.
May 8 10:37:01 newton kernel: Serial sub-system self-test: passed.
May 8 10:37:01 newton kernel: Internal registers self-test: passed.
May 8 10:37:01 newton kernel: ROM checksum self-test: passed (0x49caa8d6).
May 8 10:37:01 newton kernel: Receiver lock-up workaround activated.
May 8 10:37:01 newton kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
May 8 10:37:01 newton kernel: eepro100.c: $Revision: 1.20.2.3 $ 2000/03/02
Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
May 8 10:37:01 newton kernel: 1.20.2.3kb 2000/05/17 Kamlesh Bans
workaroundPartition check:
May 8 10:37:01 newton kernel: sda: sda1 sda2 sda3 < sda5 sda6 sda7 >

May 8 10:37:01 newton kernel: mdio_read() timed out with val = 08000000.
May 8 10:37:01 newton kernel: eth0: Too much work at interrupt, status=0x2000.
May 8 10:37:01 newton last message repeated 2 times
May 8 10:37:01 newton kernel: mdio_read() timed out with val = 08050000.
May 8 10:37:01 newton kernel: eth0: Too much work at interrupt, status=0x2000.
May 8 10:37:02 newton kernel: eth0: Too much work at interrupt, status=0x4000.
May 8 10:37:03 newton kernel: eth0: Too much work at interrupt, status=0xa000.
May 8 10:37:03 newton kernel: eth0: Too much work at interrupt, status=0x4000.
May 8 10:37:03 newton kernel: mdio_read() timed out with val = 08050000.

At 10:29 AM 05/17/2000 +0800, Andrey Savochkin wrote:
>Hello,
>
>On Tue, May 16, 2000 at 02:21:52PM -0700, Kamlesh Bans wrote:
> > At the suggestion of Alan Cox (thanks Alan), I tried the 2.2.14 eepro100.c
> > (Revision: 1.18 $ 1999/12/29) instead of the 2.2.15 one (Revision:
> 1.20.2.3
> > $ 2000/03/02) with the 2.2.15 kernel, however I am getting the same
> > problem. Excerpt from kern.log (still wrong date):
> >
> > May 8 10:44:30 newton kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
> > http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
> > May 8 10:44:30 newton kernel: eepro100.c: $Revision: 1.18 $ 1999/12/29
> > Modified by Andrey V. Savochkin <saw@msu.ru>
> > May 8 10:44:30 newton kernel: eth0: Invalid EEPROM checksum 0x0000, check
> > settings before activating this device!
> > May 8 10:44:30 newton kernel: eth0: Intel PCI EtherExpress Pro100 at
> > 0xc8808000, 00:00:00:00:00:00, IRQ 11.
>
>I've debugged this problem and hope to provide the fix in a day or two.
>As a workaround, you may replace eepro_delay macro body by udelay(100).
>
>Best regards
> Andrey V.
> Savochkin

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



This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:13 EST