From owner-freebsd-net Sun Mar 25 9:52:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 5F9B337B718 for ; Sun, 25 Mar 2001 09:52:51 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f2PHp2506960; Sun, 25 Mar 2001 12:51:03 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <001301c0b554$1f87aec0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Ed Wynn" , References: Subject: Re: D-Link problem Date: Sun, 25 Mar 2001 12:50:46 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Okay, I've managed to get the debug kernel built and save the core file. > I'll include the output of some basic debugging below. If there's anything > else that would be helpful, let me know. The D-Link driver disk includes C > source for a Linux driver, so when the problem gets narrowed down, I or > someone more familiar with the code might be able to use this to determine > the correct settings. > > First, though, I should have included this before, but I didn't notice it > until much later. Here's an excerpt from the boot messages that gets shown > before the crash. During a GENERIC boot: > > rl0: port 0xd800-0xd8ff > mem 0xe5800000-0xe58000ff irq 11 at device 11.0 on pci0 > rl0: Ethernet address xx:xx:xx:xx:xx:xx > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: no media present I'd change the device naming in pci/if_rl.c to identify the card vendor & model (D-Link 538TX/R, in the style of the Accton MPX driver) rather than the card chipset (which would be used for a generic card). > It then proceeds through the normal boot sequence to the crash. Here's the > gdb log I threatened above. Warning: it's long. [snip] Sorry 'bout that. I was working on the assumption that the driver was working properly, and was just dying during userland init (ifconfig). The "rlphy0: no media present" line tells us that the driver isn't 100% healthy, at least with this card. It would be interesting to see what the result of the PHY_READ call is (just before the 'no media present' printf line). It could be that the D-Link card is encoding media types differently (which means that BMSR_MEDIAMASK needs updating), or is simply really telling us nothing. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message