On Wed, Sep 17, 2008 at 03:20:50PM +0300, Pasi Kärkkäinen wrote: > On Wed, Sep 17, 2008 at 01:46:14PM +0300, Pasi Kärkkäinen wrote: > > On Wed, Sep 17, 2008 at 01:21:24PM +0300, Pasi Kärkkäinen wrote: > > > On Thu, Sep 11, 2008 at 07:02:20PM +0300, Pasi Kärkkäinen wrote: > > > > On Thu, Sep 11, 2008 at 11:52:42AM -0400, Tom Sightler wrote: > > > > > On Thu, 2008-09-11 at 12:26 +0300, Pasi Kärkkäinen wrote: > > > > > > Hello! > > > > > > > > > > > > I have some IBM HS21-8853 blades, and they work all fine as long as > > > > > > I don't > > > > > > plug in IBM Qlogic QMC4052 iSCSI HBA.. > > > > > > > > > > > > After adding QMC4052 HBA, IRQ routing (?) gets messed up and the > > > > > > USB-based console > > > > > > in IBM bladecenter/chassis (keyboard and mouse) don't work very > > > > > > well anymore.. > > > > > > every keypress gets doubled, and mouse is really wild :) so can't > > > > > > really use > > > > > > the console for anything.. Other devices seem to work fine, ie. it > > > > > > _seems_ to only > > > > > > affect the USB console. > > > > > > > > > > > > Screenshot of what kernel says during system startup: > > > > > > http://pasik.reaktio.net/ibm-hs21-blade-usb-problem-02.jpg > > > > > > > > > > > > irq 74: nobody cared (try booting with the "irqpoll" option) > > > > > > .. > > > > > > Disabling IRQ #74 > > > > > > > > > > > > This problem gets fixed with the suggested "irqpoll" option to the > > > > > > kernel > > > > > > cmdline, ie. console works normally after giving "irqpoll" option > > > > > > to the > > > > > > kernel. Although the "nobody cared" error will still happen during > > > > > > bootup.. > > > > > > > > > > > > I'm running RHEL 5.2 (2.6.18-92) atm. > > > > > > > > > > > > Any ideas how to fix this? I'm running latest IBM BIOS (v1.13) on > > > > > > the > > > > > > Blades.. Is there some option in BIOS that could affect this? > > > > > > > > > > > > Same QMC4052 HBAs work all fine in older IBM HS20-8843 blades.. > > > > > > > > > > We have exactly this same problem on the same hardware, IBM 8853 > > > > > blades > > > > > with QMC4052 HBA's, and I've had a support case open with Redhat for > > > > > about a month. So far the only feedback has been to try the latest > > > > > kernel version (we were running 2.6.18-92.1.6). I haven't been able > > > > > to > > > > > try the newest kernel because I've been waiting on a maintenance > > > > > window > > > > > to reboot the system, which should happen this weekend. > > > > > > > > > > > > > Nice to hear from you again! :) > > > > > > > > > I do have a workaround though, if you build the initrd using the > > > > > "--without-usb" option of the mkinitrd command, it seems to > > > > > effectively > > > > > work around this bug. The usb modules will still be loaded during > > > > > system initialization, just not until after the initrd is finished. > > > > > For > > > > > whatever reason, having the USB modules loaded after the qla4xxx > > > > > module > > > > > seems to work around the issue. > > > > > > > > > > > > > Ok.. that's weird. I'll try "--without-usb" now. > > > > > > > > > > Yes, indeed "--without-usb" for mkinitrd seems to fix the problem. > > > So there's a workaround at least. > > > > > > When comparing dmesg output between normal initrd image, and the one > > > generated with > > > "--without-usb", the difference seems to be in IRQ assignment. > > > > > > "--without-usb" generated initrd image seems to get/assign different IRQ > > > to > > > qla4xxx card then the normal/default one.. > > > > > > -- Pasi > > > > > > > I just tried the latest RHEL 5.3 beta kernel 2.6.18-115.el5PAE (with default > > settings/initrd) and it seems to have the same problem than released RHEL > > 5.x kernels. > > > > This starts to look like a bug in IBM HS21 blade BIOS/ACPI/firmware or > > something.. > > > > I just tried RHEL 5.2 kernel 2.6.18-92.1.10.el5PAE, and it has the same > problem.. just like expected. > > "--without-usb" fixes the problem for all kernel versions in RHEL 5.x. >
And yet another reply to my own mail :) I did some more testing, and the same problem happens with all RHEL5.x versions (5.0, 5.1 and 5.2), and also with RHEL4.6 and RHEL4.7 (didn't try any other 4.x version). Except that it's even worse with RHEL4.x. With RHEL5.x console keyboard repeats every character twice, but with RHEL4.x console keyboard is totally dead after loading qla4xxx module. Obviously using RHEL installer (we're booting from iSCSI SAN, so we need to have the HBA plugged in straight from the beginning) is a pain with this problem.. can't type any IP addresses, it's difficult to choose anything etc.. Basicly scripted kickstart installs are the only way to get RHEL installed into HS21 blades with QMC4052 HBA.. at least before this bug is fixed, where ever the problem actually is.. I also tried Fedora 9, and it didn't have this problem.. console keyboard worked fine after qla4xxx module was loaded! -- Pasi _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
