Re: Hang on -current
On 04/20/12 07:24, David Coppa wrote: On Thu, Apr 19, 2012 at 11:31 PM, STeve Andre' wrote: I had a system hang I've never seen before: Apr 19 15:24:18 s6 /bsd: uvm_km_kmem_grow: grown to 0xffc0 This is only a "diagnostic" informative message, btw... I've updated things and I haven't gotten the message, so thats good. It wasn't quite what I would call a diagnostic though, as it was continuously displayed with everything else frozen. But, it's gone now. --STeve Andre'
Re: Hang on -current
On Thu, Apr 19, 2012 at 11:31 PM, STeve Andre' wrote: > I had a system hang I've never seen before: > > Apr 19 15:24:18 s6 /bsd: uvm_km_kmem_grow: grown to 0xffc0 This is only a "diagnostic" informative message, btw...
Re: Hang on -current
On Thu, Apr 19, 2012 at 05:31:25PM -0400, STeve Andre' wrote: > I had a system hang I've never seen before: > > Apr 19 15:24:18 s6 /bsd: uvm_km_kmem_grow: grown to 0xffc0 > > It was in an infinite loop; I couldn't ssh into the machine nor could > I crtl-alt-F2 to another console, so I have no other info to go on. > This is a package builder, last compiled > > OpenBSD 5.1-current (GENERIC.MP) #0: Wed Apr 18 21:39:10 EDT 2012 > (i386) > > I didn't have a keyboard plugged in and because the kernel was spitting > out that one message it couldn't detect the keyboard(?). Any ideas on > further investigating this would be good--if this happens again. > > --STeve Andre' > Possibly the uvm work being done, which is currently backed out, so please try again with a newer tree/snap. Ken
Hang on -current
I had a system hang I've never seen before: Apr 19 15:24:18 s6 /bsd: uvm_km_kmem_grow: grown to 0xffc0 It was in an infinite loop; I couldn't ssh into the machine nor could I crtl-alt-F2 to another console, so I have no other info to go on. This is a package builder, last compiled OpenBSD 5.1-current (GENERIC.MP) #0: Wed Apr 18 21:39:10 EDT 2012 (i386) I didn't have a keyboard plugged in and because the kernel was spitting out that one message it couldn't detect the keyboard(?). Any ideas on further investigating this would be good--if this happens again. --STeve Andre'
