[Bug 272416] Seldom crash happening with RTL8125
Date: Fri, 07 Jul 2023 16:26:52 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272416 Bug ID: 272416 Summary: Seldom crash happening with RTL8125 Product: Base System Version: 13.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: jon@xyinn.org Created attachment 243309 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=243309&action=edit re-driver-crash Hello all, I'm not sure if this should be filed for the base system or for the port given that my system needs the "net/realtek-re-kmod" to have a working ethernet connection. I'm using 13.2-RELEASE with a mostly stock kernel, with the only addition of me adding a DELAY(5000) that I'm testing for a separate crash happening for my AMD Raven HDA Controller (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393#c48). Given the different subsystems, hopefully this isn't interfering. I believe I've experienced this crash before it would only happen seldomly if anything. I wanted to report just so that we can start collecting data on the problem. I've attached a crash dump as well. re0@pci0:12:0:0: class=0x020000 rev=0x05 hdr=0x00 vendor=0x10ec device=0x8125 subvendor=0x1043 subdevice=0x87d7 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8125 2.5GbE Controller' class = network subclass = ethernet /etc/rc.conf hostname="weshly" dumpdev="AUTO" kld_list="amdgpu vboxdrv fusefs" clear_tmp_enable="YES" # Disable Mail sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" # Networking ifconfig_re0="DHCP" ifconfig_re0_ipv6="inet6 accept_rtadv" # Services zfs_enable="YES" dbus_enable="YES" seatd_enable="YES" mixer_enable="YES" syncthing_enable="YES" syncthing_user="jon" syncthing_group="jon" # NFS nfs_client_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" When the crash happened, I did have virtualbox running in the background (although it was mostly idle). The VM was a Windows 10 VM and it had the network adapter settings set to NAT. Thank you, Jonathan -- You are receiving this mail because: You are the assignee for the bug.