From: Mack Wallace <mackbw@mapinternet.com>
To: 9front@9front.org
Subject: Re: [9front] 9front on Raspberry Pi 400
Date: Wed, 27 Jan 2021 02:32:57 +0000 [thread overview]
Message-ID: <0100017741afd09d-da43b097-8dba-46b2-98d9-05414e118708-000000@email.amazonses.com> (raw)
In-Reply-To: <358AB57987F7B4208CD18104830D2852@felloff.net>
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
… {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=0xc00853e8 0xc134bc78=0xc0084358 0xc134bcc8=0xc013bf28 0xc134bcd8=0xc008374c
0xc134bcf8=0xc00dce78 0xc134bd08=0xc00834fc 0xc134bd28=0xc00f9efc 0xc134bd38=0xc00f8ffc
0xc134bd48=0xc008433c 0xc134bd68=0xc0084350 0xc134bd78=0xc014792c 0xc134bd88=0xc00ab5d8
0xc134bda0=0xc00888cc 0xc134bdb8=0xc0080308 0xc134bdc8=0xc00ee7c0 0xc134bdd8=0xc00fd0e4
0xc134bdf8=0xc008374c 0xc134bed8=0xc0080308 0xc134bee8=0xc00ab60c 0xc134bef0=0xc00888cc
0xc134bef8=0xc00ab5d8 0xc134bf08=0xc014792c 0xc134bf28=0xc00ab948 0xc134bf38=0xc01066f8
0xf134bf58=0xc00ac448 0xc134bf88=0xc00ac3d4 0xc134bfa8=0xc00ac2a4 0xc134bfb8=0xc00fb1e4
0xc134bfc8=0xc00f14a8 0xc134bfd8=0xc00f1560 0xc134bfe8=0xc00fb1e4 0xc134c018=0xc00fb1d0
0xc134c038=0xc0085238
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’d love to have a serial console as it would same me from having to transcribe things like that dump.
I’m 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 ‘cycles.’
Mack
> On Jan 26, 2021, at 7:09 AM, cinap_lenrek@felloff.net wrote:
>
>> I tried the kernel this. evening,
>
> ok, because these roundtrips take alot of time.
>
> i proactively made you two kernel images:
>
> http://felloff.net/usr/cinap_lenrek/9pi4-pcienable
> http://felloff.net/usr/cinap_lenrek/9pi4-xhcihook
>
> sha1sums:
>
> 2ca5e6d696aef196585723da33790eadf85e0f68 9pi4-pcienable
> 8c3543c4ccdcfea1efb0575f49823b3f3e0b47db 9pi4-xhcihook
>
> the 9pi4-pcienable adds the pcienable() call before the
> xhcireset() firmware call as shown in the patch of the
> previous mail.
>
> 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.
>
> 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).
>
> --
> cinap
>
next prev parent reply other threads:[~2021-01-27 5:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 17:23 Mack Wallace
2021-01-23 16:11 ` cinap_lenrek
2021-01-23 21:08 ` Mack Wallace
2021-01-23 21:13 ` Mack Wallace
2021-01-23 23:42 ` cinap_lenrek
2021-01-24 15:01 ` cinap_lenrek
2021-01-26 3:33 ` Mack Wallace
2021-01-26 3:35 ` Mack Wallace
2021-01-26 11:21 ` cinap_lenrek
2021-01-26 12:09 ` cinap_lenrek
2021-01-27 2:32 ` Mack Wallace [this message]
2021-01-27 14:30 ` cinap_lenrek
2021-01-27 17:04 ` cinap_lenrek
2021-01-27 17:57 ` cinap_lenrek
2021-01-29 14:58 ` cinap_lenrek
2021-01-30 2:43 ` Mack Wallace
2021-01-30 5:54 ` cinap_lenrek
2021-01-30 19:23 ` Mack Wallace
2021-01-30 19:41 ` cinap_lenrek
2021-01-30 19:46 ` cinap_lenrek
2021-02-01 1:16 ` Mack Wallace
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0100017741afd09d-da43b097-8dba-46b2-98d9-05414e118708-000000@email.amazonses.com \
--to=mackbw@mapinternet.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).