From nobody Mon Feb 12 17:45:27 2024 X-Original-To: freebsd-current@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 4TYX1D1XrWz5BDlC; Mon, 12 Feb 2024 17:45:36 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (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 (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "R3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TYX1C6ZB6z4WvB; Mon, 12 Feb 2024 17:45:35 +0000 (UTC) (envelope-from imb@protected-networks.net) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding:content-type :content-type:in-reply-to:from:from:content-language:references :subject:subject:user-agent:mime-version:date:date:message-id; s=201508; t=1707759928; bh=NDeTl7pk6+Z1BEM+tQOohzw3kDNFsnUqJhMg OFayl3A=; b=i+TXyAalo7udPf14NYGCPhDhMH0R6ctY9mCD3uGQJi6CuYZSP/Lz eOlLm1Td4a6SzGFDaf44QXc7l1PFdBYT1ufaqn9fhSECqvKfC1eGp/JKfjIYrZEf fBZPHRKSuVyNio95PAiS4WurM5LC6q5Zd5naQCfrJ35cbvpl7RfTKv4= Received: from [IPV6:2600:4040:53d9:8200:f21f:afff:fe66:957e] (unknown [IPv6:2600:4040:53d9:8200:f21f:afff:fe66:957e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 8B64E394F0; Mon, 12 Feb 2024 12:45:28 -0500 (EST) Message-ID: Date: Mon, 12 Feb 2024 12:45:27 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: request" leads to panic To: John Baldwin , Mark Millard , FreeBSD ARM List , Current FreeBSD Cc: Warner Losh , Bakul Shah References: <76AB969F-5BC5-4116-8AF4-3ED2CABEBBA5.ref@yahoo.com> <76AB969F-5BC5-4116-8AF4-3ED2CABEBBA5@yahoo.com> <2FE8FA48-180B-4F0D-BCD8-F7F33053B0F7@iitbombay.org> <986D2CD6-6241-4EBE-8BD2-9821AB693BA7@yahoo.com> Content-Language: en-NZ From: Michael Butler Autocrypt: addr=imb@protected-networks.net; keydata= xsDiBETHZAURBACJicNaIbVVVZahtQcdJeogtTLjCYAdj4kFMpy6Y3Ac19UNWDM+TrD4yFPi 5nc/pp9M/5Q4RNBr6a97fTYroTaq+vDwWdklOHwD2ZXs7FqwWOtVSIPT/rev5fUvwEF2VFYE sNDbpE5HHpP/oFUw5scEJZVyOBJSGvYb1IhV55NWswCgzkUGbG8A3s+oZXkHqTCYGW/seukD +wTo/L835xLpbTJxoxEKeGA3aWifSsRvpWWHyXye6sTkSN3SmtE9A8Pqmdb1dBEO0eOms6GD RamvCFgdvg2HesAv9l7L/7Mm9iKJs6uTAa+taIQslpumGh4PRc94IepVFzAa4Ef/FA4mWx9w P/EqNsKUPE2U5HI1decbopkxH/d/A/9Hupc10lPsXVMACd54/YZRsSTTcArheekm8qE/f8Hl 1Q7At+yuFgfMll4QPAhefnrLUanXF1bWtxG5PmaJktDYp3HOmy43giZgacgt+a3TVd6vu8Gs DnI4FOfYllq7mZFezMIulCWUYtnkMEXEeyzp39dygi7blPIjckWlQ2sc380rTWljaGFlbCBC dXRsZXIgPGltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0PsJgBBMRAgAgBQJEx2QFAhsDBgsJ CAcDAgQVAggDBBYCAwECHgECF4AACgkQQv9rrgRC1JL7mgCdEnPeo22kqT/bES+D78QSGhNR r8cAn2xOMeu6pBrc2tDY8Ky/70HBctmjzsFNBETHZA4QCACKbm/PMn4QcyDEvIn4MF+t2E1A zgiBAkPCMtWT1CcqeUj13OwNM8qJD/mBWjCZCnr1hKVbvzOmgKaM4uDCWIcSCdoDTJx1DqMx abr+EpHz1fL6aagEOKHz5sCYOkDXt3zzZ/5RBMdkEJwunXYtAbu5e68oty+d0DFzAM3pBp6l GC0TE3VutmFR/KK66rf0KB83YQBf/IAtyqsRIQPP9t0SLfJ+kqKXf73nvAUFEtb21gZSzhTm QP87QKyQvenE8o4PQ2tEslq2jICB7pGcqIrwP4o3Hl4V+HXi3lA26MMJ5rakQB2sKKWroPVQ BiRXO+W8Qf+0oQFq38oMXR5sPOs/AAMFB/sEKcjzvkwviZOsDElthxtgrmqUNKC9G/4Fw0tK k6fMynv+bcKz85k2uWOIfefUKBFoQ0SCphU4jquJENqqy6BPTkXePlIJok2/GkF7xtHm2FPq tTTuYmoBrGsls28Z9dn2LcBwFHz59SSWM9JFPIvFr9HCkKtp6zPUsJd5b02+0wgzDubTMQS9 M2LwGSh9xK6xl4MGgngl22b0TZDh5qHwmsywOX6SbGsQfeNpkptJ4gPjShypusFyF+pevnCM wTfUPCBd/AFbu2fHFQjA8sgkr5IqXuc4PoiIBXc9upoFpDqGkYssAKbzGcRsK94a8hRROJV9 bzPyYempIWaPXr2EwkkEGBECAAkFAkTHZA4CGwwACgkQQv9rrgRC1JKqhwCeOov6gTo8eWte es3gbLr2n2b5AXMAoItSlajet574lkouzY3u3scSRfiE In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4TYX1C6ZB6z4WvB X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On 2/12/24 12:36, John Baldwin wrote: > On 2/10/24 2:09 PM, Michael Butler wrote: >> I have stability problems with anything at or after this commit >> (b377ff8) on an amd64 laptop. While I see the following panic logged, no >> crash dump is preserved :-( It happens after ~5-6 minutes running in KDE >> (X). >> >> Reverting to 36efc64 seems to work reliably (after ACPI changes but >> before the problematic PCI one) >> >> kernel: Fatal trap 12: page fault while in kernel mode >> kernel: cpuid = 2; apic id = 02 >> kernel: fault virtual address     = 0x48 >> kernel: fault code                = supervisor read data, page not >> present >> kernel: instruction pointer       = 0x20:0xffffffff80acb962 >> kernel: stack pointer             = 0x28:0xfffffe00c4318d80 >> kernel: frame pointer             = 0x28:0xfffffe00c4318d80 >> kernel: code segment              = base 0x0, limit 0xfffff, type 0x1b >> kernel:                   = DPL 0, pres 1, long 1, def32 0, gran 1 >> kernel: processor eflags  = interrupt enabled, resume, IOPL = 0 >> kernel: current process           = 2 (clock (0)) >> kernel: rdi: fffff802e460c000 rsi: 0000000000000000 rdx: 0000000000000002 >> kernel: rcx: 0000000000000000  r8: 000000000000001e  r9: fffffe00c4319000 >> kernel: rax: 0000000000000002 rbx: fffff802e460c000 rbp: fffffe00c4318d80 >> kernel: r10: 0000000000001388 r11: 000000007ffc765d r12: 000f000000000000 >> kernel: r13: 0002000000000000 r14: fffff8000193e740 r15: 0000000000000000 >> kernel: trap number               = 12 >> kernel: panic: page fault >> kernel: cpuid = 2 >> kernel: time = 1707573802 >> kernel: Uptime: 6m19s >> kernel: Dumping 942 out of 16242 >> MB:..2%..11%..21%..31%..41%..51%..62%..72%..82%..92% >> kernel: Dump complete >> kernel: Automatic reboot in 15 seconds - press a key on the console to >> abort > > Without a stack trace it is pretty much impossible to debug a panic like > this. > Do you have KDB_TRACE enabled in your kernel config?  I'm also not sure > how the > PCI changes can result in a panic post-boot.  If you were going to have > problems > they would be during device attach, not after you are booted and running X. > > Short of a stack trace, you can at least use lldb or gdb to lookup the > source > line associated with the faulting instruction pointer (as long as it > isn't in > a kernel module), e.g. for gdb you would use 'gdb /boot/kernel/kernel' > and then > 'l *', e.g. from above: 'l > *0xffffffff80acb962' I suspect the absence of a core dump was due to my use of tmpfs for /tmp and /var/tmp while still having clear_tmp enabled in rc.conf (that may touch swap on restart). Since then, I've removed tmpfs, everything under /usr/obj am rebuilding from scratch. I'll update when it finally finishes (i5-3340s are quick :-() Michael