Bug 120724 - use of ifdown script or neat cause kernel panic
Summary: use of ifdown script or neat cause kernel panic
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-13 14:42 UTC by Todd Fisher
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-04-16 08:57:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Todd Fisher 2004-04-13 14:42:41 UTC
Description of problem:
If I use ifdown or neat to deactivate my ethernet card my
system locks up.

Version-Release number of selected component (if applicable):
kernel - 2.6.5-1.315
system-config-network - 1.3.16
net-tools - 1.60
ifconfig 1.42 (2001-04-13)

How reproducible:
ifdown eth0 or neat select eth0 and click deactivate
  
Additional info:
also, whenever I issue the command
su -
shutdown -r now or shutdown -h now
i get the following kernel panic:
reproduced here as closely as possible to what I read from the 
crashed machine.

generic_file_aoi_read
do_page_fault
sel_write_user
pte_alloc_one
pte_alloc_map
handle_mm_fault
get_user_pages
str_vm
elf_map
zero_user_size
load_elf_interp
load_elf_binary
avc_has_perm
search_binary_handler
[<0216c697>] do_execve+0x187/0x219
[<02104958>] sys_execve+0x2a/0x6f

kernel/timer.c:295 spin_lock(kernel/timer.c:023313e0) already locked
by kernel/timer.c/392
Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing

Comment 1 Arjan van de Ven 2004-04-13 14:43:44 UTC
what kind of network card is this ?
(eg which kernel module)

Comment 2 Todd Fisher 2004-04-13 16:20:48 UTC
neat hardware tab:

82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller
Prism 2.5 Wavelan chipset
orinoco_pci

from /etc/sysconfig/hwconf

class: NETWORK
bus: PCI
detached: 0
device: eth
driver: e100
desc: "Intel Corp.|82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller"
vendorId: 8086
deviceId: 1031
subVendorId: 1014
subDeviceId: 0209
pciType: 1

and the wireless card:

class: OTHER
bus: PCI
detached: 0
driver: orinoco_pci
desc: "Harris Semiconductor|Prism 2.5 Wavelan chipset"
vendorId: 1260
deviceId: 3873
subVendorId: 1668
subDeviceId: 0406
pciType: 1

My system was originally a redhat 9 machine.  I used apt to upgrade it
to fc1 and then downloaded the fc2-test2 iso used the installer to
upgrade to fc2-test2 and have since switched to yum downloading all
the updates todate.

Comment 3 Todd Fisher 2004-04-13 17:43:03 UTC
looks like the problem was fixed in the change to 2.6.5-1.319
ifdown doesn't lock up the system and shutdown -r doesn't cause
a kernel panic anymore.

Comment 4 Arjan van de Ven 2004-04-16 08:57:07 UTC
hmmmmm ok I'll close it then.
If it comes back please reopen..


Note You need to log in before you can comment on or make changes to this bug.