public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Mike Edwards <medwards@mobile.mirkwood.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Mylex AcceleRAID 170 + myrb/myrs causing crash
Date: Fri, 14 Jul 2023 17:18:04 +0200	[thread overview]
Message-ID: <4a0b76f5-9980-7976-bed1-801a98ecb7d8@suse.de> (raw)
In-Reply-To: <CALM2zXX9LfshDUaFpKL5KURQy7p8J=5KpSi_foVaC1BfAB9sJg@mail.gmail.com>

On 7/14/23 17:03, Mike Edwards wrote:
> I can try openSUSE Leap, certainly.
> 
> However, those debugging statements are going to be hard - the process
> lockup occurs at initial module load, before init really starts doing
> much of anything.  I've even tried passing init=/bin/bash on the
> commandline, with no luck - I never made it to a shell before things
> went south.  For the same reason, there are no logs to speak of, alas
> - but I can try seeing if I can get a serial console going, as that
> will let me dump output.
> 
> I'll verify that the driver in OpenSUSE Leap has the same issue, and
> will open a bug report when it (almost certainly!) dies the same way.
> 
You can try with the live system from the ISO image; that will load the 
modules only afterwards, so you should be able to see some messages there.

And I think there is even a magic commandline sequence to enable dynamic 
debug...

Cheers,

Hannes


  reply	other threads:[~2023-07-14 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALM2zXUDAqAzCQR+sJDwoxxEEnG7cLJ4QazCVscJX-rR49=V2A@mail.gmail.com>
2023-07-13 19:24 ` Mylex AcceleRAID 170 + myrb/myrs causing crash Mike Edwards
2023-07-14  6:04 ` Hannes Reinecke
2023-07-14 15:03   ` Mike Edwards
2023-07-14 15:18     ` Hannes Reinecke [this message]
2023-07-14 15:33       ` Mike Edwards
2023-07-21  0:19   ` Mike Edwards

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=4a0b76f5-9980-7976-bed1-801a98ecb7d8@suse.de \
    --to=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=medwards@mobile.mirkwood.net \
    /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