Bug 440648
| Summary: | system/kernel lockup on service NetworkManager start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew Farris <lordmorgul> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | dcbw, fernandoatrio, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.smolts.org/show?uuid=pub_78677281-8dfd-41a6-86f4-2460453c168d | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-04-10 23:27:30 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
Andrew Farris
2008-04-04 12:05:33 UTC
Is the capslock light flashing to indicate a kernel panic? Can you turn NM off with chkconfig, then boot up and switch to a VT, then from there start NetworkManager to capture some of the panic? If the machine hardlocks, it's almost certainly a kernel driver bug. Capslock was not flashing any time its happened yet (none of the LEDS were). I have NM off via chkconfig already, and was doing the service start manually. No output shows up other than the 'Starting NetworkManager..[ok]' and my next terminal prompt (I use a complicated custom $PS1, it finishes doing that). Then, and only after the bash prompt.. the cursor stops blinking. I've tried in runlevel 3 and 5. Right now I don't know if its actually a kernel lock or not because I have no network response to check (it has no active interface). BTW, until I turned off NM it was partially working at one time in rawhide, but it was not correctly configuring the wired interfaces then. It was at least able to start the service, and it would use DHCP on both interfaces but without any DNS. I know it was working with kernel-2.6.25-0.121.rc5.git4.fc9.i686 because thats the reason I've still got it installed. It now fails with that kernel, so I'm not sure how to decide if its a kernel bug or not. I see the exact same bug on a fedora 8 machine running the latest kernel update, kernel-2.6.24.4-64.fc8. Everything works fine if I go back to kernel-2.6.24.3-50.fc8. This is my smolt profile: http://www.smolts.org/client/show/pub_a29d08fe-f229-45fe-9559-887ca3105085 Thats interesting Fernando. It looks like we have a somewhat similar wireless adapter, although yours is using the rt61 driver and mine is using the rt2500pci driver. Dan, I may be able to test using only the two wired adapters. Other than me removing my wireless adapter, or blacklisting the driver, how do I turn it off or prevent NM from trying to configure it when the service starts? Right now I do not have anything configured for that adapter in system-config-network at all. There are no config scripts in /etc/sysconfig/network* for it either. Would NM take any action trying to auto- configure that adapter in this case? I have narrowed this down a little bit. I used system-config-network to create a configuration for ifcfg-wlan0 using the rt2500pci driver and setting the adapter to be NM controlled. The system now allows NetworkManager to start, and control all the adapters. The problem seems to be related to some attempt at auto configuration when the kernel driver for the wireless device was loaded but no config was present yet. Any chance you can revert to the broken setup and try sysrq on the box to see where it's hanging? would be good to track down the hang even if it's not a panic... http://en.wikipedia.org/wiki/Magic_SysRq_key I removed the configuration for my wlan0 in /etc/sysconfig/network-scripts and
/etc/sysconfig/networking/{default,profiles/default}, then attempted to
reproduce the problem and I cannot.
When starting from a fresh boot, no configuration scripts in place for wlan,
ifconfig shows an unconfigured adapter and NM starts up fine.
I had to blacklist the tulip module due to my tulip device problems to test this
but once I did I cannot get any hang now (only tested .204 kernel). Going to
close until it can be reproduced. I'll try with a fresh Preview install.
Everything works fine here, running kernel-2.6.24.5-85.fc8 |