From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Linux regressions mailing list <regressions@lists.linux.dev>
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
bvanassche@acm.org, hare@suse.de, hch@lst.de,
ming.lei@redhat.com, sumanesh.samanta@broadcom.com,
michael.christie@oracle.com, john.garry@huawei.com,
johannes.thumshirn@wdc.com, axboe@kernel.dk, osandov@fb.com,
kashyap.desai@broadcom.com, gregkh@linuxfoundation.org
Subject: Re: scsi: Recent kernels drop into emergency shell
Date: Mon, 20 Feb 2023 12:48:50 +0100 [thread overview]
Message-ID: <99455c99-dd5c-4ab4-2c86-058aaf6d17c9@leemhuis.info> (raw)
In-Reply-To: <20230220112328.GA803890@linux.vnet.ibm.com>
On 20.02.23 12:23, Srikar Dronamraju wrote:
> * Linux regression tracking (Thorsten Leemhuis) <regressions@leemhuis.info> [2023-02-20 08:40:09]:
>
>> [CCing the regression list, as it should be in the loop for regressions:
>> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>>
>> On 20.02.23 07:15, Srikar Dronamraju wrote:
>>> On a freshly installed system, booting latest upstream kernels causes the
>>> system to drop into emergency shell. The reason for dropping into emergency
>>> shell is system is unable to mount /home partition.
>>
>> What kind of storage hardware do you have? Is this maybe related to this
>> fix, that afaics never was merged?
>
> $ lsslot
> # Slot Description Linux Name Device(s)
> U9080.HEX.134C1E8-V9-C0 Virtual I/O Slot 30000000 vty
> U9080.HEX.134C1E8-V9-C2 Virtual I/O Slot 30000002 l-lan
> U9080.HEX.134C1E8-V9-C109 Virtual I/O Slot 3000006d v-scsi
>
> $ ls-vscsi
> host0 U9080.HEX.134C1E8-V9-C109-T0
>
> $ lsscsi
> [0:0:1:0] disk AIX VDASD 0001 /dev/sda
> [0:0:2:0] cd/dvd AIX VOPTA /dev/sr0
>
> Incase you need any other details please let me know.
>
>> https://lore.kernel.org/all/20220928181350.9948-1-leeman.duncan@gmail.com/
>
> Thanks that fixes the problem. I have added a tested-by for the same.
Great, thx. Hopefully that will revive the discussion to get this
finally solved.
#regzbot monitor:
https://lore.kernel.org/all/20220928181350.9948-1-leeman.duncan@gmail.com/
> Thanks for pointing out.
Yw. FWIW, I just found it by searching on lore for "c92a6b5d*".
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-02-20 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230220061559.GJ159593@linux.vnet.ibm.com>
2023-02-20 7:40 ` scsi: Recent kernels drop into emergency shell Linux regression tracking (Thorsten Leemhuis)
2023-02-20 11:23 ` Srikar Dronamraju
2023-02-20 11:48 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-04-05 13:29 ` Linux regression tracking #update (Thorsten Leemhuis)
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=99455c99-dd5c-4ab4-2c86-058aaf6d17c9@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=johannes.thumshirn@wdc.com \
--cc=john.garry@huawei.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.com \
--cc=regressions@lists.linux.dev \
--cc=srikar@linux.vnet.ibm.com \
--cc=sumanesh.samanta@broadcom.com \
/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).