linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	linux-block@vger.kernel.org, linux-s390@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: s390 boot woe due to "block: fix busy device checking in blk_drop_partitions"
Date: Thu, 9 Apr 2020 19:33:25 -0400	[thread overview]
Message-ID: <AD16A450-794F-4EEA-A7BF-42452F18294A@lca.pw> (raw)

Reverted the linux-next commit on today’s tree,

d3ef5536274f (“block: fix busy device checking in blk_drop_partitions”)

makes IBM partition to be recognized again on s390 rootfs,

01: [   83.443963]  dasda:VOL1/  0X0121: dasda1                                 
01: [   85.124667] qeth 0.0.8000 enc8000: renamed from eth0                     
01: [   85.731860] dasd-eckd 0.0.0120: DASD with 4 KB/block, 72122400 KB total s
01: ize, 48 KB/track, compatible disk layout                                    
01: [   86.076722]  dasdb:VOL1/  0X0120: dasdb1 dasdb2

Otherwise, it is DOA,

00:          Starting Show Plymouth Boot Screen...                              
00: [   37.202263] qeth 0.0.8000: portname is deprecated and is ignored         
00: [   37.677993] qdio: 0.0.8002 OSA on SC 4 using AI:1 QEBSM:0 PRI:1 TDD:1 SIG
00: A:RW A                                                                      
00: [   37.770970] qeth 0.0.8000: MAC address 02:de:ad:be:ef:87 successfully reg
00: istered                                                                     
00: [   37.771547] qeth 0.0.8000: Device is a Virtual NIC QDIO card (level: V642
00: )                                                                           
00: [   37.771547] with link type Virt.NIC QDIO.                                
00: [   38.036231] ccw_init (415) used greatest stack depth: 56496 bytes left   
00:          Starting dracut initqueue hook...                                  
00: [   39.176304] dasd-eckd 0.0.0120: A channel path to the device has become o
00: perational                                                                  
00: [   39.453273] dasd-eckd 0.0.0120: New DASD 3390/0E (CU 3990/01) with 100170
00:  cylinders, 15 heads, 224 sectors                                           
00: [   39.655564] dasd-eckd 0.0.0121: A channel path to the device has become o
00: perational                                                                  
00: [   39.722706] dasd-eckd 0.0.0121: New DASD 3390/0E (CU 3990/01) with 100170
00:  cylinders, 15 heads, 224 sectors                                           
01: [   41.133963] dasd-eckd 0.0.0121: DASD with 4 KB/block, 72122400 KB total s
01: ize, 48 KB/track, compatible disk layout                                    
01: [   41.145510] dasd-eckd 0.0.0120: DASD with 4 KB/block, 72122400 KB total s
01: ize, 48 KB/track, compatible disk layout                                    
01: [   41.609625] qeth 0.0.8000 enc8000: renamed from eth0  
01: [   41.609625] qeth 0.0.8000 enc8000: renamed from eth0                     
01: Warning: /dev/mapper/rhel_ibm--z--135-root does not exist                   
01: Warning: /dev/rhel_ibm-z-135/root does not exist                            
01: Warning: /dev/rhel_ibm-z-135/swap does not exist                            
01:                                                                             
01: Generating "/run/initramfs/rdsosreport.txt"                                 
01:                                                                             
01:                                                                             
01: Entering emergency mode. Exit the shell to continue.                        
01: Type "journalctl" to view system logs.                                      
01: You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /b
01: oot                                                                         
01: after mounting them and attach it to a bug report.                          
01:                                                                             
01:                                                                             
00: dracut:/# 


             reply	other threads:[~2020-04-09 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 23:33 Qian Cai [this message]
2020-04-10  5:45 ` s390 boot woe due to "block: fix busy device checking in blk_drop_partitions" Christoph Hellwig
2020-04-10 12:20   ` Qian Cai
2020-04-23 11:07   ` Michal Koutný
2020-04-27 16:10     ` Christoph Hellwig

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=AD16A450-794F-4EEA-A7BF-42452F18294A@lca.pw \
    --to=cai@lca.pw \
    --cc=axboe@kernel.dk \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.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).