From nobody Wed Aug 17 13:12:07 2022 X-Original-To: freebsd-arm@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 4M77hw6lh6z4ZQr4 for ; Wed, 17 Aug 2022 13:12:16 +0000 (UTC) (envelope-from SRS0=JOj7=YV=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4M77hv6JcLz3CFl for ; Wed, 17 Aug 2022 13:12:15 +0000 (UTC) (envelope-from SRS0=JOj7=YV=klop.ws=ronald-lists@realworks.nl) Date: Wed, 17 Aug 2022 15:12:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1660741928; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=tczAnZKn+q7grqB6T1vEq81IAqu+zppv7o4M60NOMl8=; b=FisLiQalXd7K6mphfLCZDJ3bT5k12fHeFO/X9EJntLBzSwP9+Itp6/P6xZdWTxfWnnH1id gEBlpUyJeNrNrYyM2evRew5dwhHvCamNDalsE01yjnka7iw8VrTnwlFI6ANVCO/c0yJ4yz UCpn5Tgmhhxo5CXvLTuLvUIvPSg/Z6fKArvy0a20tUm8Zn6dKj+R4IwQDaA4SmL6s/td5A i0nfKaSqOd6kcBR99i+csPGNNC3l2In/hslVyG5XklN1Sx2/xefMUjTq2xN56miasrd7hh /uzAyob4/mQotxKVXtUo45uXJtDvvGyOVao18A6rLOC1KGE305E8ADCwZ8Ld9g== From: Ronald Klop To: soumar@soudny.net Cc: freebsd-arm Message-ID: <848514130.250.1660741927565@localhost> In-Reply-To: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> References: <15b7779f-db37-efd7-69ba-378636b93017@soudny.net> Subject: Re: kernel: Fatal data abort - issue on rpi4 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_249_1865712854.1660741927496" X-Mailer: Realworks (619.111) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4M77hv6JcLz3CFl X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=FisLiQal; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=JOj7=YV=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=JOj7=YV=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.20 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=JOj7=YV=klop.ws=ronald-lists@realworks.nl]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ZERO(0.00)[0]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_HAS_DN(0.00)[]; HAS_X_PRIO_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=JOj7=YV=klop.ws=ronald-lists@realworks.nl] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_249_1865712854.1660741927496 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, Another SD card is worth a try. According to the forum post SanDisk works good. My RPI4 runs from USB-disk which works stable. Regards, Ronald. Van: Marek Soudny Datum: woensdag, 17 augustus 2022 11:10 Aan: freebsd-arm Onderwerp: kernel: Fatal data abort - issue on rpi4 > > Hello, > > I am quite new to arm/aarch64. I recently purchased rpi4, burned an sdcard image and have been trying to run it. Time to time (but actually quite often) the box becomes unresponsive. I can not ping it, neither ssh into it. I am running fbsd 13.1-release. > > The syslog only shows the following: > > Aug 16 08:27:54 maxwell kernel: Fatal data abort: > Aug 16 08:27:54 maxwell kernel: x0: 1 > Aug 16 08:27:54 maxwell kernel: x1: 0 > Aug 16 08:27:54 maxwell kernel: x2: ffffa00004a99500 > Aug 16 08:27:54 maxwell kernel: x3: 13ffffe8e > Aug 16 08:27:54 maxwell kernel: x4: ffff0000e00ab4d4 > Aug 16 08:27:54 maxwell kernel: x5: ffffa00001319000 > Aug 16 08:27:54 maxwell kernel: > Aug 16 08:27:54 maxwell kernel: x6: 0 > Aug 16 08:27:54 maxwell kernel: x7: 100 > Aug 16 08:27:54 maxwell kernel: x8: ffffa00004a99500 > Aug 16 08:27:54 maxwell kernel: x9: 0 > Aug 16 08:27:54 maxwell kernel: x10: ffff000000c35378 > Aug 16 08:27:54 maxwell kernel: x11: 0 > Aug 16 08:27:54 maxwell kernel: x12: 1 > Aug 16 08:27:54 maxwell kernel: x13: 0 > Aug 16 08:27:54 maxwell kernel: x14: 700000000 > Aug 16 08:27:54 maxwell kernel: > Aug 16 08:27:54 maxwell kernel: x15: 39 > Aug 16 08:27:54 maxwell kernel: x16: ffff0000e00c9be0 > Aug 16 08:27:54 maxwell kernel: x17: ffff000000614fd4 > Aug 16 08:27:54 maxwell kernel: x18: ffff0000dfbf4760 > Aug 16 08:27:54 maxwell kernel: > Aug 16 08:27:54 maxwell kernel: x19: ffffa00001319198 > Aug 16 08:27:54 maxwell kernel: x20: ffffa00001319000 > Aug 16 08:27:54 maxwell kernel: x21: ffffa00004d3b800 > Aug 16 08:27:54 maxwell kernel: x22: ffffa000013191b8 > Aug 16 08:27:54 maxwell kernel: > Aug 16 08:27:54 maxwell kernel: x23: ffffa000013190e0 > Aug 16 08:27:54 maxwell kernel: x24: ffffa000013191a0 > Aug 16 08:27:54 maxwell kernel: x25: ffffa000016e7200 > Aug 16 08:27:54 maxwell kernel: x26: ffff0000e009768e > Aug 16 08:27:54 maxwell kernel: > Aug 16 08:27:54 maxwell kernel: x27: ffffa00004a99500 > Aug 16 08:27:54 maxwell kernel: x28: ffffa00004e82d00 > Aug 16 08:27:54 maxwell kernel: x29: ffff0000dfbf4770 > Aug 16 08:27:54 maxwell kernel: sp: ffff0000dfbf4760 > > Does it sound familiar? Am I doing something wrong? As it's currently not stable, I can perform any tests with it, if required. I actually found a similar issue https://forums.freebsd.org/threads/fatal-kernel-mode-data-abort-every-2-3-boots-on-raspberry-pi-b.49066/ - do you think it's an sdcard issue? If so, is there a recommended list for purchase new ones? > > Thank you, > Marek > > > > ------=_Part_249_1865712854.1660741927496 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

Another SD card is worth a try.
According to the forum post SanDisk works good.
My RPI4 runs from USB-disk which works stable.

Regards,
Ronald.

 

Van: Marek Soudny <soumar@soudny.net>
Datum: woensdag, 17 augustus 2022 11:10
Aan: freebsd-arm <freebsd-arm@freebsd.org>
Onderwerp: kernel: Fatal data abort - issue on rpi4

Hello,

I am quite new to arm/aarch64. I recently purchased rpi4, burned an sdcard image and have been trying to run it. Time to time (but actually quite often) the box becomes unresponsive. I can not ping it, neither ssh into it. I am running fbsd 13.1-release.

The syslog only shows the following:

Aug 16 08:27:54 maxwell kernel: Fatal data abort:
Aug 16 08:27:54 maxwell kernel:   x0:                1
Aug 16 08:27:54 maxwell kernel:   x1:                0
Aug 16 08:27:54 maxwell kernel:   x2: ffffa00004a99500
Aug 16 08:27:54 maxwell kernel:   x3:        13ffffe8e
Aug 16 08:27:54 maxwell kernel:   x4: ffff0000e00ab4d4
Aug 16 08:27:54 maxwell kernel:   x5: ffffa00001319000
Aug 16 08:27:54 maxwell kernel:
Aug 16 08:27:54 maxwell kernel:   x6:                0
Aug 16 08:27:54 maxwell kernel:   x7:              100
Aug 16 08:27:54 maxwell kernel:   x8: ffffa00004a99500
Aug 16 08:27:54 maxwell kernel:   x9:                0
Aug 16 08:27:54 maxwell kernel:  x10: ffff000000c35378
Aug 16 08:27:54 maxwell kernel:  x11:                0
Aug 16 08:27:54 maxwell kernel:  x12:                1
Aug 16 08:27:54 maxwell kernel:  x13:                0
Aug 16 08:27:54 maxwell kernel:  x14:        700000000
Aug 16 08:27:54 maxwell kernel:
Aug 16 08:27:54 maxwell kernel:  x15:               39
Aug 16 08:27:54 maxwell kernel:  x16: ffff0000e00c9be0
Aug 16 08:27:54 maxwell kernel:  x17: ffff000000614fd4
Aug 16 08:27:54 maxwell kernel:  x18: ffff0000dfbf4760
Aug 16 08:27:54 maxwell kernel:
Aug 16 08:27:54 maxwell kernel:  x19: ffffa00001319198
Aug 16 08:27:54 maxwell kernel:  x20: ffffa00001319000
Aug 16 08:27:54 maxwell kernel:  x21: ffffa00004d3b800
Aug 16 08:27:54 maxwell kernel:  x22: ffffa000013191b8
Aug 16 08:27:54 maxwell kernel:
Aug 16 08:27:54 maxwell kernel:  x23: ffffa000013190e0
Aug 16 08:27:54 maxwell kernel:  x24: ffffa000013191a0
Aug 16 08:27:54 maxwell kernel:  x25: ffffa000016e7200
Aug 16 08:27:54 maxwell kernel:  x26: ffff0000e009768e
Aug 16 08:27:54 maxwell kernel:
Aug 16 08:27:54 maxwell kernel:  x27: ffffa00004a99500
Aug 16 08:27:54 maxwell kernel:  x28: ffffa00004e82d00
Aug 16 08:27:54 maxwell kernel:  x29: ffff0000dfbf4770
Aug 16 08:27:54 maxwell kernel:   sp: ffff0000dfbf4760

Does it sound familiar? Am I doing something wrong? As it's currently not stable, I can perform any tests with it, if required. I actually found a similar issue https://forums.freebsd.org/threads/fatal-kernel-mode-data-abort-every-2-3-boots-on-raspberry-pi-b.49066/ - do you think it's an sdcard issue? If so, is there a recommended list for purchase new ones?

Thank you,
Marek
 
------=_Part_249_1865712854.1660741927496--