From: Paul Bame <bame@debian.fc.hp.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Today's boot experience on a 735
Date: Tue, 16 Nov 1999 13:18:20 -0700 [thread overview]
Message-ID: <199911162018.NAA15083@debian.fc.hp.com> (raw)
In-Reply-To: Your message of "Tue, 16 Nov 1999 14:58:07 EST." <199911161958.OAA01327@hiauly1.hia.nrc.ca>
= This is a transcript of the boot messages on a 735 using the default
= CVS config:
=
= kernel(0x0000001), 0x04DFF870, 0x04DFF900, 0x00016A70)
= Clear BSS 0x00118470-->0x0012FA80
= Boot loader: HP-UX ISL
= Warning realmode_setup.c *guessing* where free mem starts!
= realmode_setup exiting.
=
= This is better than yesterday when there was no output. The BSS
= region looks ok. HP-UX ISL is correct. The address of _end in the
= vmlinux object looks reasonable:
=
= _end |0xc012fa80|extern|data |$DLT$
=
= Why does realmode_setup have to guess where free mem starts?
The _end symbol is not a reliable indicator of where
the kernel's memory ends. And the hpux
bootloader doesn't provide the SOM header from whence this could
theoretically be calculated. I haven't tried out the _end trick
posted last week, but it looks like it'll work (don't call the symbol
_end if you try it). As long as your kernel links, the guess is
probably OK for now.
-P
next prev parent reply other threads:[~1999-11-16 20:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-16 19:58 [parisc-linux] Today's boot experience on a 735 John David Anglin
1999-11-16 20:18 ` Paul Bame [this message]
1999-11-16 20:52 ` John David Anglin
1999-11-16 22:56 ` John David Anglin
1999-11-17 2:04 ` John David Anglin
1999-11-17 2:22 ` Jeffrey A Law
1999-11-17 2:48 ` John David Anglin
1999-11-17 3:35 ` Jeffrey A Law
1999-11-17 6:34 ` Philipp Rumpf
1999-11-17 18:12 ` John David Anglin
1999-11-17 20:54 ` Philipp Rumpf
1999-11-17 17:34 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
1999-11-20 0:57 Cary Coutant
1999-11-20 18:40 ` John David Anglin
1999-11-22 9:40 ` Philipp Rumpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199911162018.NAA15083@debian.fc.hp.com \
--to=bame@debian.fc.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox