Kaleb Pederson wrote:
>
> Alan Cox Wrote:
> > Start with the easy bits. Check the CPU fans, run memtest86, reseat all
> the cards
> > ... Also if your windows test wasnt SMP its not going to have tested much.
>
> I just reseated everything on my system and it still keeps rebooting. I
> have two nice fans for my processors using thermal compound and both are
> working correctly. I forgot to mention that I ran through several
> iterations of memtest86 a few weeks ago and it found no problems. I also
> re-ran it two days ago and it again passed several iterations without errors
> at which point I started looking to other things. LKML is my last resort.
Are you running the _same_ version of linux that worked with the drive
that broke?
If not, try an older kernel. The current one could be buggy in some
way.
Assuming that the new drive is the only difference, try using hdparm
and deliberately run a slower transfer mode than what you do now.
Or try turning off DMA. The new drive could have different
timing requirements, and fail to work with a linux setup "tweaked"
for the other drive. Windows don't necessarily use the same
transfer speed as linux and could be fine because of that.
Also, consider mounting /var synchronous. This is slow, a
debugging-only thing, but you stand a better chance of logging
the failure in /var/log/syslog. (You have looked there
already?) Any kind of error message will help us
find out whats wrong. You may also want to try
booting without X to see if you get any oops/panic/bug
messages on the console when it crashes.
Helge Hafting
-
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/
This archive was generated by hypermail 2b29 : Tue Jan 07 2003 - 22:00:35 EST