From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] nvme driver crashy on a shitty OEM drive
Date: Wed, 21 Jul 2021 18:43:04 +0200 [thread overview]
Message-ID: <F6A15143DE22B66DC565DE7226D3A62B@felloff.net> (raw)
In-Reply-To: <CAF=5iUWSHg2mB24PAx+9Vnu6SWgDsk7mBTso22tJVjd7a1zodw@mail.gmail.com>
that linux thread hints on some physical layer issues... they'r trying
to reset the whole pci bus to force it to recover and tuning some timing
delay loops...
we do not have a pci error handler except generic machine check
handler, so we might just freeze up instead of seeing the errors
linux prints.
it is really odd, especially as it starts to not hang when you
boot with usb disk inserted.
it might well be a timing dependency right there.
for one, i'd suggest to take the ahci out of the equation by setting
*noahci=1 in 9boot > prompt before booting the kernel.
then maybe take a look at the linux quirk routine in detail.
(i have not dont yet).
--
cinap
next prev parent reply other threads:[~2021-07-21 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 1:23 Lucas Francesco
2021-07-21 7:57 ` hiro
2021-07-21 16:43 ` cinap_lenrek [this message]
2021-07-21 17:38 ` hiro
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=F6A15143DE22B66DC565DE7226D3A62B@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).