From: Markus Dahms <mad@automagically.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.6 on IP22 (Indy)
Date: Tue, 28 Jun 2005 19:04:25 +0200 [thread overview]
Message-ID: <20050628170425.GA5189@gaspode.automagically.de> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506281204190.13758@blysk.ds.pg.gda.pl>
Hello Maciej,
>> [R4600 tlbex.c patch]
>> This doesn't seem to be enough.
> Well, there can be something else. But to be sure I haven't missed
> anything in these TLB handlers, could you please generate the dumps I
> mentioned yesterday and send them to me? You need to uncomment the
> definition of DEBUG_TLB at the top of arch/mips/mm/tlbex.c for that.
I think I found the trick. Just following the hint that the R4600
is similar to the R5000 I added CPU_R4600 to build_tlb_probe_entry().
After that I got a prompt :-). Everything worked fine so far...
The next problem appeared on shutdown, where I got a kernel panic
(as the R4000 does with the 32-bit kernel, too) - something related
too the UART/serial console I suspect. As it's not on serial output
I need to find a way to get it without pencil and paper ;).
If you have further things to try, just send patches :)
Markus
next prev parent reply other threads:[~2005-06-28 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 10:07 2.6 on IP22 (Indy) Markus Dahms
2005-06-27 13:17 ` Maciej W. Rozycki
2005-06-27 14:18 ` Markus Dahms
2005-06-27 20:54 ` Maciej W. Rozycki
2005-06-28 6:21 ` Markus Dahms
2005-06-28 9:05 ` Maciej W. Rozycki
2005-06-28 10:20 ` Markus Dahms
2005-06-28 11:25 ` Maciej W. Rozycki
2005-06-28 17:04 ` Markus Dahms [this message]
2005-06-29 16:54 ` Maciej W. Rozycki
2005-07-19 18:21 ` Markus Dahms
2005-07-20 1:45 ` Thiemo Seufer
2005-06-28 12:23 ` Stephen P. Becker
2005-06-28 12:44 ` Maciej W. Rozycki
2005-06-28 13:03 ` Stephen P. Becker
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=20050628170425.GA5189@gaspode.automagically.de \
--to=mad@automagically.de \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.