Bug 51063
Summary: | USB hangs on boot in UP mode | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | James Cook <bonkabonka> | ||||
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | roswell | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2001-09-07 22:12:57 UTC | Type: | --- | ||||
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
James Cook
2001-08-06 23:40:01 UTC
Please look at VC3 (switch over as soon as you can) and let us know the last few lines that get printed out. Also VC4 is helpful. We (Red Hat) should really try to fix this before next release. It appears to have something to do with USB. What shows up on VC4 prior to the hang is: <6>usb.c: registered new driver usbdevfs <6>usb.c: registered new driver hub <6>usb-uhci.c: $Revision: 1.259 $ time 15:38:25 Jul 24 2001 <6>usb-uhci.c: High bandwidth mode enabled <6>usb-uhci.c: USB UHCI at I/O 0xef80, IRQ 9 <4>usb-uhci.c: Detected 2 ports On VC3 it says: * looking for usb controllers * found USB controller usb-uhci * going to insmod usbcore.o (path is NULL) * going to insmod usb-uhci.o (path is NULL) On the theory that USB was causing the installer to hang, I went into the BIOS and disabled USB. The installer came up just fine at that point. That's all well and good, but I'm using a USB keyboard and mouse on it ... ;) So, another reboot to re-enable the USB and to try fiddling with some of the USB settings in the BIOS. Enabling or disabling "Port 64/60 Emulation" didn't do anything for me, nor did enabling or disabling "USB KB/Mouse Legacy Support". So, to make the installer happy, I scrounged up an old PS/2 keyboard and mouse and used that instead. Once installed, USB functions just fine, it's just the installer that has heartburn. If you have usb enabled in the bios, and boot with 'nousb' on the command line when booting the installer, does it not hang? I know this will not let you use the keyboard and mouse, just want to check this helps with the hanging. Doing a "linux nousb" at the ldlinux prompt made the load up just fine. Ugh, that english doesn't parse very well. s/made the load up/made the installer load up/ (duh) It occurs to me that if it'd be helpful to see the machine, I live in Durham and it wouldn't be a problem for me to bring the machine by some time. Besides, it'd be fun to get the nickel tour. :) There are known problems with some machines and USB in the kernel, which is why we have the 'nousb' option. Passing to the kernel team, this appears to be related to drivers and hardware. I have two questions for the requestor. 1. It was indicated that switching VTs worked. When switching to tty2, did the bash prompt respond to <Enter>? 2. Did hitting <alt>-<sysrq>-P produce anything? It may be disabled sometimes. I assume you may test this without destroying the current installation because the hang happens very early. Sorry it took me so long to check this ... In regards to the first question, the shell is never launched because the hang occurs during the rinning of /sbin/loader. Once the system hangs, hitting alt-sysrq-p has no effect. Gah, I can spell, really I can. s/rinning/running/ The note of 08/07 says "once [OS] is installed, USB works fine". That means the difference between i386-BOOT and i686smp kernels is significant. Can you try "nousb" with regular reboot and see if the thing hangs (or better yet, use i686 kernel that is installed by default even on SMP machines)? BTW, Never enable "Port 60/64 Emulation" - I do not guarantee that psaux driver is compatible with all [broken] SMM emulators that BIOS vendors ship. Oops, I am sorry - I meant "nosmp", not "nousb". See if it locks in UP mode. Aha! That's what that port 64/60 jazz is all about! :) Thanks for that tidbit. Booted the system up off the harddrive and told Grub to load the single-processor kernel. System hung when it went to initialize the USB controller. Intriguing! Just tried the Rowswell 2 release, same issue when using the uni-processor kernel. Installer also still hangs when not specifying the nousb parameter. Since you have the hardware, we have to debug on your box, if you are interested in pursuing it. Can you compile kernels, or do you need RPMs from me? Also, please verify for me that you box is not based on 440GX chipset. I'd be happy to help debug. It's not a problem to compile kernels either. :) The board is based on the 440GX chipset for what it's worth. Created attachment 30254 [details]
VA patch (for 2.2 kernel!)
Could you try adding "apic" to the syslinux prompt ? eg type "linux apic" on the very very first screen ? The apic option works great! The installer booted right up and detected my USB stuff. I discussed it with the team and we decided not to try to pull VA fix. It is a vendor specific workaround for a broken hardware. Also, "apic" works. |