| To: | Jos Vos <jos@xxxxxx> |
|---|---|
| Subject: | Re: e1000 driver problem with Intel Pro/1000 MT adapter |
| From: | Francois Romieu <romieu@xxxxxxxxxxxxx> |
| Date: | Sat, 4 Dec 2004 01:59:46 +0100 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <200412032325.iB3NPdG04693@xos037.xos.nl> |
| References: | <200412032325.iB3NPdG04693@xos037.xos.nl> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
Jos Vos <jos@xxxxxx> :
[misbehaving multi port e1000]
> Any suggestions how to solve this are welcome. I can provide more
> information if needed.
<I am not the e1000 maintainer>
The error code for the ioctl most probably comes through
e1000_open
-> e1000_up
-> request_irq
That + (2) + SMP suggests an irq routing issue due to a broken acpi
table ("suggests").
I would compile a (monolithic) recent 2.6.x to see its log and
give a look at http://acpi.sourceforge.net/dsdt/index.php (once the
ticket is opened at http://bugzilla.redhat.com of course :o) )
--
Ueimor
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | e1000 driver problem with Intel Pro/1000 MT adapter, Jos Vos |
|---|---|
| Next by Date: | Re: e1000 driver problem with Intel Pro/1000 MT adapter, Jos Vos |
| Previous by Thread: | e1000 driver problem with Intel Pro/1000 MT adapter, Jos Vos |
| Next by Thread: | Re: e1000 driver problem with Intel Pro/1000 MT adapter, Jos Vos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |