From owner-freebsd-bugs@freebsd.org Fri Apr 29 13:58:19 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 441B1B1F020 for ; Fri, 29 Apr 2016 13:58:19 +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 mx1.freebsd.org (Postfix) with ESMTPS id 347A71518 for ; Fri, 29 Apr 2016 13:58:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3TDwIdX048173 for ; Fri, 29 Apr 2016 13:58:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 209099] ata2: already running! panic: bad link elm 0xfffff80003b7e6a0 prev->next != elm Date: Fri, 29 Apr 2016 13:58:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: furstenwerth@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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.21 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 13:58:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209099 --- Comment #3 from Greg Furstenwerth --- It seems that when running 'salt-call -l debug state.apply' there is no real issue. It executes the command and does not create any problem. Once states= are applied if I reboot and the minion restarts, it panic's just after loading = the minion. Yet running 'salt machine state.apply' still does same behavior. Running salt-call I get enormous output. However, the paste here. If you take a look at line 9, "please install 'virt-what'" when running 'salt machine state.apply' this is the last line printed with debugging turned on the minion before panic.=20 [DEBUG ] Reading configuration from /usr/local/etc/salt/minion [DEBUG ] Including configuration from '/usr/local/etc/salt/minion.d/_schedule.conf' [DEBUG ] Reading configuration from /usr/local/etc/salt/minion.d/_schedule.conf [DEBUG ] Configuration file path: /usr/local/etc/salt/minion [WARNING ] Insecure logging configuration detected! Sensitive data may be logged. [DEBUG ] Reading configuration from /usr/local/etc/salt/minion [DEBUG ] Including configuration from '/usr/local/etc/salt/minion.d/_schedule.conf' [DEBUG ] Reading configuration from /usr/local/etc/salt/minion.d/_schedule.conf [DEBUG ] Please install 'virt-what' to improve results of the 'virtual' grain. [DEBUG ] Initializing new SAuth for ('/usr/local/etc/salt/pki/minion', 'machine.lan', 'tcp://salt.master.lan:4506') [DEBUG ] Generated random reconnect delay between '1000ms' and '11000ms' (1950) [DEBUG ] Setting zmq_reconnect_ivl to '1950ms' [DEBUG ] Setting zmq_reconnect_ivl_max to '11000ms' [INFO ] Determining pillar cache [DEBUG ] Initializing new AsyncZeroMQReqChannel for ('/usr/local/etc/salt/pki/minion', 'machine.lan', 'tcp://salt.master.lan:45= 06', 'aes') [DEBUG ] Initializing new SAuth for ('/usr/local/etc/salt/pki/minion', 'machine.lan', 'tcp://salt.master.lan:4506') [DEBUG ] Initializing new AsyncZeroMQReqChannel for ('/usr/local/etc/salt/pki/minion', 'machine.lan', 'tcp://salt.master.lan:45= 06', 'clear') [DEBUG ] Decrypting the current master AES key [DEBUG ] Loaded minion key: /usr/local/etc/salt/pki/minion/minion.pem [DEBUG ] Loaded minion key: /usr/local/etc/salt/pki/minion/minion.pem [DEBUG ] LazyLoaded jinja.render [DEBUG ] LazyLoaded yaml.render [DEBUG ] LazyLoaded state.apply [DEBUG ] LazyLoaded grains.get [DEBUG ] LazyLoaded saltutil.is_running [DEBUG ] Initializing new AsyncZeroMQReqChannel for ('/usr/local/etc/salt/pki/minion', 'machine.lan', 'tcp://salt.master.lan:45= 06', 'aes') [DEBUG ] Initializing new SAuth for ('/usr/local/etc/salt/pki/minion', 'machine.lan', 'tcp://salt.master.lan:4506') [INFO ] Determining pillar cache [DEBUG ] Initializing new AsyncZeroMQReqChannel for ('/usr/local/etc/salt/pki/minion', 'machine.lan', 'tcp://salt.master.lan:45= 06', 'aes') [DEBUG ] Initializing new SAuth for ('/usr/local/etc/salt/pki/minion', 'machine.lan', 'tcp://salt.master.lan:4506') [DEBUG ] Loaded minion key: /usr/local/etc/salt/pki/minion/minion.pem [INFO ] Loading fresh modules for state activity [DEBUG ] LazyLoaded jinja.render [DEBUG ] LazyLoaded yaml.render [DEBUG ] In saltenv 'prod', looking at rel_path u'top.sls' to resolve u'salt://top.sls' [DEBUG ] In saltenv 'prod', ** considering ** path u'/var/cache/salt/minion/files/prod/top.sls' to resolve u'salt://top.sls' [INFO ] Fetching file from saltenv 'prod', ** skipped ** latest already = in cache u'salt://top.sls' [DEBUG ] compile template: /var/cache/salt/minion/files/prod/top.sls [DEBUG ] Jinja search path: ['/var/cache/salt/minion/files/prod'] [PROFILE ] Time (in seconds) to render '/var/cache/salt/minion/files/prod/top.sls' using 'jinja' renderer: 0.00688982009888 [DEBUG ] Rendered data from file: /var/cache/salt/minion/files/prod/top.s= ls: --=20 You are receiving this mail because: You are the assignee for the bug.=