Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*e1000\s+driver\s+problem\s+with\s+Intel\s+Pro\/1000\s+MT\s+adapter\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*e1000\s+driver\s+problem\s+with\s+Intel\s+Pro\/1000\s+MT\s+adapter\s*$/: 18 ]

Total 18 documents matching your query.

1. ssion limit (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Sat, 04 Dec 2004 00:25:39 +0100; - An 82541 at PCI 32/66. - An 82546 at PCI-X 64/100, N; /archives/netdev/2004-12/msg00051.html (9,048 bytes)
2. MT adapter (score: 1): Author: Francois Romieu <romieu@xxxxxxxxxxxxx>; Date: Sat, 4 Dec 2004 01:59:46 +0100; the e1000 driver (I tried both the version supplied by; /archives/netdev/2004-12/msg00052.html (9,019 bytes)
3. MT adapter (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Sat, 4 Dec 2004 02:14:44 +0100; 1000_open -> request_irq That + (2) + SMP suggests an i; /archives/netdev/2004-12/msg00053.html (9,455 bytes)
4. ssion limit (score: 1): Author: Francois Romieu <romieu@xxxxxxxxxxxxx>; Date: Sat, 4 Dec 2004 13:03:28 +0100; rs: case overhead phi-32-33-82540-2.6.9 1.86 us phi-32-; /archives/netdev/2004-12/msg00056.html (9,195 bytes)
5. MT adapter (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Sat, 4 Dec 2004 18:20:13 +0100; nt 2.6.x will provide a different datapoint and a wider; /archives/netdev/2004-12/msg00057.html (9,880 bytes)
6. mory access (score: 1): Author: Scott Feldman <sfeldma@xxxxxxxxx>; Date: Sat, 04 Dec 2004 16:00:01 -0800; or the user space, but both kernel module and user prog; /archives/netdev/2004-12/msg00059.html (8,998 bytes)
7. ward_alloc) (score: 1): Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>; Date: Sun, 05 Dec 2004 00:37:19 -0800; . Without the patch we need to find two expensive machi; /archives/netdev/2004-12/msg00063.html (10,474 bytes)
8. omisation (revised) (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Mon, 6 Dec 2004 10:42:39 +0100; loopback address I agree with Stephen' conclusion, that the cost of the MD4 gets lost in the noise. I did not measure the variance, since this probably descri; /archives/netdev/2004-12/msg00103.html (9,198 bytes)
9. ress family problem (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Mon, 6 Dec 2004 12:51:51 +0100; it fixes. You need to do a lot more testing to verify it doesnt. Actually you should probably fix whats being invoked for the ifa messages when PF_UNSPEC is se; /archives/netdev/2004-12/msg00108.html (9,299 bytes)
10. e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Sat, 04 Dec 2004 00:25:39 +0100; Hello, I have a problem with an Intel Pro/1000 MT 4-port card in a Supermicro (non-HT) Pentium 4 system using RHEL3 (2.4.21 kernel "the RH way") with the e1000 driver (I tried both the version suppli; /archives/netdev/2004-12/msg01002.html (9,048 bytes)
11. Re: e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Francois Romieu <romieu@xxxxxxxxxxxxx>; Date: Sat, 4 Dec 2004 01:59:46 +0100; Jos Vos <jos@xxxxxx> : [misbehaving multi port e1000] <I am not the e1000 maintainer> The error code for the ioctl most probably comes through e1000_open -> request_irq That + (2) + SMP suggests an i; /archives/netdev/2004-12/msg01003.html (9,115 bytes)
12. Re: e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Sat, 4 Dec 2004 02:14:44 +0100; IIRC ACPI is disabled in the BIOS (not sure), but I'm using a RHEL3 2.4.21 kernel that does not support ACPI at all (due to the RH patches rebuilding the kernel with ACPI enbabled does not work anymo; /archives/netdev/2004-12/msg01004.html (9,620 bytes)
13. Re: e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Francois Romieu <romieu@xxxxxxxxxxxxx>; Date: Sat, 4 Dec 2004 13:03:28 +0100; Jos Vos <jos@xxxxxx> : [...] 1 - Imho people at RedHat/wherever need more details (chipset, mobo, dmesg, lspci -vx, 2.4.21 savor ?). 2 - Testing recent 2.6.x will provide a different datapoint and a; /archives/netdev/2004-12/msg01007.html (9,314 bytes)
14. Re: e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Sat, 4 Dec 2004 18:20:13 +0100; Mainboard: Supermicro P4SCT+ Output of lspci -vx: attached Red Hat kernel: 2.4.21-20.EL Yes, ok, I might install RHEL4 beta or Fedora Core 3 on it next week and see how that works. -- -- Jos Vos <jos; /archives/netdev/2004-12/msg01008.html (10,071 bytes)
15. Re: e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Scott Feldman <sfeldma@xxxxxxxxx>; Date: Sat, 04 Dec 2004 16:00:01 -0800; The 4-port card has two 82546 dual-port controllers behind a PCI-X bridge. Your symptoms suggest interrupt routing didn't get setup correctly for the controllers behind the bridge. I've seen more tha; /archives/netdev/2004-12/msg01010.html (9,064 bytes)
16. Re: e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>; Date: Sun, 05 Dec 2004 00:37:19 -0800; I have a problem with an Intel Pro/1000 MT 4-port card in a Supermicro (non-HT) Pentium 4 system using RHEL3 (2.4.21 kernel "the RH way") with the e1000 driver (I tried both the version supplied by; /archives/netdev/2004-12/msg01014.html (10,481 bytes)
17. Re: e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Mon, 6 Dec 2004 10:42:39 +0100; Unfortunately, the latest BIOS for the MB is already installed :-(. -- -- Jos Vos <jos@xxxxxx> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6; /archives/netdev/2004-12/msg01054.html (9,338 bytes)
18. Re: e1000 driver problem with Intel Pro/1000 MT adapter (score: 1): Author: Jos Vos <jos@xxxxxx>; Date: Mon, 6 Dec 2004 12:51:51 +0100; I just a prerelease of their next BIOS from Supermicro and that seems to solve the problem! I still have to boot the SMP kernel to get APIC working, in UP mode incoming packets are not seen, but I ca; /archives/netdev/2004-12/msg01059.html (9,439 bytes)

Current List: 1 - 18
Page: [1]