• watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd:1] (2/2)

    From Dennis Clarke@21:1/5 to Mike Tremaine on Sat Mar 13 20:40:01 2021
    [continued from previous message]

    /dev/sda2: Clearing orphaned inode 658310 (uid=0, gid=0, mode=0100755, size=1071888)
    /dev/sda2: Clearing orphaned inode 661016 (uid=0, gid=0, mode=0100755, size=258912)
    /dev/sda2: Clearing orphaned inode 6610[ 89.995218] crc32c_sparc64:
    sparc64 crc32c opcode not available.
    14 (uid=0, gid=0, mode=0100755, size=159000)
    /dev/sda2: Clearing orphaned inode 661000 (uid=0, gid=0, mode=0100755, size=1702256)
    /dev/sda2: Clearing orphaned inode 654542 (uid=0, gid=0, mod[
    90.284993] EXT4-fs (sda2): mounted filesystem with ordered data mode.
    Opts: (null)
    e=0100644, size=2584584)
    /dev/sda2: Clearing orphaned inode 663150 (uid=0, gid=0, mode=0100644, size=445600)
    /dev/sda2: Clearing orphaned inode 654417 (uid=0, gid=0, mode=0100644, size=715000)
    /dev/sda2: Clearing orphaned inode 663146 (uid=0, gid=0, mode=0100644, size=227768)
    /dev/sda2: Clearing orphaned inode 654386 (uid=0, gid=0, mode=0100644, size=808616)
    /dev/sda2: Clearing orphaned inode 657782 (uid=0, gid=0, mode=0100755, size=65000)
    /dev/sda2: Clearing orphaned inode 657778 (uid[ 90.899027] Not
    activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
    =0, gid=0, mode=0100600, size=72312)
    /dev/sda2: Clearing orphaned inode 656102 (uid=0, gid=0, mode=0100644, size=368408)
    /dev/sda2: Clearing orphaned inode 656113 (uid=0, gid=0, mode=0100644, size=165480)
    /dev/sda2: Clearing orphaned inode 657495 (uid=0, gid=0, mode=0100644, size=36488)
    /dev/sda2: Clearing orphaned inode 655748 (uid=0, gid=0, mode=0100644, size=321680)
    /dev/sda2: Clearing orphaned inode 525606 (uid=0, gid=0, mode=0100644, size=391565)
    /dev/sda2: clean, 47529/1013824 files, 629339/4049080 blocks
    done.
    done.
    Begin: Running /scripts/local-bottom ... done.
    Begin: Running /scripts/init-bottom ... done.
    [ 92.245962] systemd[1]: System time before build time, advancing clock.
    [ 92.581158] systemd[1]: Inserted module 'autofs4'
    [ 92.948572] systemd[1]: systemd 247.3-1 running in system mode. (+PAM
    +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
    +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD -SECCOMP +BLKID +ELFUTILS +KMOD
    +IDN2 -IDN +PCRE2 default-hierarchy=unified)
    [ 93.242159] systemd[1]: Detected architecture sparc64.

    Welcome to Debian GNU/Linux bullseye/sid!

    [ 93.407914] systemd[1]: Set hostname to <ceres>.
    [ 96.605030] systemd[1]: Queued start job for default target Rescue Mode.
    [ 96.704166] systemd[1]: Created slice system-modprobe.slice.
    [ OK ] Created slice system-modprobe.slice.
    [ 96.858820] systemd[1]: Created slice system-systemd\x2dfsck.slice.
    [ OK ] Created slice system-systemd\x2dfsck.slice.
    [ 97.032609] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    [ OK ] Started Dispatch Password b&ts to Console Directory Watch.
    [ 97.245493] systemd[1]: Set up automount Arbitrary Executable File
    Formats File System Automount Point.
    [ OK ] Set up automount Arbitraryb&s File System Automount Point.
    [ 97.476173] systemd[1]: Reached target Local Encrypted Volumes.
    [ OK ] Reached target Local Encrypted Volumes.
    [ 97.633471] systemd[1]: Listening on fsck to fsckd communication Socket.
    [ OK ] Listening on fsck to fsckd communication Socket.
    [ 97.817886] systemd[1]: Listening on Journal Audit Socket.
    [ OK ] Listening on Journal Audit Socket.
    [ 97.969139] systemd[1]: Listening on Journal Socket (/dev/log).
    [ OK ] Listening on Journal Socket (/dev/log).
    [ 98.137336] systemd[1]: Listening on Journal Socket.
    [ OK ] Listening on Journal Socket.
    [ 98.285795] systemd[1]: Listening on udev Control Socket.
    [ OK ] Listening on udev Control Socket.
    [ 98.436955] systemd[1]: Listening on udev Kernel Socket.
    [ OK ] Listening on udev Kernel Socket.
    [ 98.595161] systemd[1]: Mounting Huge Pages File System...
    Mounting Huge Pages File System...
    [ 98.755808] systemd[1]: Mounting POSIX Message Queue File System...
    Mounting POSIX Message Queue File System...
    [ 98.944046] systemd[1]: Mounting Kernel Debug File System...
    Mounting Kernel Debug File System...
    [ 99.129496] systemd[1]: Mounting Kernel Trace File System...
    Mounting Kernel Trace File System...
    [ 99.312949] systemd[1]: Starting Set the console keyboard layout...
    Starting Set the console keyboard layout...
    [ 99.491286] systemd[1]: Starting Create list of static device nodes
    for the current kernel...
    Starting Create list of stb&odes for the current kernel...
    [ 99.716828] systemd[1]: Starting Load Kernel Module configfs...
    Starting Load Kernel Module configfs...
    [ 99.901465] systemd[1]: Starting Load Kernel Module fuse...
    [ 100.084072] fuse: init (API version 7.32)
    Starting Load Kernel Module fuse...
    [ 100.242945] systemd[1]: Condition check resulted in Set Up Additional
    Binary Formats being skipped.
    [ 100.479937] systemd[1]: Condition check resulted in File System Check
    on Root Device being skipped.
    [ 100.757612] systemd[1]: Starting Journal Service...
    Starting Journal Service...
    [ 101.057538] systemd[1]: Starting Load Kernel Modules...
    Starting Load Kernel Modules...
    [ 101.416276] systemd[1]: Starting Remount Root and Kernel File Systems...
    Starting Remount Root and Kernel File Systems...
    [ 101.883390] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
    [ 101.973534] systemd[1]: Starting Coldplug All udev Devices...
    Starting Coldplug All udev Devices...
    [ 102.326974] systemd[1]: Started Journal Service.
    [ OK ] Started Journal Service.
    [ OK ] Mounted Huge Pages File System.
    [ OK ] Mounted POSIX Message Queue File System.
    [ OK ] Mounted Kernel Debug File System.
    [ OK ] Mounted Kernel Trace File System.
    [ OK ] Finished Create list of stb& nodes for the current kernel.
    [ OK ] Finished Load Kernel Module configfs.
    [ OK ] Finished Load Kernel Module fuse.
    [ OK ] Finished Load Kernel Modules.
    [ OK ] Finished Remount Root and Kernel File Systems.
    Mounting FUSE Control File System...
    Mounting Kernel Configuration File System...
    Starting Flush Journal to Persistent Storage...
    Starting Load/Save Random Seed...
    Starting Apply Kernel Variables...
    Starting 104.060008] systemd-journald[174]: Received client
    request to flush runtime journal.
    9mCreate System Users...
    [ OK ] Finished Set the console keyboard layout.
    [ OK ] Mounted FUSE Control File System.
    [ OK ] Mounted Kernel Configuration File System.
    [ OK ] Finished Load/Save Random Seed.
    [ OK ] Finished Apply Kernel Variables.[ 104.708686]
    systemd-journald[174]: File /var/log/journal/4a727eeed1c9429f860a24d0362f23de/system.journal
    corrupted or uncleanly shut down, renaming and replacing.

    [ OK ] Finished Coldplug All udev Devices.
    [ OK ] Finished Create System Users.
    Starting Create Static Device Nodes in /dev...
    [ OK ] Finished Flush Journal to Persistent Storage.
    [ OK ] Finished Create Static Device Nodes in /dev.
    [ OK ] Reached target Local File Systems (Pre).
    Starting Rule-based Manageb&for Device Events and Files...
    [ OK ] Started Rule-based Manager for Device Events and Files.
    [ 107.307305] /pci@1f,0/pci@1,1/ebus@1/flashprom@10,0: OBP Flash, RD 1fff0000000[100000] WR 1fff0000000[100000]
    [ 107.539485] d7s: 7-Segment Display/pci@1f,0/pci@1,1/ebus@1/display7seg@14,200040 at [ (FLIPPED):0x1fff1200040]
    [ 107.679253] envctrl: Initialized
    [ 107.679267] [gpio 0x72]
    [ 107.722853] [gpio 0x70]
    [ 107.756050] [adc 0x9e]
    [ 108.184098] sd 2:0:0:0: Attached scsi generic sg0 type 0
    [ 108.367514] /pci@1f,0/pci@1,1/ebus@1/flashprom@10,400000: OBP Flash,
    RD 1fff0400000[200000] WR 1fff0400000[200000]
    [* ] (1 of 2) A start job is running forb&aac[ 108.563316] sd
    2:0:1:0: Attached scsi generic sg1 type 0
    [ 108.667460] envctrl: probe of f0088200 failed with error -22

    [** ] (1 of 2) A start job is running forb&aac1-21d8b95f317f (12s /
    1min 30s)
    [*** ] (1 of 2) A start job is running forb&aac1-21d8b95f317f (12s /
    1min 30s)
    [ 109.662860] /pci@1f,0/pci@1,1/ebus@1/flashprom@10,800000: OBP Flash,
    RD 1fff0[ OK ] Found device ST318404LSUN18G.
    [ 110.534730] flash: probe of f0085c48 failed with error -16
    [ OK ] Found device ST318404LSUN18G 4.
    Activating swap /dev/disk/b&314c-428d-a705-de972bb638f2...
    Starting File System Checkb&a339-47c5-aac1-21d8b95f317f...
    [ 113.428077] Adding 992704k swap on /dev/sda4. Priority:-2 extents:1 across:992704k FS
    [ OK ] Activated swap /dev/disk/bb&d-314c-428d-a705-de972bb638f2.
    [ OK ] Found device Happy Meal 10/100 Ethernet [hme].
    [ OK ] Reached target Swap.
    [ OK ] Started File System Check Daemon to report status.
    [ OK ] Finished File System Checkb&2-a339-47c5-aac1-21d8b95f317f.
    Mounting /boot...
    [ 132.217113] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
    [ 133.115924] EXT4-fs (sda1): mounted filesystem without journal. Opts:
    (null)
    [ 133.957017] ext2 filesystem being mounted at /boot supports
    timestamps until 2038 (0x7fffffff)
    [ OK ] Mounted /boot.
    [ OK ] Reached target Local File Systems.
    [ OK ] Started ifup for enp1s1f1.
    Starting Create Volatile Files and Directories...
    [ OK ] Finished Create Volatile Files and Directories.
    Starting Update UTMP about System Boot/Shutdown...
    [ OK ] Finished Update UTMP about System Boot/Shutdown.
    [ OK ] Reached target System Initialization.
    [ OK ] Started Rescue Shell.
    [ OK ] Reached target Rescue Mode.
    Starting Update UTMP about System Runlevel Changes...
    [ 139.956457] enp1s1f1: Link is up using
    [ 139.956480] external
    [ 140.006864] transceiver at
    [ 140.036714] 100Mb/s, Full Duplex.
    [ OK ] Finished Update UTMP about System Runlevel Changes.
    You are in rescue mode. After logging in, type "journalctl -xb" to view
    system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
    to boot into default mode.
    Give root password for maintenance

    root@ceres:~# uname -a
    Linux ceres 5.10.0-1-sparc64 #1 Debian 5.10.5-1 (2021-01-09) sparc64
    GNU/Linux
    root@ceres:~#

    That answers the question about the Linux kernel version as well as all
    the data anyone would want about the hardware. Yes that is a 100Mbit old
    happy meal and I think that was renamed in the boot process to enp1s1f1
    and yes it is working :

    ceres# ip link show
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: enp1s1f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
    state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 08:00:20:c2:46:48 brd ff:ff:ff:ff:ff:ff
    3: enp1s3f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
    DEFAULT group default qlen 1000
    link/ether 08:00:20:c2:46:48 brd ff:ff:ff:ff:ff:ff
    ceres#

    However there must be a bug somewhere because the physical MAC address
    is the same on both interfaces.

    Regardless :

    ceres#
    ceres# ip addr show dev enp1s1f1
    2: enp1s1f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
    state UNKNOWN group default qlen 1000
    link/ether 08:00:20:c2:46:48 brd ff:ff:ff:ff:ff:ff
    inet 172.16.35.61/26 brd 172.16.35.63 scope global enp1s1f1
    valid_lft forever preferred_lft forever
    inet6 2607:fea8:99a0:fab0:a00:20ff:fec2:4648/64 scope global dynamic mngtmpaddr
    valid_lft 172790sec preferred_lft 172790sec
    inet6 fe80::a00:20ff:fec2:4648/64 scope link
    valid_lft forever preferred_lft forever
    ceres#

    SystemD claims we are running just fine :

    ceres#
    ceres# LC_ALL=C systemctl status
    * ceres
    State: running
    Jobs: 0 queued
    Failed: 0 units
    Since: Thu 1970-01-01 00:01:28 GMT; 51 years 2 months ago
    CGroup: /
    |-user.slice
    | `-user-0.slice
    | |-session-1.scope
    | | |- 305 /bin/login -p --
    | | |-1534 -bash
    | | |-1560 systemctl status
    | | `-1561 pager
    | `-user@0.service ...
    | `-init.scope
    | |-1515 /lib/systemd/systemd --user
    | `-1516 (sd-pam)
    |-init.scope
    | `-1 /sbin/init single verbose
    `-system.slice
    |-systemd-udevd.service
    | `-189 /lib/systemd/systemd-udevd
    |-cron.service
    | `-267 /usr/sbin/cron -f
    |-systemd-journald.service
    | `-174 /lib/systemd/systemd-journald
    |-ssh.service
    | `-312 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups
    |-rsyslog.service
    | `-277 /usr/sbin/rsyslogd -n -iNONE
    |-ntp.service
    | `-307 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:112
    |-dbus.service
    | `-269 /usr/bin/dbus-daemon --system --address=systemd:
    --nofork >
    |-system-getty.slice
    | `-getty@tty1.service
    | `-304 /sbin/agetty -o -p -- \x5cu --noclear tty1 linux
    `-systemd-logind.service
    `-290 /lib/systemd/systemd-logind
    ceres#

    OKay so that will get us to the point where I can demonstrate the system
    lockup when I attempt to "upgrade".


    I do not have a Netra handy (but I have one in storage, like everyone
    ;p ). I have an Ultra 5 here so UltraSparc IIi CPU. It does not
    expect this behavior. Any chance the memory module need to be
    reseated?

    As we see in the POST output the ECC memory is healthy.


    I have unstable the mix but as point of reference….

    mgt@xray:~$ uname -a
    Linux xray 5.10.0-3-sparc64 #1 Debian 5.10.13-1 (2021-02-06) sparc64
    GNU/Linux
    mgt@xray:~$ cat /etc/debian_version
    bullseye/sid
    mgt@xray:~$ cat /proc/cpuinfo
    cpu : TI UltraSparc IIi (Sabre)
    fpu : UltraSparc IIi integrated FPU
    pmu : ultra12
    prom : OBP 3.31.0 2001/07/25 20:36
    type : sun4u
    ncpus probed : 1
    ncpus active : 1
    D$ parity tl1 : 0
    I$ parity tl1 : 0
    Cpu0ClkTck : 0000000013d92d40
    cpucaps : flush,stbar,swap,muldiv,v9,mul32,div32,v8plus,vis
    MMU Type : Spitfire
    MMU PGSZs : 8K,64K,512K,4MB


    We are very similar here :

    ceres#
    ceres# uname -a
    Linux ceres 5.10.0-1-sparc64 #1 Debian 5.10.5-1 (2021-01-09) sparc64
    GNU/Linux
    ceres# cat /etc/debian_version
    bullseye/sid
    ceres# cat /proc/cpuinfo
    cpu : TI UltraSparc IIi (Sabre)
    fpu : UltraSparc IIi integrated FPU
    pmu : ultra12
    prom : OBP 3.10.27 2000/06/22 16:45
    type : sun4u
    ncpus probed : 1
    ncpus active : 1
    D$ parity tl1 : 0
    I$ parity tl1 : 0
    Cpu0ClkTck : 000000001a3a2356
    cpucaps : flush,stbar,swap,muldiv,v9,mul32,div32,v8plus,vis
    MMU Type : Spitfire
    MMU PGSZs : 8K,64K,512K,4MB
    ceres#


    root@xray:/home/users/mgt# apt update
    Get:1 http://deb.debian.org/debian-ports sid InRelease [55.3 kB]
    Get:2 http://deb.debian.org/debian-ports unreleased InRelease [56.6 kB]
    Get:3 http://deb.debian.org/debian-ports sid/main all Packages [9,069
    kB]

    Get:4 http://deb.debian.org/debian-ports sid/main sparc64 Packages
    [21.5 MB]

    Fetched 30.7 MB in 1min 55s (266 kB/s)


    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    111 packages can be upgraded. Run 'apt list --upgradable' to see them. root@xray:/home/users/mgt# apt list --upgradeable
    Listing… Done
    .
    .

    apt upgrade was then run and 111 packages upgraded without issue….


    I wish that I could also see that sort of a result.

    I get a total lock up *every* time :

    ceres#
    ceres# apt update
    Get:1 http://deb.debian.org/debian-ports sid InRelease [55.3 kB]
    Get:2 http://deb.debian.org/debian-ports sid/main sparc64 Packages [21.5 MB] Get:3 http://deb.debian.org/debian-ports sid/main all Packages [9069 kB]

    Fetched 30.7 MB in 1min 32s (335 kB/s)

    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    176 packages can be upgraded. Run 'apt list --upgradable' to see them.
    ceres#

    ceres# apt upgrade
    E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
    correct the problem.
    ceres#

    ceres#
    ceres# dpkg --configure -a
    Setting up perl-modules-5.32 (5.32.1-2) ...
    Setting up systemd (247.3-1) ...
    [ 1461.972071] systemd[1]: systemd 247.3-1 running in system mode. (+PAM
    +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
    +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD -SECCOMP +BLKID +ELFUTILS +KMOD
    +IDN2 -IDN +PCRE2 default-hierarchy=unified)
    [ 1462.267197] systemd[1]: Detected architecture sparc64.
    [ 1486.944128] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [ 1487.033443] Modules linked in: drm(E) drm_panel_orientation_quirks(E) i2c_core(E) sg(E) envctrl(E) display7seg(E) flash(E) fuse(E) configfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) sd_mod(E) t10_pi(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_common(E) ata_generic(E) pata_cmd64x(E) libata(E) sym53c8xx(E) scsi_transport_spi(E) scsi_mod(E) sunhme(E)
    [ 1487.501587] CPU: 0 PID: 1 Comm: systemd Tainted: G E 5.10.0-1-sparc64 #1 Debian 5.10.5-1
    [ 1487.625180] TSTATE: 0000000011001604 TPC: 000000000094c4ec TNPC: 000000000094c4f0 Y: 00000000 Tainted: G E
    [ 1487.772853] TPC: <misc_open+0x4c/0x180>
    [ 1487.823247] g0: fffff800065a1140 g1: 000000001000a830 g2:
    0000000000000000 g3: 0000000000000002
    [ 1487.937628] g4: fffff80004193c60 g5: 0000000000dcb214 g6:
    fffff80004198000 g7: 0000000000500008
    [ 1488.052108] o0: 0000000000f24960 o1: fffff800044f1010 o2:
    0000000000040000 o3: 0000000000000000
    [ 1488.166609] o4: 0000000000000000 o5: 0000000000000000 sp:
    fffff8000419af81 ret_pc: 000000000094c4c0
    [ 1488.285655] RPC: <misc_open+0x20/0x180>
    [ 1488.336074] l0: 0000000000f24800 l1: fffff800041cb021 l2:
    00000003936449cb l3: 00000003936449cb
    [ 1488.450559] l4: 0000000000020000 l5: fffff8000419b8f0 l6:
    0000000000e12000 l7: 0000000000000001
    [ 1488.565040] i0: fffff8000adf7840 i1: fffff800044f1000 i2:
    0000000000f24800 i3: 0000000000f24978
    [ 1488.679518] i4: 00000000000000eb i5: 000000001000a818 i6:
    fffff8000419b031 i7: 0000000000665838
    [ 1488.794016] I7: <chrdev_open+0x98/0x1e0>
    [ 1488.845557] Call Trace:
    [ 1488.877596] [<0000000000665838>] chrdev_open+0x98/0x1e0
    [ 1488.946340] [<000000000065ae30>] do_dentry_open+0x170/0x420
    [ 1489.019626] [<000000000065ca68>] vfs_open+0x28/0x40
    [ 1489.083791] [<0000000000671348>] path_openat+0x988/0x1100
    [ 1489.154806] [<0000000000673dd0>] do_filp_open+0x50/0x100
    [ 1489.224673] [<000000000065cd30>] do_sys_openat2+0x70/0x180
    [ 1489.296831] [<000000000065d268>] sys_openat+0x48/0xc0
    [ 1489.363285] [<0000000000406174>] linux_sparc_syscall+0x34/0x44
    ~
    Type 'go' to resume
    ok

    That always happens. Always.


    OKay, also you said :
    The Netra’s have few different devices wonder if there is a bug in
    one of those drivers?

    Good question. The same MAC address on both of the hme interfaces is
    strange. I can check the firmware and see what it says :


    ok cd /pci@1f,0/pci@1,1/
    ok ls
    f0096138 network@3,1
    f00902bc scsi@2
    f00885f4 network@1,1
    f006b270 ebus@1
    ok cd network@1,1
    ok .properties
    local-mac-address 08 00 20 c2 46 48
    assigned-addresses 82010910 00000000 e0000000 00000000 00007020
    hm-rev 000000c1
    device_type network
    interrupts 00000001
    address-bits 00000030
    max-frame-size 00004000
    reg 00010900 00000000 00000000 00000000 00000000
    02010910 00000000 00000000 00000000 00007020 compatible SUNW,hme
    name network
    fast-back-to-back
    devsel-speed 00000001
    class-code 00020000
    max-latency 00000005
    min-grant 0000000a
    revision-id 00000001
    device-id 00001001
    vendor-id 0000108e
    ok
    ok cd ..
    ok cd network@3,1
    ok .properties
    local-mac-address 08 00 20 c2 46 49
    assigned-addresses 82011910 00000000 e0010000 00000000 00007020
    hm-rev 000000c1
    device_type network
    address-bits 00000030
    max-frame-size 00004000
    reg 00011900 00000000 00000000 00000000 00000000
    02011910 00000000 00000000 00000000 00007020 compatible SUNW,hme
    name network
    fast-back-to-back
    devsel-speed 00000001
    class-code 00020000
    interrupts 00000001
    max-latency 00000005
    min-grant 0000000a
    revision-id 00000001
    device-id 00001001
    vendor-id 0000108e
    ok

    That says the hardware is fine. However we know the MAC addresses are
    wrong from the output of "ip link show" as seen above. Very hard for
    me to believe that the old old happy meal driver hme is borked.

    I will install a scsi card which also has network and see what happens.


    --
    Dennis Clarke
    RISC-V/SPARC/PPC/ARM/CISC
    UNIX and Linux spoken
    GreyBeard and suspenders optional

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)