All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Martens <nickm@kabelfoon.nl>
To: Nick Martens <nickm@kabelfoon.nl>
Cc: linux-kernel@vger.kernel.org, rowan.ingvar.wilson@0800dial.com
Subject: Re: 2.4.18 Boot problem
Date: Mon, 08 Apr 2002 22:32:56 +0200	[thread overview]
Message-ID: <3CB1FE78.6050606@kabelfoon.nl> (raw)
In-Reply-To: <3CB1B505.2010505@kabelfoon.nl>

I don't expect it to be a memory problem my system is really stable and 
the weirdest about the problem is that it only happens the first time I 
boot up after my pc has been turned off for a while and there are no 
problems when i boot 2.5.1 it only crashes on shutdowns on that kernel. 
I have tried updating all kind of things, but noting seems to work

Thanks for your reply



rowan.ingvar.wilson wrote:
 > If it happened on previous kernels it may be a memory problem?
 > Just a suggestion as I'm not an expert.
 > Tell me how you get on.
 >
 > <riw>
 >
 > -----Original Message-----
 > From: linux-kernel-owner@vger.kernel.org
 > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Nick Martens
 > Sent: 08 April 2002 16:20
 > To: linux-kernel@vger.kernel.org
 > Subject: 2.4.18 Boot problem
 >
 > When I boot my PC the kernel (2.4.18) gets loaded fine but somehow it
 > crashes at the line saying
 > Freeing Unused kernel memory: 220K freed.
 > nothing happens afterwards and when I reset my system it'll boot up
 > normally again
 > This does only happen when my pc has been turned of for some time.
 > It happened on several previous kernels too, but not with 2.4.5 can
 > someone help me out ?
 >
 > My .config:
 >
 > #
 > # Automatically generated by make menuconfig: don't edit
 > #
 > CONFIG_X86=y

bla bla

 > # CONFIG_BLUEZ is not set
 >
 > #
 > # Kernel hacking
 > #
 > # CONFIG_DEBUG_KERNEL is not set
 >
 > -
 > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
 > in
 > the body of a message to majordomo@vger.kernel.org
 > More majordomo info at  http://vger.kernel.org/majordomo-info.html
 > Please read the FAQ at  http://www.tux.org/lkml/
 >
 >


  reply	other threads:[~2002-04-08 21:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 15:19 2.4.18 Boot problem Nick Martens
2002-04-08 20:32 ` Nick Martens [this message]
2002-04-09 14:43   ` Denis Vlasenko
2002-04-09 10:18     ` Guillaume Gimenez
2002-04-09 16:01       ` Nick Martens
2002-04-09 15:52     ` Nick Martens
     [not found]       ` <200204100517.g3A5HhX04634@Port.imtp.ilyichevsk.odessa.ua>
2002-04-11 21:01         ` Nick Martens
     [not found]           ` <200204121056.g3CAuQX13845@Port.imtp.ilyichevsk.odessa.ua>
2002-04-17 17:46             ` Nick Martens
2002-04-19 19:47               ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2002-04-09 19:30 Andrew Burgess

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=3CB1FE78.6050606@kabelfoon.nl \
    --to=nickm@kabelfoon.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rowan.ingvar.wilson@0800dial.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 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.