From owner-freebsd-riscv@freebsd.org Mon Dec 16 19:13:16 2019 Return-Path: Delivered-To: freebsd-riscv@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 E88C01CC66F for ; Mon, 16 Dec 2019 19:13:16 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47c9sS5lN7z4DJ7 for ; Mon, 16 Dec 2019 19:13:16 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: from mail-ot1-f54.google.com (mail-ot1-f54.google.com [209.85.210.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: mhorne) by smtp.freebsd.org (Postfix) with ESMTPSA id A871FC47 for ; Mon, 16 Dec 2019 19:13:16 +0000 (UTC) (envelope-from mhorne@freebsd.org) Received: by mail-ot1-f54.google.com with SMTP id i4so10436947otr.3 for ; Mon, 16 Dec 2019 11:13:16 -0800 (PST) X-Gm-Message-State: APjAAAX4PHfZBvjVI8G7rjzggtQN1UXtzdK6TrIN7p+wknrAn7y0Yroj 3T08/UIJV6LFR9wqVJ7sLPQ9RvAicFNoo51DyGw= X-Google-Smtp-Source: APXvYqwRroH6aDLElZe3wuCWOJciHQBTcJXBgys6AwDOlipgHIFbcrg+d+k//EpLWY3vPoDw4xXbokn00mxHyVMsAUI= X-Received: by 2002:a05:6830:1d1:: with SMTP id r17mr35349519ota.151.1576523595601; Mon, 16 Dec 2019 11:13:15 -0800 (PST) MIME-Version: 1.0 References: <2bc61d55-e45d-0b10-34ee-14bad17ed693@blastwave.org> In-Reply-To: <2bc61d55-e45d-0b10-34ee-14bad17ed693@blastwave.org> From: Mitchell Horne Date: Mon, 16 Dec 2019 14:13:03 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: r355009 dies with a kernel panic To: Dennis Clarke Cc: freebsd-riscv Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-riscv@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD on the RISC-V instruction set architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2019 19:13:17 -0000 On Thu, Nov 28, 2019 at 3:15 PM Dennis Clarke wrote: > > > While is it fine that the CI does a bare bones compile I don't know > if anyone actually tries to run it for a period of time. If r355009 > is left running for a few hours ( on QEMU ) it merely dies with a > panic : > > > panic: deadlres_td_sleep_q: possible deadlock detected for > 0xffffffd04630a560, blocked for 180225 ticks > > cpuid = 0 > time = 1574915402 > KDB: stack backtrace: > db_trace_self() at db_read_token_flags+0x696 > pc = 0xffffffc0004ca28a ra = 0xffffffc0000d289c > sp = 0xffffffc024bb4790 fp = 0xffffffc024bb49b0 > > db_read_token_flags() at kdb_backtrace+0x2e > pc = 0xffffffc0000d289c ra = 0xffffffc00026b98c > sp = 0xffffffc024bb49b0 fp = 0xffffffc024bb4a60 > > kdb_backtrace() at vpanic+0x14a > pc = 0xffffffc00026b98c ra = 0xffffffc00022dfac > sp = 0xffffffc024bb4a60 fp = 0xffffffc024bb4aa0 > > vpanic() at panic+0x22 > pc = 0xffffffc00022dfac ra = 0xffffffc00022dfe4 > sp = 0xffffffc024bb4aa0 fp = 0xffffffc024bb4ac0 > > panic() at acct_process+0x676 > pc = 0xffffffc00022dfe4 ra = 0xffffffc0001de0aa > sp = 0xffffffc024bb4ac0 fp = 0xffffffc024bb4b80 > > acct_process() at fork_exit+0x5c > pc = 0xffffffc0001de0aa ra = 0xffffffc0001fbd02 > sp = 0xffffffc024bb4b80 fp = 0xffffffc024bb4bc0 > > fork_exit() at fork_trampoline+0xa > pc = 0xffffffc0001fbd02 ra = 0xffffffc0004d768a > sp = 0xffffffc024bb4bc0 fp = 0xffffffc0001ddea4 > > fork_trampoline() at 0xb7e1dbe985ce8b81 > pc = 0xffffffc0004d768a ra = 0xb7e1dbe985ce8b81 > sp = 0xffffffc0001ddea4 fp = 0x40a7d7b3000a3783 > > KDB: enter: panic > [ thread pid 0 tid 100030 ] > Stopped at kdb_enter+0x3a: c.ebreak > db> Killed > Hi Dennis, thanks for the report. I have encountered this panic in the past as well. Were you running something on your RISC-V system when this happened or was it idle? How many cpus did you run qemu with? I tried to recreate it with an idle system as I have done in the past but have seen nothing yet: root@qemu:~ # uptime 10:15PM up 4 days, 19:45, 1 user, load averages: 0.18, 0.28, 0.30 Could you try again with a more recent HEAD (note there is some breakage at the exact time of writing) and let me know if the issue is still present? Mitchell > > So is anyone anywhere trying to run FreeBSD on RISC-V at all or just me? > > -- > Dennis Clarke > RISC-V/SPARC/PPC/ARM/CISC > UNIX and Linux spoken > GreyBeard and suspenders optional > _______________________________________________ > freebsd-riscv@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-riscv > To unsubscribe, send any mail to "freebsd-riscv-unsubscribe@freebsd.org" From owner-freebsd-riscv@freebsd.org Mon Dec 16 21:11:52 2019 Return-Path: Delivered-To: freebsd-riscv@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 216C31CED34 for ; Mon, 16 Dec 2019 21:11:52 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mail-yw1-f44.google.com (mail-yw1-f44.google.com [209.85.161.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47cDVJ04FSz4Kg8; Mon, 16 Dec 2019 21:11:51 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: by mail-yw1-f44.google.com with SMTP id b186so3091570ywc.1; Mon, 16 Dec 2019 13:11:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=p96iWYR20AvJ7P4uuKsYYsOo+OyTpg5umh8HH+XprVU=; b=giQ6iB3Om4mudf03XbZNU+dlFqC4EORGYqrdtgPM1S8MT8fIA7SXDwwqn7W6Wu8o/6 YVgVZO8jgGqc6WtqDDhDL+qNlkzv0Fz0jcFG4ZohTPuVeP3+mWdyRm9GB5txgXnCP5/d kuremytiqs09l0Mb9JWwZzwuDHUPJmYeOU/+nKrkmzl34vp6z5El+25ttwcMnYvI9vY3 Zad3KOj1Gu0kpXv8IwnajDKh68+5+NzFyXeWcezOrcNv9d4oJRsIM6HeFLz4888/l2d9 SZfG/F5SsaJ7QdtSifErY24jX6T6WKjNWVQbRRX+FUSzXvn+zhp7BVnKVU5r43MZMuCD gEFw== X-Gm-Message-State: APjAAAXGCzB5aPZkkWGHBHqCPHkKczBMQiq0xfqNjSnwUelEREqZDp2z INeKQUMWKiocrIKu0O2ro30/6DmyJgzD7IFs8YFRb9KT X-Google-Smtp-Source: APXvYqxsNrc8GB+DIC35WqUoaHVvpPXe9+R+Idr0Ug22Bb74tRTrLMzFheKZZHWYJdVIrEuI+yubGYWI/PMCzVVYs9k= X-Received: by 2002:a0d:c3c2:: with SMTP id f185mr20404622ywd.21.1576530710510; Mon, 16 Dec 2019 13:11:50 -0800 (PST) MIME-Version: 1.0 References: <2bc61d55-e45d-0b10-34ee-14bad17ed693@blastwave.org> In-Reply-To: From: Li-Wen Hsu Date: Tue, 17 Dec 2019 05:11:37 +0800 Message-ID: Subject: Re: r355009 dies with a kernel panic To: Mitchell Horne Cc: Dennis Clarke , freebsd-riscv Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 47cDVJ04FSz4Kg8 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-riscv@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD on the RISC-V instruction set architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2019 21:11:52 -0000 Please check that the CI actually also has a test job running with qemu: https://ci.freebsd.org/job/FreeBSD-head-riscv64-test/ For now it's just running a boot test. But in the near future we're going to run regression test in it. If you have a reproducible case to trigger this panic, we can add to the test suite. Li-Wen