On Sun, Jul 06, 2014 at 03:46:22PM +, Steve Wills wrote:
> I should have noted this system is running in bhyve. Also I'm told this panic
> may be related to the fact that the system is running in bhyve.
>
> Looking at it a little more closely:
>
> (kgdb) list *__mtx_lock_sleep+0xb1
> 0xff
On 7/6/2014 8:53 AM, Steve Wills wrote:
> Hi,
>
> Just experienced this tmpfs panic on r268160:
>
> Freed UMA keg (TMPFS node) was not empty (16 items). Lost 1 pages of memory.
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 12; apic id = 0c
> fault virtual address = 0x378
> f
On Sun, Jul 06, 2014 at 01:49:04PM -0700, Neel Natu wrote:
> Hi Steve,
>
> On Sun, Jul 6, 2014 at 8:46 AM, Steve Wills wrote:
> > I should have noted this system is running in bhyve. Also I'm told this
> > panic
> > may be related to the fact that the system is running in bhyve.
> >
> > Looking
On 7/6/14 11:12 AM, Konstantin Belousov wrote:
On Sun, Jul 06, 2014 at 05:25:12PM +, Steve Wills wrote:
On Sun, Jul 06, 2014 at 12:28:07PM -0400, Ryan Stone wrote:
On Sun, Jul 6, 2014 at 11:46 AM, Steve Wills wrote:
I should have noted this system is running in bhyve. Also I'm told this p
Hi Steve,
On Sun, Jul 6, 2014 at 8:46 AM, Steve Wills wrote:
> I should have noted this system is running in bhyve. Also I'm told this panic
> may be related to the fact that the system is running in bhyve.
>
> Looking at it a little more closely:
>
> (kgdb) list *__mtx_lock_sleep+0xb1
> 0xff
On Sun, Jul 06, 2014 at 05:25:12PM +, Steve Wills wrote:
> On Sun, Jul 06, 2014 at 12:28:07PM -0400, Ryan Stone wrote:
> > On Sun, Jul 6, 2014 at 11:46 AM, Steve Wills wrote:
> > > I should have noted this system is running in bhyve. Also I'm told this
> > > panic
> > > may be related to the
On Sun, Jul 06, 2014 at 12:28:07PM -0400, Ryan Stone wrote:
> On Sun, Jul 6, 2014 at 11:46 AM, Steve Wills wrote:
> > I should have noted this system is running in bhyve. Also I'm told this
> > panic
> > may be related to the fact that the system is running in bhyve.
> >
> > Looking at it a littl
On Sun, Jul 6, 2014 at 11:46 AM, Steve Wills wrote:
> I should have noted this system is running in bhyve. Also I'm told this panic
> may be related to the fact that the system is running in bhyve.
>
> Looking at it a little more closely:
>
> (kgdb) list *__mtx_lock_sleep+0xb1
> 0x809638d1
I should have noted this system is running in bhyve. Also I'm told this panic
may be related to the fact that the system is running in bhyve.
Looking at it a little more closely:
(kgdb) list *__mtx_lock_sleep+0xb1
0x809638d1 is in __mtx_lock_sleep (/usr/src/sys/kern/kern_mutex.c:431).
426
On 四, 2012-06-28 at 10:09 +0300, Gleb Kurtsou wrote:
> On (27/06/2012 13:29), Kevin Lo wrote:
> > Kevin Lo wrote:
> > > Konstantin Belousov wrote:
> > > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote:
> > > > > Konstantin Belousov wrote:
> > > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0
On (27/06/2012 13:29), Kevin Lo wrote:
> Kevin Lo wrote:
> > Konstantin Belousov wrote:
> > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote:
> > > > Konstantin Belousov wrote:
> > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote:
> > > > > > I've observed a panic in recent
Konstantin Belousov wrote:
> On Wed, Jun 27, 2012 at 01:29:14PM +0800, Kevin Lo wrote:
> > Kevin Lo wrote:
> > > Konstantin Belousov wrote:
> > > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote:
> > > > > Konstantin Belousov wrote:
> > > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Ke
On Wed, Jun 27, 2012 at 01:29:14PM +0800, Kevin Lo wrote:
> Kevin Lo wrote:
> > Konstantin Belousov wrote:
> > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote:
> > > > Konstantin Belousov wrote:
> > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote:
> > > > > > I've observed
Kevin Lo wrote:
> Konstantin Belousov wrote:
> > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote:
> > > Konstantin Belousov wrote:
> > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote:
> > > > > I've observed a panic in recent -current several times but I only
> > > > > have a
Konstantin Belousov wrote:
> On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote:
> > Konstantin Belousov wrote:
> > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote:
> > > > I've observed a panic in recent -current several times but I only
> > > > have a picture of the backtrace:
>
On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote:
> Konstantin Belousov wrote:
> > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote:
> > > I've observed a panic in recent -current several times but I only
> > > have a picture of the backtrace:
> > > http://people.freebsd.org/~kevlo/
Konstantin Belousov wrote:
> On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote:
> > I've observed a panic in recent -current several times but I only
> > have a picture of the backtrace:
> > http://people.freebsd.org/~kevlo/panic_tmpfs.jpg
> >
> > Does this look at all familiar to anyone?
>
Hello Kevin,
May you rebuild your kernel with some options that will make the dump of
the crash easier to send to people?
Try to follow these steps:
1) Configure KERNEL with the folowing options:
options KDB
options GDB
options DDB
2) Configure rc.conf:
dumpdev="/dev/ad0s1
On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote:
> I've observed a panic in recent -current several times but I only
> have a picture of the backtrace:
> http://people.freebsd.org/~kevlo/panic_tmpfs.jpg
>
> Does this look at all familiar to anyone?
Can you look up the line corresponding
19 matches
Mail list logo
