From nobody Sat Apr 23 18:12:52 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 291F6199103C for ; Sat, 23 Apr 2022 18:12:54 +0000 (UTC) (envelope-from leres@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KlzsL0b4Cz3rgq; Sat, 23 Apr 2022 18:12:54 +0000 (UTC) (envelope-from leres@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1650737574; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3NrkFG0NojS+UXR6ROUnUlHrQ32aolBcwqIr/N5RiVQ=; b=BT6fzU279xQRNH2AXEttXgADU+D9NOLeWvWdto8C0uiJRFRbhlsUiM3BjaUpuD0rwcxSwk tYcRyzwCxg4wa/k86x2N4j+ja+hnRcqoUjr33SZ3WvTVya/adc5HuTHWHvZbqYhTYB+7dQ 1QWCAuaVuvinMFyR9wu/qw/eeZ0exQ3hQt/5aCgpSikA6jGIhsWF8QNm1lMlFSDxDX8Ebm Q862StagHB8nKtUwhFa+U92Wxwty4agfOc4sv7/CPOaQK8J3Ih9DbazzqMH61D992uglZu j330GrV58Ld3UvDMB0mUtFbUlaKm/2GQcdJA0bwpiwwXCJLNhbScTutG0bXKZg== Received: from [IPV6:fd:1965::2] (unknown [IPv6:2600:1700:a570:e20:f2ad:4eff:fe0b:a065]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: leres) by smtp.freebsd.org (Postfix) with ESMTPSA id A6E902785C; Sat, 23 Apr 2022 18:12:53 +0000 (UTC) (envelope-from leres@freebsd.org) Message-ID: <421d0c0d-4109-3370-9147-85168051deed@freebsd.org> Date: Sat, 23 Apr 2022 11:12:52 -0700 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: kernel crash making a vlan on a wlan Content-Language: en-US To: Jeff Anton , freebsd-hackers@freebsd.org References: From: Craig Leres In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1650737574; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3NrkFG0NojS+UXR6ROUnUlHrQ32aolBcwqIr/N5RiVQ=; b=IGlwOb+snD+TvUClT33w9K68eQeATOqpRVF9Nh5Y+/7hoZIyNeGixZtBBUVo/i+RNvU9pu V+UMUVkLI26FycwYc8It3iNCmLz4lRqgjjAa2Xt7X03HAs+Pkxk0RazFOtDBfkBdOQ6muU 2CQJI3gW8KdmKzLSGBXuaxi3eF8tL8BYkqNkeYWLx8/JHTBMH5ws8/gW/o2UCGMpbjyvlQ oEI4D+nnBKlE9BllKnJ8cdTJVPSdw9WZtKEH3S0Ma0mx69tWfwTBsR8Tq1TR58z0YIUDev fWiDSO+jfwC4RDgjUye+AXY7IasoKMqcqwV40Jp8KUZ7jXLylXPNqCJKL9Yykw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1650737574; a=rsa-sha256; cv=none; b=N5SbRKUtFYOCdMj+9kOZtkB1Pmb2RHXekoY3BsDYw0FHTI5QN7H0cs3tW7X1a831s0eCSx /M70/SSwuFMWtR6FtB4a3RlPwDtOa1u3QuNp5vlzNLybZiL1AW7fdl/QB3Kp40oy3zlt06 4IE6NvC2/2WXj98Zet9chWSFfAC1x2i721XGqgQXwfiWSuras4Zzk28T5YclzOswn1sGcY R0TQ6GiCTlnFb+tNTlXJxbzjbpBxm93/J2wtE2rTSiw6mZpC9eUVDGXrWrJl5HbtYXcz3Y 7u3EqseS2iKExlCkM2WJSwAPC1ijFZry7qRZgXrDW9T/GNtbRuuUfeQM7g4ZVg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 4/19/22 10:46, Jeff Anton wrote: > A few days ago I tried setting up a vlan for a wlan on a non-critical > 13.0 amd64 (Atom processor) machine and it crashed hard. And because I > set it up in the rc.conf it loop crashed and eventually would not boot > and standalone fsck could not repair the filesystem and it would not > even get past the btx loader so that machine is out of action. It was > taking kernel dumps but to the same corrupt root fs. Sigh. > > What I can remember from the crash report was the process was ifconfig > and there were calls to like wlan_ioctl and other ioctl's on the stack. > > I probably set something like the following in rc.conf > > vlans_wlan0="vlan0" > create_args_vlan0="vlan 1234" > ifconfig_vlan0="inet 192.168.2.3" > static_routes="mcast" > route_mcast="-net 224.0.0.0/4 -iface vlan0" > > Anyone want to risk attempting recreation while I rebuild my now dead > machine? I am able to reproduce the crash with 13.1-RC4. I did an install on a spare SSD and put it in a foxconn nt-510. With the appended rc.conf (and an appropriate wpa_supplicant.conf for my wifi) the system boots up and can talk to the network. All it takes to crash it is to run: ifconfig vlan0 192.168.1.1 I also appended the stack trace from /var/log/messages. Craig ============================== hostname="test.alameda.xse.com" sshd_enable="YES" dumpdev="AUTO" keymap="us.ctrl" wlans_iwn0="wlan0" ifconfig_wlan0="WPA SYNCDHCP" vlans_wlan0="vlan0" create_args_vlan0="vlan 1234" wpa_supplicant="YES" ============================== Apr 22 11:03:09 test kernel: Fatal trap 12: page fault while in kernel mode Apr 22 11:03:09 test kernel: cpuid = 0; apic id = 00 Apr 22 11:03:09 test kernel: fault virtual address = 0x0 Apr 22 11:03:09 test kernel: fault code = supervisor read instruction, page not present Apr 22 11:03:09 test kernel: instruction pointer = 0x20:0x0 Apr 22 11:03:09 test kernel: stack pointer = 0x28:0xfffffe00946589b8 Apr 22 11:03:09 test kernel: frame pointer = 0x28:0xfffffe0094658ac0 Apr 22 11:03:09 test kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Apr 22 11:03:09 test kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Apr 22 11:03:09 test kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Apr 22 11:03:09 test kernel: current process = 1404 (ifconfig) Apr 22 11:03:09 test kernel: trap number = 12 Apr 22 11:03:09 test kernel: panic: page fault Apr 22 11:03:09 test kernel: cpuid = 0 Apr 22 11:03:09 test kernel: time = 1650650520 Apr 22 11:03:09 test kernel: KDB: stack backtrace: Apr 22 11:03:09 test kernel: #0 0xffffffff80c69285 at kdb_backtrace+0x65 Apr 22 11:03:09 test kernel: #1 0xffffffff80c1b93f at vpanic+0x17f Apr 22 11:03:09 test kernel: #2 0xffffffff80c1b7b3 at panic+0x43 Apr 22 11:03:09 test kernel: #3 0xffffffff810afdf5 at trap_fatal+0x385 Apr 22 11:03:09 test kernel: #4 0xffffffff810afe4f at trap_pfault+0x4f Apr 22 11:03:09 test kernel: #5 0xffffffff81087348 at calltrap+0x8 Apr 22 11:03:09 test kernel: #6 0xffffffff80dadbfd at arp_ifinit+0x6d Apr 22 11:03:09 test kernel: #7 0xffffffff80d4192d at vlan_ioctl+0x1dd Apr 22 11:03:09 test kernel: #8 0xffffffff80db5baf at in_control+0x9bf Apr 22 11:03:09 test kernel: #9 0xffffffff80d323bd at ifioctl+0x3bd Apr 22 11:03:09 test kernel: #10 0xffffffff80c895eb at kern_ioctl+0x25b Apr 22 11:03:09 test kernel: #11 0xffffffff80c892f1 at sys_ioctl+0xf1 Apr 22 11:03:09 test kernel: #12 0xffffffff810b06ec at amd64_syscall+0x10c Apr 22 11:03:09 test kernel: #13 0xffffffff81087c5b at fast_syscall_common+0xf8 Apr 22 11:03:09 test kernel: Uptime: 11m2s Apr 22 11:03:09 test kernel: Dumping 277 out of 2005 MB:..6%..12%..24%..35%..41%..52%..64%..75%..81%..93%---<>---