From: "Stephen P. Becker" <geoman@gentoo.org>
To: Markus Dahms <mad@automagically.de>
Cc: linux-mips@linux-mips.org
Subject: Re: 2.6 on IP22 (Indy)
Date: Tue, 28 Jun 2005 08:23:45 -0400 [thread overview]
Message-ID: <42C14151.5050209@gentoo.org> (raw)
In-Reply-To: <20050628102013.GA10442@gaspode.automagically.de>
> [R4600 tlbex.c patch]
>
> This doesn't seem to be enough. The patch applies almost cleanly on
> current CVS (offset -1 line), but the resulting kernel (I tried 64
> and 32-bit) still stops after "INIT: ...".
>
This might be a good time to mention that cvs HEAD seems to have serious
problems with 64-bit ip22 kernels (at least on r5000 systems...I don't
have a working r4x00 box to test with), and it may be contributing to
your problems. Basically, numerous messages about vmalloc dump to the
kernel log while doing a number of things disk related:
allocation failed: out of vmalloc space - use vmalloc=<size> to increase
size.
Symptons include ricerfs partitions not being able to mount (ext3 seems
to work, but still triggers the vmalloc error message), swapon failing
to turn the swap partition on, dd having major problems when dumping
large blocks, etc. The initial probing of the scsi controller at boot
time also triggers the message.
I haven't tried a 32-bit kernel since 2.6.12_rc2 or so, however when I
did, everything seemed to work just fine, while a 64-bit kernel compiled
from the same checkout had the same problems I mention above. At one
point I was trying to work out when this was introduced, and I *think*
it was the initial 2.6.11 merge, but I would have to double check that.
I've been running a 64-bit 2.6.10 checkout since the beginning of the
year on that box, and the machine has been very stable.
-Steve
next prev parent reply other threads:[~2005-06-28 12:25 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
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 [this message]
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=42C14151.5050209@gentoo.org \
--to=geoman@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=mad@automagically.de \
/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