http://defect.opensolaris.org/bz/show_bug.cgi?id=8370

           Summary: nwamd SEGV and restarting frequently
    Classification: Development
           Product: nwam
           Version: unspecified
          Platform: ANY/Generic
        OS/Version: All
            Status: NEW
 Status Whiteboard: nwam1-build:2009-04-20
          Severity: blocker
          Priority: P1
         Component: ON daemon
        AssignedTo: nwam-dev at opensolaris.org
        ReportedBy: dkenny at opensolaris.org
         QAContact: nwam-dev at opensolaris.org


I've noticed that nwamd is restarting very frequently.

Unfortunately, it's not generating a core file (guess this is because netadm
doesn't have permissions in /).

I ran a script I've modified from the DTraceToolkit which uses dtrace to
capture information about processes that crash, and it generated the 
information at the end of the description. 

It would appear to be in the wlan scan code - which I wouldn't have expected
since I have a cable plugged in and the wired driver is prio 0 and the wireless
prio 1 - but that doesn't mean there isn't still an issue...


-----------------------------------------------------
CRASH DETECTED at 2009 Apr 23 10:49:12
-----------------------------------------------------
Type:    SIGSEGV
Program: nwamd
Args:    /lib/inet/nwamd0
PID:     126596
TID:     14
LWPs:    12
PPID:    1
UID:     16
GID:     65
TaskID:  1667
ProjID:  3
PoolID:  0
ZoneID:  0
zone:    global
CWD:     /
errno:   0

User Stack Backtrace,
libc.so.1`strlen+0x30
libc.so.1`vsnprintf+0x65
nwamd`log_format+0x4c
nwamd`nlog+0x19
nwamd`wlan_scan_thread+0x198
libc.so.1`_thrp_setup+0x7e
libc.so.1`_lwp_start

Kernel Stack Backtrace,
genunix`sigaddqa+0x75
genunix`trapsig+0x12b
unix`trap+0x150b
unix`0xfffffffffb8002c0

Ansestors,
126596 /lib/inet/nwamd0
1 /sbin/init0
0 sched0

Times,
User:    1 ticks
Sys:     3 ticks
Elapsed: 5835 ms

Sizes,
Heap:   536560 bytes

-- 
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Reply via email to