mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Ramdisk Initialization Problem
@ 2001-05-24 21:15 Jaswinder Singh
  2001-05-25  1:06 ` H. Peter Anvin
  0 siblings, 1 reply; 3+ messages in thread
From: Jaswinder Singh @ 2001-05-24 21:15 UTC (permalink / raw)
  To: linux-kernel

    I am using kernel 2.4.1 with compressed Ramdisk on  Hitachi SH board ,
with no battery.   When i run kernel first time , it works fine , it
uncompress Ramdisk and i get my shell prompt .    But when i restart it
second time (with out  removing power cable ) kernel dies when
uncompressing Ramdisk.   But , if i remove my power supply for more than 5
minutes , and then i start again , it works again.   It seems that in 2.4.1
and/or later versions has  Ramdisk Initailization or uninitialised memory
problem. But i faced no problem  with 2.2.12 kernel.   Thank you,  

Best Regards,   Jaswinder (and his wonder machine).
--
These are my opinions not  3Di.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Ramdisk Initialization Problem
  2001-05-24 21:15 Ramdisk Initialization Problem Jaswinder Singh
@ 2001-05-25  1:06 ` H. Peter Anvin
  2001-05-25  1:51   ` Jaswinder Singh
  0 siblings, 1 reply; 3+ messages in thread
From: H. Peter Anvin @ 2001-05-25  1:06 UTC (permalink / raw)
  To: linux-kernel

Followup to:  <l03130306b7332a134958@[209.239.217.188]>
By author:    "Jaswinder Singh" <jaswinder.singh@3disystems.com>
In newsgroup: linux.dev.kernel
>
>     I am using kernel 2.4.1 with compressed Ramdisk on  Hitachi SH board ,
> with no battery.   When i run kernel first time , it works fine , it
> uncompress Ramdisk and i get my shell prompt .    But when i restart it
> second time (with out  removing power cable ) kernel dies when
> uncompressing Ramdisk.   But , if i remove my power supply for more than 5
> minutes , and then i start again , it works again.   It seems that in 2.4.1
> and/or later versions has  Ramdisk Initailization or uninitialised memory
> problem. But i faced no problem  with 2.2.12 kernel.   Thank you,  
> 
> Best Regards,   Jaswinder (and his wonder machine).
> 

First of all, try the latest kernel if you are going to report a bug.

For the kernel people, this is classic evidence of relying on
uninitialized memory; the "few minutes" is roughly how long it takes
modern SDRAM to *reliably* discharge.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Ramdisk Initialization Problem
  2001-05-25  1:06 ` H. Peter Anvin
@ 2001-05-25  1:51   ` Jaswinder Singh
  0 siblings, 0 replies; 3+ messages in thread
From: Jaswinder Singh @ 2001-05-25  1:51 UTC (permalink / raw)
  To: linux-kernel, H. Peter Anvin; +Cc: Jaswinder Singh

"H. Peter Anvin" <hpa@zytor.com> wrote :
>
> First of all, try the latest kernel if you are going to report a bug.
>

As far as i know , Regarding Ramdisk linux-2.4.4 and 2.4.1 are similar.
, no body fixed this problem after 2.4.1 , If somebody please let me know .

Anyhow i will try with latest kernel and let you know , but it will take
some time .

> For the kernel people, this is classic evidence of relying on
> uninitialized memory; the "few minutes" is roughly how long it takes
> modern SDRAM to *reliably* discharge.
>

In my case , If i restart after 5 minutes it works fine , but if i restart
after 1 or 2 minutes kernel hangs during uncompressing ramdisk.

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.

> -hpa



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-05-25  1:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-05-24 21:15 Ramdisk Initialization Problem Jaswinder Singh
2001-05-25  1:06 ` H. Peter Anvin
2001-05-25  1:51   ` Jaswinder Singh

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®