public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kristofer T. Karas" <ktk@ENTERPRISE.BIDMC.HARVARD.EDU>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Linux 2.4.24-pre1: Instant reboot
Date: Tue, 16 Dec 2003 14:57:22 -0500	[thread overview]
Message-ID: <3FDF63A2.9090205@enterprise.bidmc.harvard.edu> (raw)

Hi Marcelo, et al,

Just wanted to report an instantaneous reboot problem with 2.4.24-pre1.

I don't even see any printk's to the screen; as soon as LILO is finished 
loading the new kernel, the screen blanks and the BIOS goes through its 
boot sequence again.  Since I seem to be the only one reporting this to 
LKML, I suspect I'll have to back out various patches to try to track 
this down. :-P

I'm using the same .config as in 2.4.23 with new questions left at their 
defaults (e.g. XFS=n, OOM_KILLER=n).  I've had no problems with this 
otherwise rock-stable platform for all varieties of 2.4.x, save for some 
early USB EHCI issues long ago.

At work now, so I don't have a full .config handy, but:
* Slackware 8.1 based; glibc 2.2.5; gcc 2.95.3
* Soltek SL-75DRV2 (UP, Athlon XP 1700, VIA KT266A [VT8366A/VT8233])
* Root = ext3 on IDE partition
* DevFS, DevPTS, IDE-SCSI=cdrom0, USBStorage, USB EHCI, VFAT
* RadeonFB, IPTables, Realtek-8139
Everything else in .config is pretty vanilla (e.g. Linus defaults or 
thereabouts).

Kris


             reply	other threads:[~2003-12-16 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-16 19:57 Kristofer T. Karas [this message]
2003-12-16 20:16 ` Linux 2.4.24-pre1: Instant reboot Richard B. Johnson
2003-12-16 22:38 ` Matthias Andree
2003-12-17  6:07   ` [Answer] " Kristofer T. Karas
2003-12-17 12:45     ` Tomas Szepe
2003-12-17 18:20     ` Mike Fedyk

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=3FDF63A2.9090205@enterprise.bidmc.harvard.edu \
    --to=ktk@enterprise.bidmc.harvard.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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