Yalung / netmap

Automatically exported from code.google.com/p/netmap
0 stars 0 forks source link

FreeBSD kernel panic #10

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install FreeBSD 10/amd 64
2. Compile latest netmap module
3. Start bridge example: ./bridge -v -i netmap:igb0 -i netmap:igb1
4. pull out cables from igb0 & igb1, wait 5 seconds and insert cables back
5. repeat stet 4 for 3-4 times
6. try sshing to a FreeBSD box
7. get a kernel panic message 

What is the expected output? What do you see instead?
Kernel panic message

What version of the product are you using? On what operating system?
FreeBSD 10/amd64, latest netmap module gited from 
https://code.google.com/p/netmap

Please provide any additional information below.
Linux netmap on the same box works fine in this situation.

Original issue reported on code.google.com by sergey.s...@gmail.com on 24 Jun 2014 at 3:19

GoogleCodeExporter commented 9 years ago
Dear Sergey,
I tried to reproduce the panic but I failed.

I used FreeBSD 10-STABLE and the latest netmap module from 
https://code.google.com/p/netmap branch master.

Can you send us the kernel panic message?

In step 6, you try to connect from A to C via ssh, right?

A-------B--------C
B runs bridge between the two interfaces (igb0 and igb1).

Cheers,
Stefano

Original comment by stefanog...@gmail.com on 15 Jul 2014 at 12:11

GoogleCodeExporter commented 9 years ago
Hello,

You need to ssh from D to B. I think any network activity will kill B. I
will send you panic report later today.

2014-07-15 15:11 GMT+03:00 <netmap@googlecode.com>:

Original comment by sergey.s...@gmail.com on 15 Jul 2014 at 2:24

GoogleCodeExporter commented 9 years ago
Hi,
I tried to ssh from D to B (re interface) after disconnecting/reconnecting the 
cables from igb0/1 more times, but I didn't have the panic.

Stefano

Original comment by stefanog...@gmail.com on 16 Jul 2014 at 12:26

GoogleCodeExporter commented 9 years ago
I have the same 

Crash logs 
# tail /var/crash/info.last                                                     

                                                                              |
  Blocksize: 512
  Dumptime: Wed Apr 22 09:42:53 2015
  Hostname: 
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 10.1-RELEASE-p9 #0: Tue Apr  7 01:09:46 UTC 2015
    root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
  Panic String: in generic_xmit_frame
  Dump Parity: 2520819054
  Bounds: 9
  Dump Status: good

# tail /var/crash/core.txt.9                                                    

                                                                              |
device  virtio_scsi
device  virtio_balloon
device  hyperv
device  xenpci
device  vmx

------------------------------------------------------------------------
ddb capture buffer

ddb: ddb_capture: kvm_nlist

# tail -f /var/crash/vmcore.9                                                   

                                                                              |
#1 0xffffffff80928125 at panic+0x155
#2 0xffffffff81c310c4 at generic_xmit_frame+0x194
#3 0xffffffff81c2be9f at generic_netmap_txsync+0x2ef
#4 0xffffffff81c274b2 at netmap_poll+0x3d2
#5 0xffffffff80817e2a at devfs_poll_f+0x6a
#6 0xffffffff8097bead at sys_poll+0x30d
#7 0xffffffff80d25891 at amd64_syscall+0x351
#8 0xffffffff80d0aaab at Xfast_syscall+0xfb

Original comment by ja.sem.d...@gmail.com on 22 Apr 2015 at 7:07

GoogleCodeExporter commented 9 years ago
Hello,
Is there any progress with solving this issue. 

FreeBSD  10.1-RELEASE-p9
netmap src from https://code.google.com/p/netmap branch master
var/crash log 

#1 0xffffffff80928125 at panic+0x155
#2 0xffffffff81c310c4 at generic_xmit_frame+0x194
#3 0xffffffff81c2be9f at generic_netmap_txsync+0x2ef
#4 0xffffffff81c274b2 at netmap_poll+0x3d2
#5 0xffffffff80817e2a at devfs_poll_f+0x6a
#6 0xffffffff8097bead at sys_poll+0x30d
#7 0xffffffff80d25891 at amd64_syscall+0x351
#8 0xffffffff80d0aaab at Xfast_syscall+0xfb

Original comment by ipmifire...@gmail.com on 22 Apr 2015 at 8:15

GoogleCodeExporter commented 9 years ago
In my previous post i forgot mentioned that this issue occure when one of 
bridge interfaces status is no carrier for example when the machine after 
bridge is power off.

-- 
Sincerely 
Joseph

Original comment by ipmifire...@gmail.com on 22 Apr 2015 at 8:25