Date: Wed, 18 Jan 2012 10:50:12 GMT From: Peter Jeremy <peterjeremy@acm.org> To: freebsd-sparc64@FreeBSD.org Subject: Re: sparc64/164227: Can't boot 9.0-RELEASE/sparc64 on Blade 1500 Message-ID: <201201181050.q0IAoClv086271@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR sparc64/164227; it has been noted by GNATS.
From: Peter Jeremy <peterjeremy@acm.org>
To: "C. P. Ghost" <cpghost@cordula.ws>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: sparc64/164227: Can't boot 9.0-RELEASE/sparc64 on Blade 1500
Date: Wed, 18 Jan 2012 19:43:55 +1100
--cWoXeonUoKmBZSoM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2012-Jan-17 00:47:14 +0000, "C. P. Ghost" <cpghost@cordula.ws> wrote:
>Booting a FreeBSD-9.0-RELEASE kernel on a Blade 1500 panics with:
>
>panic: kmem_suballoc: bad status return of 3
>cpuid =3D 0
>KDB: stack backtrace:
> #0 0xc079841c at ??+0
> #1 0xc04ca59c at ??+0
> #2 0xc0487f90 at ??+0
> #3 0xc0098028 at ??+0
>
>This is on a Blade 1500 with 2 GB of RAM.
I can reproduce this on my SB1500 but only with 2GB RAM (4x512MB
DIMMs) installed. When I install 1GB RAM (4x256MB) or 4GB RAM
(4x1GB), FreeBSD-9.0-RELEASE-sparc64-disc1.iso boots successfully.
The problem is still present in 10-current:
ok boot freebsd
Boot device: /pci@1e,600000/ide@d/disk@1,0 File and args:=20
=20
>> FreeBSD/sparc64 boot block
Boot path: /pci@1e,600000/ide@d/disk@1,0:a
Boot loader: /boot/loader
Consoles: Open Firmware console
FreeBSD/sparc64 bootstrap loader, Revision 1.0
(root@sb1500.vk2pj.dyndns.org, Fri Jan 6 14:29:31 EST 2012)
bootpath=3D"/pci@1e,600000/ide@d/disk@1,0:a"
Loading /boot/defaults/loader.conf
/boot/kernel/kernel data=3D0x576f58+0x1fbea8 syms=3D[0x8+0x7db80+0x8+0x7298=
1]
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
jumping to kernel entry at 0xc0070000.
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-CURRENT #4 r229481M: Tue Jan 10 15:54:52 EST 2012
root@sb1500.vk2pj.dyndns.org:/usr/obj/usr/src/sys/sb1500 sparc64
WARNING: WITNESS option enabled, expect reduced performance.
panic: kmem_suballoc: bad status return of 3
KDB: stack backtrace:
(null)() at 0xc02a0330
(null)() at 0xc04526fc
(null)() at 0xc028a894
(null)() at 0xc024da70
(null)() at 0xc0070028
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at 0xc02d5dc0: ta %xcc, 1
db> bt
Tracing pid 0 tid 0 td 0xc0587890
(null)() at 0xc02a0374
(null)() at 0xc04526fc
(null)() at 0xc028a894
(null)() at 0xc024da70
(null)() at 0xc0070028
db>=20
Since DDB isn't seeing the symbols, I didn't go further but expanded
those addresses later via kgdb:
0x00000000c02a0330 <panic+336>: call 0xc02d6340 <kdb_backtrace>
0x00000000c02a0374 <panic+404>: call 0xc02d5d40 <kdb_enter>
0x00000000c04526fc <kmem_suballoc+124>: call 0xc02a01e0 <panic>
0x00000000c028a894 <kmeminit+756>: call 0xc0452680 <kmem_suballoc>
0x00000000c024da70 <mi_startup+464>: call %g1
0x00000000c0070028 <btext+40>: call 0xc024d8a0 <mi_startup>
Overall, this suggests that Marius is correct in his suspicion that
this is related to strangeness in the RAM layout.
--=20
Peter Jeremy
--cWoXeonUoKmBZSoM
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)
iEYEARECAAYFAk8WhksACgkQ/opHv/APuIcTGgCfQKe0Djq8IU4V9kb8pneJV26F
tfkAoJWeLUjZGaWVXu/KeRZ5ZnHMWFsF
=g7Py
-----END PGP SIGNATURE-----
--cWoXeonUoKmBZSoM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201181050.q0IAoClv086271>