From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] Strange boot behaviour
Date: Thu, 12 Feb 2004 15:48:47 +0200 [thread overview]
Message-ID: <20040212154846.E4743@cackle.proxima.alt.za> (raw)
Given:
sd53c8xx: SYM53C1010 rev. 0x01 intr=5 command=2300007
sd53c8xx: SYM53C1010 rev. 0x01 intr=10 command=2300007
sd53c8xx: bios scntl3(70) stest2(00)
sd53c8xx: bios scntl3(70) stest2(00)
ether#0: elnk3: port 0x300 irq 11: 00A0244026C9
Unknown boot device: sd00!9fat!9pcf
Boot devices: fd0 ether0
boot from: ether0!/386/9pcf.gz
tickle (192.96.32.69!67): /386/9pcf.gz
gz...874346 => 867828+1146820+108996=2123644
entry: 80100020
Plan 9
apicbase 0xFEE00100
cpu0: 501MHz GenuineIntel Celeron (cpuid: AX 0x0665 DX 0x183F9FF)
ELCR: 1420
#l0: elnk3: 10Mbps port 0x300 irq 11: 00A0244026C9
sd53c8xx: SYM53C1010 rev. 0x01 intr=5 command=2300007
sd53c8xx: SYM53C1010 rev. 0x01 intr=10 command=2300007
#U/usb0: uhci: port 0xE400 irq 10
19287 free pages, 77148K bytes, 309148K swap
root is from (tcp, il, local)[local!#S/sd00/fossil]:
user[none]: glenda
sd53c8xx: bios scntl3(00) stest2(00)
boot: can't connect to file server: '#S/sd00/fossil' does not exist
panic: boot process died: unknown
pdumpstack
anic: boot process died: unknown
ktrace /kernel/path 801serialoq 1758 printed 1770
06978 8000a63c
estackx 8000a8f0
8000a5dc=801067ab 8000a5e4=801ae986 8000a610=8013a6ca 8000a624=80106978
8000a638=80106978 8000a63c=801067af 8000a644=8013a94c 8000a690=801c8960
8000a694=801c89c9 8000a6a4=801c8d4d 8000a6ac=801c8c17 8000a6b8=801c8960
8000a6c4=801c99b1 8000a6d4=801c8b92 8000a6fc=801ca19a 8000a708=8019f282
8000a710=8019f282 8000a718=801b760a 8000a724=801ca50c 8000a730=801aee18
8000a738=801aee64 8000a73c=8019f557 8000a74c=801a9000 8000a758=801a1a79
8000a76c=801abc67 8000a790=801c8b92 8000a7b8=801ca19a 8000a7c8=801b66ca
8000a7d4=801b760a 8000a7d8=801b6ff2 8000a7e8=801b7136 8000a7f4=801b760a
8000a7f8=80307950 8000a7fc=8023431c 8000a800=801c7357 8000a804=8000a820
8000a808=24cdc88c 8000a80c=00000002 8000a810=00001605 8000a814=00000000
8000a818=80300d58 8000a81c=00000000 8000a820=24cdde91 8000a824=00000002
8000a828=805ee480 8000a82c=801b20e9 8000a830=8010603b 8000a834=802ec71c
8000a838=7fffefe8 8000a83c=801c6529 8000a840=00000007 8000a844=00001605
8000a848=00000000 8000a84c=805ee480 8000a850=00001605 8000a854=00000000
8000a858=00000000 8000a85c=7fffefc8 8000a860=802ea978 8000a864=00000000
8000a868=80106d88 8000a86c=80307274 8000a870=00000023 8000a874=00000200
8000a878=7fffefcc 8000a87c=0000001b 8000a880=801027ff 8000a884=00000008
8000a888=8019eead 8000a88c=00000000 8000a890=ffffffff 8000a894=7fffed5c
8000a898=00000000 8000a89c=80100a1e 8000a8a0=8000a8a4 8000a8a4=7fffed5c
8000a8a8=00000000 8000a8ac=00000000 8000a8b0=8000a8c4 8000a8b4=00000000
8000a8b8=ffffffff 8000a8bc=00000001 8000a8c0=00000008 8000a8c4=0000001b
8000a8c8=0000001b 8000a8cc=0000001b 8000a8d0=0000001b 8000a8d4=00000040
8000a8d8=80100569 8000a8dc=00006d96 8000a8e0=00000023 8000a8e4=00000286
8000a8e8=7fffed5c 8000a8ec=0000001b
cpu0: exiting
There are a few questions.
1. Why does 9load not pick up #S/sd00 as a valid boot location? It
only offers fd0 and ether0 as options. Is the missing #S/
significant? If so, then the installation is faulty.
2. Why does the fossil kernel 9pcf.gz not find #S/sd00/fossil? It
was created by the installation procedure and 9pcdisk.gz is aware of
it. Hm, a missing "disk"?
Note that I have added the PCI IDs for the SCSI controller card to
sd53c8xx.c and this was OK for the installation process.
Lastly, 9loaddebug differs from 9load only in the absence of a -H3
load option and two hash out commands. It doesn't work, either,
unless the -H3 is entered, in which case it is not different from
9load. Is it worth keeping?
Suggestions on what I must do to get over this hurdle? I will try
fossil loaded manually over 9pcdisk.gz, but I'm not sure what I'll
learn from there.
++L
next reply other threads:[~2004-02-12 13:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 13:48 Lucio De Re [this message]
2004-02-12 14:35 ` David Presotto
2004-02-12 16:16 ` [9fans] seeking for the truth rog
2004-02-12 16:32 ` David Presotto
2004-02-12 17:10 ` rog
2004-02-12 16:50 ` Dave Lukes
2004-02-12 16:59 ` Rob Pike
2004-02-12 17:03 ` Fco.J.Ballesteros
2004-02-12 17:17 ` Charles Forsyth
2004-02-12 17:22 ` Charles Forsyth
2004-02-12 18:00 ` rob pike, esq.
2004-02-12 18:05 ` Charles Forsyth
2004-02-12 18:10 ` rog
2004-02-12 18:10 ` David Presotto
2004-02-12 17:26 ` Fco.J.Ballesteros
2004-02-12 17:35 ` Dave Lukes
2004-02-12 20:19 ` boyd, rounin
2004-02-13 6:15 ` [9fans] Strange boot behaviour Lucio De Re
2004-02-13 12:58 ` Lucio De Re
2004-02-14 21:49 ` David Presotto
2004-02-16 5:52 ` Lucio De Re
2004-02-16 6:39 ` Lucio De Re
2004-02-16 9:22 ` Lucio De Re
2004-02-17 15:20 ` Lucio De Re
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=20040212154846.E4743@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).