On Mon, Jun 10, 2019 at 05:38:56PM +0900, Masanobu SAITOH wrote:
> On 2019/06/10 17:17, Thomas Klausner wrote:
> > I tried some more stuff.
> >
> > Enabling the NVME_QUIRK_DELAY_B4_CHK_RDY quirk didn't help, it paniced
> > during boot. However, forcing nvme_pci_force_intx to 1 makes it boot
> >
On 2019/06/10 17:17, Thomas Klausner wrote:
> I tried some more stuff.
>
> Enabling the NVME_QUIRK_DELAY_B4_CHK_RDY quirk didn't help, it paniced
> during boot. However, forcing nvme_pci_force_intx to 1 makes it boot
> successfully!
Please show the following information:
- "FULL" dmesg
I tried some more stuff.
Enabling the NVME_QUIRK_DELAY_B4_CHK_RDY quirk didn't help, it paniced
during boot. However, forcing nvme_pci_force_intx to 1 makes it boot
successfully!
Should this variable default to 1, or how do we improve the situation
in general?
Cheers,
Thomas
On Wed, May 29, 2019 at 09:04:25AM +1000, Matthew Green wrote:
> i have a change in testing that makes nvme mostly attach after interrupts
> happen. i need it on arm64 where the interrupt controller isn't setup
> properly yet and attemtping to setup affinity doesn't work.
>
> i wonder if this
i have a change in testing that makes nvme mostly attach after interrupts
happen. i need it on arm64 where the interrupt controller isn't setup
properly yet and attemtping to setup affinity doesn't work.
i wonder if this would help here, since nvm_poll() would be called later.
unfortunately, i
