linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Bernstein <mb--lkml@dcs.qmul.ac.uk>
To: Andi Kleen <ak@muc.de>
Cc: Andrew Morton <akpm@digeo.com>,
	elenstev@mesatop.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: 2.5.68-mm4
Date: Tue, 6 May 2003 16:50:52 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.55.0305061641360.3237@r2-pc.dcs.qmul.ac.uk> (raw)
In-Reply-To: <20030506143533.GA22907@averell>

At 16:35 +0200 Andi Kleen wrote:

>On Tue, May 06, 2003 at 04:15:55PM +0200, Matt Bernstein wrote:
>> Is this helpful?
>
>What I really need is an probably decoded with ksymoops oops, not jpegs.

OK, I'll do this tomorrow morning (I think I can do it without a serial 
console now).

>Also you seem to be the only one with the problem so just to avoid
>any weird build problems do a make distclean and rebuild from scratch
>and reinstall the modules.

The only odd thing I think I'm doing is hacking this into rc.sysinit:

awk '/version 2\.5\./ {exit 1}' /proc/version || egrep -v '^#' /etc/sysconfig/modules | while read i
do
        action $"Loading $i module: " /sbin/modprobe $i
done

This might be naughty, but it shouldn't be able to hang the box!

I'd prefer to have a proper set of aliases for 2.5 in /etc/modules.conf,
but I'm too lazy to google for one. Also, I'd prefer yet more to shunt
this stuff into an initramfs but I'll wait for documentation to appear for
that :)

Cheers,

Matt

  reply	other threads:[~2003-05-06 15:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  9:01 2.5.68-mm4 Andrew Morton
2003-05-02 13:18 ` 2.5.68-mm4 William Lee Irwin III
2003-05-02 16:47   ` 2.5.68-mm4 Dave Hansen
2003-05-02 14:45 ` 2.5.68-mm4 Steven Cole
2003-05-02 15:00   ` 2.5.68-mm4 Steven Cole
2003-05-02 15:35 ` 2.5.68-mm4 Anton Blanchard
2003-05-03 14:12   ` 2.5.68-mm4 Eric W. Biederman
2003-05-02 16:54 ` 2.5.68-mm4 Martin J. Bligh
2003-05-02 20:04 ` 2.5.68-mm4 Steven Cole
2003-05-02 20:34   ` 2.5.68-mm4 Andrew Morton
2003-05-02 20:49     ` 2.5.68-mm4 Steven Cole
2003-05-02 21:01       ` 2.5.68-mm4 Steven Cole
2003-05-02 21:05       ` 2.5.68-mm4 Andrew Morton
2003-05-02 21:20         ` 2.5.68-mm4 Steven Cole
2003-05-02 21:49           ` 2.5.68-mm4 Andy Pfiffer
2003-05-02 22:00             ` 2.5.68-mm4 Steven Cole
2003-05-02 23:22           ` 2.5.68-mm4 Matt Bernstein
2003-05-02 23:41             ` 2.5.68-mm4 Andrew Morton
2003-05-03  2:53               ` 2.5.68-mm4 Andi Kleen
2003-05-03  7:08                 ` 2.5.68-mm4 Matt Bernstein
     [not found]                   ` <Pine.LNX.4.55.0305061511020.3237@r2-pc.dcs.qmul.ac.uk>
2003-05-06 14:35                     ` 2.5.68-mm4 Andi Kleen
2003-05-06 15:50                       ` Matt Bernstein [this message]
2003-05-07 10:27                       ` 2.5.68-mm4 Matt Bernstein
2003-05-07 12:35                         ` 2.5.68-mm4 Andi Kleen
2003-05-07 15:45                           ` 2.5.68-mm4 Matt Bernstein
2003-05-03  3:14               ` 2.5.68-mm4 Andi Kleen
2003-05-03 13:51               ` 2.5.68-mm4 Diego Calleja García
2003-05-03  1:14     ` 2.5.68-mm4 Herbert Xu
2003-05-05  3:46 ` 2.5.68-mm4 && kexec Eric W. Biederman
2003-05-02 19:58 2.5.68-mm4 J. Hidding
2003-05-03 11:52 2.5.68-mm4 cb-lkml

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=Pine.LNX.4.55.0305061641360.3237@r2-pc.dcs.qmul.ac.uk \
    --to=mb--lkml@dcs.qmul.ac.uk \
    --cc=ak@muc.de \
    --cc=akpm@digeo.com \
    --cc=elenstev@mesatop.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).