From: Andi Kleen <ak@suse.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: kl@vsen.dk, linux-kernel@vger.kernel.org
Subject: Re: [Bug 1428] New: 3c59x won't work at all with 2.6.0-test kernels
Date: 27 Oct 2003 16:24:16 +0100 [thread overview]
Message-ID: <p73fzheaelb.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <600810000.1067231679@[10.10.2.4].suse.lists.linux.kernel>
"Martin J. Bligh" <mbligh@aracnet.com> writes:
> http://bugme.osdl.org/show_bug.cgi?id=1428
>
> Summary: 3c59x won't work at all with 2.6.0-test kernels.
> Kernel Version: 2.6.0-test4-mmX to 2.6.0-test8-mm1
> Status: NEW
> Severity: blocking
Does not deserve a blocking.
> Owner: jgarzik@pobox.com
> Submitter: kl@vsen.dk
>
>
> Distribution: Gentoo Linux
> Hardware Environment: IBM Thinkpad X20 - miniPCI 3com network:
> lspci with 2.4.22 kernel:
> 00:0a.0 Ethernet controller: 3Com Corporation 3c556B Hurricane CardBus (rev 20)
>
> Software Environment:
> glibc-2.3.2, gcc-3.2.3 - anything else?
> Problem Description:
> My 3c59x miniPci network card won't work at all with 2.6.0-test kernels.I think
> I've seen it work once, with an old 2.6.0-test kernel, but I'm not sure, and
> I've tried all the way back to 2.6.0-test3, and can't reproduce it (working that
> is).
> the Hardware mac address is set to all FF's on 2.60. ifconfig works fine - I
> just can't ping anything.
>
> with 2.4.22 it all works like a charm.
>
> Steps to reproduce:
> compile 2.6.0-testX with 3c59x as module or built-in.
3c59x works fine for me in 2.6.0test9
Most likely the user has some problems with interrupt routing.
I would try with pci=noacpi or acpi=off or disable IO-APIC support.
-Andi
next parent reply other threads:[~2003-11-18 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <600810000.1067231679@[10.10.2.4].suse.lists.linux.kernel>
2003-10-27 15:24 ` Andi Kleen [this message]
2003-10-27 5:14 Martin J. Bligh
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=p73fzheaelb.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=kl@vsen.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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
all inboxes | Powered by JetHome®