From: willy@thepuffingroup.com
To: Ulrich Strelow <ulrich_strelow@yahoo.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] State Of The Port [2000/02/13]
Date: Mon, 14 Feb 2000 15:06:14 -0500 [thread overview]
Message-ID: <20000214150614.M9944@thepuffingroup.com> (raw)
In-Reply-To: <20000214165620.28571.qmail@web502.mail.yahoo.com>; from Ulrich Strelow on Mon, Feb 14, 2000 at 08:56:20AM -0800
On Mon, Feb 14, 2000 at 08:56:20AM -0800, Ulrich Strelow wrote:
> Compiling and booting the latest (20000213) cvs
> version on my 715/33 is partly successful. It ends
> with the RAMDISK loaded message because after this the
> kernel is switching to a serial console which does not
> (yet) exist.
Yup, sounds right.
> It seems that CONFIG_GSC_PS2 is needed to include
> these routines (although the 715/33 does not have a
> GSC or PS2). But after defining CONFIG_GSC_PS2=y the
> kernel boot ends with the attempt to kill the init
> task. And the are two "kernel BUG" messages again,
> this time in block_dev.c:411!
The block_dev kernel BUG messages aren't really a problem. We get
them on every architecture; it's a `feature' of initrd not yet being
completely fixed. I agree the HIL driver needs some work. I've put it
on the joblist :-) [The joblist is about to be published in the website
update I'm putting together right this minute]
> So everything has improved compared to the state
> before the 2.3.42 merge, where even a defconfig-kernel
> ended with lots of kernel BUG messages on my 715/33.
Yay!
> I have attached the complete boot log of this test.
> Has anyone an idea what's going wrong?
>
> Also: the HIL-driver is still not working. If I
> include it I get lots of kernel BUG messages in
> pagetable_init.
>
> Ulrich
[...]
> No such device
> current = c2fe6000, mm = c2ec1040, mmap_sem = c2ec105c
> set_pte c2ec5068 02c1a605
> current = c2fe6000, mm = c2ec1040, mmap_sem = c2ec105c
> set_pte c2ebc038 0100e605
> Kernel panic: Attempted to kill init!
The `No such device' message makes me curious. What ramdisk.bin are
you using?
next prev parent reply other threads:[~2000-02-14 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-14 16:56 [parisc-linux] State Of The Port [2000/02/13] Ulrich Strelow
2000-02-14 20:06 ` willy [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-15 15:59 Ulrich Strelow
2000-02-13 21:22 willy
2000-02-13 23:35 ` Dominik Kubla
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=20000214150614.M9944@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=ulrich_strelow@yahoo.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