From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti+fossil, the boot process, and 48-bit lba
Date: Wed, 22 Oct 2003 10:10:17 -0700 [thread overview]
Message-ID: <20031022171017.GZ834@cassie.foobarbaz.net> (raw)
In-Reply-To: <2fe61d2b01e01d7db540f3315d679848@caldo.demon.co.uk>
On Wed, Oct 22, 2003 at 04:57:55PM +0100, Charles Forsyth wrote:
>
> how does 9load cause that to happen?
> the thing that starts venti is a normal kernel, which
> should handle 48-bit LBA. does 9load (not knowing
> about them) leave the ATA in a state where the kernel
> can't use 48-bits either?
no idea. my conclusion was a semi-educated guess.
> i can see that 9load not knowing 48-bit addressing wouldn't
> be able to see boot/9fat partitions beyond a certain point,
> or perhaps with the right geometry.
something weird is going on. i originally had the venti conf
on one of the 167G drives, it would get to 'time...' in the
boot sequence, and then suicide with an invalid address. so
i moved the venti conf to one of the smaller discs, and then
it found the venti conf and barfed because it couldn't open
the arenas on the 167G discs. based on that, i am assuming
something is hating those large discs.
do you have any other ideas?
--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin
next prev parent reply other threads:[~2003-10-22 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 15:43 Christopher Nielsen
2003-10-22 15:57 ` Charles Forsyth
2003-10-22 17:10 ` Christopher Nielsen [this message]
2003-10-22 17:29 ` Christopher Nielsen
2003-10-22 17:58 ` Charles Forsyth
2003-10-22 18:06 ` Russ Cox
2003-10-22 20:07 ` vdharani
2003-10-22 19:59 ` Christopher Nielsen
2003-10-23 2:16 ` Christopher Nielsen
2003-10-24 4:32 ` [9fans] trouble down t'labs George Michaelson
2003-10-27 7:48 ` [9fans] venti+fossil, the boot process, and 48-bit lba Christopher Nielsen
2003-10-22 16:08 ` ron minnich
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=20031022171017.GZ834@cassie.foobarbaz.net \
--to=cnielsen@pobox.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).