08-08-2015
In my experience most "long beeps" are generated by the hardware's BIOS and indicate memory problems. I would recommend you re-seat all the RAM memory first (in case of a simple poor connection between the memory module and the motherboard), followed by selected removal and testing of a subset of memory modules until the beeps cease. Of course, I could be completely wrong.
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi friends,
i am getting the following error while booting my system which has SCo UNIX .
=========================
H iinit
PANIC: srmountfun-Error 22
mounting of rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : Space for only 0 pages.
Dump not completed.
safe to power off... (3 Replies)
Discussion started by: sveera
3 Replies
2. SCO
hi, i m a newbie and installed sco unix on my machine. Also i installed win-xp. i tried to modify the boot.ini file but it does not give me a choice in the begining.
please guide me on this. do we get a boot loader for unix like LILO or GRUB?
:confused: (3 Replies)
Discussion started by: 187final
3 Replies
3. SCO
anyone know where I can download or get a boot disk for sco unix v/386? I have an old PC running sco unix v/386 3.2. I dont have an install or boot disk. I need to reset the root password. I have looked all over the internet and cannot find it anywhere. any help would be greatly appreciated.... (5 Replies)
Discussion started by: format
5 Replies
4. HP-UX
I am new to HP-UX. I have a external SCSI drive with HP-UX on it. I was trying to clone it to another external scsi drive. I added the new drive to existing LVM. Then I used dd command. But it failed with I/O error. Now I cannot boot it from original drive. It's saying panic: LVM: Configuration... (11 Replies)
Discussion started by: forhad
11 Replies
5. SCO
Hi i have a problem after boot with N1 disk and putting N2 disk and pressing the enter in this message:Insert N2(filesystem) floppy and press after by this(pressing enter) the system is reboot!! why??? :confused:
my old pc is a Pentium II 333mhz 3gb hd 64mb ram
please help!! :( (3 Replies)
Discussion started by: panos_pit
3 Replies
6. SCO
Our system is not booting up properly. It keeps going to this screen:
Enter Run Level (0-6, s or S):
I tried to hit all nos# 0-6 is just goes to hung state.
Tried s or S & it brings me to single user mode. I've checked the file systems & found out that all three had 98%. I tried to... (86 Replies)
Discussion started by: jedimaster
86 Replies
7. UNIX for Dummies Questions & Answers
UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies
8. SCO
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies
9. UNIX for Advanced & Expert Users
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (5 Replies)
Discussion started by: Joaoalpande
5 Replies
10. SCO
hi
i have image SCo Unix 5.0.6 and I want transfer on my HP ML350 G5
after Transfer show this message :
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
this hp server used smart array E200i and P400 and sco not recognized HDD
tanks (7 Replies)
Discussion started by: moein.mojtaba
7 Replies
FREE(9r) FREE(9r)
NAME
FREE - General: Deallocates (frees) the allocated kernel virtual memory
SYNOPSIS
#include <sys/malloc.h>
FREE(
void *addr,
int type );
ARGUMENTS
Specifies the memory pointer that points to the allocated memory to be freed. You must have previously set this pointer in the call to MAL-
LOC. You also define the data type for this argument in the call to MALLOC. Specifies the purpose for which the memory is being allocated.
The memory types are defined in the file <malloc.h>. Typically, kernel modules use the constant M_DEVBUF to indicate that kernel module
memory is being allocated (or freed).
DESCRIPTION
The FREE routine deallocates (frees) the allocated kernel virtual memory, which you allocated in a previous call to MALLOC.
NOTES
A memory corruption can occur if a kernel module continues to use the memory after freeing it. The operating system provides a built-in
mechanism to debug such erroneous use of memory. You can enable this debugging feature at boot time by providing the following boot parame-
ter: kmem_debug=1. When you enable this debugging feature, the FREE routine stores the following in the last word of freed memory: The pro-
gram counter (pc) of the module that last freed the memory The checksum of the memory content
The MALLOC routine checks the checksum of the memory content before reallocating this corrupted memory. If the checksum of the memory con-
tent does not match the corrupted memory, MALLOC stores the debug information and then causes the kernel to panic. The MALLOC routine
stores the address and size of the corrupted memory and the pc of the routine that last freed it in a kmem_corrupt_data structure.
You should consider the following when using this debugging feature: This debugging feature does not detect cases where the corruption
occurs after malloc reallocates the freed memory to some other module. There is a small chance that the pc of the routine that freed the
memory (stored in the last word of freed memory) may itself become corrupted.
RETURN VALUES
None
SEE ALSO
Routines: MALLOC(9r)
FREE(9r)