* How to begin debugging ACPI/network driver interrupt problem?
@ 2003-07-09 17:34 Kevin P. Fleming
0 siblings, 0 replies; only message in thread
From: Kevin P. Fleming @ 2003-07-09 17:34 UTC (permalink / raw)
To: acpi-support, netdev
I've got a system here using an MSI KT266-based motherboard that's
been running 2.5.X successfully for months now. However, 2.5.73/74
have introduced a problem that (so far) I have only been able to cure
by either not compiling in ACPI or using acpi=off on the kernel
command line.
The system three NICs:
eth0 is a National Semiconductor DP83815
eth1 is a National Semiconductor DP83820
eth2 is a Lite-On 82C168
All three NICs work fine. However, on the newer kernels, with ACPI
compiled in, during initialization of eth0 the kernel generates "IRQ
17 and nobody cared!" messages and disables IRQ 17, which causes eth0
to be useless :-)
With older kernels, or ACPI not turned on, eth0 still gets assigned
IRQ 17, and works just fine. IRQ 17 is not shared with any other devices.
I don't think I can handle the additional message traffic of these two
mailing lists, so I haven't subscribed... If anyone can suggest a
course of action for how to debug this problem, please cc me on any
responses.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-07-09 17:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-07-09 17:34 How to begin debugging ACPI/network driver interrupt problem? Kevin P. Fleming
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).