Date: Wed, 4 Oct 2000 13:29:21 -0700 (MST) From: John Reynolds~ <jreynold@sedona.ch.intel.com> To: Warner Losh <imp@village.org> Cc: stable@freebsd.org Subject: Re: breakage with two ed network devices Message-ID: <14811.37665.447008.535024@hip186.ch.intel.com> In-Reply-To: <200010021625.KAA11862@harmony.village.org> References: <14808.45618.368338.347768@hip186.ch.intel.com> <14804.65209.8908.316746@hip186.ch.intel.com> <200009292130.PAA03763@harmony.village.org> <200010021625.KAA11862@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[ On Monday, October 2, Warner Losh wrote: ]
>
> Yes. It works. I have one the follwoing in my dmesg output:
>
> ed0 at port 0x280-0x29f iomem 0xd8000-0xd9fff irq 10 on isa0
> ed0: address 00:00:c0:79:2a:f0, type SMC8416T (16 bit)
> ed1 at port 0x300-0x31f iomem 0xd0000 irq 5 on isa0
> ed1: address 00:00:1b:1e:23:dc, type NE2000 (16 bit)
>
> So I'm not sure what's going on..
>
OK. I've finally had a chance to start figuring out why 4.1.1 kernels don't
see both of my ed devices. Here's what I've done thus far:
1) I took the 4.1.1-RELEASE branded files (all of them) in sys/dev/ed and
moved those into my 4.1-RELEASE sys/dev/ed directory. Thereby replacing
the 4.1-RELEASE code with 4.1.1-RELEASE code.
2) I compiled a kernel and installed it.
3) Booted the kernel manually (as I installed it under a different name).
Now, the ed0 and ed1 devices probe and attach correctly! So, in my layman's
mind that seems to rule out the rather substantial MFC of the ed driver from
4.1-RELEASE to 4.1.1-RELEASE as the culprit--seeing as how I had a 4.1-RELEASE
kernel with just the bits from the 4.1.1-RELEASE ed driver in there.
If that theory is true, then something else has gone south in the kernel from
4.1 to 4.1.1 which is causing my problem.
The problem is, I don't know where to look from here. What could be causing
the ed0 device to not probe? I'm certainly willing to incrementally add
changes to a 4.1-R kernel until the problem shows up (so that we can then
figure out what it is and nail it) but I need some suggestions about which
areas to look at.
My normal dmesg output for these devices is:
ed0 at port 0x2c0-0x2df iomem 0xd8000 irq 15 on isa0
ed0: address 00:40:05:6e:67:c0, type NE2000 (16 bit)
ed1 at port 0x340-0x35f iomem 0xd8000 irq 9 on isa0
ed1: address 00:40:05:6e:67:9c, type NE2000 (16 bit)
and the kernel config for them is:
device ed0 at isa? port 0x2c0 irq 15 iomem 0xd8000
device ed1 at isa? port 0x340 irq 9 iomem 0xd8000
The cards are two Linksys Ether16 ISA cards in a BX based ABit BP6
motherboard. Warner seems to not have the problem but he's got different cards
for ed0 and ed1.
-Jr
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds WCCG, CCE, Higher Levels of Abstraction |
| Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 |
| jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14811.37665.447008.535024>