Re: Dell Latitude 7400 - nvme0: Missing interrupt

2021-10-17 Thread Pavel Timofeev 
вс, 17 окт. 2021 г. в 11:19, Alexander Motin :

> It may be a noise, but comparing logs I see in reboot case also
> "acpi_ec0: not getting interrupts, switched to polled mode".  I am
> thinking whether the problem may be caused not by SSD, but by some
> resource conflict/misconfiguration in the system.  Pavel, can you
> compare `devinfo -vr` and `lspci -v` in both cases. looking for any
> differences?  Are you running the latest BIOS?
>
> On 12.10.2021 15:56, Warner Losh wrote:
> > One piece of data that would be good to have:
> >
> > nvmecontrol identify nvme0
> >
> > There's an optional feature that none of my drives have, but that the
> Linux
> > driver does oddly
> > weird things when enabled. The output of that command will help me
> > understand if that may
> > be in play. Maybe we need to do oddly weird things too :)
> >
> > Warner
> >
> > On Sun, Oct 10, 2021 at 11:00 PM Warner Losh  wrote:
> >
> >>
> >>
> >> On Sun, Oct 10, 2021 at 10:48 PM Pavel Timofeev 
> wrote:
> >>
> >>> сб, 9 окт. 2021 г. в 14:59, Warner Losh :
> >>>
> 
> 
>  On Sat, Oct 9, 2021, 8:44 AM Pavel Timofeev  wrote:
> 
> >
> >
> > пт, 8 окт. 2021 г. в 14:49, Warner Losh :
> >
> >>
> >>
> >> On Fri, Oct 8, 2021 at 2:42 PM Pavel Timofeev 
> >> wrote:
> >>
> >>>
> >>>
> >>> сб, 21 авг. 2021 г. в 15:22, Warner Losh :
> >>>
> 
> 
>  On Sat, Aug 21, 2021 at 3:06 PM Pavel Timofeev 
>  wrote:
> 
> >
> >
> >  Warner Losh :
> >
> >>
> >>
> >> On Fri, Aug 20, 2021 at 10:42 PM Pavel Timofeev <
> tim...@gmail.com>
> >> wrote:
> >>
> >>>  Pavel Timofeev :
> >>>
> 
>  Chuck Tuffli :
> 
> > On Mon, Aug 16, 2021 at 7:43 PM Pavel Timofeev <
> >>> tim...@gmail.com> wrote:
> >>
> >> Hello
> >> I've got a Dell Latitude 7400 and tried installing the
> latest
> > 14.0-CURRENT
> >> (main-n248636-d20e9e02db3) on it.
> >> Despite other things the weird one which concerns me is
> >>   nvme0: Missing interrupt
> >> message I get sometimes on the console.
> >> It seems like I get it only after the reboot of the laptop,
> >>> i. e. not
> >> getting that message if I power cycle the laptop, at least I
> >>> haven't
> > seen
> >> them for now in such cases.
> >> So when the laptop is rebooted I can't even take advantage
> of
> >> nvmecontrol(8) quickly.
> >> Well, it still works, but it takes tens of seconds to return
> >>> the output.
> > ...
> >> dmesg when power cycled -
> >>
> >>>
> https://drive.google.com/file/d/1dB27oB1O2CcnZy6DvOOhmFO8SN8V8SwJ
> >> dmesg when rebooted -
> >>
> >>>
> https://drive.google.com/file/d/1DsKTMkihp_OmUcirByLaVO4o2mU38Bxh
> >
> > I'm sort of curious about the time stamps for the log
> messages
> >>> in the
> > failing case. Something like:
> >
> > $ grep "nv\(me\|d\)" /var/log/messages
> >
> > --chuck
> >
> 
>  Well, I can't see timestamps in the verbose boot log. Am I
> >>> missing some
>  configuration for that?
> 
>  $ grep "nv\(me\|d\)" /var/log/messages
>  nvme0:  mem
> 
> >>>
> 0xcc10-0xcc103fff,0xcc105000-0xcc105fff,0xcc104000-0xcc104fff at device
>  0.0 on pci6
>  nvme0: attempting to allocate 5 MSI-X vectors (17 supported)
>  nvme0: using IRQs 133-137 for MSI-X
>  nvme0: CapLo: 0x140103ff: MQES 1023, CQR, TO 20
>  nvme0: CapHi: 0x0030: DSTRD 0, NSSRS, CSS 1, MPSMIN 0,
> >>> MPSMAX 0
>  nvme0: Version: 0x00010300: 1.3
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvd0:  NVMe namespace
>  GEOM: new disk nvd0
>  nvd0: 488386MB (1000215216 512 byte sectors)
> 
> >>>
> >>>
> >>> Ah, sorry, provided wrong output.
> >>> Here is what you requested:
> >>> $ grep "nv\(me\|d\)" /var/log/messages
> >>> Aug 21 04:34:36 nostromo kernel: nvme0: 
> mem
> >>>
>

Re: Dell Latitude 7400 - nvme0: Missing interrupt

2021-10-17 Thread Alexander Motin 
It may be a noise, but comparing logs I see in reboot case also
"acpi_ec0: not getting interrupts, switched to polled mode".  I am
thinking whether the problem may be caused not by SSD, but by some
resource conflict/misconfiguration in the system.  Pavel, can you
compare `devinfo -vr` and `lspci -v` in both cases. looking for any
differences?  Are you running the latest BIOS?

On 12.10.2021 15:56, Warner Losh wrote:
> One piece of data that would be good to have:
> 
> nvmecontrol identify nvme0
> 
> There's an optional feature that none of my drives have, but that the Linux
> driver does oddly
> weird things when enabled. The output of that command will help me
> understand if that may
> be in play. Maybe we need to do oddly weird things too :)
> 
> Warner
> 
> On Sun, Oct 10, 2021 at 11:00 PM Warner Losh  wrote:
> 
>>
>>
>> On Sun, Oct 10, 2021 at 10:48 PM Pavel Timofeev  wrote:
>>
>>> сб, 9 окт. 2021 г. в 14:59, Warner Losh :
>>>


 On Sat, Oct 9, 2021, 8:44 AM Pavel Timofeev  wrote:

>
>
> пт, 8 окт. 2021 г. в 14:49, Warner Losh :
>
>>
>>
>> On Fri, Oct 8, 2021 at 2:42 PM Pavel Timofeev 
>> wrote:
>>
>>>
>>>
>>> сб, 21 авг. 2021 г. в 15:22, Warner Losh :
>>>


 On Sat, Aug 21, 2021 at 3:06 PM Pavel Timofeev 
 wrote:

>
>
>  Warner Losh :
>
>>
>>
>> On Fri, Aug 20, 2021 at 10:42 PM Pavel Timofeev 
>> wrote:
>>
>>>  Pavel Timofeev :
>>>

 Chuck Tuffli :

> On Mon, Aug 16, 2021 at 7:43 PM Pavel Timofeev <
>>> tim...@gmail.com> wrote:
>>
>> Hello
>> I've got a Dell Latitude 7400 and tried installing the latest
> 14.0-CURRENT
>> (main-n248636-d20e9e02db3) on it.
>> Despite other things the weird one which concerns me is
>>   nvme0: Missing interrupt
>> message I get sometimes on the console.
>> It seems like I get it only after the reboot of the laptop,
>>> i. e. not
>> getting that message if I power cycle the laptop, at least I
>>> haven't
> seen
>> them for now in such cases.
>> So when the laptop is rebooted I can't even take advantage of
>> nvmecontrol(8) quickly.
>> Well, it still works, but it takes tens of seconds to return
>>> the output.
> ...
>> dmesg when power cycled -
>>
>>> https://drive.google.com/file/d/1dB27oB1O2CcnZy6DvOOhmFO8SN8V8SwJ
>> dmesg when rebooted -
>>
>>> https://drive.google.com/file/d/1DsKTMkihp_OmUcirByLaVO4o2mU38Bxh
>
> I'm sort of curious about the time stamps for the log messages
>>> in the
> failing case. Something like:
>
> $ grep "nv\(me\|d\)" /var/log/messages
>
> --chuck
>

 Well, I can't see timestamps in the verbose boot log. Am I
>>> missing some
 configuration for that?

 $ grep "nv\(me\|d\)" /var/log/messages
 nvme0:  mem

>>> 0xcc10-0xcc103fff,0xcc105000-0xcc105fff,0xcc104000-0xcc104fff 
>>> at device
 0.0 on pci6
 nvme0: attempting to allocate 5 MSI-X vectors (17 supported)
 nvme0: using IRQs 133-137 for MSI-X
 nvme0: CapLo: 0x140103ff: MQES 1023, CQR, TO 20
 nvme0: CapHi: 0x0030: DSTRD 0, NSSRS, CSS 1, MPSMIN 0,
>>> MPSMAX 0
 nvme0: Version: 0x00010300: 1.3
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvme0: Missing interrupt
 nvd0:  NVMe namespace
 GEOM: new disk nvd0
 nvd0: 488386MB (1000215216 512 byte sectors)

>>>
>>>
>>> Ah, sorry, provided wrong output.
>>> Here is what you requested:
>>> $ grep "nv\(me\|d\)" /var/log/messages
>>> Aug 21 04:34:36 nostromo kernel: nvme0:  mem
>>> 0xcc10-0xcc103fff,0xcc105000-0xcc105fff,0xcc104000-0xcc104fff
>>> at device
>>> 0.0 on pci6
>>> Aug 21 04:34:36 nostromo kernel: nvme0: attempting to allocate 5
>>> MSI-X
>>> vectors (17 supported)
>>> Aug 21 04:34:36 nostromo kernel: nvme0: using IRQs 133-137 for
>>> MSI-X
>>> Aug 21 04:34:36 nostromo kernel:

Re: Dell Latitude 7400 - nvme0: Missing interrupt

2021-10-17 Thread Warner Losh 
On Sun, Oct 17, 2021, 11:19 AM Alexander Motin  wrote:

> It may be a noise, but comparing logs I see in reboot case also
> "acpi_ec0: not getting interrupts, switched to polled mode".  I am
> thinking whether the problem may be caused not by SSD, but by some
> resource conflict/misconfiguration in the system.  Pavel, can you
> compare `devinfo -vr` and `lspci -v` in both cases. looking for any
> differences?  Are you running the latest BIOS?
>

I'm leaning the same way since I have an identical drive not showing
problems in my system. It's also weird that the completion record for the
identify didn't show up after reboot. It makes me think it went to the
wrong place or didn't make it back up the bridge hierarchy.

Warner


On 12.10.2021 15:56, Warner Losh wrote:
> > One piece of data that would be good to have:
> >
> > nvmecontrol identify nvme0
> >
> > There's an optional feature that none of my drives have, but that the
> Linux
> > driver does oddly
> > weird things when enabled. The output of that command will help me
> > understand if that may
> > be in play. Maybe we need to do oddly weird things too :)
> >
> > Warner
> >
> > On Sun, Oct 10, 2021 at 11:00 PM Warner Losh  wrote:
> >
> >>
> >>
> >> On Sun, Oct 10, 2021 at 10:48 PM Pavel Timofeev 
> wrote:
> >>
> >>> сб, 9 окт. 2021 г. в 14:59, Warner Losh :
> >>>
> 
> 
>  On Sat, Oct 9, 2021, 8:44 AM Pavel Timofeev  wrote:
> 
> >
> >
> > пт, 8 окт. 2021 г. в 14:49, Warner Losh :
> >
> >>
> >>
> >> On Fri, Oct 8, 2021 at 2:42 PM Pavel Timofeev 
> >> wrote:
> >>
> >>>
> >>>
> >>> сб, 21 авг. 2021 г. в 15:22, Warner Losh :
> >>>
> 
> 
>  On Sat, Aug 21, 2021 at 3:06 PM Pavel Timofeev 
>  wrote:
> 
> >
> >
> >  Warner Losh :
> >
> >>
> >>
> >> On Fri, Aug 20, 2021 at 10:42 PM Pavel Timofeev <
> tim...@gmail.com>
> >> wrote:
> >>
> >>>  Pavel Timofeev :
> >>>
> 
>  Chuck Tuffli :
> 
> > On Mon, Aug 16, 2021 at 7:43 PM Pavel Timofeev <
> >>> tim...@gmail.com> wrote:
> >>
> >> Hello
> >> I've got a Dell Latitude 7400 and tried installing the
> latest
> > 14.0-CURRENT
> >> (main-n248636-d20e9e02db3) on it.
> >> Despite other things the weird one which concerns me is
> >>   nvme0: Missing interrupt
> >> message I get sometimes on the console.
> >> It seems like I get it only after the reboot of the laptop,
> >>> i. e. not
> >> getting that message if I power cycle the laptop, at least I
> >>> haven't
> > seen
> >> them for now in such cases.
> >> So when the laptop is rebooted I can't even take advantage
> of
> >> nvmecontrol(8) quickly.
> >> Well, it still works, but it takes tens of seconds to return
> >>> the output.
> > ...
> >> dmesg when power cycled -
> >>
> >>>
> https://drive.google.com/file/d/1dB27oB1O2CcnZy6DvOOhmFO8SN8V8SwJ
> >> dmesg when rebooted -
> >>
> >>>
> https://drive.google.com/file/d/1DsKTMkihp_OmUcirByLaVO4o2mU38Bxh
> >
> > I'm sort of curious about the time stamps for the log
> messages
> >>> in the
> > failing case. Something like:
> >
> > $ grep "nv\(me\|d\)" /var/log/messages
> >
> > --chuck
> >
> 
>  Well, I can't see timestamps in the verbose boot log. Am I
> >>> missing some
>  configuration for that?
> 
>  $ grep "nv\(me\|d\)" /var/log/messages
>  nvme0:  mem
> 
> >>>
> 0xcc10-0xcc103fff,0xcc105000-0xcc105fff,0xcc104000-0xcc104fff at device
>  0.0 on pci6
>  nvme0: attempting to allocate 5 MSI-X vectors (17 supported)
>  nvme0: using IRQs 133-137 for MSI-X
>  nvme0: CapLo: 0x140103ff: MQES 1023, CQR, TO 20
>  nvme0: CapHi: 0x0030: DSTRD 0, NSSRS, CSS 1, MPSMIN 0,
> >>> MPSMAX 0
>  nvme0: Version: 0x00010300: 1.3
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvme0: Missing interrupt
>  nvd0:  NVMe namespace
>  GEOM: new disk nvd0
>  nvd0: 488386MB (1000215216 512 byte sectors)
>

VMMR0InitVM … kernel panic: fatal trap 9: general protection fault while in kernel mode

2021-10-17 Thread Graham Perrin 

Is it worth opening a bug for what's below?

GENERIC-NODEBUG, main-n249988-2c614481fd5



Gut feeling: it might be very difficult to reproduce.

From :

…
Unread portion of the kernel message buffer:
VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)


Fatal trap 9: general protection fault while in kernel mode
cpuid = 3; apic id = 03
instruction pointer = 0x20:0x810bc0a6
stack pointer   = 0x28:0xfe00c5303ba0
frame pointer   = 0x28:0xfe00c5303ba0
code segment    = base 0x0, limit 0xf, type 0x1b
    = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags    = interrupt enabled, resume, IOPL = 0
current process = 19 (arc_reap)
trap number = 9
panic: general protection fault
cpuid = 3
time = 1634464447
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 
0xfe00c53038a0

vpanic() at vpanic+0x187/frame 0xfe00c5303900
panic() at panic+0x43/frame 0xfe00c5303960
trap_fatal() at trap_fatal+0x387/frame 0xfe00c53039c0
trap() at trap+0x8b/frame 0xfe00c5303ad0
calltrap() at calltrap+0x8/frame 0xfe00c5303ad0
--- trap 0x9, rip = 0x810bc0a6, rsp = 0xfe00c5303ba0, rbp = 
0xfe00c5303ba0 ---
pmap_invalidate_all_pcid_noinvpcid_cb() at 
pmap_invalidate_all_pcid_noinvpcid_cb+0x36/frame 0xfe00c5303ba0
smp_targeted_tlb_shootdown() at smp_targeted_tlb_shootdown+0x2b7/frame 
0xfe00c5303c20

pmap_invalidate_all() at pmap_invalidate_all+0x117/frame 0xfe00c5303c90
pmap_remove() at pmap_remove+0x5ae/frame 0xfe00c5303d10
_kmem_unback() at _kmem_unback+0x32/frame 0xfe00c5303d60
kmem_free() at kmem_free+0x2d/frame 0xfe00c5303d80
keg_free_slab() at keg_free_slab+0xdc/frame 0xfe00c5303dc0
keg_drain_domain() at keg_drain_domain+0x1c1/frame 0xfe00c5303e00
zone_reclaim() at zone_reclaim+0x1aa/frame 0xfe00c5303e50
arc_kmem_reap_soon() at arc_kmem_reap_soon+0x61/frame 0xfe00c5303e80
arc_reap_cb() at arc_reap_cb+0x9/frame 0xfe00c5303e90
zthr_procedure() at zthr_procedure+0xba/frame 0xfe00c5303ef0
fork_exit() at fork_exit+0x8a/frame 0xfe00c5303f30
fork_trampoline() at fork_trampoline+0xe/frame 0xfe00c5303f30
--- trap 0x4dda280, rip = 0x1, rsp = 0, rbp = 0x1a99c090 ---
KDB: enter: panic
…
fstat

USER CMD  PID   FD MOUNT  INUM MODE SZ|DV R/W
grahampe VirtualBoxVM  3085 root / 4 drwxr-xr-x 37  r
…


Context:  lines 1285–1372.