Bug 426714
Summary: | fc9 tagged kernels cause network service to stall system, fc8 tagged .. no stall | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jim Cornette <jim.cornette> | ||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | low | Docs Contact: | |||||||||||
Priority: | low | ||||||||||||
Version: | rawhide | CC: | notting | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | All | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | kernel-2.6.25-0.35.rc1.fc9.i686 | Doc Type: | Bug Fix | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2008-02-14 11:16:24 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
Jim Cornette
2007-12-24 19:44:26 UTC
Created attachment 290357 [details]
My Ethernet Card ifup script which is used for system
Problem still exists kernel-2.6.23.9-85.fc8 - network starts OK kernel-2.6.24-0.133.rc6.git8.fc9 - locks up after network is started and replies OK Is the system completely hung, or is just the startup process hung? If you boot with 'confirm' and choose to not set up the network, does it hang if you start it by hand? I believe it is the startup process. I can change from the GUI rhgb screen to screen 1 text. It locks up if you start network after the system is ready also. If network services are not launched automatically and networkmanager is used I have connectivity plus wireless with fc9 tagged kernels. Both service network start and metworkmanager work with fc8 kernels which I tried with no problem. (not both on at the same time, used individully) Can you do 'service network start' on one terminal, wait for the hang, and do 'ps axf' on the other terminal (and capture the output?) Created attachment 291026 [details]
ps axf after network service started
Yes it was possible to start the network service from one vt in runlevel 3
while able to use a second vt to save process information. I saved the output
before starting network too but did not add it to the report.
Using kernel-2.6.24-0.138.rc7.fc9 for test. Looking through the attachment it looks like eth1 is trying to be initialized. It is a wireless PCMCIA card that is not supposed to be started at boot. I have no wireless modem so my neighbors networks are seen but are not used so the card should not be initialized on boot. eth1: cat /etc/sysconfig/network-scripts/ifcfg-eth1 # Cisco Systems 350 Series Wireless LAN Adapter DEVICE=eth1 BOOTPROTO=dhcp ONBOOT=no HWADDR=00:0e:38:c7:bc:10 [root@HP-JCF7 ~]# cat /etc/sysconfig/networking/devices/ifcfg-eth1 # Cisco Systems 350 Series Wireless LAN Adapter DEVICE=eth1 ONBOOT=no BOOTPROTO=dhcp HWADDR=00:0e:38:c7:bc:10 NETMASK= DHCP_HOSTNAME= IPADDR= DOMAIN= TYPE=Wireless USERCTL=no IPV6INIT=no PEERDNS=yes ESSID= CHANNEL=1 MODE=Master RATE=Auto Tcat /etc/sysconfig/network-scripts/ifcfg-eth0 # National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:0B:CD:34:B0:16 ONBOOT=yes DHCP_HOSTNAME=HP-JCF7 TYPE=Ethernet [root@HP-JCF7 ~]# cat /etc/sysconfig/networking/devices/ifcfg-eth0 # National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:0B:CD:34:B0:16 ONBOOT=yes DHCP_HOSTNAME=HP-JCF7 TYPE=Ethernet This is the card that I want below which happens for the fc8 tagged but apparently not for fc9 tagged versions, if I'm reading the information correctly. eth0: cat /etc/sysconfig/network-scripts/ifcfg-eth0 # National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:0B:CD:34:B0:16 ONBOOT=yes DHCP_HOSTNAME=HP-JCF7 TYPE=Ethernet [root@HP-JCF7 ~]# cat /etc/sysconfig/networking/devices/ifcfg-eth0 # National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:0B:CD:34:B0:16 ONBOOT=yes DHCP_HOSTNAME=HP-JCF7 TYPE=Ethernet 1161 ? D< 0:00 /sbin/modprobe pcmcia:m015Fc000Af06fn00pfn00paA17C320Epb3D011600pc00000000pd00000000 This command is hanging - this is a kernel issue (presumably in that driver.) Created attachment 291035 [details]
ps axf for fc8 tagged kernel
The system was brought up with network services initially off for startup. I
logged into two vt terminals and comparatively repeated the same procedures
that I tried for the previous fc9 tagged kernel. This kernel is kernel version
2.6.23.9-85.fc8 which seems to work as expected.
Thanks! So the unused at home wireless card is causing the hang? Should I file a bug against the kernel and driver or redirect this bug report to the pcmcia wireless driver? This is already moved to the kernel - no new bug required. The network does not stall when using kernel-2.6.23.14-107.fc8 but still does for kernel-2.6.24-0.157.rc8.fc9. Was there a major change in 2.6.24 from 2.6.23 which accounts for the service network start problem that I'm currently stuck with? Cisco Aironet wireless PCMCIA adapter seems to be the identity of the driver causing the lockup according to Chuck Ebbert from a mailing list posting. Created attachment 293084 [details]
ps axf when connected
It appears that I can still connect to the network.
I am in runlevel 3 and started network services which hung but seemed to
connect my wired connection fine.
With kernel-2.6.25-0.35.rc1.fc9.i686 the lockup at starting network services is no longer a problem. I do get a wired connection. The wireless driver will be examined later which caused the initial service network start lockup with kernel 2.6.24 series kernels. |