Matthias Drochner wrote:
j+nbsd%2008.salmi.ch@localhost said:db{0}> config_deactivate(5,1,3222dca4,0,c04c11a0,1,cc22dc7c,c02eb601,c2 068f00,5) at netbsd:config_deactivate+0x14 config_deactivate(c2068f00,5,0,0,cc22dc8c,cc22dca4,0,c1b17500,1,4) at netbsd:config_deactivate+0x49 config_detach(c2068f00,1,c1a66c1c,c038959c,cacc7be0,c1a631b0,c1a66c1c,10,c1a631b0,c1b17500) at netbsd:config_detach+0xa1I don't see problems with umass devices like a memory stick. Also the stacktrace doesn't make much sense because config_deactivate() can't recurse into itself. So I'd suspect some memory corruption, a guess would be in the umodem code because this is something I can't test.
FYI, I've had a bunch of crashes recently when connecting/disconnecting USB devices as well (none of them umodems, only umass) but I never did get a stack trace as I always had X running at the time.
Cheers, Jared