Some more info: I compiled it with support for IANS and without, but I get the same outcome, only setting E1000_IMS_RXSEQ will cause endless interrupts that cannot be stopped not with int_disable and not with cli(), so I guess there must be a bug somewhere, so I activated it on 2.2.x and surprisingly it works ok. Another thing is that without E1000_IMS_RXSEQ, I can see that the interrupt handler is being evoked, but the driver does not try to receive or send although I try pinging in and out of my machine. Ofer - 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/
- Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
- Re: Intel-e1000 for Linux 2.0.36-pre14 kernel
- Re: Intel-e1000 for Linux 2.0.36-pre14 Richard B. Johnson
- Re: Intel-e1000 for Linux 2.0.36-pre14 Matthew Jacob
- Re: Intel-e1000 for Linux 2.0.36-pre14 Richard B. Johnson
- RE: Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
- RE: Intel-e1000 for Linux 2.0.36-pre14 kernel
- Re: Intel-e1000 for Linux 2.0.36-pre14 Jes Sorensen
- RE: Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
- RE: Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
- RE: Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
- RE: Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
- RE: Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
- RE: Intel-e1000 for Linux 2.0.36-pre14 Ofer Fryman
- RE: Intel-e1000 for Linux 2.0.36-pre14 Matthew Jacob