Robert Craig
10/13/2008 2:02 PM
post14919
|
Just to confirm: The driver has been completely re-built within the new io-pkt source base?
Can you try running with lsm-pf-v4 and see if that makes any difference (or can things not operate at all without NAT?
)
Is it possible to set up secondary ethernet interface so that you can run a second instance of the stack and then run a
debug version of io-pkt so that you can see exactly where things are crashing?
Is dumper running? Can you get us a core dump in the case the stack dies?
We're dealing with four potential problems here:
1) The stack
2) The filter
3) The Ethernet driver
4) The Atheros driver
Have there been any customized changes to either the Ethernet driver or Atheros driver?
Robert
|
|
|
Andrew Boyd(deleted)
10/14/2008 12:26 PM
post14969
|
> io-pkt stack had been hang ... two types of errors.
> First, the state of io-pkt-v4-hc is MUTEX.
> the second is there is no list of io-pkt.
When io-pkt goes away, it probably has faulted.
Before you start io-pkt, run dumper to create a
core dump of io-pkt in /tmp.
When io-pkt locks up on a mutex, do a pidin to
get the pid of io-net (say 12345) then do this:
# dumper -p 12345
which will cause dumper to create a core file of
io-pkt, even though it didn't fault.
Now that you have a core dump, start io-pkt really
simply - without the wifi - just with a single ethernet
port, and ifconfig the port with an IP address, so
that you can ftp the core file produced by dumper
off the box, and send it to us.
--
aboyd
|
|
|