From: ebiederm@xmission.com (Eric W. Biederman)
To: Nick Martens <nickm@kabelfoon.nl>
Cc: vda@port.imtp.ilyichevsk.odessa.ua, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 Boot problem
Date: 19 Apr 2002 13:47:21 -0600 [thread overview]
Message-ID: <m1r8lb4gja.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3CB1B505.2010505@kabelfoon.nl> <200204100517.g3A5HhX04634@Port.imtp.ilyichevsk.odessa.ua> <3CB5F98C.7010206@kabelfoon.nl> <200204121056.g3CAuQX13845@Port.imtp.ilyichevsk.odessa.ua> <3CBDB4E2.3050406@kabelfoon.nl>
Nick Martens <nickm@kabelfoon.nl> writes:
> Sorry for the long time without responding but I haven't had any time lately
> I'm not sure how to solve it yet I don't know about that ECC mem problem but are
>
> there any other devices for which this is typical behaviour or even some BIOS
> setting which may cause this
>
>
>
> Denis Vlasenko wrote:
> > On 11 April 2002 19:01, Nick Martens wrote:
> >
> >>I've tried to do the break thing and then boot after 2 minutes, but the
> >>problem remains. Is it passible that due to the HW-reset some device
> >>gets resetted too and works fine afterwards ???
> > Yes, I can imagine some hw which needs to be warm to operate properly.
> > It may be unable to reset/init in cold state.
> > Is it true that some types of (ECC?) memory need several read passes over them
>
> > to initialize?
ECC memory must be written to ensure the ECC bits are in a consistent
state but that should just take a second or two.
Eric
next prev parent reply other threads:[~2002-04-19 19:54 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
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 [this message]
-- 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=m1r8lb4gja.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickm@kabelfoon.nl \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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