From: Nick Martens <nickm@kabelfoon.nl>
To: vda@port.imtp.ilyichevsk.odessa.ua, linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 Boot problem
Date: Thu, 11 Apr 2002 23:01:00 +0200 [thread overview]
Message-ID: <3CB5F98C.7010206@kabelfoon.nl> (raw)
In-Reply-To: <3CB1B505.2010505@kabelfoon.nl> <200204090939.g399dlX02029@Port.imtp.ilyichevsk.odessa.ua> <3CB30E53.8020905@kabelfoon.nl> <200204100517.g3A5HhX04634@Port.imtp.ilyichevsk.odessa.ua>
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 ???
Denis Vlasenko wrote:
> On 9 April 2002 13:52, Nick Martens wrote:
>
>>Yes much longer, more like for ever... Is there a way to find out what
>>is causing it other then removing each piece of hardware one by one ??
>
>
> Removing hardware is a good idea.
>
> You may verify heat problem:
> * Turn on your box, press <pause> to freeze boot before it loads OS.
> * Keep it in this state for a minute or two.
> * Power off, wait five second
> * Power on
>
> If it works flawlweesly after that, it's definitely hw problem.
> --
> vda
>
next prev parent reply other threads:[~2002-04-11 22:05 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 [this message]
[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=3CB5F98C.7010206@kabelfoon.nl \
--to=nickm@kabelfoon.nl \
--cc=linux-kernel@vger.kernel.org \
--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