Bug 1353836
| Summary: | kexec boot kernel guest had Call Trace | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | weliao <weliao> | ||||||
| Component: | seabios | Assignee: | Bandan Das <bdas> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Xueqiang Wei <xuwei> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 7.3 | CC: | bdas, chayang, coli, juzhang, knoel, kraxel, virt-maint, xfu, xuwei | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-11-15 01:27:37 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
weliao
2016-07-08 07:15:50 UTC
(In reply to weliao from comment #0) > Description of problem: > Guest run kexec -l followed by kexec -e, had Call Trace. > > Version-Release number of selected component (if applicable): > Host: > 3.10.0-461.el7.x86_64 > qemu-kvm-rhev-2.6.0-11.el7.x86_64 > seabios-bin-1.9.1-4.el7.noarch > Guest: > 3.10.0-456.el7.x86_64 > How reproducible: > 50% > > Steps to Reproduce: > 1.Launch a guest. > /usr/libexec/qemu-kvm -name guest=7.3,debug-threads=on -machine pc -cpu > Opteron_G5 -m 2048 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 > -uuid 41b02868-1e28-4b59-8cc9-0e7516167755 -no-user-config -nodefaults -rtc > base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet > -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 > -boot menu=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device > ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on, > addr=0x6 -device > ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device > ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device > virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive > file=/home/RHEL-Server-7.3-64-virtio.qcow2,format=qcow2,if=none,id=drive- > virtio-disk0,snapshot=off -device > virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0, > id=virtio-disk0 -netdev tap,id=hostnet0,vhost=on -device > virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:eb:79:88,bus=pci.0,addr=0x13 > -device usb-tablet,id=input0 -spice > port=5900,addr=0.0.0.0,disable-ticketing,streaming-video=all,seamless- > migration=on -device > qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0, > vgamem_mb=16,bus=pci.0,addr=0x2 -device > intel-hda,id=sound0,bus=pci.0,addr=0x4 -device > hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev > spicevmc,id=charredir0,name=usbredir -device > usb-redir,chardev=charredir0,id=redir0 -chardev > spicevmc,id=charredir1,name=usbredir -device > usb-redir,chardev=charredir1,id=redir1 -device > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on -monitor > stdio -qmp tcp:0:4444,server,nowait -serial unix:/tmp/console,server,nowait > 2.Guest run kexec > kexec -l /boot/vmlinuz-3.10.0-433.el7.x86_64 > --initrd=/boot/initramfs-3.10.0-433.el7.x86_64.img > --append=root=/dev/mapper/rhel_virtlab--66--85--156-root ro console=tty0 > crashkernel=auto rd.lvm.lv=rhel_virtlab-66-85-156/root > rd.lvm.lv=rhel_virtlab-66-85-156/swap biosdevname=0 net.ifnames=0 > console=ttyS0,115200 LANG=en_US.UTF-8 > kexec -e > 3. > > Actual results: > Guest had Call Trace after reboot. > > Expected results: > Guest no Call Trace. > > Additional info: > [ 3.826285] usb 1-1: SerialNumber: 42 > [ 3.915514] irq 10: nobody cared (try booting with the "irqpoll" option) This looks like a device that was not safely shutdown when kexec was called, and now, the kexec kernel gets an interrupt for a driver that hasn't been initialized yet. Can you please retry this and see if it still exists ? (In reply to Bandan Das from comment #2) > > This looks like a device that was not safely shutdown when kexec was called, > and now, > the kexec kernel gets an interrupt for a driver that hasn't been initialized > yet. > > Can you please retry this and see if it still exists ? That is no problem at all. I keep the needinfo status just avoid I forget this. I will update results once I have. Thanks (In reply to Bandan Das from comment #2) > > This looks like a device that was not safely shutdown when kexec was called, > and now, > the kexec kernel gets an interrupt for a driver that hasn't been initialized > yet. > > Can you please retry this and see if it still exists ? Hi Bandan: I have tested this in lastest qemu and RHEL8.1.0 guest. I repeated exactly same steps in the original issue and I got different result. Please see the attachment. Version: Host: Red Hat Enterprise Linux release 8.1 Beta (Ootpa) kernel:4.18.0-131.el8.x86_64 qemu-kvm-4.0.0-6.module+el8.1.0+3736+a2aefea3.x86_64 guest: kenrel:4.18.0-128.el8.x86_64 Created attachment 1603642 [details]
result1
Created attachment 1603643 [details]
result2
|