linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* iopener reboot
@ 2001-01-02 14:51 Matthew Galgoci
  2001-01-02 15:07 ` Richard B. Johnson
  0 siblings, 1 reply; 2+ messages in thread
From: Matthew Galgoci @ 2001-01-02 14:51 UTC (permalink / raw)
  To: linux-kernel

Hi,

I've gone and tried the ultimate acid test of crappy x86 hardware on the 
vanilla prerelease kernel, and installed it on my iopener. The kernel 
loads, uncompresses, initializes hardware, and then immediately reboots.

It all happens so fast that I do not really get a chance to see the last thing
printed before it fails.

The last kernel that I had running on this was a test12 pre something.

Any ideas?

--Matt Galgoci

-- 
"Hey Y'all, Watch this!" --Mike Wangsmo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

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

* Re: iopener reboot
  2001-01-02 14:51 iopener reboot Matthew Galgoci
@ 2001-01-02 15:07 ` Richard B. Johnson
  0 siblings, 0 replies; 2+ messages in thread
From: Richard B. Johnson @ 2001-01-02 15:07 UTC (permalink / raw)
  To: Matthew Galgoci; +Cc: linux-kernel

On Tue, 2 Jan 2001, Matthew Galgoci wrote:

> Hi,
> 
> I've gone and tried the ultimate acid test of crappy x86 hardware on the 
> vanilla prerelease kernel, and installed it on my iopener. The kernel 
> loads, uncompresses, initializes hardware, and then immediately reboots.
> 
> It all happens so fast that I do not really get a chance to see the last thing
> printed before it fails.
> 
> The last kernel that I had running on this was a test12 pre something.
> 
> Any ideas?
> 
> --Matt Galgoci
> 

Recompile as 'generic' as you can get. Pretend you have a '486. Use
a known good 'C' compiler even though it may not be 'optimum'. Once
this boots okay, try compiling for a Pentium '586' etc. You may
have found some problem with CPU identification.

A quick hack at the possibility of a BIOS reporting the wrong amount
of memory is to put append="mem=16m" in your LILO config just to
pretend that you only have 16 megabytes of RAM. Assuming you have
more than 16 megabytes, if the machine boots, you have isolated the
problem to bad BIOS reporting.

Step-by-step, using these kinds of tricks, you should be able to
find the problem.

Cheers,
Dick Johnson

Penguin : Linux version 2.4.0 on an i686 machine (799.54 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

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

end of thread, other threads:[~2001-01-02 15:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-01-02 14:51 iopener reboot Matthew Galgoci
2001-01-02 15:07 ` Richard B. Johnson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).