PCI range checking under qemu-system-sparc64
Mark Cave-Ayland
mark.cave-ayland at ilande.co.uk
Wed Nov 18 00:20:41 UTC 2015
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.
More information about the freebsd-sparc64
mailing list