> > There is no such thing as a "bad frame pointer crash". That's a > > diagnostic message from ddb that it can't find anything further up the > > stack trace, which is correct, since the function sched_sync is on top > > of the stack. > > > > Now, what the kernel tells you is that your kernel didn't panic, so > > I'm not entirely sure how you end up in ddb, since there is no panic > > or fault in the traceback. What does the traceback on other cpus show? > > "machine ddbcpu 0" will switch to cpu0, make a trace on each of them. > > > > //art > > Thanks, Art. > > I was advised to try a current snapshot so if the server crashes again with > the same problem I will be sure to get the traceback from the rest of the > cpus. >
> > > I filed a PR 6593 on Apr 26 on this. Right now it is running i386 > > > -current > > > from Apr 27, upgraded after I filed the PR. > > > ariane@ has integrated new vmmap into current, the devs might know if old version of it was in snapshots. So to remove ambiguity, you have to upgrade to current. The vmmap version in current is much stable than what it was a few weeks ago, having shaken out the crashing bugs. I don't have crashes in Firefox4. Just a FYI to those lurkers reluctant to upgrade. I did have a hang which I reported to him, it was a one-off.So many people reported the crashing problems in browsers. If more poeple upgrade their snapshots the devs might have better idea where any remaining showstopper bugs are. thanks
