From owner-freebsd-bugs@freebsd.org Mon Jul 23 23:05:06 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4887D1056C2E for ; Mon, 23 Jul 2018 23:05:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D40E07243A for ; Mon, 23 Jul 2018 23:05:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 949711056C2A; Mon, 23 Jul 2018 23:05:05 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54DAF1056C29 for ; Mon, 23 Jul 2018 23:05:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C948772438 for ; Mon, 23 Jul 2018 23:05:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 13AEEF8C2 for ; Mon, 23 Jul 2018 23:05:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6NN53NX036779 for ; Mon, 23 Jul 2018 23:05:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6NN53eG036777 for bugs@FreeBSD.org; Mon, 23 Jul 2018 23:05:03 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 229995] [panic, regression] radeonkms "timed sleep before timers are working" Date: Mon, 23 Jul 2018 23:05:04 +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: 11.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: andrew.daugherity@gmail.com 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 attachments.created 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.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 23:05:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229995 Bug ID: 229995 Summary: [panic, regression] radeonkms "timed sleep before timers are working" Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: andrew.daugherity@gmail.com Created attachment 195401 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D195401&action= =3Dedit dmesg w/panic On a system where I have radeonkms activated via /boot/loader.conf: kern.vty=3Dvt radeonkms_load=3D"YES" radeonkmsfw_R100_cp_load=3D"YES" This worked properly in 10.2 and 10.3. I recently upgraded to 11.2 and was greeted by a kernel panic: =3D=3D=3D=3D drmn0: on vgapci0 info: [drm] RADEON_IS_PCI [...] info: [drm] Loading R100 Microcode info: [drm] radeon: ring at 0x00000000C0001000 info: [drm] ring test succeeded in 2 usecs panic: timed sleep before timers are working cpuid =3D 2 KDB: stack backtrace: #0 0xffffffff80b3d567 at kdb_backtrace+0x67 #1 0xffffffff80af6b07 at vpanic+0x177 #2 0xffffffff80af6983 at panic+0x43 #3 0xffffffff80b4a363 at sleepq_set_timeout_sbt+0x103 #4 0xffffffff80a96bbc at _cv_timedwait_sbt+0x13c #5 0xffffffff826e6b05 at radeon_fence_wait_seq+0x1d5 #6 0xffffffff826e68ea at radeon_fence_wait+0x2a #7 0xffffffff8271e2c2 at r100_ib_test+0x202 #8 0xffffffff826f803a at radeon_ib_ring_tests+0x2a #9 0xffffffff826e1e61 at radeon_device_init+0x511 #10 0xffffffff826ee443 at radeon_driver_load_kms+0xa3 #11 0xffffffff8289aa06 at drm_get_pci_dev+0x436 #12 0xffffffff8289d6fa at drm_attach_helper+0x13a #13 0xffffffff826e579f at radeon_attach+0x4f #14 0xffffffff80b2fc98 at device_attach+0x3b8 #15 0xffffffff80b30f3d at bus_generic_attach+0x3d #16 0xffffffff8077f0fe at vga_pci_attach+0x3e #17 0xffffffff80b2fc98 at device_attach+0x3b8 Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort =3D=3D=3D=3D It only panics when loading the module at boot. If I 'kldload radeonkms' a= fter the system has booted, there is no problem. (So doing that via rc.local is= a workaround at least...) Note that when the system is up, kldload will automatically load the necess= ary firmware modules, but loader(8) will not, hence my specifying radeonkmsfw_R100_cp_load explicitly. If I leave that line out, the radeonk= ms driver will complain about missing firmware, but the system will not panic. The full dmesg is attached. For comparison, a successful load of radeonkms after bootup produces mostly the same output up to the "ring test succeeded message", after which it prints another 30 lines or so: =3D=3D=3D=3D info: [drm] ring test succeeded in 0 usecs info: [drm] ib test succeeded in 0 usecs info: [drm] radeon_device_init: Taking over the fictitious range 0xe0000000-0xe4000000 radeon_iicbb0 on drmn0 iicbus0: on iicbb0 addr 0xff iic0: on iicbus0 radeon_iicbb1 on drmn0 iicbus1: on iicbb1 addr 0xff iic1: on iicbus1 radeon_iicbb2 on drmn0 iicbus2: on iicbb2 addr 0xff iic2: on iicbus2 radeon_iicbb3 on drmn0 iicbus3: on iicbb3 addr 0xff iic3: on iicbus3 info: [drm] Radeon Display Connectors info: [drm] Connector 0: info: [drm] VGA-1 info: [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 info: [drm] Encoders: info: [drm] CRT1: INTERNAL_DAC1 info: [drm] Connector VGA-1: get mode from tunables: info: [drm] - kern.vt.fb.modes.VGA-1 info: [drm] - kern.vt.fb.default_mode info: [drm] fb mappable at 0xE0040000 info: [drm] vram apper at 0xE0000000 info: [drm] size 2621440 info: [drm] fb depth is 16 info: [drm] pitch is 2560 fbd0 on drmn0 VT: Replacing driver "vga" with new "fb". =3D=3D=3D=3D Workaround: Comment out any 'radeonkms*_load' lines in /boot/loader.conf and add 'kldlo= ad radeonkms' to /etc/rc.local, to load the driver later in the boot process. --=20 You are receiving this mail because: You are the assignee for the bug.=