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

           Summary: After failed WLAN connect, nwam didn't notice me
                    plugging in wired cable
    Classification: Development
           Product: nwam
           Version: unspecified
          Platform: ANY/Generic
        OS/Version: All
            Status: NEW
 Status Whiteboard: nwam1-build:2009-05-20
          Severity: minor
          Priority: P4
         Component: ON daemon
        AssignedTo: nwam-dev at opensolaris.org
        ReportedBy: dkenny at opensolaris.org
         QAContact: nwam-dev at opensolaris.org


Created an attachment (id=1999)
 --> (http://defect.opensolaris.org/bz/attachment.cgi?id=1999)
NWAM Debug messages

After the unsuccessful WLAN attempts, I tried to go back to using the wired
network.

Unfortunately, despite an event being sent at the dlpi level (as in the log)
that the cable had been connected to the e1000g0 device, nothing seemed to
happen and nwamd continued to do scans and try connecting on the WLAN.

In nwamadm interact, I didn't see any event that said I had connected a cable,
or any other event to do with e1000g0 either. 

A refresh of nwam didn't seem to achieve anything either, so I had to resort to
disabling nwam (which took about 30 seconds to shutdown) and then re-enabling
it. After re-enabling it it all started to work fine again.

During the shutdown, I though that nwamd could be in a dead-lock situation, but
it did shutdown eventually. While waiting I did several pstack requests which I
will also attach, but I failed to grab a core since the process was gone when I
tried.

I'm attaching a log, and the relevant point where I inserted the cable starts
at:

May 21 09:47:50 starbug-r600 mac: [ID 435574 kern.info] NOTICE: e1000g0 link
up, 1000 Mbps, full duplex
May 21 09:47:50 starbug-r600 nwamd[663]: [ID 505737 daemon.debug] 10:
dlpi_notify: created event for e1000g0
...

-- 
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