From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_03_06,DKIM_SIGNED, DKIM_VALID autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 22436 invoked from network); 27 Jan 2021 05:55:07 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 27 Jan 2021 05:55:07 -0000 Received: from a48-181.smtp-out.amazonses.com ([54.240.48.181]) by 1ess; Tue Jan 26 21:33:06 -0500 2021 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1611714777; h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:To:In-Reply-To:Message-Id:Feedback-ID; bh=+Deh04t+iZMn1IewBn0yhpzzBKH259E0I3CRssq4QMo=; b=KgL5Tm/4rRnsYwRcMn5tuormlk7YYsaGPXzKR0IIMUFxVOj+Sqyzjhxrjlv8BBPH 3X3++rIm6+Bjz1/Z7xoMg6l1ZuD21J44Zj+BHLMWqKKG1/jSNNp7Hj6LmLe2/k1VEdl i26XveNh7wl5d7jI22HaDiZsZTMvQ/0qsVX64AxE= X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.202.122.66; envelope-from=; From: Mack Wallace Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) Date: Wed, 27 Jan 2021 02:32:57 +0000 References: <358AB57987F7B4208CD18104830D2852@felloff.net> To: 9front@9front.org In-Reply-To: <358AB57987F7B4208CD18104830D2852@felloff.net> Message-ID: <0100017741afd09d-da43b097-8dba-46b2-98d9-05414e118708-000000@email.amazonses.com> X-Mailer: Apple Mail (2.3608.120.23.2.1) X-Authenticated-User: mackbw@mapinternet.com X-SES-Outgoing: 2021.01.27-54.240.48.181 Feedback-ID: 1.us-east-1.X+xhoL9JiEQ8K0gzGjV36WZnSewOzOs8YCWuakKsLBY=:AmazonSES List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: realtime pipelining service realtime-java generator Subject: Re: [9front] 9front on Raspberry Pi 400 Reply-To: 9front@9front.org Precedence: bulk So I tried the two kernels you sent. No revelations there. The pci enable kernel leave me with about the same thing. The only = difference this time is the emmc: error went away and the line for the = BCM Host Controller. So we get this: xhci 600000000: controller not ready before reset: 00000815 xhci 600000000: controller not halted after reset: 00000815 xhci 600000000: controller not ready after run: 0000080d #l0: phy1 id 600d84a2 oui 80361 xhci 600000000: controller not ready before reset: 0000080d sdhc: read error intr 2008002 stat 1fff0000 ... sdhc: read error intr 2008002 stat 1fff0000 /dev/sdM0: BCM SD Host Controller 02 Version 10x sdhc: read error intr 2008002 stat 1fff0000 ... sdhc: read error intr 2008002 stat 1fff0000 bootargs is (tcp, tls, il, local!device)[]xhci 600000000: controller not = halted after reset: 00000811 xhci 600000000: controller not ready after run: 0000080d xhci 600000000: controller not ready before reset: 0000080d xhci 600000000: controller not halted after reset: 00000811 xhci 600000000: controller not ready after run: 0000080d xhci 600000000: controller not ready before reset: 0000080d xhci 600000000: controller not halted after reset: 00000811 =E2=80=A6 {repeats} The xhcihookm, rather than repeating the messages after the bootargs = prompt, terminates with a core dump: ... bootargs is (tcp, tls, il, local!device)[]xhci 600000000: controller not = halted after reset: 00000811 xhci 600000000: controller not ready after run: 0000080d cpu1: dumpregs ureg 0xffffffffc134be08 process 154: xhcirecover R0 0000000000000000 R1 0000000000000000 R2 00000000000003d4 R3 0000000000000000 R4 0000000000000000 R5 0000000000000000 R6 ffffffffc0080000 R7 ffffffffc14a0acb R8 0000000000000000 R9 00000000000003de R10 ffffffffc09b8cb8 R11 ffffffffc09bb8cb8 R12 000000000000001e R13 0000000000000001 R14 0000000000002000 R15 00000001fefeff98 R16 63c809a18a03a022 R17 0000000040000000 R18 b68c2c109411ce00 R19 de8a818f00000000 R20 95c174970c010000 R21 ad5ea04b40cb4cb8 R22 84c8bff000000000 R23 2c1e994900000000 R24 b0d56acc02000000. R25 c2e3d27b00000000 R26 ffffffffc008905c R27 00000000c04c90890 R28 ffffffffc00ab60c R29 ffffffffc00888cc PC 0xffffffffc014792c SP 0xffffffffc134bf28 LR 0xffffffffc00ab5d8 PSR = a0000005 TYPE bf000002 panic: SError interrupt ktrace /kernel/path 0xffffffffc00855ac 0xffffffffc134bc70 = 0xffffffffc134bda # pc, sp, link 0xc134bx70=3D0xc00853e8 0xc134bc78=3D0xc0084358 0xc134bcc8=3D0xc013bf28 = 0xc134bcd8=3D0xc008374c 0xc134bcf8=3D0xc00dce78 0xc134bd08=3D0xc00834fc 0xc134bd28=3D0xc00f9efc = 0xc134bd38=3D0xc00f8ffc 0xc134bd48=3D0xc008433c 0xc134bd68=3D0xc0084350 0xc134bd78=3D0xc014792c = 0xc134bd88=3D0xc00ab5d8 0xc134bda0=3D0xc00888cc 0xc134bdb8=3D0xc0080308 0xc134bdc8=3D0xc00ee7c0 = 0xc134bdd8=3D0xc00fd0e4 0xc134bdf8=3D0xc008374c 0xc134bed8=3D0xc0080308 0xc134bee8=3D0xc00ab60c = 0xc134bef0=3D0xc00888cc 0xc134bef8=3D0xc00ab5d8 0xc134bf08=3D0xc014792c 0xc134bf28=3D0xc00ab948 = 0xc134bf38=3D0xc01066f8 0xf134bf58=3D0xc00ac448 0xc134bf88=3D0xc00ac3d4 0xc134bfa8=3D0xc00ac2a4 = 0xc134bfb8=3D0xc00fb1e4 0xc134bfc8=3D0xc00f14a8 0xc134bfd8=3D0xc00f1560 0xc134bfe8=3D0xc00fb1e4 = 0xc134c018=3D0xc00fb1d0 0xc134c038=3D0xc0085238 I did bring in my wires and connect the serial adapter to the GPIO of = the PI 400. However, I am not sure what the syntax is to put the console = to the serial port for a Pi in the config.txt. If it is the same at 9 on = a intel machine, or if there is a specific port number or address number = that needs to be entered. My cursory search did not turn up anything. = (And of course I=E2=80=99d love to have a serial console as it would = same me from having to transcribe things like that dump. I=E2=80=99m also thinking of setting up a VMs for an Auth Server to boot = the Pi off of, to as you recommended a place to build kernels and net = boot, and see the results all in one place. Thank you very very much. I know this takes time and =E2=80=98cycles.=E2=80= =99 Mack > On Jan 26, 2021, at 7:09 AM, cinap_lenrek@felloff.net wrote: >=20 >> I tried the kernel this. evening,=20 >=20 > ok, because these roundtrips take alot of time. >=20 > i proactively made you two kernel images: >=20 > http://felloff.net/usr/cinap_lenrek/9pi4-pcienable > http://felloff.net/usr/cinap_lenrek/9pi4-xhcihook >=20 > sha1sums: >=20 > 2ca5e6d696aef196585723da33790eadf85e0f68 9pi4-pcienable > 8c3543c4ccdcfea1efb0575f49823b3f3e0b47db 9pi4-xhcihook >=20 > the 9pi4-pcienable adds the pcienable() call before the > xhcireset() firmware call as shown in the patch of the > previous mail. >=20 > the 9pi4-xhcihook adds a hook in the xhci driver to place > the firmware call just hafter the xhci handoff, which > then should be exactly the same place as with richards > version. >=20 > both files are flat kernel images to be put on the sdcard, > but renamed as 9pi4 (or you edit the config.txt file to > change the kernel name). >=20 > -- > cinap >=20