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.
Bug 1352821 - Key "," can not be inputted during SLOF and yaboot stage
Summary: Key "," can not be inputted during SLOF and yaboot stage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: SLOF
Version: 7.3
Hardware: ppc64le
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Thomas Huth
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-05 07:52 UTC by Min Deng
Modified: 2016-11-04 04:34 UTC (History)
6 users (show)

Fixed In Version: SLOF-20160223-5.gitdbbfda4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 04:34:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
yaboots (31.85 KB, image/png)
2016-07-08 08:23 UTC, Min Deng
no flags Details
sloflog (1.44 KB, text/plain)
2016-07-08 08:24 UTC, Min Deng
no flags Details
US keyboard keys (59.02 KB, image/png)
2016-07-08 08:33 UTC, Laurent Vivier
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2355 0 normal SHIPPED_LIVE SLOF bug fix and enhancement update 2016-11-03 13:48:37 UTC

Description Min Deng 2016-07-05 07:52:31 UTC
Description of problem:
Key  "," can not be inputted during SLOF stage

Version-Release number of selected component (if applicable):
kernel-3.10.0-456.el7
qemu-kvm-rhev-2.6.0-10.el7
SLOF-20160223-4.gitdbbfda4.el7
Guest kernel to: kernel-2.6.32-642.3.1.el6

How reproducible:
5

Steps to Reproduce:
1.boot up guest with 
  ...-device nec-usb-xhci,id=controller3 -device usb-hub,id=usbhub33,bus=controller3.0,port=1 -device usb-mouse,id=usbmouse,port=1.1 -device usb-kbd,id=usbkbd,port=1.2 -device usb-tablet,id=usbtablet,port=1.3 ...
2.During SLOF stage and press "s"
3.input "," via keyboard

Actual results:
Key "," can't be inputted except for login OS

Expected results:
Key "," can be inputted 

Additional info:
Change several key boards but still can reproduce the issue.The hardware is good.

Comment 2 Karen Noel 2016-07-05 10:44:41 UTC
Is this Power or X86?

Comment 3 Min Deng 2016-07-06 05:59:50 UTC
(In reply to Karen Noel from comment #2)
> Is this Power or X86?

 It is on power platform,any issues please let me know!thanks.

Comment 4 Laurent Vivier 2016-07-07 13:15:50 UTC
According to what I've seen for BZ1352765, in this configuration (XHCI + USB HUB) the keyboard is not detected by SLOF:

- Is it possible to have the full SLOF logs?
- are you able to input some other keys?

If you boot linux, can you input ","?

if you have this kind of message in SLOF, this BZ is a duplicate of BZ1352765:

Scanning USB 
  XHCI: Initializing
    USB HUB 
usb-hub: unable to setup device on port 0
usb-hub: unable to setup device on port 1
usb-hub: unable to setup device on port 2

Comment 5 Min Deng 2016-07-08 08:22:00 UTC
(In reply to Laurent Vivier from comment #4)
> According to what I've seen for BZ1352765, in this configuration (XHCI + USB
> HUB) the keyboard is not detected by SLOF:
> 
> - Is it possible to have the full SLOF logs?
   ok,I will upload it right now.
> - are you able to input some other keys?
   Yes,I can 
> If you boot linux, can you input ","?
   I cannot input "," except for login OS (mentioned in the bug) 
   It is also can be reproduced via yaboot's stage.please see attach
   Notes,please connect to guest with remote-viewer or vncviewer and then input ","

> if you have this kind of message in SLOF, this BZ is a duplicate of
> BZ1352765:
> Scanning USB 
>   XHCI: Initializing
>     USB HUB 
> usb-hub: unable to setup device on port 0
> usb-hub: unable to setup device on port 1
> usb-hub: unable to setup device on port 2
  
  In order to avoid the BZ1352765 and I will remove hub and boot up with the following cli,Still,can reproduce the bug.
  /usr/libexec/qemu-kvm -name avocado-vt-vm1 -sandbox off -machine pseries -nodefaults -vga std -chardev socket,id=serial_id_serial0,path=/var/tmp/3,server,nowait -device spapr-vty,chardev=serial_id_serial0 -device nec-usb-xhci,id=controller1 -device usb-storage,id=storage,bus=controller1.0,drive=drive0,bootindex=0 -drive file=RHEL-Server-6.8-ppc64-virtio-scsi.qcow2,id=drive0,if=none,format=qcow2 -device spapr-vscsi,id=scsi0,reg=0x1000 -drive if=none,id=drive-scsi0-0-1-0,readonly=on,file=RHEL-6.8-20160414.0-Server-ppc64-dvd1.iso -device scsi-cd,bus=scsi0.0,drive=drive-scsi0-0-1-0,bootindex=1,id=scsi0-0-1-0 -m 8G -smp 8,maxcpus=8,cores=4,threads=1,sockets=2 -vnc :1 -enable-kvm -monitor stdio -uuid cbf8e8f5-6bb7-4d73-9581-d29b43aab22a -device virtio-net-pci,mac=9a:d4:d5:d6:d7:d8,id=idkdMjSW,vectors=4,netdev=hostnet0,disable-legacy=off,disable-modern=on -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown -qmp tcp:0:4441,server,nowait -device nec-usb-xhci,id=controller0 -device usb-mouse,id=usbmouse,bus=controller0.0 -device usb-kbd,id=usbkbd,bus=controller0.0 -device usb-tablet,id=usbtablet,bus=controller0.0

Comment 6 Min Deng 2016-07-08 08:23:17 UTC
Created attachment 1177566 [details]
yaboots

Comment 7 Min Deng 2016-07-08 08:24:47 UTC
Created attachment 1177567 [details]
sloflog

Comment 8 Laurent Vivier 2016-07-08 08:33:54 UTC
Created attachment 1177580 [details]
US keyboard keys

Are you using an US keyboard?
The position of the ',' can differ between keyboards.

Comment 9 Min Deng 2016-07-10 15:09:58 UTC
SLOF-20160223-4.gitdbbfda4.el7.noarch

Comment 10 Min Deng 2016-07-10 15:11:06 UTC
(In reply to Laurent Vivier from comment #8)
> Created attachment 1177580 [details]
> US keyboard keys
> 
> Are you using an US keyboard?
> The position of the ',' can differ between keyboards.

 yes,I think so
 And I used different machine with keyboards to test it.

Comment 11 Thomas Huth 2016-07-14 11:46:51 UTC
I've now found the part of the code in SLOF that causes this problem and sent a patch upstream to fix this issue:
https://patchwork.ozlabs.org/patch/648342/

Comment 12 Miroslav Rezanina 2016-07-26 07:47:02 UTC
Fix included in SLOF-20160223-5.gitdbbfda4.el7

Comment 14 Min Deng 2016-08-09 02:00:01 UTC
Verified the bug on build SLOF-20160223-6.gitdbbfda4.el7.noarch.rpm
Now it has been fixed on,thanks a lot.

Comment 16 errata-xmlrpc 2016-11-04 04:34:32 UTC
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/RHEA-2016-2355.html


Note You need to log in before you can comment on or make changes to this bug.