From: stevie@kamalatta.ddnss.de
To: 9front@9front.org
Subject: Re: [9front] BUG: thinclient not booting with usbehci,usbohci
Date: Sun, 10 Jan 2021 10:29:40 +0100 [thread overview]
Message-ID: <F950D112708020D77BFDA545239EA08D@kamalatta.ddnss.de> (raw)
In-Reply-To: <B7D9832A601B87280FEB076260290D74@felloff.net>
hi cinap!
I tested it on amd64 and 386. Skipping the EHCI controller leaves me with the same result as in my first mail.
Skipping OHCI boots on amd64 and 386 with:
cpu0: spurious interrupt 39, last 0
and with no prompt on 386, but the box is not frozen.
On amd64 instead I get the same cpu0: message, but also get a prompt and the box boots fine.
Surprisingly for me this message gets not logged in /dev/kmesg, I can only see it on the "boot screen".
So I guess OHCI is the culprit? Why had *nousbohci= not the same effect?
Hope this helps.
-- stevie
next prev parent reply other threads:[~2021-01-10 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 9:22 stevie
2021-01-09 9:46 ` stevie
2021-01-09 17:12 ` cinap_lenrek
2021-01-09 18:29 ` stevie
2021-01-09 23:09 ` cinap_lenrek
2021-01-10 9:29 ` stevie [this message]
2021-01-10 19:34 ` cinap_lenrek
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=F950D112708020D77BFDA545239EA08D@kamalatta.ddnss.de \
--to=stevie@kamalatta.ddnss.de \
--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).