From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm5 dies booting, possibly network related
Date: Tue, 20 Jan 2004 11:51:43 +0100 [thread overview]
Message-ID: <400D083F.6080907@aitel.hist.no> (raw)
In-Reply-To: <20040120000535.7fb8e683.akpm@osdl.org>
2.6.1-mm5 didn't get very far, only about a page of bootup messages.
The last two were:
NET registered protocol family 1
NET registered protocol family 10
And then nothing. I tried twice - sysrq+B worked the first
time, not the second. There were no oops or other messages.
I used the new mregparm=3 option - it works for 2.6.1-mm4
Helge Hafting
WARNING: multiple messages have this Message-ID (diff)
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm5 dies booting, possibly network related
Date: Tue, 20 Jan 2004 11:51:43 +0100 [thread overview]
Message-ID: <400D083F.6080907@aitel.hist.no> (raw)
In-Reply-To: <20040120000535.7fb8e683.akpm@osdl.org>
2.6.1-mm5 didn't get very far, only about a page of bootup messages.
The last two were:
NET registered protocol family 1
NET registered protocol family 10
And then nothing. I tried twice - sysrq+B worked the first
time, not the second. There were no oops or other messages.
I used the new mregparm=3 option - it works for 2.6.1-mm4
Helge Hafting
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-20 10:39 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 8:05 2.6.1-mm5 Andrew Morton
2004-01-20 8:05 ` 2.6.1-mm5 Andrew Morton
2004-01-20 10:51 ` Helge Hafting [this message]
2004-01-20 10:51 ` 2.6.1-mm5 dies booting, possibly network related Helge Hafting
[not found] ` <20040120175408.GA12805@lsc.hu>
2004-01-20 18:23 ` Andrew Morton
2004-01-20 18:53 ` Valdis.Kletnieks
2004-01-20 20:52 ` GCS
2004-01-20 22:12 ` Helge Hafting
2004-01-21 9:35 ` 2.6.1-mm5 dies booting, possibly ipv6 related Helge Hafting
2004-01-21 9:29 ` Andrew Morton
2004-01-21 13:25 ` Helge Hafting
2004-01-21 14:28 ` GCS
2004-01-21 15:43 ` GCS
2004-01-20 11:14 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 11:14 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 16:37 ` 2.6.1-mm5 Andrew Morton
2004-01-20 16:37 ` 2.6.1-mm5 Andrew Morton
2004-01-20 11:35 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 11:35 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 13:20 ` [patch] 2.6.1-mm5: compile error with IDE legacy driver Adrian Bunk
2004-01-20 15:37 ` Bartlomiej Zolnierkiewicz
2004-01-20 13:45 ` [PATCH] missing space in printk message (was Re: 2.6.1-mm5) Sean Neakums
2004-01-20 13:45 ` Sean Neakums
2004-01-20 13:54 ` Vojtech Pavlik
2004-01-20 13:54 ` Vojtech Pavlik
2004-01-20 14:09 ` Sean Neakums
2004-01-20 14:09 ` Sean Neakums
2004-01-20 16:03 ` 2.6.1-mm5 [Compile error] Tim Cambrant
2004-01-20 16:08 ` 2.6.1-mm5 (compile stats) John Cherry
2004-01-20 16:08 ` John Cherry
2004-01-20 21:57 ` Adrian Bunk
2004-01-20 21:57 ` Adrian Bunk
2004-01-20 22:15 ` John Cherry
2004-01-20 22:15 ` John Cherry
2004-01-20 22:27 ` Adrian Bunk
2004-01-20 22:27 ` Adrian Bunk
2004-01-20 22:50 ` John Cherry
2004-01-20 22:50 ` John Cherry
2004-01-20 18:30 ` 2.6.1-mm5 Mike Fedyk
2004-01-20 18:30 ` 2.6.1-mm5 Mike Fedyk
2004-01-20 18:36 ` 2.6.1-mm5 Andrew Morton
2004-01-20 18:36 ` 2.6.1-mm5 Andrew Morton
2004-01-21 0:10 ` I2C sensors error (Re: 2.6.1-mm5) Zack Winkles
2004-01-21 0:10 ` Zack Winkles
2004-01-21 0:34 ` Greg KH
2004-01-21 0:34 ` Greg KH
2004-01-21 6:38 ` 2.6.1-mm5 - oops during network initialization Valdis Kletnieks
2004-01-21 8:31 ` Catalin BOIE
2004-01-21 15:46 ` GCS
2004-01-21 16:59 ` Valdis.Kletnieks
2004-01-21 18:58 ` Andrew Morton
2004-01-21 19:35 ` Valdis.Kletnieks
2004-01-21 23:19 ` GCS
2004-01-22 21:54 ` Valdis.Kletnieks
2004-01-22 9:35 ` Catalin BOIE
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=400D083F.6080907@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.