Bug 13605
| Summary: | errors during boot | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Gene Czarcinski <gczarcinski> |
| Component: | initscripts | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 | CC: | rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | Winston rc1 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-08-05 13:17:32 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: | |||
|
Description
Gene Czarcinski
2000-07-08 20:19:17 UTC
Do you get the same errors when running hdparm manually? No. I ran hdparm manually on hda and hde with "no" parameters and with "-q -c3 -A1" which I got from examining /etc/rc.sysinit and /etc/sysconfig/harddisks. The only message I got was "setting drive read-lookahead to 1 (on)" which was the same in both cases. The only "strangeness" was that the disk on the promise card does not use LBA and has a geometry of 39566/16/63. Then it's a problem with the way it's invoked in the init scripts; reassigning This defect is considered MUST-FIX for Winston Release-Candidate #1 I took a look for this problem in pinstripe. Something has changed but I am not sure that the bug is fixed. One of the problems is trying to spot this while the messages flash by on the screen. I appear to be still getting the "Hint ... IO or IRQ ..." message but I am not sure it is following a "Setting hard drive parameters for hde" message. IN fact, I believe I did not see any "Setting hard drive ..." messages. I wish there was some way to slow up or capture these messages someplace. Gene C. They should show up in /var/log/boot.log. If they don't that's another bug. :( The "hints" message do NOT show up in /var/log/boot.log under with beta3 or beta5. Under beta3, I get these "hint" messages after the "Setting hard drive parameters ..." messages (which do appear in boot.log. Under beta5 (pinstript), there are NO "Setting hard drive ..." messages in boot.log or on the screen. The "hints" messages show up on the screen only. I now conclude that the "Hint" messages have NOTHING to do with the Promise controller -- they are issued by "insmod" (found with the strings command). This has something to do with loading/installing some module. I will look/test further later today or tonight. If the insmod-generated message is not in boot.log, is this an error? Gene What does lspci -v say? This is probably an error when it goes to try and initialize the USB controller. Also, what's in /etc/modules.conf? As built by the install process (anaconda): alias scsi_hostadapter ncr53c8xx alias eth0 3c59x alias parport_lowlevel parport_pc alias sound-slot-0 es1370 alias usb-controller uhci OK, I have found the problem and it concerns the usb support shich is new. 1. My motherboard has a usb controller but is disabled as much as possible to "save" the IRQs. I do not currently have any usb peripherals. 2. The two error messages result from the modprobe issued at lines 153 and 165 in /etc/rc.d/rc.sysinit. I "instrumented" /etc/rc.d/rc.sysinit by putting some "echo" commands in and they nailed it. 3. I am closing this bug as NOTABUG but I am openin a new bug against initscripts: I tried to put "nousb" into /proc/cmdline but it has no effect initscripts. |