From: Thomas Backlund <tmb@iki.fi>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
Juan Quintela <quintela@mandrakesoft.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3c59x gives HWaddr FF:FF:...
Date: Sun, 30 Mar 2003 13:53:52 +0300 [thread overview]
Message-ID: <021301c2f6aa$ae726140$9b1810ac@xpgf4> (raw)
In-Reply-To: 1049019577.597.6.camel@teapot
----- Original Message -----
From: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
To: "Juan Quintela" <quintela@mandrakesoft.com>
Cc: "Thomas Backlund" <tmb@iki.fi>; "J.A. Magallon" <jamagallon@able.es>;
"LKML" <linux-kernel@vger.kernel.org>
Sent: Sunday, March 30, 2003 1:19 PM
Subject: Re: 3c59x gives HWaddr FF:FF:...
| On Sun, 2003-03-30 at 04:21, Juan Quintela wrote:
| > In my experience, that bug is related with acpi. In a kernel compiled
| > without acpi, the card works perfectly, in a kernel compiled with acpi
| > it depend on the phase of the moon and similar things :(
|
| I'm not using ACPI but APM and, on a vanilla 2.4.20 kernel, that's what
| I'm seeing with my 3CCFE575CT on my kernel dmesg ring:
|
| <snip>
| Yenta IRQ list 08d8, PCI irq5
| Socket status: 30000020
| Yenta IRQ list 08d8, PCI irq10
| Socket status: 30000006
| cs: cb_alloc(bus 6): vendor 0x10b7, device 0x5257
| PCI: Failed to allocate resource 0(1000-2c3) for 06:00.0
| PCI: Enabling device 06:00.0 (0000 -> 0003)
| <snip>
| eth0: command 0x5800 did not complete! Status=0xffff
| eth0: command 0x2804 did not complete! Status=0xffff
| <snip>
|
| However, Alan Cox patches for 2.4.20 and Red Hat's linux kernel both
| seem to work OK... I think it's related to PCI resource assignment.
|
Have you tried with pci=noapic?
When I used the 3c59x on my integrated 3Com (on Asus nForce2 board), it
always got to the point that it got the IP, but no traffic was going
through...
(same thing happends with the 3Com 3c90x driver...)
This was solved by either booting with acpi=off or pci=noapic...
Thomas
next prev parent reply other threads:[~2003-03-30 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 14:51 3c59x gives HWaddr FF:FF: J.A. Magallon
2003-03-28 15:57 ` Eric Weigle
2003-03-28 20:48 ` Andrew Morton
2003-03-28 23:05 ` J.A. Magallon
2003-03-28 23:16 ` Andrew Morton
2003-03-29 0:46 ` J.A. Magallon
2003-03-29 17:12 ` Thomas Backlund
2003-03-29 19:45 ` Felipe Alfaro Solana
2003-03-30 2:21 ` Juan Quintela
2003-03-30 10:19 ` Felipe Alfaro Solana
2003-03-30 10:53 ` Thomas Backlund [this message]
2003-03-30 11:16 ` Felipe Alfaro Solana
2003-03-31 19:09 ` Bas Vermeulen
2003-03-29 0:29 ` Felipe Alfaro Solana
2003-03-29 0:44 ` Andrew Morton
2003-03-29 1:23 ` Felipe Alfaro Solana
-- strict thread matches above, loose matches on Subject: below --
2003-03-28 16:13 Alex Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='021301c2f6aa$ae726140$9b1810ac@xpgf4' \
--to=tmb@iki.fi \
--cc=felipe_alfaro@linuxmail.org \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=quintela@mandrakesoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox