[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99455c99-dd5c-4ab4-2c86-058aaf6d17c9@leemhuis.info>
Date: Mon, 20 Feb 2023 12:48:50 +0100
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Linux regressions mailing list <regressions@...ts.linux.dev>
Cc: "James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
bvanassche@....org, hare@...e.de, hch@....de, ming.lei@...hat.com,
sumanesh.samanta@...adcom.com, michael.christie@...cle.com,
john.garry@...wei.com, johannes.thumshirn@....com, axboe@...nel.dk,
osandov@...com, kashyap.desai@...adcom.com,
gregkh@...uxfoundation.org
Subject: Re: scsi: Recent kernels drop into emergency shell
On 20.02.23 12:23, Srikar Dronamraju wrote:
> * Linux regression tracking (Thorsten Leemhuis) <regressions@...mhuis.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.
Powered by blists - more mailing lists