Date: Sun, 27 Mar 2022 09:58:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262856] kernel panic at boot time Message-ID: <bug-262856-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262856 Bug ID: 262856 Summary: kernel panic at boot time Product: Base System Version: 13.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: bsd@volki.at A few days ago, I tried to upgrade from 12-STABLE to 13-STABLE but the new kernel panicked instantly. Here's a transscript of the screen photo I made: avail memory =3D 1552841136 (14889 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: <ALASKA A M I> FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x28 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80396715 stack pointer =3D 0x28:0xffffffff80e17f70 frame pointer =3D 0x28:0xffffffff80e17f80 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 0 () trap number =3D 12 panic: page fault cpuid =3D 0 time =3D 1 Uptime: 1s original photo: http://www.volki.at/austausch/panic_2022-03/screenshot_panic.jpg kernel: http://www.volki.at/austausch/panic_2022-03/kernel kernel config: http://www.volki.at/austausch/panic_2022-03/CU08 Of course, I could try a GENERIC kernel and, if it works, change line by li= ne until the panic happens again, but this is a production system so I want to avoid experiments as long as I don't know if they are necessary. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262856-227>