Steven Stallion wrote:
> Garrett D'Amore wrote:
>
>> That sounds suspiciously like a memory corruption.
>>
>
> It was; bug squashed.
>
> I'm running into a new issue with auto_nicdrv.
>
> All of the tests up to (and including) test08 are passing with flying
> colors, however after test08 cleans up, the test client becomes
> unresponsive at the console (the first time this happened, a console
> message complained about kbd being unloaded). I also cannot drop into kmdb.
>
> The peculiar bit, is that the interface is still responding to ping
> requests, however I am not able to shell in via rsh or ssh. This happens
> on both interfaces (21140-AF and 21143-PC), and is reproducible. The
> nicdrv logs indicate that cleanup is finished, and nothing else.
>
> Any ideas of what could cause this, or a better method of diagnosing the
> problem?
>
Have a look at the IP configuration, and make sure that nicdrv didn't
leave you with an unusable IP configuration. ifconfig -a and netstat
-rn are useful here.
Othr than that, I'd have to look more carefully.
You aren't relying on the dnet as your primary console access, are you?
-- Garrett
> Cheers,
>
> Steve
>
>
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
