Mandrake lockup problem...
 

For some odd reason mandrake 10 has been locking up on me when i leave it running with an open session in screen...i do alot of SSH remote downloading to my home computer and i just started using screen to detatch from console sessions in order to leave remotely initialized downloads running. When i leave it going for a long time (I.E. over night) and try to reconnect i get a host unreachable error, then when i get home and look at the computer there is no video and it is just running, but i cant tell whats going on. Anyone have any experience with this?

Bill

Trying adding noapic nolapic to your kernel parameters. I have a Asus A7n8x motherboard and nforce chipset and I had a lot of lockups (á la Windows 95) without those.

ok...where exactly do i add this? do i have to recompile the kernel?

No, just edit /etc/lilo.conf and rerun lilo.

Add those to "append" on the entry that you boot.

alright i added them exactly as you have them typed, no arguements or anything...well see if theres any diff...

Hi everybody...
I seem to have the same problem as wpg9210. I am using the mandrake 10.0 community release.

I too have added noapic nolapic to my kernel parameters and still I get
random lockups (after a day or so since the last successful access) . The pc seems to be on but I cannot access it though ssh, ping, vnc or any other means...The only way out is "cold" reboot. Since I basically manage this pc remotely (it is actually located in a different city miles away), this is cold reboot is a rather frustrating task...

Also I get no pertinent error message in the messages log file...

Any other suggestions above how to resolve this? I would really appreciate some help with this, since I am totally lost!

I have this problem too, with Mandrake 10 and an a7n8x mother board. I added the noapic and nolapic parameters, but it doesn't make any difference, it still locks up all the time. It's a completely fresh install, I didn't install any additional software at all, only mandrake itself.

In some other threads I see that people are also using a noacpi parameter.
which one should I use? And what do they all do?

Try them all :D

Actually trying them all won't work too. I have already tried adding the noacpi parameter ! Still the pc inexpicably locks up !

I too have tried them all, and I still get the lock ups all the time

Tell mandrake expert.

Hey all, I had this same problem with 9.2 and 10. You need to add the noapic nolapic like an earlier poster said but you also must remove the resume=/dev/hdX phrase from the append line as well. Keep acpi=ht. That should straighten you out.

If that does not work go into the power and control module and set it so it does not suspend after a preset time.


Thane

I'm not at my linux box at the moment but if you'd like my actual append line let me know and I'll post it later.

Yes, please post your lilo.conf.

There is no resume parameter in my appen list. My lilo.conf looks like this:

# File generated by DrakX/drakboot
# WARNING: do not forget to run lilo after modifying this file

boot=/dev/hda
map=/boot/map
install=menu
default="linux"
keytable=/boot/us-latin1.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label="linux"
root=/dev/hda4
initrd=/boot/initrd.img
append="devfs=mount acpi=ht splash=silent noapic nolapic"
vga=788
read-only
image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda4
initrd=/boot/initrd.img
append="devfs=mount acpi=ht"
read-only
image=/boot/vmlinuz
label="failsafe"
root=/dev/hda4
initrd=/boot/initrd.img
append="failsafe acpi=ht devfs=nomount"
read-only
other=/dev/hda1
label="windows"
table=/dev/hda
other=/dev/fd0
label="floppy"
unsafe

How do I set it that it doesn suspend? I've looked in HardDrake, but I couldn't find it.