Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I've finally had a chance to look at this.
It looks as if the i6300esb code is setting its timeout to a negative value, due to an integer overflow.
What I haven't understood yet, is how it's working on x86, which looks as if it should be subject to exactly the same problem.
Xu, never mind.
I've found a different, ppc64 only bug that caused the problem here.
A side effect of the bug was that it made it easier to trigger the first bug I found, which will also appear on x86, but not with the default configuration of the watchdog driver in the guest side. I will file a different BZ for that bug.
Ok, overflow bug filed as 1203914.
The ppc64 specific bug reported here (technically it will happen on any platform considered by qemu to be big-endian by default) is much simpler. The IO ports on the i6300esb device are marked in qemu as being NATIVE_ENDIAN, when they should (as a PCI device) be LITTLE_ENDIAN.
Reproduce this bug with BE guest ang LE guest on the "qemu-kvm-rhev-2.1.2-23.el7.ppc64" host,hit the same issue.
Verify this bug with BE guest and LE guest on the "qemu-kvm-rhev-2.3.0-12.el7.ppc64" host,not hit this issue.
Verify this bug with Be guest and LE guest on the "qemu-kvm-rhev-2.3.0-13.el7.ppc64le" host,not hit this issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2546.html
Description of problem: The timer expires immediately just by opening the '/dev/watchdog' interface. Both BE and LE guests hit this issue. Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.2.0-5.el7.ppc64 How reproducible: 100% Steps to Reproduce: 1. Boot guest with i6300esb watchdog timer. /usr/libexec/qemu-kvm ... \ -device i6300esb,id=watchdog0 -watchdog-action pause # dmesg | grep -i i6300esb [ 3.499000] i6300esb: Intel 6300ESB WatchDog Timer Driver v0.05 [ 3.499044] i6300ESB timer 0000:00:00.0: enabling device (0100 -> 0102) [ 3.500952] i6300esb: initialized (0xd000080080080000). heartbeat=30 sec (nowayout=0) 2. Open watchdog interface. # python Python 2.7.5 (default, Dec 19 2014, 13:08:28) [GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> wd = open("/dev/watchdog", "w") Actual results: The timer expires immediately. (qemu) info status VM status: paused (watchdog) Expected results: This device works properly. Additional info: CMDline: /usr/libexec/qemu-kvm \ -name watchdog-test-xuhan \ -machine pseries,accel=kvm,usb=off \ -m 4096 \ -cpu POWER8 \ -smp 4,sockets=2,cores=2,threads=1 \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,path=monitor,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=utc \ -boot strict=on \ -device pci-ohci,id=usb,bus=pci.0,addr=0x1 \ -device spapr-vscsi,id=scsi0,reg=0x2000 \ -drive file=rhel72.qcow2,if=none,id=drive-scsi0-0-0-0,format=qcow2 \ -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 \ -netdev tap,id=hostnet0 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5d:c7:9e,bus=pci.0,addr=0x2 \ -chardev socket,id=charserial0,path=serial,server,nowait \ -device spapr-vty,chardev=charserial0,reg=0x30000000 \ -device usb-kbd,id=input0 \ -device usb-mouse,id=input1 \ -device i6300esb,id=watchdog0 -watchdog-action ${action} \ -vnc 0.0.0.0:50 \ -k en-us \ -device VGA,id=video0,vgamem_mb=16,bus=pci.0,addr=0x3 \ -monitor stdio