On 2/20/06, Russell Johnson <[EMAIL PROTECTED]> wrote: > I can't seem to find an archive of this list anywhere so I'm posting what > might be a repeated question.
http://marc.theaimsgroup.com/?l=linux-netdev BTW the e1000-devel _at_ lists.sf.net mailing list is an excellent place for very e1000 specific questions. You're not likely to get a lot of help on the main linux mailing lists if you haven't reproduced this on a kernel.org kernel. > I'm finding issues using ACPI and the E1000 driver 6.3.9. I understand this > to be a known issue but would like to find out more information so that I > can make a proper decision on how to configure my kernel. The E1000 driver > only mentions "If ACPI is turned on in the kernel, dual port adapters may > not work. This is due to a limitation in ACPI. Currently, this affects all > new versions of SUSE.". Are you running a uniprocessor or smp version of the kernel? The ACPI problems if any seem to always be related to interrupt routing. Simply upgrading to a recent kernel.org kernel may fix your problem. Sometimes upgrading your BIOS may actually help get the interrupt routing right as well. > I'm curious if anyone knows why this note indicates it only affects SUSE? > This might indicate that I can change my distribution and fix this issue. > If that is so I'd like to understand what to change. If you're running a SUSE version based on a 2.6.5 kernel that could have some relationship due to the age of the ACPI code in that kernel. > The note makes no mention of a specific symptom or mode of failure. My > system will load the e1000 driver and properly configure the first NIC but > will hang hard when configuring the second NIC. Is this the mode of failure > noticed by others? > > Do either of the 'acpi=ht' or 'acpi=noirq' options work around this issue? > They seem to work for me but I'd rather not find out later that they don't > work around the issue completely. Once you get interrupts working its likely to stay that way, its generally an all or nothing thing. If you've got it working, and are satisfied, then I would suggest sticking with it unless you're feeling like chasing down any issues that may come from changing more things. Jesse - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
