USB Keyboard MM2 IBM - no input after Installation

[Christoph Mack]

After the installation is no interaction with the Keyboard of the IBM Bladecenter with Management Module MM2 possible.
The Installation-Method is with no problem possible and all keyboard inputs are OK. With the old version 12.04 the keyboard inputs are also good.

But after installation it isn't possible to do keyboard inputs. The inputs over the IPMI softkey works also not.

After switching to another server on the IPMI tool and then switching back the server the first inputs are accepted, but after input an ENTER all other inputs are ignored - IPMI softkey too.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic 3.13.0-23.45
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Apr 8 18:20 seq
 crw-rw---- 1 root audio 116, 33 Apr 8 18:20 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue Apr 8 18:22:42 2014
HibernationDevice: RESUME=UUID=a323327a-a13f-4149-a6e3-6d8e85a88841
InstallationDate: Installed on 2014-04-08 (0 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
Lsusb:
 Bus 001 Device 003: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 003: ID 04b3:4002 IBM Corp.
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM BladeCenter LS22 -[790162G]-
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=87173c3f-0c0d-4147-b281-51a3bbeffb8c ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-23-generic N/A
 linux-backports-modules-3.13.0-23-generic N/A
 linux-firmware 1.127
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/25/2011
dmi.bios.vendor: IBM
dmi.bios.version: -[L8E164AUS-1.07]-
dmi.board.name: Server Blade
dmi.board.vendor: IBM
dmi.chassis.type: 17
dmi.chassis.vendor: IBM
dmi.modalias: dmi:bvnIBM:bvr-[L8E164AUS-1.07]-:bd05/25/2011:svnIBM:pnBladeCenterLS22-[790162G]-:pvr:rvnIBM:rnServerBlade:rvr:cvnIBM:ct17:cvr:
dmi.product.name: BladeCenter LS22 -[790162G]-
dmi.sys.vendor: IBM

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

[Christoph Mack (c-mack)]

I have tested it with the new kernel 3.14, but the same failure as 3.13

I have it also tested with another Bladecenter H with MM2 and Bladeserver LS22 with 14.04. and the same problem.

Best regards

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

[Joseph Salisbury (jsalisbury)]

Also, this issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Alexey Dushechkin (alexey.dushechkin)]

Observing the same with HS23. I believe that it has nothing to do with kernel.

Spotted #1371403 and fixed this by adding /lib/udev/rules.d/95-ibm-amm-power-workaround.rules file with the following content:

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="04b3", ATTR{idProduct}=="4002", TEST=="power/control", ATTR{power/control}="on"

[Steffen Kupfer (s-kupfer)]

I can confirm the same behavior with a LS21, kernel 3.16.0-31-generic and the management modele with part number 39Y9659.

[suletom (suletom)]

The same on centos 7 running on HS21 XM