Hello, I was hoping it could have been some "bad timing" with the snapshots back then but the problem is still there with the latest snapshot: this ethernet card cannot work under -current, but works fine under 6.3, and used to work under -current up to july-august (I'm sorry I can't be more exact).
The dmesg from the **working** (6.3) box: bge0 at pci3 dev 0 function 0 "Broadcom BCM5761" rev 0x10, BCM5761 A1 (0x5761100), APE firmware DASH 1.54.1.0bge0: APE event 0x00020510 send timed out brgphy0 at bge0 phy 1: BCM5761 10/100/1000baseT PHY, rev. 0 Any help on how I can provide further info that might be useful..? Problem description in the original message: On Sat, Sep 8, 2018 at 2:45 PM Thanos Tsouanas <[email protected]> wrote: > So, my box was working fine from a relatively recent snapshot (first > days of Aug). Then I upgraded to a snapshot of Sep 5th, and I can no > longer connect to my local network: > dhclient responds with "got link" but ends with "no lease", and bge0 > has no IP assigned to it. > Even if I assign inet IP, netmask, and gateway manually, there is no > connectivity. > I cannot ping my gateway (or anything else, for that matter). > On the other hand, booting with the miniroot63.fs and exiting to > shell, indeed everything works fine. > I tried the miniroot64.fs's of 5/sep and the most recent one of 7/sep, > and both behave the same way. I believe this is a card-specific > problem because the same snapshots work fine on a different machine on > the same network (my laptop for example). > > The interface is a bge, and I do get some error messages from the kernel: > > APE event 0x... send timed out > > But I've always had those error messages with this particular ethernet > card and never experienced any problems, and when I boot on the > miniroot63.fs, the same messages appear, but the interface is still > working fine. > > Any help on how to debug this / or how to provide more useful > information, would be appreciated! Cheers -- Thanos Tsouanas http://www.tsouanas.org/
