> On Dec 13, 2022, at 4:38 PM, Brook Milligan <brook%nmsu.edu@localhost> wrote: > >> On Dec 13, 2022, at 3:07 PM, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote: >> >> On Tue, Dec 13, 2022 at 11:55:31AM -0700, Brook Milligan wrote: >>> I have booted a NetBSD 9.99.99 XEN3_DOM0 kernel, but it does not detect a carrier on the network interface (ixg). A GENERIC kernel from the same sources booted normally detected the carrier just fine and the interface works well. >>> >>> Are there any suggestions on where to look for the problem? >> >> Look at differences in interrupt setup. I remember fixing some code >> in this area but I can't remember if it was before or after 9.99.99 Here is the result on the dom0 9.99.108 kernel of # ifconfig ixg0 ixg0: flags=0x8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500 capabilities=0x7ff80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx> capabilities=0x7ff80<TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Rx> capabilities=0x7ff80<TCP6CSUM_Tx,UDP6CSUM_Rx,UDP6CSUM_Tx,TSO6> enabled=0 ec_capabilities=0xf<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWFILTER> ec_enabled=0x7<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU> address: a0:42:3f:4b:f4:26 media: Ethernet autoselect (none) status: no carrier inet6 fe80::a242:3fff:fe4b:f426%ixg0/64 flags 0x8<DETACHED> scopeid 0x1 The GENERIC kernel dectects a carrier on the same interface. I am also attaching the diffs between the /var/run/dmesg.out from the netbsd-9.99.99 kernel (which works) (-) and the netbsd-9.99.108 dom0 (+) which does not, grepped for ixg0. I’m not sure what to make of these differences or whether I should be looking elsewhere. Thanks for your help. Cheers, Brook
Attachment:
ixg0.diff
Description: Binary data