Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Nov 2015 00:20:07 +0000
From:      Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To:        Adrian Chadd <adrian.chadd@gmail.com>
Cc:        Marius Strobl <marius@alchemy.franken.de>,  Alexey Dokuchaev <danfe@freebsd.org>, "freebsd-sparc64@freebsd.org" <freebsd-sparc64@freebsd.org>
Subject:   Re: PCI range checking under qemu-system-sparc64
Message-ID:  <564BC437.4020909@ilande.co.uk>
In-Reply-To: <CAJ-Vmom_8GiZtrz38w_GRUw5nZNEcs1M1yTDnU-r=%2BEafoPCew@mail.gmail.com>
References:  <20150913180126.GC7862@alchemy.franken.de>	<55F89861.1030107@ilande.co.uk>	<20150916031030.GA6711@FreeBSD.org>	<55F9C2B8.7030605@ilande.co.uk>	<20150916211914.GD18789@alchemy.franken.de>	<20150917082817.GA71811@FreeBSD.org>	<55FBB662.4080708@ilande.co.uk>	<20150919211420.GK18789@alchemy.franken.de>	<55FDEA3C.1010804@ilande.co.uk>	<20150920043630.GA36162@FreeBSD.org>	<20150922221404.GA81100@alchemy.franken.de>	<563F8722.9050503@ilande.co.uk>	<56462A41.4030707@ilande.co.uk>	<CAJ-Vmo=eaDCp4CoDJQu50PPSr6F3XSa0nLLj8460YhifzTEn6g@mail.gmail.com>	<564B94A9.70003@ilande.co.uk> <CAJ-Vmom_8GiZtrz38w_GRUw5nZNEcs1M1yTDnU-r=%2BEafoPCew@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 17/11/15 23:12, Adrian Chadd wrote:

> cool, thanks!
> 
> can you do "show registers" and "bt" there? Do we know what's going on?

WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from cd9660:/dev/iso9660/TEST [ro]...
[ thread pid 1 tid 100002 ]
Stopped at      tl1_trap+0x24:  stx             %o0, [%sp + 0x997]
db> show registers
g0          0xfffff800015e84d0
g1                  0xc0c8ab38
g2                  0xc0c8a800
g3                         0x1
g4          0xfffff800015efb80
g5                    0x2d7400
g6                  0xc3a6d980
g7                  0xc0f791d0  pcpu0+0x1800
i0                        0x11  pcpup+0xa
i1                         0x1
i2                           0
i3                           0
i4                           0
i5                           0
i6                           0
i7                    0x101264
tnpc                0xc00b0fe8  tl1_trap+0x28
tpc                 0xc00b0fe4  tl1_trap+0x24
tstate            0x9958001507
tl1_trap+0x24:  stx             %o0, [%sp + 0x997]
db> bt
Tracing pid 1 tid 100002 td 0xfffff800015e84d0
KDB: reentering
KDB: stack backtrace:
kdb_reenter() at kdb_reenter+0x5c
trap() at trap+0x2fc
-- kernel stack fault %o7=0xc05743e0 --
sched_clock() at sched_clock+0x94
KDB: reentering
KDB: stack backtrace:
kdb_reenter() at kdb_reenter+0x5c
trap() at trap+0x2fc
-- kernel stack fault %o7=0xc011a050 --
db_read_bytes() at db_read_bytes+0x44
KDB: reentering
KDB: stack backtrace:
kdb_reenter() at kdb_reenter+0x5c
trap() at trap+0x2fc
-- kernel stack fault %o7=0xc011a050 --
db_read_bytes() at db_read_bytes+0x44
KDB: reentering
KDB: stack backtrace:
kdb_reenter() at kdb_reenter+0x5c
trap() at trap+0x2fc
-- kernel stack fault %o7=0xc011a050 --
db_read_bytes() at db_read_bytes+0x44
KDB: reentering
KDB: stack backtrace:
kdb_reenter() at kdb_reenter+0x5c
trap() at trap+0x2fc
-- kernel stack fault %o7=0xc011a050 --
panic: longjmp botch
cpuid = -1012475520
KDB: stack backtrace:
Uptime: 22s
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot,
--> or switch off the system now.


Definitely looks like the stack is corrupted here.


ATB,

Mark.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?564BC437.4020909>