9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] nvme driver crashy on a shitty OEM drive
Date: Wed, 21 Jul 2021 19:38:05 +0200	[thread overview]
Message-ID: <CAFSF3XMyzgSCGmgohoVwZ8gYU89ceingDOyWh+fPeNHbpEJfmg@mail.gmail.com> (raw)
In-Reply-To: <F6A15143DE22B66DC565DE7226D3A62B@felloff.net>

i generally wouldn't bother trying to understand linux quirks too
hard, they are often stupid and wrong, too.

i had problems with some nvme drives out of the box from the vendor on
the lenovo thinkcentre, and it didn't go away until today with an
up-to-date ubuntu either.

replacing the nvme drive to another brand clearly changes the
frequency of my pcie bus crashing the system.

you'll have to do it yourself. linux is misleading.

On 7/21/21, cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> wrote:
> 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
>

      reply	other threads:[~2021-07-21 17:44 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
2021-07-21 17:38   ` hiro [this message]

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=CAFSF3XMyzgSCGmgohoVwZ8gYU89ceingDOyWh+fPeNHbpEJfmg@mail.gmail.com \
    --to=23hiro@gmail.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).