From nobody Tue Sep 24 06:46:56 2024 X-Original-To: freebsd-hardware@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 4XCWJT70KRz5XR9S for ; Tue, 24 Sep 2024 07:12:09 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Received: from mail.stormshield.eu (mail.stormshield.eu [91.212.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.stormshield.eu", Issuer "Sectigo RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XCWJS6RXvz4kDC for ; Tue, 24 Sep 2024 07:12:08 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=stormshield.eu header.s=signer2 header.b=pJQZSCm5; dmarc=pass (policy=quarantine) header.from=stormshield.eu; spf=pass (mx1.freebsd.org: domain of Stephane.ROCHOY@stormshield.eu designates 91.212.116.25 as permitted sender) smtp.mailfrom=Stephane.ROCHOY@stormshield.eu DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stormshield.eu; s=signer2; t=1727161920; h=From:Subject:Date:Message-ID:To:Cc :MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To :References; bh=EBYZ5hUdaAjr5BioJ5hP44ODvV9BKpHw9ftaIzeJZWY=; b=pJQZSCm5K modM6c2tJ2QIMLlwF4XyxNB4Pisg7+1pd7oxuo0uszI8XbhpTzwO1cNeUBg6iGGJouCFS/uZk 7rqwD7YXeRHXZUehB95718iQTI3Gezc5n35TLNJ5R7jViJg9q2gI+N+u8CkT/vXJlMQqc/yc3 7JNDB6pEVb6Qdf3k7iKKz3BOcyF05495LvepQrr9cjtjdkfGXWWIu9EhXy6PtNx09RH/zhSpd CKZM2ZlCQfNaaOVhDK8GGDM4KR4jTIoC4zxRcsO01ug0TLWic9sA6LXIBRsC7TU7Qsx3kkAow vz2U9L6P83asMUnN1M7fIekGsj5nnumE+xR4q3eXQ==; References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> User-agent: mu4e 1.10.7; emacs 29.4 From: Stephane Rochoy To: mike tancsa CC: Subject: Re: watchdog timer programming Date: Tue, 24 Sep 2024 08:46:56 +0200 In-Reply-To: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> Message-ID: <86plotbk5b.fsf@cthulhu.stephaner.labo.int> List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: ICTDCCEXCH003.one.local (10.180.4.3) To ICTDCCEXCH002.one.local (10.180.4.2) X-DKIM-Signer: DkimX (v3.60.360) X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[stormshield.eu,quarantine]; R_SPF_ALLOW(-0.20)[+a:mail.stormshield.eu]; R_DKIM_ALLOW(-0.20)[stormshield.eu:s=signer2]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:49068, ipnet:91.212.116.0/24, country:FR]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hardware@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[stormshield.eu:+] X-Rspamd-Queue-Id: 4XCWJS6RXvz4kDC X-Spamd-Bar: --- mike tancsa writes: > I am trying to get > > superio0: at port 0x2e-0x2f=20 > on isa0 > itwd0: at WDT ldn 0x07 on=20 > superio0 > itwd0: Configured for system reset on timeout > > working on FreeBSD. The driver seems to load / attach fine, but=20 > it does > not want to reboot the box. Adding a #define DIAGNOSTICS 1 > > shows > > itwd0: at WDT ldn 0x07 on=20 > superio0 > itwd0: Configured for system reset on timeout > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > > when I do > > watchdogd -t 3 > killall -9 watchdogd > > but never a reboot :( > > Any idea how to get this hardware working ? Do you know if, at least, the pre-timeout is working? Glancing at the code, this chip can be configured to use a=20 specific IRQ (its default one is 0x40) and have an "NMI mode" (relying on an explicitly configured IRQ). Maybe playing with the dev.itwd.irq=20 and .nwi tunables could get us some hints. Also this code from itwd's wd_func puzzle me a bit: superio_write(dev, 0x73, val); if (superio_read(dev, 0x73) !=3D val) superio_write(dev, 0x73, val); It let me think that we either are writing twice to the same I/O port by mistake or the corresponding chip's register enforce a specific protocol to modify it. If the later, the code don't seems to be able to detect a "protocol error". By the way, do you have the datasheet of the ITE chip? (I know I must be very optimistic to ask such a question ;)) Regards, --=20 St=C3=A9phane Rochoy O: Stormshield From nobody Tue Sep 24 13:01:40 2024 X-Original-To: freebsd-hardware@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 4XCg4329RZz5Xm8r for ; Tue, 24 Sep 2024 13:01:55 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from mail-vk1-xa34.google.com (mail-vk1-xa34.google.com [IPv6:2607:f8b0:4864:20::a34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XCg4211Mlz41f3 for ; Tue, 24 Sep 2024 13:01:54 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=gRIlwUh3; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of chrcoluk@gmail.com designates 2607:f8b0:4864:20::a34 as permitted sender) smtp.mailfrom=chrcoluk@gmail.com Received: by mail-vk1-xa34.google.com with SMTP id 71dfb90a1353d-502c106737cso161800e0c.2 for ; Tue, 24 Sep 2024 06:01:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727182911; x=1727787711; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ZuifsWsmtgqCsGNFg7qoARhTmFOXG6q2iSA+mQtXGcw=; b=gRIlwUh3JgYSCcVgSnbt8d+PzCk34d3wUDIg/tbH02fiF+mtFJnnwgW3Kd1u4prcPs Up+zTzEPue6RHS9jr1JD8YAB5NviC2WGO1mKnNUsqC76omwXdx3DrqfCYXBbCiv8X8Mo KOQLQQIwuQ11bh8TCsenRfavaeGcK4N00XCBgBDE58hjQ4Bqc4Eic/HBuMEWvDhn5cU1 F5An3jhIv172LuhhsFIvx2VcenVGoKBZSm2p2pFUWv/r2NVpSQam4196YLJThjdhzvBY ixrbx7AurC5R7tnPbb4+QEUNQkUOnnw4D4YWEi2j8L6PkyzQT2bNmso+CCbGTA2RTSv+ WgsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727182911; x=1727787711; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ZuifsWsmtgqCsGNFg7qoARhTmFOXG6q2iSA+mQtXGcw=; b=uhc7l3NRZxcodEz3Lpa0Kz5dMcAQw7Gm/xb3f8NY7F+NQdVddDAuBVt9D9llRP/M5R W3tR2TBVH7DTpQXfYipFKy00IvbBhfTjJkJD/zbfR01pAO83hd9PdD3YG+7/lcxsy8ot tnUHs70e6/CnZ+TTXxGL8xX6SU4R1gVb4NAdk/KzsSUp85xAPodcaw2dDNdvbMZ3MAao LAf50uLl4jhYDYdllX7wcKV5+CU/tRMFuRGeQ/tbSlGzI1CyDOOyl/VJ3JhVeWekiNAv cYxe85wyf5o21RJoq9rFkxn9qcP+3wREL4dPhWDzXTVtoQxL0U+u9BJMrWrfErzbFCzq lrCQ== X-Gm-Message-State: AOJu0Yxr66X8j3Zy7cNH4SsK1m3UG3u0rBbK9yvn+zNdxLhoHvfs56+a b1I4mC9ap3BIqQFoHKxkopz+9QKS99XJfuz643XCh1rHxf75MW79cRk1pW5XyzDQxqurQbqmu4P chTGgQsBFzGp98KHxmIMtsr+kgwLg4A== X-Google-Smtp-Source: AGHT+IENGkO3bSDVR+E6/fTqpBxE7sf8bziRaaL7iS5TPe/CGwDLOY1mN742XDvkNddxWq+KcX/SVVZKUcHHR1sD/CM= X-Received: by 2002:ac5:c934:0:b0:501:319:d0b0 with SMTP id 71dfb90a1353d-503e04e275emr3159506e0c.2.1727182910941; Tue, 24 Sep 2024 06:01:50 -0700 (PDT) List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 From: Chris Date: Tue, 24 Sep 2024 14:01:40 +0100 Message-ID: Subject: unsubscribe To: freebsd-hardware@freebsd.org Content-Type: multipart/alternative; boundary="000000000000de75630622dd1b0e" X-Spamd-Result: default: False [0.50 / 15.00]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; NEURAL_SPAM_SHORT(0.99)[0.994]; NEURAL_HAM_LONG(-0.99)[-0.989]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_PARTS_DIFFER(0.50)[100.0%]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DKIM_TRACE(0.00)[gmail.com:+]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hardware@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::a34:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-hardware@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4XCg4211Mlz41f3 X-Spamd-Bar: / --000000000000de75630622dd1b0e Content-Type: text/plain; charset="UTF-8" unsubscribe --000000000000de75630622dd1b0e Content-Type: text/html; charset="UTF-8"
unsubscribe
--000000000000de75630622dd1b0e-- From nobody Tue Sep 24 15:29:35 2024 X-Original-To: freebsd-hardware@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 4XCkLc2TGmz5Xvbh for ; Tue, 24 Sep 2024 15:29:44 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 "smarthost1.sentex.ca", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XCkLb0Yjxz4GjH for ; Tue, 24 Sep 2024 15:29:43 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mike@sentex.net designates 2607:f3e0:0:1::12 as permitted sender) smtp.mailfrom=mike@sentex.net Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.18.1/8.18.1) with ESMTPS id 48OFTYQC063192 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Tue, 24 Sep 2024 11:29:34 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:3084:877e:6ade:cdc] ([IPv6:2607:f3e0:0:4:3084:877e:6ade:cdc]) by pyroxene2a.sentex.ca (8.18.1/8.15.2) with ESMTPS id 48OFTY7U049879 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 24 Sep 2024 11:29:34 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> Date: Tue, 24 Sep 2024 11:29:35 -0400 List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: watchdog timer programming To: Chris6 via freebsd-hardware References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plotbk5b.fsf@cthulhu.stephaner.labo.int> Content-Language: en-US From: mike tancsa Autocrypt: addr=mike@sentex.net; keydata= xsBNBFywzOMBCACoNFpwi5MeyEREiCeHtbm6pZJI/HnO+wXdCAWtZkS49weOoVyUj5BEXRZP xflV2ib2hflX4nXqhenaNiia4iaZ9ft3I1ebd7GEbGnsWCvAnob5MvDZyStDAuRxPJK1ya/s +6rOvr+eQiXYNVvfBhrCfrtR/esSkitBGxhUkBjOti8QwzD71JVF5YaOjBAs7jZUKyLGj0kW yDg4jUndudWU7G2yc9GwpHJ9aRSUN8e/mWdIogK0v+QBHfv/dsI6zVB7YuxCC9Fx8WPwfhDH VZC4kdYCQWKXrm7yb4TiVdBh5kgvlO9q3js1yYdfR1x8mjK2bH2RSv4bV3zkNmsDCIxjABEB AAHNHW1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5uZXQ+wsCOBBMBCAA4FiEEmuvCXT0aY6hs 4SbWeVOEFl5WrMgFAl+pQfkCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQeVOEFl5W rMiN6ggAk3H5vk8QnbvGbb4sinxZt/wDetgk0AOR9NRmtTnPaW+sIJEfGBOz47Xih+f7uWJS j+uvc9Ewn2Z7n8z3ZHJlLAByLVLtcNXGoRIGJ27tevfOaNqgJHBPbFOcXCBBFTx4MYMM4iAZ cDT5vsBTSaM36JZFtHZBKkuFEItbA/N8ZQSHKdTYMIA7A3OCLGbJBqloQ8SlW4MkTzKX4u7R yefAYQ0h20x9IqC5Ju8IsYRFacVZconT16KS81IBceO42vXTN0VexbVF2rZIx3v/NT75r6Vw 0FlXVB1lXOHKydRA2NeleS4NEG2vWqy/9Boj0itMfNDlOhkrA/0DcCurMpnpbM7ATQRcsMzk AQgA1Dpo/xWS66MaOJLwA28sKNMwkEk1Yjs+okOXDOu1F+0qvgE8sVmrOOPvvWr4axtKRSG1 t2QUiZ/ZkW/x/+t0nrM39EANV1VncuQZ1ceIiwTJFqGZQ8kb0+BNkwuNVFHRgXm1qzAJweEt RdsCMohB+H7BL5LGCVG5JaU0lqFU9pFP40HxEbyzxjsZgSE8LwkI6wcu0BLv6K6cLm0EiHPO l5G8kgRi38PS7/6s3R8QDsEtbGsYy6O82k3zSLIjuDBwA9GRaeigGppTxzAHVjf5o9KKu4O7 gC2KKVHPegbXS+GK7DU0fjzX57H5bZ6komE5eY4p3oWT/CwVPSGfPs8jOwARAQABwsB2BBgB CAAgFiEEmuvCXT0aY6hs4SbWeVOEFl5WrMgFAl+pQfkCGwwACgkQeVOEFl5WrMiVqwf9GwU8 c6cylknZX8QwlsVudTC8xr/L17JA84wf03k3d4wxP7bqy5AYy7jboZMbgWXngAE/HPQU95NM aukysSnknzoIpC96XZJ0okLBXVS6Y0ylZQ+HrbIhMpuQPoDweoF5F9wKrsHRoDaUK1VR706X rwm4HUzh7Jk+auuMYfuCh0FVlFBEuiJWMLhg/5WCmcRfiuB6F59ZcUQrwLEZeNhF2XJV4KwB Tlg7HCWO/sy1foE5noaMyACjAtAQE9p5kGYaj+DuRhPdWUTsHNuqrhikzIZd2rrcMid+ktb0 NvtvswzMO059z1YGMtGSqQ4srCArju+XHIdTFdiIYbd7+jeehg== In-Reply-To: <86plotbk5b.fsf@cthulhu.stephaner.labo.int> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.86 X-Spamd-Result: default: False [-2.13 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.986]; NEURAL_HAM_LONG(-0.97)[-0.969]; NEURAL_SPAM_SHORT(0.21)[0.212]; R_SPF_ALLOW(-0.20)[+ip6:2607:f3e0::/32]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[199.212.134.19:received]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA]; FREEFALL_USER(0.00)[mike]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; DMARC_NA(0.00)[sentex.net]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hardware@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4XCkLb0Yjxz4GjH X-Spamd-Bar: -- On 9/24/2024 2:46 AM, Stephane Rochoy wrote: > > mike tancsa writes: > >> I am trying to get >> >> superio0: at port 0x2e-0x2f on isa0 >> itwd0: at WDT ldn 0x07 on superio0 >> itwd0: Configured for system reset on timeout >> >> working on FreeBSD.  The driver seems to load / attach fine, but it does >> not want to reboot the box.  Adding a #define DIAGNOSTICS 1 >> >> shows >> >> itwd0: at WDT ldn 0x07 on superio0 >> itwd0: Configured for system reset on timeout >> itwd0: setting timeout to 4 >> itwd0: setting timeout to 4 >> itwd0: setting timeout to 4 >> itwd0: setting timeout to 4 >> itwd0: setting timeout to 4 >> itwd0: setting timeout to 4 >> >> when I do >> >>  watchdogd -t 3 >>  killall -9 watchdogd >> >> but never a reboot :( >> >> Any idea how to get this hardware working ? > > Do you know if, at least, the pre-timeout is working? Hi,     How do I check that ? > > Glancing at the code, this chip can be configured to use a specific > IRQ (its > default one is 0x40) and have an "NMI mode" (relying on an > explicitly configured IRQ). Maybe playing with the dev.itwd.irq and .nwi > tunables could get us some hints. > > Also this code from itwd's wd_func puzzle me a bit: > >    superio_write(dev, 0x73, val); >    if (superio_read(dev, 0x73) != val) >      superio_write(dev, 0x73, val); > > It let me think that we either are writing twice to the same I/O > port by mistake or the corresponding chip's register enforce a > specific protocol to modify it. If the later, the code don't seems > to be able to detect a "protocol error". > > By the way, do you have the datasheet of the ITE chip? (I know I > must be very optimistic to ask such a question ;)) I dont have the datasheet sadly. However, they do seem to be at http://www.ite.com.tw/  and are publicly available according to the Linux driver. I did load up ubuntu on the box, and the watchdog does seem to work correctly.   sysctl doesnt seem to allow for setting those values sysctl -A dev.itwd dev.itwd.0.%parent: superio0 dev.itwd.0.%pnpinfo: type=WDT dev.itwd.0.%location: ldn=0x07 dev.itwd.0.%driver: itwd dev.itwd.0.%desc: Watchdog Timer on ITE SuperIO dev.itwd.%parent: On linux, modprobe it87_wdt ] it87_wdt: Chip IT8613 revision 12 initialized. timeout=60 sec (nowayout=0 testmode=0) wdctl Device:        /dev/watchdog0 Identity:      IT87 WDT [version 1] Timeout:       60 seconds Pre-timeout:    0 seconds FLAG           DESCRIPTION               STATUS BOOT-STATUS KEEPALIVEPING  Keep alive ping reply          1           0 MAGICCLOSE     Supports magic close char      0           0 SETTIMEOUT     Set timeout (in seconds)       0           0 The code is at https://github.com/torvalds/linux/blob/master/drivers/watchdog/it87_wdt.c if that helps shed any light. i tried defining the irq and playing with the nmi at 1 or 0, and still no luck. e.g. setting it to 0x05 and nmi 0, kldload (with boot verbose) and then starting up watchdogd -t 8... wait 9 seconds,  and then killall -9 watchdogd, still does not reboot the box itwd0: at WDT ldn 0x07 on superio0 ioapic0: routing intpin 5 (ISA IRQ 5) to lapic 0 vector 56 itwd0: Using IRQ5 to signal timeout itwd0: setting timeout to 8 itwd0: setting timeout to 8 itwd0: setting timeout to 8 itwd0: setting timeout to 8 itwd0: setting timeout to 8 itwd0: setting timeout to 8 itwd0: got interrupt, wdt status = 1 Same with irq at 0x0f with and without nmi=0 or 1. itwd0: at WDT ldn 0x07 on superio0 itwd0: Using IRQ15 to signal timeout itwd0: setting timeout to 16 itwd0: setting timeout to 16 itwd0: setting timeout to 16 itwd0: setting timeout to 16 itwd0: setting timeout to 4 itwd0: setting timeout to 4 itwd0: setting timeout to 4 itwd0: setting timeout to 4 itwd0: setting timeout to 4 itwd0: setting timeout to 4 itwd0: setting timeout to 4 itwd0: setting timeout to 4     ---Mike > > Regards, From nobody Wed Sep 25 07:13:20 2024 X-Original-To: freebsd-hardware@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 4XD8FX0D5Jz5X7pL for ; Wed, 25 Sep 2024 07:56:48 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Received: from mail.stormshield.eu (mail.stormshield.eu [91.212.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.stormshield.eu", Issuer "Sectigo RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XD8FW3mtcz4M00 for ; Wed, 25 Sep 2024 07:56:47 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stormshield.eu; s=signer2; t=1727251000; h=From:Subject:Date:Message-ID:To:Cc :MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To :References; bh=1vNvUiSKbn3iSQ5Ub5C0R8JKvoyb3CESgM0R9EXv5I4=; b=mBgNiHFkM eOfGLSQanPh2jxOMf2r+4H4AECfLhhByzwFkeOq3egBmovEhaHau53n+rQ8vQi1P3aiZxhTKM ur0dxeLCPtH3TR6O7ff2PTHJbtp+8x8zbUPzFbT4oguZ9UBkIxe9qk/PpMLQR7kgQsnIf9UGf Dv4+SiZTZntNA/13D6nBNUnnvNSNRuCME46qfc9eMhz8VMB+UQGNv3xNEch6Y0z1ASJiEWZ21 ATgu45J7YaOVD9cMVPXFjEyQpGB7Ydbx+g9QNJi2ho9CKcwKWEax974CqKakdMa/cUv9u2H7w JLjw+wcIUKdvlCJtCqzb7vtTK6OhEWQSX6nMy1KfQ==; References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plotbk5b.fsf@cthulhu.stephaner.labo.int> <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> User-agent: mu4e 1.10.7; emacs 29.4 From: Stephane Rochoy To: mike tancsa CC: Chris6 via freebsd-hardware Subject: Re: watchdog timer programming Date: Wed, 25 Sep 2024 09:13:20 +0200 In-Reply-To: <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> Message-ID: <86plosdv48.fsf@cthulhu.stephaner.labo.int> List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: ICTDCCEXCH003.one.local (10.180.4.3) To ICTDCCEXCH002.one.local (10.180.4.2) X-DKIM-Signer: DkimX (v3.60.360) X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:49068, ipnet:91.212.116.0/24, country:FR] X-Rspamd-Queue-Id: 4XD8FW3mtcz4M00 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated mike tancsa writes: > On 9/24/2024 2:46 AM, Stephane Rochoy wrote: >> >> mike tancsa writes: >> >>> I am trying to get >>> >>> superio0: at port=20 >>> 0x2e-0x2f on isa0 >>> itwd0: at WDT ldn 0x07 on=20 >>> superio0 >>> itwd0: Configured for system reset on timeout >>> >>> working on FreeBSD. The driver seems to load / attach fine,=20 >>> but it does >>> not want to reboot the box. Adding a #define DIAGNOSTICS 1 >>> >>> shows >>> >>> itwd0: at WDT ldn 0x07 on=20 >>> superio0 >>> itwd0: Configured for system reset on timeout >>> itwd0: setting timeout to 4 >>> itwd0: setting timeout to 4 >>> itwd0: setting timeout to 4 >>> itwd0: setting timeout to 4 >>> itwd0: setting timeout to 4 >>> itwd0: setting timeout to 4 >>> >>> when I do >>> >>> watchdogd -t 3 >>> killall -9 watchdogd >>> >>> but never a reboot :( >>> >>> Any idea how to get this hardware working ? >> >> Do you know if, at least, the pre-timeout is working? > > How do I check that ? Using --pretimeout and --pretimeout-action. See watchdogd(8) for more details. >> By the way, do you have the datasheet of the ITE chip? (I know=20 >> I >> must be very optimistic to ask such a question ;)) > > I dont have the datasheet sadly. However, they do seem to be at > =E2=80=A6 > and are publicly available according to the > Linux driver. > > I did load up ubuntu on the box, and the watchdog does seem to=20 > work > correctly. sysctl doesnt seem to allow for setting those=20 > values The .nmi and .irq are FreeBSD-specific I guess. And they have to be set via loader.conf(5). Note sysctl !=3D tunable but tunable is, most of the time, made available as sysctl. > sysctl -A dev.itwd > dev.itwd.0.%parent: superio0 > dev.itwd.0.%pnpinfo: type=3DWDT > dev.itwd.0.%location: ldn=3D0x07 > dev.itwd.0.%driver: itwd > dev.itwd.0.%desc: Watchdog Timer on ITE SuperIO > dev.itwd.%parent: > > On linux, > modprobe it87_wdt > ] it87_wdt: Chip IT8613 revision 12 initialized. timeout=3D60 sec > (nowayout=3D0 testmode=3D0) > > wdctl > Device: /dev/watchdog0 > Identity: IT87 WDT [version 1] > Timeout: 60 seconds > Pre-timeout: 0 seconds > FLAG DESCRIPTION STATUS BOOT-STATUS > KEEPALIVEPING Keep alive ping reply 1 0 > MAGICCLOSE Supports magic close char 0 0 > SETTIMEOUT Set timeout (in seconds) 0 0 > > The code is at > https://github.com/torvalds/linux/blob/master/drivers/watchdog/it87_wdt.c > if that helps shed any light. So chip is IT8613. > i tried defining the irq and playing with the nmi at 1 or 0, and=20 > still > no luck. e.g. setting it to 0x05 and nmi 0, kldload (with boot=20 > verbose) > and then starting up watchdogd -t 8... wait 9 seconds, and then=20 > killall > -9 watchdogd, still does not reboot the box > > itwd0: at WDT ldn 0x07 on=20 > superio0 > ioapic0: routing intpin 5 (ISA IRQ 5) to lapic 0 vector 56 > itwd0: Using IRQ5 to signal timeout > itwd0: setting timeout to 8 > itwd0: setting timeout to 8 > itwd0: setting timeout to 8 > itwd0: setting timeout to 8 > itwd0: setting timeout to 8 > itwd0: setting timeout to 8 > itwd0: got interrupt, wdt status =3D 1 > > Same with irq at 0x0f with and without nmi=3D0 or 1. > > itwd0: at WDT ldn 0x07 on=20 > superio0 > itwd0: Using IRQ15 to signal timeout > itwd0: setting timeout to 16 > itwd0: setting timeout to 16 > itwd0: setting timeout to 16 > itwd0: setting timeout to 16 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 > itwd0: setting timeout to 4 OK no luck. The Linux driver don't seems to set IRQ either. Regards, --=20 St=C3=A9phane Rochoy O: Stormshield From nobody Thu Sep 26 15:56:59 2024 X-Original-To: freebsd-hardware@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 4XDysK1Nkbz5XSdN for ; Thu, 26 Sep 2024 15:57:09 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 "smarthost1.sentex.ca", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XDysJ375wz4nLs for ; Thu, 26 Sep 2024 15:57:08 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of mike@sentex.net designates 2607:f3e0:0:1::12 as permitted sender) smtp.mailfrom=mike@sentex.net; dmarc=none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.18.1/8.18.1) with ESMTPS id 48QFv1RL026177 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Thu, 26 Sep 2024 11:57:02 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:edfc:b0e1:861f:21fe] ([IPv6:2607:f3e0:0:4:edfc:b0e1:861f:21fe]) by pyroxene2a.sentex.ca (8.18.1/8.15.2) with ESMTPS id 48QFuwFS038843 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 26 Sep 2024 11:57:00 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> Date: Thu, 26 Sep 2024 11:56:59 -0400 List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: watchdog timer programming To: Chris6 via freebsd-hardware References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plotbk5b.fsf@cthulhu.stephaner.labo.int> <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> <86plosdv48.fsf@cthulhu.stephaner.labo.int> Content-Language: en-US From: mike tancsa Autocrypt: addr=mike@sentex.net; keydata= xsBNBFywzOMBCACoNFpwi5MeyEREiCeHtbm6pZJI/HnO+wXdCAWtZkS49weOoVyUj5BEXRZP xflV2ib2hflX4nXqhenaNiia4iaZ9ft3I1ebd7GEbGnsWCvAnob5MvDZyStDAuRxPJK1ya/s +6rOvr+eQiXYNVvfBhrCfrtR/esSkitBGxhUkBjOti8QwzD71JVF5YaOjBAs7jZUKyLGj0kW yDg4jUndudWU7G2yc9GwpHJ9aRSUN8e/mWdIogK0v+QBHfv/dsI6zVB7YuxCC9Fx8WPwfhDH VZC4kdYCQWKXrm7yb4TiVdBh5kgvlO9q3js1yYdfR1x8mjK2bH2RSv4bV3zkNmsDCIxjABEB AAHNHW1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5uZXQ+wsCOBBMBCAA4FiEEmuvCXT0aY6hs 4SbWeVOEFl5WrMgFAl+pQfkCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQeVOEFl5W rMiN6ggAk3H5vk8QnbvGbb4sinxZt/wDetgk0AOR9NRmtTnPaW+sIJEfGBOz47Xih+f7uWJS j+uvc9Ewn2Z7n8z3ZHJlLAByLVLtcNXGoRIGJ27tevfOaNqgJHBPbFOcXCBBFTx4MYMM4iAZ cDT5vsBTSaM36JZFtHZBKkuFEItbA/N8ZQSHKdTYMIA7A3OCLGbJBqloQ8SlW4MkTzKX4u7R yefAYQ0h20x9IqC5Ju8IsYRFacVZconT16KS81IBceO42vXTN0VexbVF2rZIx3v/NT75r6Vw 0FlXVB1lXOHKydRA2NeleS4NEG2vWqy/9Boj0itMfNDlOhkrA/0DcCurMpnpbM7ATQRcsMzk AQgA1Dpo/xWS66MaOJLwA28sKNMwkEk1Yjs+okOXDOu1F+0qvgE8sVmrOOPvvWr4axtKRSG1 t2QUiZ/ZkW/x/+t0nrM39EANV1VncuQZ1ceIiwTJFqGZQ8kb0+BNkwuNVFHRgXm1qzAJweEt RdsCMohB+H7BL5LGCVG5JaU0lqFU9pFP40HxEbyzxjsZgSE8LwkI6wcu0BLv6K6cLm0EiHPO l5G8kgRi38PS7/6s3R8QDsEtbGsYy6O82k3zSLIjuDBwA9GRaeigGppTxzAHVjf5o9KKu4O7 gC2KKVHPegbXS+GK7DU0fjzX57H5bZ6komE5eY4p3oWT/CwVPSGfPs8jOwARAQABwsB2BBgB CAAgFiEEmuvCXT0aY6hs4SbWeVOEFl5WrMgFAl+pQfkCGwwACgkQeVOEFl5WrMiVqwf9GwU8 c6cylknZX8QwlsVudTC8xr/L17JA84wf03k3d4wxP7bqy5AYy7jboZMbgWXngAE/HPQU95NM aukysSnknzoIpC96XZJ0okLBXVS6Y0ylZQ+HrbIhMpuQPoDweoF5F9wKrsHRoDaUK1VR706X rwm4HUzh7Jk+auuMYfuCh0FVlFBEuiJWMLhg/5WCmcRfiuB6F59ZcUQrwLEZeNhF2XJV4KwB Tlg7HCWO/sy1foE5noaMyACjAtAQE9p5kGYaj+DuRhPdWUTsHNuqrhikzIZd2rrcMid+ktb0 NvtvswzMO059z1YGMtGSqQ4srCArju+XHIdTFdiIYbd7+jeehg== In-Reply-To: <86plosdv48.fsf@cthulhu.stephaner.labo.int> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.86 X-Spamd-Result: default: False [-1.91 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.97)[-0.974]; NEURAL_SPAM_SHORT(0.45)[0.451]; R_SPF_ALLOW(-0.20)[+ip6:2607:f3e0::/32]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[199.212.134.19:received]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA]; FREEFALL_USER(0.00)[mike]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; DMARC_NA(0.00)[sentex.net]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hardware@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4XDysJ375wz4nLs X-Spamd-Bar: - On 9/25/2024 3:13 AM, Stephane Rochoy wrote: >>>> >>>> Any idea how to get this hardware working ? >>> >>> Do you know if, at least, the pre-timeout is working? >> >>     How do I check that ? > > Using --pretimeout and --pretimeout-action. See watchdogd(8) for > more details. > Reverting to the code thats in the tree, I started it up with watchdogd --pretimeout 10 --pretimeout-action log -t 15 Doesnt seem to work or at least it doesnt make sense to me. After I start that up, I see in the logs about 25 seconds after it starts, but not always. Sep 26 11:31:20 mpki2024 kernel: watchdog pre-timeout, WD_SOFT_LOG Sep 26 11:31:20 mpki2024 kernel: Sep 26 11:31:20 pki2024 kernel: watchdog pre-timeout, WD_SOFT_LOG and then doing a kill -9 does nothing :(     ---Mike From nobody Fri Sep 27 06:09:31 2024 X-Original-To: freebsd-hardware@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 4XFNWB0SYGz5Xgts for ; Fri, 27 Sep 2024 08:12:54 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Received: from mail.stormshield.eu (mail.stormshield.eu [91.212.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.stormshield.eu", Issuer "Sectigo RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XFNW91w7rz4LXC for ; Fri, 27 Sep 2024 08:12:53 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stormshield.eu; s=signer2; t=1727424765; h=From:Subject:Date:Message-ID:To:Cc :MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To :References; bh=ndASs+nr4YzXjVLfBYmlUtfl/RIpr5HBKfknmq3rdyk=; b=ux8OTuXuK GtqhUoW9U+0ZNme9AYAckgxFBpfphBZOPOxGFxWlxe6n38p7h8Nix2qws02UjD1ulGavaau2D j3E9FqXPJi43yqXcSlCklUPH1y9SzeY2GrHQcHhgYDJgeUsqXs0LiIgrBbvQFgFQFo7LVhEcA uCqbybHU76hyagWdeoLI55CZOzg0PXpjV5VKjJj7Px/PrRaVscIZHetJqaqOvfHUjJnNz2rOE aG6A/BdY9oq3J2TJJuBpkT5cXbuPzgF2Om+wiw0UKR/WpSHKBoimE+i2nJJwJZTFGGVMlJPFe IxYQBWJVdPDuolv+FOR9yX/21nXoSli/UhA4KIitQ==; References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plotbk5b.fsf@cthulhu.stephaner.labo.int> <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> <86plosdv48.fsf@cthulhu.stephaner.labo.int> <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> User-agent: mu4e 1.10.7; emacs 29.4 From: Stephane Rochoy To: mike tancsa CC: Chris6 via freebsd-hardware Subject: Re: watchdog timer programming Date: Fri, 27 Sep 2024 08:09:31 +0200 In-Reply-To: <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> Message-ID: <86h6a1egcs.fsf@cthulhu.stephaner.labo.int> List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: ICTDCCEXCH003.one.local (10.180.4.3) To ICTDCCEXCH002.one.local (10.180.4.2) X-DKIM-Signer: DkimX (v3.60.360) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:49068, ipnet:91.212.116.0/24, country:FR] X-Rspamd-Queue-Id: 4XFNW91w7rz4LXC X-Spamd-Bar: ---- mike tancsa writes: > On 9/25/2024 3:13 AM, Stephane Rochoy wrote: >>>>> >>>>> Any idea how to get this hardware working ? >>>> >>>> Do you know if, at least, the pre-timeout is working? >>> >>> How do I check that ? >> >> Using --pretimeout and --pretimeout-action. See watchdogd(8)=20 >> for >> more details. >> > Reverting to the code thats in the tree, I started it up with > > watchdogd --pretimeout 10 --pretimeout-action log -t 15 > > Doesnt seem to work or at least it doesnt make sense to me.=20 > After I > start that up, I see in the logs about 25 seconds after it=20 > starts, but > not always. > > Sep 26 11:31:20 mpki2024 kernel: watchdog pre-timeout,=20 > WD_SOFT_LOG > Sep 26 11:31:20 mpki2024 kernel: Sep 26 11:31:20 pki2024 kernel: > watchdog pre-timeout, WD_SOFT_LOG > > and then doing a kill -9 does nothing :( AFAIK, the pre-timeout should trigger reliably. Weird. --=20 St=C3=A9phane Rochoy O: Stormshield From nobody Fri Sep 27 13:04:30 2024 X-Original-To: freebsd-hardware@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 4XFVzl2G71z5XywF for ; Fri, 27 Sep 2024 13:04:35 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 "smarthost1.sentex.ca", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XFVzk2mwcz4x7f for ; Fri, 27 Sep 2024 13:04:34 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of mike@sentex.net designates 2607:f3e0:0:1::12 as permitted sender) smtp.mailfrom=mike@sentex.net; dmarc=none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.18.1/8.18.1) with ESMTPS id 48RD4X5e016978 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Fri, 27 Sep 2024 09:04:33 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:c94c:1f38:9f55:9ad6] ([IPv6:2607:f3e0:0:4:c94c:1f38:9f55:9ad6]) by pyroxene2a.sentex.ca (8.18.1/8.15.2) with ESMTPS id 48RD4UEV004716 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 27 Sep 2024 09:04:32 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: Date: Fri, 27 Sep 2024 09:04:30 -0400 List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: watchdog timer programming To: Chris6 via freebsd-hardware References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plotbk5b.fsf@cthulhu.stephaner.labo.int> <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> <86plosdv48.fsf@cthulhu.stephaner.labo.int> <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> <86h6a1egcs.fsf@cthulhu.stephaner.labo.int> Content-Language: en-US From: mike tancsa Autocrypt: addr=mike@sentex.net; keydata= xsBNBFywzOMBCACoNFpwi5MeyEREiCeHtbm6pZJI/HnO+wXdCAWtZkS49weOoVyUj5BEXRZP xflV2ib2hflX4nXqhenaNiia4iaZ9ft3I1ebd7GEbGnsWCvAnob5MvDZyStDAuRxPJK1ya/s +6rOvr+eQiXYNVvfBhrCfrtR/esSkitBGxhUkBjOti8QwzD71JVF5YaOjBAs7jZUKyLGj0kW yDg4jUndudWU7G2yc9GwpHJ9aRSUN8e/mWdIogK0v+QBHfv/dsI6zVB7YuxCC9Fx8WPwfhDH VZC4kdYCQWKXrm7yb4TiVdBh5kgvlO9q3js1yYdfR1x8mjK2bH2RSv4bV3zkNmsDCIxjABEB AAHNHW1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5uZXQ+wsCOBBMBCAA4FiEEmuvCXT0aY6hs 4SbWeVOEFl5WrMgFAl+pQfkCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQeVOEFl5W rMiN6ggAk3H5vk8QnbvGbb4sinxZt/wDetgk0AOR9NRmtTnPaW+sIJEfGBOz47Xih+f7uWJS j+uvc9Ewn2Z7n8z3ZHJlLAByLVLtcNXGoRIGJ27tevfOaNqgJHBPbFOcXCBBFTx4MYMM4iAZ cDT5vsBTSaM36JZFtHZBKkuFEItbA/N8ZQSHKdTYMIA7A3OCLGbJBqloQ8SlW4MkTzKX4u7R yefAYQ0h20x9IqC5Ju8IsYRFacVZconT16KS81IBceO42vXTN0VexbVF2rZIx3v/NT75r6Vw 0FlXVB1lXOHKydRA2NeleS4NEG2vWqy/9Boj0itMfNDlOhkrA/0DcCurMpnpbM7ATQRcsMzk AQgA1Dpo/xWS66MaOJLwA28sKNMwkEk1Yjs+okOXDOu1F+0qvgE8sVmrOOPvvWr4axtKRSG1 t2QUiZ/ZkW/x/+t0nrM39EANV1VncuQZ1ceIiwTJFqGZQ8kb0+BNkwuNVFHRgXm1qzAJweEt RdsCMohB+H7BL5LGCVG5JaU0lqFU9pFP40HxEbyzxjsZgSE8LwkI6wcu0BLv6K6cLm0EiHPO l5G8kgRi38PS7/6s3R8QDsEtbGsYy6O82k3zSLIjuDBwA9GRaeigGppTxzAHVjf5o9KKu4O7 gC2KKVHPegbXS+GK7DU0fjzX57H5bZ6komE5eY4p3oWT/CwVPSGfPs8jOwARAQABwsB2BBgB CAAgFiEEmuvCXT0aY6hs4SbWeVOEFl5WrMgFAl+pQfkCGwwACgkQeVOEFl5WrMiVqwf9GwU8 c6cylknZX8QwlsVudTC8xr/L17JA84wf03k3d4wxP7bqy5AYy7jboZMbgWXngAE/HPQU95NM aukysSnknzoIpC96XZJ0okLBXVS6Y0ylZQ+HrbIhMpuQPoDweoF5F9wKrsHRoDaUK1VR706X rwm4HUzh7Jk+auuMYfuCh0FVlFBEuiJWMLhg/5WCmcRfiuB6F59ZcUQrwLEZeNhF2XJV4KwB Tlg7HCWO/sy1foE5noaMyACjAtAQE9p5kGYaj+DuRhPdWUTsHNuqrhikzIZd2rrcMid+ktb0 NvtvswzMO059z1YGMtGSqQ4srCArju+XHIdTFdiIYbd7+jeehg== In-Reply-To: <86h6a1egcs.fsf@cthulhu.stephaner.labo.int> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.86 X-Spamd-Result: default: False [-3.36 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.972]; R_SPF_ALLOW(-0.20)[+ip6:2607:f3e0::/32]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[199.212.134.19:received]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA]; FREEFALL_USER(0.00)[mike]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hardware@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[sentex.net]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4XFVzk2mwcz4x7f X-Spamd-Bar: --- On 9/27/2024 2:09 AM, Stephane Rochoy wrote: > > mike tancsa writes: > >> On 9/25/2024 3:13 AM, Stephane Rochoy wrote: >>>>>> >>>>>> Any idea how to get this hardware working ? >>>>> >>>>> Do you know if, at least, the pre-timeout is working? >>>> >>>>     How do I check that ? >>> >>> Using --pretimeout and --pretimeout-action. See watchdogd(8) for >>> more details. >>> >> Reverting to the code thats in the tree, I started it up with >> >> watchdogd --pretimeout 10 --pretimeout-action log -t 15 >> >> Doesnt seem to work or at least it doesnt make sense to me. After I >> start that up, I see in the logs about 25 seconds after it starts, but >> not always. >> >> Sep 26 11:31:20 mpki2024 kernel: watchdog pre-timeout, WD_SOFT_LOG >> Sep 26 11:31:20 mpki2024 kernel: Sep 26 11:31:20 pki2024 kernel: >> watchdog pre-timeout, WD_SOFT_LOG >> >> and then doing a kill -9 does nothing :( > > AFAIK, the pre-timeout should trigger reliably. Weird. I also started to play around with the non hardware based watchdog timer.  For some reason, I cant get the box to reboot. It just prints a stack trace and continues This is with no driver loaded. 0{t}# watchdogd --softtimeout-action panic -t 5 0{t}# ps -auxww | grep dog root     1487   0.4  0.2   12820  12920  -  S; Fri, 27 Sep 2024 13:59:10 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Received: from mail.stormshield.eu (mail.stormshield.eu [91.212.116.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.stormshield.eu", Issuer "Sectigo RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XFXBj57tzz537F for ; Fri, 27 Sep 2024 13:59:09 +0000 (UTC) (envelope-from Stephane.ROCHOY@stormshield.eu) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stormshield.eu; s=signer2; t=1727445547; h=From:Subject:Date:Message-ID:To:Cc :MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To :References; bh=49wzRYuPlVaPSppmw24NnDgHImqrOHWxDIXDNSVOON4=; b=jIWKjloEe IbNCyEFLebrGZnmeGQLqBnMH6LHI3ngjROyL6HWqGmEK+bHGKZCuAcnnz4ibVvCAdxaH53MC7 XdyCVL7BKiuBmv/S/A2SW7oxRDHEGnIfCXVtz1YaiTl6knRKfIdyb3xV4f2Q1cvZwTLs9J6L+ aAdUJO9KeZvHj+SLKQopF8LGOHgs+j6f2WyfHhh8uLTURktiGSIM86ESkCxigtUZq/TuoYOwS ith+mDbxWvB5MdHwqwS0KrZYegKVnEcgePmX4WbDVkSV2M3OAs8Dh1wRCMYJTjGT5x7Ew+PHg WJTPapiF9EUk52tmo6nsyvQx2ccLJbvao4br13EDg==; References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plotbk5b.fsf@cthulhu.stephaner.labo.int> <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> <86plosdv48.fsf@cthulhu.stephaner.labo.int> <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> <86h6a1egcs.fsf@cthulhu.stephaner.labo.int> User-agent: mu4e 1.10.7; emacs 29.4 From: Stephane Rochoy To: mike tancsa CC: Chris6 via freebsd-hardware Subject: Re: watchdog timer programming Date: Fri, 27 Sep 2024 15:55:40 +0200 In-Reply-To: Message-ID: <868qvddwph.fsf@cthulhu.stephaner.labo.int> List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: ICTDCCEXCH003.one.local (10.180.4.3) To ICTDCCEXCH002.one.local (10.180.4.2) X-DKIM-Signer: DkimX (v3.60.360) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:49068, ipnet:91.212.116.0/24, country:FR] X-Rspamd-Queue-Id: 4XFXBj57tzz537F X-Spamd-Bar: ---- mike tancsa writes: > I also started to play around with the non hardware based=20 > watchdog > timer. For some reason, I cant get the box to reboot. It just=20 > prints a > stack trace and continues > > This is with no driver loaded. > > 0{t}# watchdogd --softtimeout-action panic -t 5 > 0{t}# ps -auxww | grep dog > root 1487 0.4 0.2 12820 12920 - S watchdogd > --softtimeout-action panic -t 5 > root 1489 0.0 0.0 12808 2636 u0 S+ 09:03=20 > 0:00.00 > grep dog > 0{t}# kill -9 1487 > 0{t}# KDB: stack backtrace: > #0 0xffffffff80b7fefd at kdb_backtrace+0x5d > #1 0xffffffff80abec93 at hardclock+0x103 > #2 0xffffffff80abfe8b at handleevents+0xab > #3 0xffffffff80ac0b7c at timercb+0x24c > #4 0xffffffff810d0ebb at lapic_handle_timer+0xab > #5 0xffffffff80fd8a71 at Xtimerint+0xb1 > #6 0xffffffff804b3685 at acpi_cpu_idle+0x2c5 > #7 0xffffffff80fc48f6 at cpu_idle_acpi+0x46 > #8 0xffffffff80fc49ad at cpu_idle+0x9d > #9 0xffffffff80b67bb6 at sched_idletd+0x576 > #10 0xffffffff80aecf7f at fork_exit+0x7f > #11 0xffffffff80fd7dae at fork_trampoline+0xe > > 0{t}# > > Should it not reboot at this point ? I don't think so. `kdb_backtrace` being involved let me think the kernel was compiled with KDB. You should play with ddb(8) to set a default action like reset when entering kdb. Regards, --=20 St=C3=A9phane Rochoy O: Stormshield From nobody Fri Sep 27 14:15:23 2024 X-Original-To: freebsd-hardware@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 4XFXYV1Q8jz5Y3hq for ; Fri, 27 Sep 2024 14:15:26 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 "smarthost1.sentex.ca", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XFXYT5L6dz54Mv for ; Fri, 27 Sep 2024 14:15:25 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of mike@sentex.net designates 2607:f3e0:0:1::12 as permitted sender) smtp.mailfrom=mike@sentex.net; dmarc=none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.18.1/8.18.1) with ESMTPS id 48REFPDO043189 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Fri, 27 Sep 2024 10:15:25 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:c94c:1f38:9f55:9ad6] ([IPv6:2607:f3e0:0:4:c94c:1f38:9f55:9ad6]) by pyroxene2a.sentex.ca (8.18.1/8.15.2) with ESMTPS id 48REFMTs024483 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 27 Sep 2024 10:15:24 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <2d850ccc-2e90-4a1a-927c-045d4750d570@sentex.net> Date: Fri, 27 Sep 2024 10:15:23 -0400 List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: watchdog timer programming To: Chris6 via freebsd-hardware References: <3065debc-8d4f-4487-abbb-c9408810cea6@sentex.net> <86plotbk5b.fsf@cthulhu.stephaner.labo.int> <9008b389-ab06-401d-9a95-84f849ca602a@sentex.net> <86plosdv48.fsf@cthulhu.stephaner.labo.int> <78e9461c-b93d-403f-b3a1-3568548b9283@sentex.net> <86h6a1egcs.fsf@cthulhu.stephaner.labo.int> <868qvddwph.fsf@cthulhu.stephaner.labo.int> Content-Language: en-US From: mike tancsa Autocrypt: addr=mike@sentex.net; keydata= xsBNBFywzOMBCACoNFpwi5MeyEREiCeHtbm6pZJI/HnO+wXdCAWtZkS49weOoVyUj5BEXRZP xflV2ib2hflX4nXqhenaNiia4iaZ9ft3I1ebd7GEbGnsWCvAnob5MvDZyStDAuRxPJK1ya/s +6rOvr+eQiXYNVvfBhrCfrtR/esSkitBGxhUkBjOti8QwzD71JVF5YaOjBAs7jZUKyLGj0kW yDg4jUndudWU7G2yc9GwpHJ9aRSUN8e/mWdIogK0v+QBHfv/dsI6zVB7YuxCC9Fx8WPwfhDH VZC4kdYCQWKXrm7yb4TiVdBh5kgvlO9q3js1yYdfR1x8mjK2bH2RSv4bV3zkNmsDCIxjABEB AAHNHW1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5uZXQ+wsCOBBMBCAA4FiEEmuvCXT0aY6hs 4SbWeVOEFl5WrMgFAl+pQfkCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQeVOEFl5W rMiN6ggAk3H5vk8QnbvGbb4sinxZt/wDetgk0AOR9NRmtTnPaW+sIJEfGBOz47Xih+f7uWJS j+uvc9Ewn2Z7n8z3ZHJlLAByLVLtcNXGoRIGJ27tevfOaNqgJHBPbFOcXCBBFTx4MYMM4iAZ cDT5vsBTSaM36JZFtHZBKkuFEItbA/N8ZQSHKdTYMIA7A3OCLGbJBqloQ8SlW4MkTzKX4u7R yefAYQ0h20x9IqC5Ju8IsYRFacVZconT16KS81IBceO42vXTN0VexbVF2rZIx3v/NT75r6Vw 0FlXVB1lXOHKydRA2NeleS4NEG2vWqy/9Boj0itMfNDlOhkrA/0DcCurMpnpbM7ATQRcsMzk AQgA1Dpo/xWS66MaOJLwA28sKNMwkEk1Yjs+okOXDOu1F+0qvgE8sVmrOOPvvWr4axtKRSG1 t2QUiZ/ZkW/x/+t0nrM39EANV1VncuQZ1ceIiwTJFqGZQ8kb0+BNkwuNVFHRgXm1qzAJweEt RdsCMohB+H7BL5LGCVG5JaU0lqFU9pFP40HxEbyzxjsZgSE8LwkI6wcu0BLv6K6cLm0EiHPO l5G8kgRi38PS7/6s3R8QDsEtbGsYy6O82k3zSLIjuDBwA9GRaeigGppTxzAHVjf5o9KKu4O7 gC2KKVHPegbXS+GK7DU0fjzX57H5bZ6komE5eY4p3oWT/CwVPSGfPs8jOwARAQABwsB2BBgB CAAgFiEEmuvCXT0aY6hs4SbWeVOEFl5WrMgFAl+pQfkCGwwACgkQeVOEFl5WrMiVqwf9GwU8 c6cylknZX8QwlsVudTC8xr/L17JA84wf03k3d4wxP7bqy5AYy7jboZMbgWXngAE/HPQU95NM aukysSnknzoIpC96XZJ0okLBXVS6Y0ylZQ+HrbIhMpuQPoDweoF5F9wKrsHRoDaUK1VR706X rwm4HUzh7Jk+auuMYfuCh0FVlFBEuiJWMLhg/5WCmcRfiuB6F59ZcUQrwLEZeNhF2XJV4KwB Tlg7HCWO/sy1foE5noaMyACjAtAQE9p5kGYaj+DuRhPdWUTsHNuqrhikzIZd2rrcMid+ktb0 NvtvswzMO059z1YGMtGSqQ4srCArju+XHIdTFdiIYbd7+jeehg== In-Reply-To: <868qvddwph.fsf@cthulhu.stephaner.labo.int> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.86 X-Spamd-Result: default: False [-3.39 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+ip6:2607:f3e0::/32]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[199.212.134.19:received]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA]; FREEFALL_USER(0.00)[mike]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hardware@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[sentex.net]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4XFXYT5L6dz54Mv X-Spamd-Bar: --- On 9/27/2024 9:55 AM, Stephane Rochoy wrote: > > mike tancsa writes: > >> I also started to play around with the non hardware based watchdog >> timer.  For some reason, I cant get the box to reboot. It just prints a >> stack trace and continues >> >> This is with no driver loaded. >> >> 0{t}# watchdogd --softtimeout-action panic -t 5 >> 0{t}# ps -auxww | grep dog >> root     1487   0.4  0.2   12820  12920  -  S> --softtimeout-action panic -t 5 >> root     1489   0.0  0.0   12808   2636 u0  S+   09:03 0:00.00 >> grep dog >> 0{t}# kill -9 1487 >> 0{t}# KDB: stack backtrace: >> #0 0xffffffff80b7fefd at kdb_backtrace+0x5d >> #1 0xffffffff80abec93 at hardclock+0x103 >> #2 0xffffffff80abfe8b at handleevents+0xab >> #3 0xffffffff80ac0b7c at timercb+0x24c >> #4 0xffffffff810d0ebb at lapic_handle_timer+0xab >> #5 0xffffffff80fd8a71 at Xtimerint+0xb1 >> #6 0xffffffff804b3685 at acpi_cpu_idle+0x2c5 >> #7 0xffffffff80fc48f6 at cpu_idle_acpi+0x46 >> #8 0xffffffff80fc49ad at cpu_idle+0x9d >> #9 0xffffffff80b67bb6 at sched_idletd+0x576 >> #10 0xffffffff80aecf7f at fork_exit+0x7f >> #11 0xffffffff80fd7dae at fork_trampoline+0xe >> >> 0{t}# >> >> Should it not reboot at this point ? > > I don't think so. `kdb_backtrace` being involved let me think the > kernel was compiled with KDB. You should play with ddb(8) to set a > default action like reset when entering kdb. > Hmmm, Its a GENERIC kernel, # Debugging support.  Always need this: options         KDB                     # Enable kernel debugger support. options         KDB_TRACE               # Print a stack trace for a panic. Do you know off hand how to set the system to just reboot ? The ddb man page seems to imply I need options DDB as well, which is not in GENERIC in order to set script actions. # sysctl -a debug.kdb debug.kdb.enter_securelevel: 0 debug.kdb.alt_break_to_debugger: 0 debug.kdb.break_to_debugger: 0 debug.kdb.stack_overflow: 0 debug.kdb.trap_code: 0 debug.kdb.trap: 0 debug.kdb.panic_str: debug.kdb.panic: 0 debug.kdb.enter: 0 debug.kdb.current: debug.kdb.available:     ---Mike