Date: Mon, 1 Feb 2021 15:46:38 -0800 From: Mark Millard <marklmi@yahoo.com> To: John-Mark Gurney <jmg@funkthat.com> Cc: freebsd-ppc <freebsd-ppc@freebsd.org> Subject: Re: Expected issue? Old PowerMac G5 [...] vs. USB [...] [RealTek EtherNet] devices (...) Message-ID: <38B76FA1-2564-4EE0-ADAE-D12F693358EB@yahoo.com> In-Reply-To: <20210201222854.GV31099@funkthat.com> References: <E79AA0EA-FAAE-412E-BB26-A66D9AB00AB8@yahoo.com> <EF3494BA-2B9C-43A5-931F-45313B3BDA7D@yahoo.com> <20210201194702.GU31099@funkthat.com> <1C53A656-75ED-4E7C-9FB0-6C605BCDEC14@yahoo.com> <20210201222854.GV31099@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Feb-1, at 14:28, John-Mark Gurney <jmg at funkthat.com> wrote: > Mark Millard wrote this message on Mon, Feb 01, 2021 at 13:34 -0800: >> On 2021-Feb-1, at 11:47, John-Mark Gurney <jmg at funkthat.com> = wrote: >>=20 >>> Mark Millard wrote this message on Sun, Jan 31, 2021 at 13:45 -0800: >>>> . . . >>=20 >> I'm working on seeing if I can get Firewire/dcons based >> access going in hopes of getting more evidence that way. >>=20 >> I hope that such can be done via a 32-bit PowerMac G4 >> against the 64-bit PowerMac G5: it looks like the only >> other G5 no longer can reliably boot (overheating that >> fast now). >=20 > I think that it should just work.. I haven't looked at the dcons code, > but IIRC, it should... If not, it should be easy to fix to make it > work.. I've got a basic telnet/dconschat going, allowing me to copy/paste text reproted via telnet output. I've replied earlier with some information gathered. I'll use some of that background to respond to later questions below. I'll presume context from the prior reply. >>>> So I tried a non-RealTek USB3 capable EtherNet device, both >>>> with and without hw.usb.xhci.use_polling=3D1 : >>>>=20 >>>> axge0 numa-domain 0 on uhub4 >>>> axge0: <NetworkInterface> on usbus4 >>>> miibus1: <MII bus> numa-domain 0 on axge0 >>>> rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 3 on = miibus1 >>>> rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, = 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, = 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow >>>> ue0: <USB Ethernet> on axge0 >>>> ue0: Ethernet address: 00:05:1b:af:1a:21 >>>> ue0: link state changed to DOWN >>>> ue0: link state changed to UP >>>>=20 >>>> So far it seems to be working just fine. I'm using it >>>> without hw.usb.xhci.use_polling=3D1 . >>>=20 >>> Is the axge a USB3 or USB3 device? The driver attached to both... >>=20 >> The axge, like all my USB Ethernet devices, is USB3 capable but >> is supposed to support use in USB2 contexts. The PowerMac, of >> course, is old and only has USB2. >=20 > Then why bother w/ xhci? Since that should apply only to USB3 > controllers... If your mac isn't USB3 compatible, shouldn't be > detected/probed/used, and you should only have ehci... I've no clue why it operates as it does. But I have example boots for ure0 also working just fine and one where axge0 had the problem. So, both sometimes work just fine, sometimes not. The problem seems to always be at the initial probing, be the device already plugged in a power up vs. plugged in later. If that initial activity works, then the device is generally operational. (I've not tried plug-in/unplug/plug-in/unplug sequences.) > This is why I was puzzled, tweaking xhci implies that the system is > USB3 capable... I'm not aware that I did anything special, other than just plugging in the devices. My kernel configurations are based on GENERIC64 (via includes), with some overrides but not of usb things. > (if xhci changes USB2 behavior, then it needs to be renamed)... No clue. >>> [...] >>>=20 >=20 > Have you verified that it works w/ other operating systems on the Mac? > Could it be that the device itself isn't compatible w/ the USB2 > controller on the mac? I have example boots for ure0 also working just fine and one where axge0 had the problem, all the same FreeBSD 14 build on the same PowerMac G5, just rebooted and trying again. I take that both devices sometimes work just fine as evidence that a USB2 controller compatibility problem in the PowerMac is unlikely for both devices. > Have you tried to add in a USB controller card and use that instead of > the onboard USB controller? No. I've no access to such a separate card as stands. (And there is the "sometimes works" evidence as well.) >>> I assume it was a hard lock enough that you were unable to break = into >>> ddb? Without more information, it will be impossible for me to = debug >>> this. >>=20 >> Yep. I CC'd you mostly so if if any other similar reports >> came in that you would know of my context's prior failure. >=20 > Yeah, I haven't heard of any, (though I've only worked on it for less > than a year)... >=20 >> I am working on seeing if I can get Firewire/dcons to operate >> in hopes of getting some information about the crash. If >> I get that going and get some more information, I'll report >> it with you CC'd again. >=20 > Yeah, dcons is a good choice, and the good thing is that short of a > complete system bus crash, you'll be able to at least get the latest > logs off of the system... And . . . I just got the telnet login console going in the telnet/dconschat so I'm no longer restricted to the display's console for all input. I'm not familiar with the Firewire/dcons context, so read a little, try a little, read . . . =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38B76FA1-2564-4EE0-ADAE-D12F693358EB>