From owner-freebsd-current@freebsd.org Sat Dec 30 21:12:03 2017 Return-Path: Delivered-To: freebsd-current@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 C6B6AEACE8E for ; Sat, 30 Dec 2017 21:12:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 5EA436D7E4 for ; Sat, 30 Dec 2017 21:12:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id vBULBspd041139 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 30 Dec 2017 23:11:57 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua vBULBspd041139 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id vBULBsm6041138; Sat, 30 Dec 2017 23:11:54 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 30 Dec 2017 23:11:54 +0200 From: Konstantin Belousov To: Matthias Apitz , freebsd-current@freebsd.org Subject: Re: panic: invalid bcd 194 Message-ID: <20171230211154.GT1684@kib.kiev.ua> References: <20171230210711.GA75976@c720-r314251> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171230210711.GA75976@c720-r314251> User-Agent: Mutt/1.9.2 (2017-12-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Dec 2017 21:12:03 -0000 On Sat, Dec 30, 2017 at 10:07:11PM +0100, Matthias Apitz wrote: > El d??a s??bado, diciembre 30, 2017 a las 10:44:57p. m. +0200, Konstantin Belousov escribi??: > > > On Sat, Dec 30, 2017 at 09:03:17PM +0100, Matthias Apitz wrote: > > > > > > Hello, > > > > > > I've got an older Acer C720 with r314251, which was not booted for some time, > > > and now panics on boot, also in single user mode, saying: > > > > > > ... > > > Dec 30 19:54:26 c720-r314251 kernel: ada0: Command Queueing enabled > > > Dec 30 19:54:26 c720-r314251 kernel: ada0: 244198MB (500118192 512 byte sectors) > > > Dec 30 19:54:26 c720-r314251 kernel: WARNING: WITNESS option enabled, expect reduced performance. > > > Dec 30 19:54:26 c720-r314251 kernel: Trying to mount root from ufs:/dev/ada0p2 [rw,noatime]... > > > panic: invalid bcd 194 > > > ... > > > > > > The message comes from > > > > > > $ find * -type f -exec fgrep "invalid bcd" {} /dev/null \; > > > sys/sys/libkern.h: ("invalid bcd %d", bcd)); > > > > > > $ vim sys/sys/libkern.h > > > ... > > > #define LIBKERN_LEN_BCD2BIN 154 > > > #define LIBKERN_LEN_BIN2BCD 100 > > > #define LIBKERN_LEN_HEX2ASCII 36 > > > > > > static inline u_char > > > bcd2bin(int bcd) > > > { > > > > > > KASSERT(bcd >= 0 && bcd < LIBKERN_LEN_BCD2BIN, > > > ("invalid bcd %d", bcd)); > > > return (bcd2bin_data[bcd]); > > > } > > > > > > Any idea what could be damaged the system and what to do or check before > > > re-setup? > > > > Show the backtrace. > > Thanks, here we have it as photo: http://www.unixarea.de/download_238222137_147226.jpg For an immediate relief, enter the BIOS setup and set up the date. Try to change it even if the BIOS date looks fine. artc(4) should do more validation of the date read from CMOS, but this is a known issue.