public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Robert Mustacchi <rm@fingolfin.org>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] panic inside lmrc driver
Date: Fri, 16 Feb 2024 07:42:10 -0800	[thread overview]
Message-ID: <0c903f2b-8c3d-4dc3-8f0e-cdc9ee6b23c7@fingolfin.org> (raw)
In-Reply-To: <17080972540.bbeEb.18650@composer.illumos.topicbox-beta.com>

Hi Maurilio,

On 2/16/24 07:27, maurilio.longo via illumos-developer wrote:
> fmadm faulty -f
> fmadm repaired  "PCI-E Slot 4"
> 
> Fixed the issue with invisible disks... sorry for the noise.

Having this happen suggests that the PCIe controller or its
corresponding root port observed AERs (PCIe's error reporting
mechanism). If you look at fmudmp -e do you have entries that relate to
around the timestamp of the original time the controller was retired?

Robert

  reply	other threads:[~2024-02-16 15:42 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 [this message]
2024-02-16 20:41                                             ` maurilio.longo
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=0c903f2b-8c3d-4dc3-8f0e-cdc9ee6b23c7@fingolfin.org \
    --to=rm@fingolfin.org \
    --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).