Messages in this thread |  | | Date | Wed, 28 Nov 2001 16:33:44 -0800 | From | Chris Wright <> | Subject | Re: [RFC] tree-based bootmem |
| |
* William Lee Irwin III (wli@holomorphy.com) wrote: > On Wed, Nov 28, 2001 at 01:04:11AM -0800, Chris Wright wrote: > > boot: 2.5.1-pre1-bootmem > > Uncompressing image... > > Loading initial ramdisk.... > > PROMLIB: obio_ranges 5 > > Fixup b f01e9720 doesn't refer to a SETHI at f0119e34[7fffc344] > > Program terminated > > Type help for more information > > <#0> ok > > > I'd be interested in finding out what this error means. Can anyone > comment on this?
i recompiled with DEBUG_BOOTMEM enabled, and it booted fine. that macro only turns on a couple printk's, so i suspect i messed up the first build. after rebuilding without DEBUG_BOOTMEM again, and booting sucessfully, i'd say it's working fine on this 32-bit SPARC20
here's the debug output, btw:
Available physical memory: vailable segment: [66347008,66424831] available segment: [2396160,2400255] available segment: [5623808,16777215] available segment: [17096704,66342911]
cheers, -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |