From: "Roel Teuwen" <Roel.Teuwen@advalvas.be>
To: <parisc-linux@thepuffingroup.com>
Subject: Re: [parisc-linux] 32-bit xc-20001206.tar.gz is foobar
Date: Sun, 10 Dec 2000 16:38:10 +0100 [thread overview]
Message-ID: <005f01c062bf$3517ed50$0300000a@terra> (raw)
In-Reply-To: Pine.LNX.4.21.0012102347330.31734-100000@front.linuxcare.com.au
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
Hello,
I am seeing the same error messages with the version fresh form CVS, the
build completes. The problem appeared a week or 2 ago.
The kernel is unable to boot, though, it dies with BUG() at bootmem.c:219
Regards,
Roel
[-- Attachment #2: log.gz --]
[-- Type: application/x-gzip, Size: 53033 bytes --]
next prev parent reply other threads:[~2000-12-10 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-10 5:23 [parisc-linux] 32-bit xc-20001206.tar.gz is foobar Grant Grundler
2000-12-10 13:02 ` Alan Modra
2000-12-10 15:38 ` Roel Teuwen [this message]
2000-12-12 0:06 ` [parisc-linux] gcc wchar patch for hppa64 John David Anglin
2000-12-12 1:43 ` Alan Modra
2000-12-12 8:28 ` [parisc-linux] 32-bit xc-20001206.tar.gz is foobar Matt Taggart
2000-12-12 8:37 ` Alan Modra
2000-12-12 8:44 ` Matt Taggart
2000-12-12 9:01 ` Alan Modra
2000-12-12 10:53 ` Alan Modra
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='005f01c062bf$3517ed50$0300000a@terra' \
--to=roel.teuwen@advalvas.be \
--cc=parisc-linux@thepuffingroup.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