Alan Cox has to say this to the problem " Most crashes on shutdown like that seem to be APM bios bugs. Especially if the EIP value is 0050:xxxxxx " > On Dec 3, 1999 at 23:26, Erle Pereira wrote: > > > Actually its more like... the registers on the cpu.... I wish I could > > That looks like a standard dump, which DOS programs sometimes give on > segfaulting. > > I get something like it during normal operation (without segfault, and > while logged in) by hitting ^-scrolllock. > > > but I also get : > > [CALL TRACE].....followed by some more values... > > Yes, that's a trace of what calls what from where, so you can trace the > program and see why it crashed. > > > Unable to handle Kernel Paging request.... > > Can't page, swap is unmounted. > > > Filesytems are unmounted...( eliminates swap space..... etc...... right > > .... or am I totally confused ? ) > > This is a memory/bios/cpu thing. > > > ( NO ERRORS WHILE BOOTING UP + RUNNING ).. and no others errors what so > > Nope, it's a RAM-only soft error. > > > On Dec 4, 1999 at 00:35, Vaibhav Arya wrote: > > > running Red Hat 6.1 and I think that it does come with amp built as default > > (apmd starts during boot up). Also, the weirdest part is that when you > > ctrl-alt-del after the registers are all shown it gives a message about > > 'shutting down md devices.' Other than that no problems what so ever... > > I'd like to know what md is, too. My guess is it's some overwatch process > that takes over the console etc when nothing else is left. > > Ok, now all the machines with garbage-on-halt (does this occur on > reboot as well?) have apm enabled, but no apm in hardware, right? Then > what's probably happening is that the kernel thinks there's apm, attempts > to turn the computer off, hits a bad interrupt/foo, and crashes what > little of the system is left at this point. Ask Linus. > -------------------------------------------------------------------- The Linux India Mailing List Archives are now available. Please search the archive at http://lists.linux-india.org/ before posting your question to avoid repetition and save bandwidth.
