mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jorge Boncompte [DTI2]" <jorge@dti2.net>
To: "Jens Hoefkens" <hoefkens@msu.edu>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.19 boot failure
Date: Wed, 12 Sep 2001 20:21:16 +0200	[thread overview]
Message-ID: <24da01c13bb7$b6495e00$061010ac@dti2.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0108282340130.12708-100000@dvorak>

----- Original Message -----
From: "Jens Hoefkens" <hoefkens@msu.edu>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Sent: Wednesday, August 29, 2001 6:21 AM
Subject: Re: 2.2.19 boot failure


> On Mon, 27 Aug 2001, Alan Cox wrote:
>
> >
> > Can you boot it with a serial console ?
> >
>
> Hi Alan.
>
> I have the same problem with the serial console. The single CPU kernel
> boots fine and dumps the log to the serial port, the SMP kernel
> freezes right after
>
> "Uncompressing Linux... OK, booting the kernel"
>
> and there is no output to the serial console. However, I have done
> some more tests with 2.4.9 kernels.
>
> 1) Single CPU 2.4.9 boots and reports tons of machine check exceptions
> (output from the serial console in [1]). I also tried my best runnung
> the OOPS trhough ksymoops ([3]).
>
> 2) Single CPU 2.4.9 with "nomce" parameter boots fine ([2]).
>
> 3) SMP 2.4.9 freezes the machine right after "OK, booting the kernel"
> (with and without the "nomce" parameter).
>
> Btw, I have swapped the CPUs around with no change. Moreover, I
> remember that an earlier 2.2 kernel worked with both CPUs on this
> board (if necessary, I can go back and try to find the last working
> kernel - although it will take some time).
>


     Hello,

   I have recently upgraded a server, from 2.4.4 to 2.4.9, with a M54p-09N
motherboard (Dual Pentium 133) and I've got the same result, with two
differences, mine boots in SMP with "nomce", and I don't get any oops, the
server just hangs after all that MCE reports.

    Is there something that I could do to debug it?

    Regards.

    -Jorge

==============================================================
Jorge Boncompte - Técnico de sistemas
DTI2 - Desarrollo de la Tecnología de las Comunicaciones
--------------------------------------------------------------
C/ Abogado Enriquez Barrios, 5   14004 CORDOBA (SPAIN)
Tlf: +34 957 761395 / FAX: +34 957 450380
--------------------------------------------------------------
jorge@dti2.net _-_-_-_-_-_-_-_-_-_-_-_-_-_ http://www.dti2.net
==============================================================
- Sin pistachos no hay Rock & Roll...
- Without wicker a basket cannot be done.
==============================================================



  reply	other threads:[~2001-09-12 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 16:09 Jens Hoefkens
2001-08-27 16:02 ` Alan Cox
2001-08-27 16:17   ` Jens Hoefkens
2001-08-29  4:21   ` Jens Hoefkens
2001-09-12 18:21     ` Jorge Boncompte [DTI2] [this message]
2001-09-12 19:21       ` Alan Cox
2001-09-12 19:36         ` Jens Hoefkens
2001-08-27 16:36 ` Richard B. Johnson
2001-08-27 17:29   ` Jens Hoefkens

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='24da01c13bb7$b6495e00$061010ac@dti2.net' \
    --to=jorge@dti2.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hoefkens@msu.edu \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®