From: Liam Davies <ldavies@agile.tv>
To: linux-mips@oss.sgi.com
Subject: Troubles with TLB refills
Date: Mon, 05 Mar 2001 13:40:01 +1000 [thread overview]
Message-ID: <3AA30A91.B5842678@agile.tv> (raw)
I am trying to get the 2.4 kernel up and running on the Cobalt boxes.
At the moment I am trying to get the initial transition from kernel
to user mode working.
The elf loader is trying to put stuff in the stack for the new user
process and *each* call to NEW_AUX_ENTRY is generating a page fault
that cannot be resolved. The address generated by the BadVAddr on the
TLBS exception is not correct. Also, I never receive a TLBrefill
exception on the accesses. It is using the except_vec0_nevada handler.
All that I can think of is that the handler at 0x80000000 is getting
smashed after it is copied in -- ala troubles with _kd_mksound last
year.
Any ideas on what is happening?? how to fix it??
Thanks
Liam
elf_entry=4000b0
elf_bss=10010130
elf_brk=10010130
start_code=400000
end_code =400130
start_data=10010130
end_data =10010130
[sh:1:10004f4c:1:8005f504]
Dump TLB all:
Dump TLB wired:
Wired: 0
Dump TLB address 10004f4c :
No entry for address 0x10004f4c in TLB
vma: start=10010000
vma: flags= 1873
Bad_Area:
no_context:
next reply other threads:[~2001-03-05 3:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 3:40 Liam Davies [this message]
2001-03-05 10:49 ` Troubles with TLB refills Ralf Baechle
2001-03-06 3:10 ` Liam Davies
2001-03-06 12:58 ` Ralf Baechle
2001-03-07 3:36 ` Problem makeing an O2 run bootp nick
2001-03-07 3:36 ` nick
2001-03-07 19:11 ` Rafal Boni
2001-03-07 19:14 ` nick
2001-03-08 7:57 ` Chris Ruvolo
2001-03-10 18:25 ` Ralf Baechle
2001-03-12 1:09 ` IP32 (O2) diff nick
2001-03-06 6:45 ` Troubles with TLB refills Liam Davies
2001-03-06 6:45 ` Liam Davies
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=3AA30A91.B5842678@agile.tv \
--to=ldavies@agile.tv \
--cc=ldavies@oz.agile.tv \
--cc=linux-mips@oss.sgi.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