Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pingfan Liu <piliu@redhat.com>
To: kexec@lists.infradead.org
Subject: Re: [PATCH 1/2] kdump-lib-initramfs.sh: ignore the failure of echo
Date: Mon, 17 Apr 2017 03:46:55 -0400 (EDT)	[thread overview]
Message-ID: <830319975.15356555.1492415215683.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1492411476-10548-1-git-send-email-piliu@redhat.com>


Please ignore these two patch, I send it to the wrong mailing list.
Sorry for the noise.



----- Original Message -----
> From: "Pingfan Liu" <piliu@redhat.com>
> To: kexec@lists.infradead.org
> Cc: "Dave Young" <dyoung@redhat.com>, "Baoquan He" <bhe@redhat.com>
> Sent: Monday, April 17, 2017 2:44:35 PM
> Subject: [PATCH 1/2] kdump-lib-initramfs.sh: ignore the failure of echo
> 
> The kdump-capture.service will fail, if the following conds are meet up.
> -1. boot up a VM with the following cmd:
> qemu-kvm   -name 'avocado-vt-vm1'  -sandbox off    -machine pc   -nodefaults
> -vga cirrus \
>     -drive
>     id=drive_image1,if=none,snapshot=off,aio=native,cache=none,format=qcow2,file=$guest_img
>     \
>     -device
>     virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=04
>     \
>     -device
>     virtio-net-pci,mac=9a:4d:4e:4f:50:51,id=id3DveCw,vectors=4,netdev=idgW5YRp,bus=pci.0,addr=05
>     \
>     -netdev tap,id=idgW5YRp \
>     -m 2048  \
>     -smp 4,maxcpus=4,cores=2,threads=1,sockets=2  \
>     -cpu 'SandyBridge',+kvm_pv_unhalt \
>     -vnc :0  \
>     -rtc base=utc,clock=host,driftfix=slew  \
>     -boot order=cdn,once=c,menu=off,strict=off \
>     -enable-kvm \
>     -monitor stdio \
>     -qmp tcp:localhost:4444,server,nowait
> -2. in kernel cmdline with the following options: console=tty0 console=ttyS0,
> 
> Because the  "-nodefaults" option in qemu cmd excludes the emulation of
> serial port, the ttyS0 will
> have no real backend device. We can observe such issue in 1st kernel by:
> 	echo teststring > /dev/console or
> 	echo teststring > /dev/ttyS0,
> It gets the error "-bash: echo: write error: Input/output error".
> Such conds cause small issue in 1st kernel, but it is a big problem for
> kdump-capture and emergency
> service.
> 
> This patch aims to work aroundthe issue in kdump-capture service:
> dump_fs() return value will affect the following code in dracut-kdump.sh
> 	DUMP_RETVAL=$?    <---
> 	do_kdump_post $DUMP_RETVAL
> 	if [ $? -ne 0 ]; then
> 	    echo "kdump: kdump_post script exited with non-zero status!"
> 	fi
> 
> Although kdump-capture saves the vmcore successfully, but it exit 1 and
> fall on emergency service.
> 
> Signed-off-by: Pingfan Liu <piliu@redhat.com>
> ---
>  kdump-lib-initramfs.sh | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/kdump-lib-initramfs.sh b/kdump-lib-initramfs.sh
> index 4c0e2e2..2c18c87 100755
> --- a/kdump-lib-initramfs.sh
> +++ b/kdump-lib-initramfs.sh
> @@ -111,6 +111,8 @@ dump_fs()
>      sync
>  
>      echo "kdump: saving vmcore complete"
> +    # improper kernel cmdline can cause the failure of echo, we can ignore
> this kind of failure
> +    return 0
>  }
>  
>  save_vmcore_dmesg_fs() {
> --
> 2.7.4
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      parent reply	other threads:[~2017-04-17  7:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17  6:44 [PATCH 1/2] kdump-lib-initramfs.sh: ignore the failure of echo Pingfan Liu
2017-04-17  6:44 ` [PATCH 2/2] kdumpctl: verify the kernel cmdline Pingfan Liu
2017-04-17  7:46 ` Pingfan Liu [this message]

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=830319975.15356555.1492415215683.JavaMail.zimbra@redhat.com \
    --to=piliu@redhat.com \
    --cc=kexec@lists.infradead.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