WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1015] New: hung of dom0 and others after rmmod xennet

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1015] New: hung of dom0 and others after rmmod xennet
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 5 Jul 2007 04:51:01 -0700
Delivery-date: Thu, 05 Jul 2007 04:52:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1015

           Summary: hung of dom0 and others after rmmod xennet
           Product: Xen
           Version: unspecified
          Platform: x86
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: P3
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: marco.strullato@xxxxxxxxx


Hi, my xen server hungs.
I have domain0 with 2 other virtual machines runnins.
dom0, dom1 and dom2 are linux fedora6.

I need three network interfaces in dom1 and dom2 so I add something like that
vif = [ 'mac=00:16:3e:17:27:05, bridge=xenbr0', 'mac=10:16:3e:17:27:05,
bridge=xenbr0', 'mac=20:16:1e:17:27:05, bridge=xenbr0' ]
to the configuration files.

Into the virtual machines I added to modprobe.conf 
alias eth0 xennet
alias eth1 xennet
alias eth2 xennet
and 
I configured the interfaces.

I had some problems with an interface in a virtual machine and I did:
rmmod xennet 
because I would to unload and reload the module.

This operation crashed the server: dom0, dom1 and dom2 hungs.

I get this with putty:

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: ------------[ cut here ]------------

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: kernel BUG at drivers/xen/core/evtchn.c:481!

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: invalid opcode: 0000 [#1]

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: SMP

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: CPU:    2

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: EIP is at retrigger+0x22/0x38

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: eax: 00000000   ebx: 02080000   ecx: f5416000   edx: 00000023

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: esi: c06d3e00   edi: 00000114   ebp: 00000000   esp: c0cc0e5c

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: ds: 007b   es: 007b   ss: 0069

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Process xenwatch (pid: 21, ti=c0cc0000 task=c0266620
task.ti=c0cc0000)

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Stack: c04426c9 c06d3e00 00000114 c06d3e28 c044240d 00000000
00000000 

c0d1a420

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:        000000f8 e0b29c00 e0b29c00 00000000 0000040c e0b29c00
ee22e8be 

00000000

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:        ee22ecd9 e0b29800 e0b29c00 c063e0a1 c054aad5 00000000
c063e145 

0000040c

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Call Trace:

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c04426c9>] check_irq_resend+0x41/0x48

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c044240d>] enable_irq+0x92/0xad

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<ee22e8be>] __netif_up+0xb/0x13 [netbk]

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<ee22ecd9>] netif_map+0x241/0x269 [netbk]

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<ee22e14f>] maybe_connect+0x2cc/0x49b [netbk]

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c054c3fa>] otherend_changed+0x74/0x79

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c054a94b>] xenwatch_handle_callback+0x12/0x44

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c054b414>] xenwatch_thread+0x108/0x11e

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c042df67>] kthread+0xc0/0xed

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c0402a69>] kernel_thread_helper+0x5/0xb

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Leftover inexact backtrace:

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  =======================

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Code: 75 96 5e 5f 5b 5e 5f 5d c3 8b 04 85 a0 1d 7f c0 8b 0d c4
a7 66 c0 

66 85 c0 74 20 0f b7 d0 0f a3 91 80 08 00 00 19 c0 85 c0 75 08 <0f> 0b e1 01 9b
d7 63 

c0 f0 0f ab 91 00 08 00 00 b8 01 00 00 00

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: EIP: [<c05462ca>] retrigger+0x22/0x38 SS:ESP 0069:c0cc0e5c
>From 10.9.94.30 icmp_seq=676 Destination Host Unreachable
>From 10.9.94.30 icmp_seq=677 Destination Host Unreachable
>From 10.9.94.30 icmp_seq=678 Destination Host Unreachable















test2 kernel: Call Trace:

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  [<c914e39f>] netfront_remove+0x16/0x1a [xennet]

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  [<c054c4d6>] xenbus_dev_remove+0x27/0x38

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  [<c05416a4>] __device_release_driver+0x60/0x78

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  [<c0541999>] driver_detach+0x99/0xc9

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  [<c0540e3b>] bus_remove_driver+0x5a/0x78

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  [<c0541aac>] driver_unregister+0x8/0x13

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  [<c0436a25>] sys_delete_module+0x192/0x1b9

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  [<c0404ea7>] syscall_call+0x7/0xb

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel: Leftover inexact backtrace:

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel:  =======================

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel: Code: 97 e6 ff e8 34 a8 05 00 e9 19 f7 e7 ff 89 c2 8b 80 94 02 00
00 85 

c0 75 0d 0f b7 42 64 29 c2 89 d0 e9 d7 50 eb ff 83 f8 03 74 08 <0f> 0b e2 0c 37
c6 64 

c0 c7 82 94 02 00 00 04 00 00 00 8d 82 f0

Message from syslogd@test2 at Thu Jul  5 14:33:23 2007 ...
test2 kernel: EIP: [<c05acc81>] free_netdev+0x1e/0x3b SS:ESP 0069:c4603f10

[root@test2 network-scripts]# modprobe xennet

[root@test2 network-scripts]# service network stop
Arresto dell'interfaccia eth0:  [  OK  ]
Arresto dell'interfaccia eth1:  [  OK  ]
Arresto dell'interfaccia eth2:  [  OK  ]
Arresto dell'interfaccia di loopback:  [  OK  ]
[root@test2 network-scripts]# rmmod xennet
ERROR: Removing 'xennet': Device or resource busy
[root@test2 network-scripts]# lsof | grep xennet
[root@test2 network-scripts]# modprobe xennet

[root@test2 network-scripts]# poweroff

Broadcast message from root (xvc0) (Thu Jul  5 14:36:27 2007):

The system is going down for system halt NOW!
INIT: Sending processes the TERM signal
[root@test2 network-scripts]# Arresto di smartd: [  OK  ]
Interruzione del demone HAL: [  OK  ]
Interruzione di atd: [  OK  ]
Interruzione di hpiod: [  OK  ]
Interruzione di hpssd: [  OK  ]
Interruzione di sshd: [  OK  ]
Arresto di sm-client: [  OK  ]
Arresto di sendmail: [  OK  ]
Interruzione di crond: [  OK  ]
Arresto di RPC idmapd: [  OK  ]
Arresto bus di messaggio del sistema: [  OK  ]
Interruzione di NFS statd: [  OK  ]
Interruzione di mcstransd: [  OK  ]
Interruzione di portmap: [  OK  ]
Interruzione del demone PC/SC smart card(pcscd): [  OK  ]
Arresto del logger del kernel: [  OK  ]
Arresto del logger di sistema: [  OK  ]
Arresto di hidd: [  OK  ]
Arresto di restorecond: [  OK  ]
Avvio di killall:  [  OK  ]
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Saving random seed:
Syncing hardware clock to system time
Turning off swap:
Turning off quotas:
Unmounting pipe file systems:
Unmounting file systems:
Halting system...
<6>md: stopping all md devices.
xenbus_dev_shutdown: device/vif/2 timeout closing device
System halted.
[root@gb-ldap ~]#  xm create PART_02
Using config file "/etc/xen/PART_02".
Going to boot Fedora Core (2.6.18-1.2798.fc6xen)
  kernel: /vmlinuz-2.6.18-1.2798.fc6xen
  initrd: /initrd-2.6.18-1.2798.fc6xen.img
Started domain PART_02
[root@gb-ldap ~]# xm console PART_02
rtc: IRQ 8 is not free.
rtc: IRQ 8 is not free.
i8042.c: No controller found.
Red Hat nash version 5.1.19 starting
  Reading all physical volumes.  This may take a while...
  Found volume group "VolGroup00" using metadata type lvm2
  2 logical volume(s) in volume group "VolGroup00" now active
                Welcome to Fedora Core
                Press 'I' to enter interactive startup.
Impostazione orologio  (utc): gio lug  5 14:38:41 CEST 2007 [  OK  ]
Avvio di udev: [  OK  ]
Impostazione dell'hostname test2:  [  OK  ]
Impostazione del Logical Volume Management:   2 logical volume(s) in volume
group 

"VolGroup00" now active
[  OK  ]
Controllo dei filesystem:
Controllo di tutti i filesystem.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00: clean, 106035/999936 files, 625529/999424 blocks
[/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/xvda1
/boot: clean, 35/26104 files, 14879/104388 blocks
[  OK  ]
Rimontaggio del filesystem root in modalitÃ?  lettura-scrittura:  [  OK  ]
Montaggio dei filesystem locali:  [  OK  ]
Abilitazione quota dei filesystem locali:  [  OK  ]
Abilitazione delle swap /etc/fstab:  [  OK  ]
INIT: Entering runlevel: 3
Inizio avvio non interattivo
Attivazione dell'interfaccia di loopback: [  OK  ]
Attivazione dell'interfaccia eth0:
Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: ------------[ cut here ]------------

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: kernel BUG at drivers/xen/core/evtchn.c:481!

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: invalid opcode: 0000 [#1]

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: SMP

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: CPU:    2

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: EIP is at retrigger+0x22/0x38

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: eax: 00000000   ebx: 02080000   ecx: f5416000   edx: 00000023

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: esi: c06d3e00   edi: 00000114   ebp: 00000000   esp: c0cc0e5c

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: ds: 007b   es: 007b   ss: 0069

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Process xenwatch (pid: 21, ti=c0cc0000 task=c0266620
task.ti=c0cc0000)

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Stack: c04426c9 c06d3e00 00000114 c06d3e28 c044240d 00000000
00000000 

c0d1a420

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:        000000f8 e0b29c00 e0b29c00 00000000 0000040c e0b29c00
ee22e8be 

00000000

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:        ee22ecd9 e0b29800 e0b29c00 c063e0a1 c054aad5 00000000
c063e145 

0000040c

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Call Trace:

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c04426c9>] check_irq_resend+0x41/0x48

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c044240d>] enable_irq+0x92/0xad

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<ee22e8be>] __netif_up+0xb/0x13 [netbk]

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<ee22ecd9>] netif_map+0x241/0x269 [netbk]

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<ee22e14f>] maybe_connect+0x2cc/0x49b [netbk]

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c054c3fa>] otherend_changed+0x74/0x79

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c054a94b>] xenwatch_handle_callback+0x12/0x44

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c054b414>] xenwatch_thread+0x108/0x11e

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c042df67>] kthread+0xc0/0xed

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  [<c0402a69>] kernel_thread_helper+0x5/0xb

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Leftover inexact backtrace:

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel:  =======================

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: Code: 75 96 5e 5f 5b 5e 5f 5d c3 8b 04 85 a0 1d 7f c0 8b 0d c4
a7 66 c0 

66 85 c0 74 20 0f b7 d0 0f a3 91 80 08 00 00 19 c0 85 c0 75 08 <0f> 0b e1 01 9b
d7 63 

c0 f0 0f ab 91 00 08 00 00 b8 01 00 00 00

Message from syslogd@gb-ldap at Thu Jul  5 14:39:22 2007 ...
gb-ldap kernel: EIP: [<c05462ca>] retrigger+0x22/0x38 SS:ESP 0069:c0cc0e5c
[  OK  ]
Attivazione dell'interfaccia eth1:


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>