From: maurilio.longo@libero.it
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] panic inside lmrc driver
Date: Fri, 16 Feb 2024 15:41:43 -0500 [thread overview]
Message-ID: <17081161030.AA4fC5EE.45783@composer.illumos.topicbox.com> (raw)
In-Reply-To: <0c903f2b-8c3d-4dc3-8f0e-cdc9ee6b23c7@fingolfin.org>
[-- Attachment #1: Type: text/plain, Size: 4042 bytes --]
Hi Robert,
yes, here it is fmdump -e at around 01:30pm
Feb 16 13:31:24.4290 ereport.io.pci.fabric
Feb 16 13:31:24.4290 ereport.io.pciex.a-nonfatal
Feb 16 13:31:24.4290 ereport.io.pciex.tl.cto
Feb 16 13:31:24.4290 ereport.io.pciex.rc.ce-msg
Feb 16 13:38:31.5763 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5764 ereport.fs.zfs.data
Feb 16 13:38:31.5763 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5765 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5766 ereport.fs.zfs.data
Feb 16 13:38:31.5771 ereport.fs.zfs.io_failure
Feb 16 15:11:59.2352 ereport.fs.zfs.io
Feb 16 15:11:59.2352 ereport.fs.zfs.io
Feb 16 15:11:59.2352 ereport.fs.zfs.io
Feb 16 15:11:59.2352 ereport.fs.zfs.io
and fmdump -v
Feb 16 13:38:31.5102 ba948ca4-681c-4d79-981c-6da3ca6e6b05 PCIEX-8000-DJ Diagnosed
40% fault.io.pciex.device-noresp
Problem in: hc://:product-id=ProLiant-ML30-Gen10-Plus:server-id=pg-1:chassis-id=CZJ2360PLT/motherboard=0/hostbridge=2/pciexrc=2/pciexbus=3/pciexdev=0/pciexfn=0
Affects: dev:////pci@0,0/pci8086,43b8@1c/pci1590,32b@0
FRU: hc://:product-id=ProLiant-ML30-Gen10-Plus:server-id=pg-1:chassis-id=CZJ2360PLT/motherboard=0/hostbridge=2/pciexrc=2/pciexbus=3/pciexdev=0
Location: PCI-E Slot 4
40% fault.io.pciex.device-interr
Problem in: hc://:product-id=ProLiant-ML30-Gen10-Plus:server-id=pg-1:chassis-id=CZJ2360PLT/motherboard=0/hostbridge=2/pciexrc=2/pciexbus=3/pciexdev=0/pciexfn=0
Affects: dev:////pci@0,0/pci8086,43b8@1c/pci1590,32b@0
FRU: hc://:product-id=ProLiant-ML30-Gen10-Plus:server-id=pg-1:chassis-id=CZJ2360PLT/motherboard=0/hostbridge=2/pciexrc=2/pciexbus=3/pciexdev=0
Location: PCI-E Slot 4
20% fault.io.pciex.bus-noresp
Problem in: hc://:product-id=ProLiant-ML30-Gen10-Plus:server-id=pg-1:chassis-id=CZJ2360PLT/motherboard=0/hostbridge=2/pciexrc=2/pciexbus=3/pciexdev=0/pciexfn=0
Affects: dev:////pci@0,0/pci8086,43b8@1c/pci1590,32b@0
FRU: hc://:product-id=ProLiant-ML30-Gen10-Plus:server-id=pg-1:chassis-id=CZJ2360PLT/motherboard=0/hostbridge=2/pciexrc=2/pciexbus=3/pciexdev=0
Location: PCI-E Slot 4
Feb 16 13:38:32.3326 447a2843-776e-4e39-a509-25817d74bf2d ZFS-8000-HC Diagnosed
100% fault.fs.zfs.io_failure_wait
Problem in: zfs://pool=dati
Affects: zfs://pool=dati
FRU: -
Location: -
Regards.
Maurilio.
[-- Attachment #2: Type: text/html, Size: 22867 bytes --]
next prev parent reply other threads:[~2024-02-16 20:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 10:31 maurilio.longo
2024-02-07 11:14 ` [developer] " Peter Tribble
2024-02-07 11:16 ` Hans Rosenfeld
2024-02-07 11:46 ` maurilio.longo
2024-02-07 12:04 ` maurilio.longo
2024-02-07 12:29 ` Hans Rosenfeld
2024-02-07 13:01 ` maurilio.longo
2024-02-07 16:47 ` maurilio.longo
2024-02-07 17:01 ` Hans Rosenfeld
2024-02-07 21:35 ` Hans Rosenfeld
2024-02-08 7:59 ` maurilio.longo
2024-02-08 10:42 ` Hans Rosenfeld
2024-02-08 11:01 ` maurilio.longo
2024-02-09 8:06 ` maurilio.longo
2024-02-09 19:55 ` Hans Rosenfeld
2024-02-09 20:36 ` maurilio.longo
2024-02-12 8:11 ` maurilio.longo
2024-02-13 19:32 ` Hans Rosenfeld
2024-02-13 20:55 ` maurilio.longo
2024-02-13 21:03 ` maurilio.longo
2024-02-15 6:50 ` maurilio.longo
2024-02-15 7:38 ` Carsten Grzemba
2024-02-15 8:11 ` Toomas Soome
2024-02-15 9:44 ` maurilio.longo
2024-02-16 14:36 ` maurilio.longo
2024-02-16 15:20 ` maurilio.longo
2024-02-16 15:27 ` maurilio.longo
2024-02-16 15:42 ` Robert Mustacchi
2024-02-16 20:41 ` maurilio.longo [this message]
2024-02-19 21:14 ` maurilio.longo
2024-02-20 8:58 ` maurilio.longo
2024-02-22 17:44 ` maurilio.longo
2024-02-26 8:59 ` maurilio.longo
2024-02-26 9:30 ` Carsten Grzemba
2024-08-26 12:30 ` manipm
2024-08-26 15:23 ` Hans Rosenfeld
2024-02-13 19:23 ` Hans Rosenfeld
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=17081161030.AA4fC5EE.45783@composer.illumos.topicbox.com \
--to=maurilio.longo@libero.it \
--cc=developer@lists.illumos.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).