Bug 167846
Summary: | FC4 Installer spews infinite of "release_dev read/write wait queue active!" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Levine <daniel.levine> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | pfrields, pjones, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-26 21:31:35 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
Daniel Levine
2005-09-08 20:27:31 UTC
Thinking about this more over the weekend, I'm not cerain if this is an anaconda issue or a kernel booting issue. I suppose I never get fully booted into anaconda. Are you trying to install the x86-64 release ? (The bug is filed against i386) The reason I ask, is that for x86-64 I believe we use the SMP kernel for installs. If so, things to try.. - booting with maxcpus=1 - booting with acpi=off It smells like a race in the tty layer to me, so limiting the install to a single CPU is probably the best behaviour. For future releases, we should probably make sure the installer always starts up with 1 cpu is isolinux. I tried your suggestions. It appears that the acpi=false option does the trick. The maxcpus=1 does not. I have 2 Intel Xeon processors with hyper threading and probably EM64T. I am definitely an SMP system. I didn't realize that it's not considered an i686 system anymore. Thanks for your help, -Dan so, if you do the install with acpi disabled, and then run yum update, it'll grab the latest updates, including a newer kernel. Can you see if that one then boots without the acpi disabled ? Unfortunately, I cannot do what you requested. The system installed is in a secure environment. However, using our SNARE enabled 2.6.12 kernel, it seems like we need the acpi=off still on boot. Otherwise, nash hangs forever (waited over 15 minutes). Normally, nash hangs for 2 minutes and then proceeds for us. Ok, given the inability to debug this further, I'll close this bug, as you have the acpi=off workaround. Thanks. |