Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 100522
| Summary: | (ACPI) acpi code breaks e100 and eepro100 drivers | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux Beta | Reporter: | Nathan G. Grennan <redhat-bugzilla> | ||||||||||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | medium | ||||||||||||||
| Version: | beta1 | CC: | acpi-bugzilla, pfrields, riel, wtogami | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | All | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2003-10-28 16:25:15 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Bug Depends On: | |||||||||||||||
| Bug Blocks: | 100643 | ||||||||||||||
| Attachments: |
|
||||||||||||||
Can you post the output of 'dmidecode' for your system? That's /usr/sbin/dmidecode -- run as root. Please also post the output of /usr/sbin/acpidmp Created attachment 93223 [details]
dmidecode output
Created attachment 93224 [details]
acpidmp output
I also tried acpi=nopci while I was at it and it didn't help. Created attachment 93243 [details]
acpidmp output
Created attachment 93244 [details]
dmidencode output
realtek 8139 module
Comment on attachment 93243 [details]
acpidmp output
realtek 8139
I don't have Gigabyte/AMD/Award or Abit/AMD/Phoenix systems handy, but severn on my Intel/Intel/AMI boxes seem to talk to e100 just fine. Is it possible to get the dmesg, /proc/interrupts, and ifconfig output for both the success and failure cases? Created attachment 93841 [details]
ACPI VT86/Award PCI interrupt patch.
This patch has fixed the ACPI interrupt problem for similar systems.
Please try applying it to a copy of your Severn BETA1 kernel to
see if works for you too:
~/src/linux-2.4.21-20.1.2024.2.1.nptl> patch -Np1 < ./pci_link-severn.patch
patching file arch/i386/kernel/io_apic.c
patching file arch/i386/kernel/mpparse.c
patching file drivers/acpi/pci_irq.c
patching file drivers/acpi/pci_link.c
patching file include/acpi/acpi_drivers.h
Dave, please take a look at this patch, thanks. AFAICT, we have an improved variant of this patch already merged since test2 Personally, I'm convinced this is fixed. I can't repeat any problems with or without acpi=on using e100 or e1000 on several boxes. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.11 (X11; Linux i686; U;) Gecko/20030720 Description of problem: I loaded Serven on my workstation at work. After booting up I found though there were no errors and the ip information was set correctly my network didn't work. I tried didn't cables, a crossover cable to another computer, e100 and eepro100 drivers. Finally I added acpi=off apci=off to the kernel during boot. Suddenly the network was working again. Next I tried just apci=off, and it didn't work again. Then I tried acpi=off by itself and it worked. Version-Release number of selected component (if applicable): kernel-2.4.21-20.1.2024.2.1.nptl How reproducible: Always Steps to Reproduce: 1. Load Serven 2. Install a Intel 10/100 card 3. Configure network with netconfig or neat 4. modprobe e100 or modprobe eepro100 5. service network start Actual Results: Everything looks good, but networking doesn't work Expected Results: Everything looks good, and networking works Additional info: