From owner-freebsd-bugs@freebsd.org Mon Nov 4 00:30:46 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 20DAA1AD32A for ; Mon, 4 Nov 2019 00:30:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 475txf04K6z3GDd for ; Mon, 4 Nov 2019 00:30:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 009901AD328; Mon, 4 Nov 2019 00:30:46 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 005C21AD327 for ; Mon, 4 Nov 2019 00:30:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 475txd6CLzz3GDc for ; Mon, 4 Nov 2019 00:30:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B89461BF70 for ; Mon, 4 Nov 2019 00:30:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xA40Ujkm032582 for ; Mon, 4 Nov 2019 00:30:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xA40UjSh032568 for bugs@FreeBSD.org; Mon, 4 Nov 2019 00:30:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241697] kernel panic on loading of i915kms.ko if custom kernel w/ MAXCPU < 256 Date: Mon, 04 Nov 2019 00:30:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kumba@gentoo.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2019 00:30:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241697 Bug ID: 241697 Summary: kernel panic on loading of i915kms.ko if custom kernel w/ MAXCPU < 256 Product: Base System Version: 12.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: kumba@gentoo.org Discovered that in both 12.0-RELEASE-p11 and 12.1-RC2-p0, on an Intel NUC8i= 5BEH with Intel Iris Graphics, if one is running a custom kernel where "options MAXCPU" is a value lower than the default of 256, loading i915kms.ko on boot (via kld_list in /etc/rc.conf), the system will panic. Partial bootlog is below, manually transcribed from an image I took of the screen: Loading kernel modules: drmn0: on vgapci0 vgapci0: child drmn0 requested pci_enable_io vgapci0: child drmn0 requested pci_enable_io <5>[drm] Unable to create a private tmpfs mount, hugepage support will be disabled(-19). <6>[drm] Found 128MB of eDRAM Failed to add WC MTRR for [0x80000000-0x8fffffff]: -22; performance may suffer<6>[drm] Got stolen memory base 0x7c000000, size 0x4000000 <6>[drm] Supports vblank timestamp caching Rev 2 (21.10.2013). <6>[drm] Driver supports precise vblank timestap query. <6>[drm] Connector eDP-1: get mode from tunables: <6>[drm] - kern.vt.fb.modes.eDP-1 <6>[drm] - kern.vt.fb.default_mode panic: Invalid CPU in callout 256 cpuid =3D 2 time =3D 1572817693 KDB: stack backtrace: #0 0xffffffff8089cc47 at kdb_backtrace+0x67 #1 0xffffffff80850276 at vpanic+0x136 #2 0xffffffff80850133 at panic+0x43 #3 0xffffffff8086ad9a at callout_reset_sbt_on+0x36a #4 0xffffffff825c3dcb at linux_queue_delayed_work_on+0x1db #5 0xffffffff8249749b at intel_dp_init_connector+0x8bb #6 0xffffffff82471195 at intel_ddi_init+0x365 #7 0xffffffff82484a88 at intel_modeset_init+0x1038 #8 0xffffffff82424b49 at i915_driver_load+0x14f9 #9 0xffffffff825be7d2 at linux_pci_attach+0x432 #10 0xffffffff8088b021 at device_attach+0x3e1 #11 0xffffffff8088d478 at bus_generic_driver_added+0xa8 #12 0xffffffff8088933a at devclass_driver_added+0x7a #13 0xffffffff8088929a at devclass_add_driver+0x16a #14 0xffffffff825bdf86 at _linux_pci_register_driver+0xf6 #15 0xffffffff8244f7fe at i915kms_evh+0x2e #16 0xffffffff8082f3a4 at module_register_init+0xa4 #17 0xffffffff8082208f at linker_load_module+0xb3f Workaround for now is to remove any change to MAXCPU from the custom kernel config, or boot with the GENERIC kernel. --=20 You are receiving this mail because: You are the assignee for the bug.=