This is what a BREAK on a serial console looks like.
On 2011-10-17, Leon Me?ner <l.mess...@physik.tu-berlin.de> wrote: > On Mon, Oct 17, 2011 at 07:02:07PM +0200, Leon Me_ner wrote: >> On Mon, Oct 17, 2011 at 09:37:37AM -0700, Bryan Irvine wrote: >> > On Mon, Oct 17, 2011 at 8:20 AM, Chris Cappuccio <ch...@nmedia.net> wrote: >> > > Time to upgrade to 5.0. Report any failures after you do that. >> > >> > I think he's saying it's been doing this since 4.6. I parsed that as >> > him being on at least the current release. >> > >> > Leon, can you send a dmesg? >> >> >> The machine is just beeing updated to a 5.0 snapshot. I had this dmesg >> still in my scrollback buffer which i took when i was doing the trace >> and ps. >> Sorry for the truncated lines. > ><snipped the dmesg> > > Upgrading to 5.0 changed nothing. After dhcping and invoking ssh the > machine froze. Trace of this freeze is below. Actually i forgot to > mention that sometimes the machine manages to unfreeze again after some > minutes. > > ddb{0}> trace > Debugger() at Debugger+0x5 > comintr() at comintr+0x268 > Xintr_ioapic_edge4() at Xintr_ioapic_edge4+0xe8 > --- interrupt --- > Bad frame pointer: 0xffff8000213dfcf0 > end trace frame: 0xffff8000213dfcf0, count: -3 > ip_output+0x5ee: