DMA intermittently disabled, spontaneous reboots and hangs ...
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The thing came with W2K pre-installed (license-tag
on case). It took 7 minutes to boot, response-times
to mouse clicks were in the 1 minute region, ...
After rebooting it came up with the primary slave
HDD being displayed as something that vaguely
resembled Kanji (not the Seagate model name).
After having powered down and up the drive came
all right, but W2K had shot itself in the foot. After a
recovery run of the CD it did the same thing.
At this stage I clean-installed W2K (which then
supposedly happily worked - no crash, fast)
but after a shutdown the 2ndry HDD was defunct
again.
I reset BIOS to conservative values (Award's
fail-safe option).
Ran Knoppix against it, booted fine, did some file
I/O (read-only on first drive, destructive on 2nd)
with no problem. Then installed Slack on 2ndry
HDD with no problem. The next day Slack came
up crawling slowly, DMA disabled. After machine
was up it was almost happy, Mozilla running in KDE,
wife browsing happily. I ssh'd into the box to configure
the kernel for SMP (all of my attempts failed, kernel
always hung after Reading BIOS data successfully)
with a blank screen, and CAPS and SCROLL-L LED's
lit up ...
The next day machine booted slow (DMA turned off)
Manually enabling DMA => HANG.
Reboot, leaving DMA disabled, compiling kernel =>
HANG.
Win2K still reasonably happy.
Decided to scratch Slack for a test, booted Knoppix,
tried to format hdb1 with XFS => Kernel Panic.
Decided to see how hda behaves. Booted W2K,
defragged NTFS. Booted Knoppix, ran ntfsresize,
ntfsresize complaining about bad blocks, bailed out.
Trying to read NTFS => Kernel Panic.
I'm not quite sure whom or what to suspect in this
scenario, the intermittent DMA switch off may be
HDD failure, may be DMA chipset problems, ... Kernel
traps (did I mention the spontaneous reboots? - had
two of those from within Knoppix when accessing HDD)
Any experience that anyone can offer greatly appreciated.
Thanks for reading on, it has become a rather long post :}
Long shot, but possibly a factor: is all the RAM the same speed or do you have assorted types? Dunno about the hard drives, but if the system has been randomly rebooting or otherwise misbehaving, that could indicate a memory problem. Personally, if I've got more than one stick of RAM installed in a box, I make sure they are all identical to one another, otherwise the likelihood of incompatibilities increases. I can't say if that's the case here but it may be worth taking a look at -- J.W.
Update ... seems the machine had some transport
related problems, after I dismantled it, ripped out
the RAM and re-seated it in the sockets it seems
to be working really well - and I even found out
how to get my SMP kernels (both 2.4.25 and 2.6.4)
to work with it - I have to disable APIC from lilo.
Cheers,
Tink
P.S.: Buzzwords for searches.
SMP DMA BIOS data hang MSI 694D
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.