10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am trying to modify the "corestat v1.1" code which is in Perl.The typical output of this code is below:
CoreId %Usr %Sys %Total
------ ----- ----- ------
5 4.91 0.01 4.92
6 0.06 ... (0 Replies)
Discussion started by: Zam_1234
2. UNIX for Dummies Questions & Answers
hello, i am new to this forum and i really could use some help, we have a risc 43p model 150 ibm server and we run prophet 21 on it. after the box boots up and then we activate prophet 21 we get a error message saying
"The data space of the process is not enough for the shm segment (1176) │
... (1 Reply)
Discussion started by: mrhose
I hope you are doing well. Can you please tell me which part of the motherboard contains the BIOS software, name that exact location. And could please give me the names of the firmwares for atleast 5 archetictures, like sun sparc, ibm power, hp alpha etc.
Looking forward to your... (0 Replies)
Discussion started by: gabam
I connected the exp400 & turned on the aix machine which is 7043-150 but now I guess probably ODM is corrupted as it does not boot. Its stuck at 0518 code.
Also, on the console it shows stuck on the kernel, which then it does not want to boot. Is it possible to fix from maintenance... (1 Reply)
Discussion started by: pdhawan
hi to everybody
I have a problem with the AIX version 4:
I can not get into failsafe session
kindly someone knows how to enter this mode?
thanks in advance (5 Replies)
Discussion started by: elektrospeed
6. Shell Programming and Scripting
hi there !
i have exactly the same problem like this guy here
i am not able to save the curl verbose output..
the sollution in this thread (redirecting stderr to a file) does not work for me.... (0 Replies)
Discussion started by: crabmeat
this is my problem:
my boss got a Model 43P 7248-100 PowerPC server with the AIX 4.2 os, but some days ago it crashed and now it doesn't want to boot up again, it stops after the initial diagnostic phase with the "PowerPC" screen!
I must recover some important data from the hard disk, so... (6 Replies)
Discussion started by: AKO
I've installed AIX 5.1 on a 43p-140, but am unable to log in. At no point in the install did it ask me for a root password. When it boots to the console prompt, I enter "root" as a username, and then after 1 second it cycles right back to another root prompt.
I am accessing the 43p-140... (4 Replies)
Discussion started by: akbar
I have a 43p 120 (7248-120) which I am trying to install AIX 5.2 on. I have built a Nimol server on a Linux PC running SUSE LES 10. I have setup the 43p to perfom a network boot (BOOTP) and all the addresses in the network settings under SMS are set to 0.0.0.0. When I power up the 43p it... (15 Replies)
Discussion started by: johnf
I have acquired a 43p 120 (7248-120) and I have two questions:
Can anyone remember what is the highest version of AIX which I can install (5.1 I believe)
Can anyone remember how to boot this from the CDROM (boot floppy?) (1 Reply)
Discussion started by: johnf
BLK_MAKE_REQUEST(9) Block Devices BLK_MAKE_REQUEST(9)
blk_make_request - given a bio, allocate a corresponding struct request.
struct request * blk_make_request(struct request_queue * q, struct bio * bio, gfp_t gfp_mask);
target request queue
The bio describing the memory mappings that will be submitted for IO. It may be a chained-bio properly constructed by block/bio layer.
gfp flags to be used for memory allocation
blk_make_request is the parallel of generic_make_request for BLOCK_PC type commands. Where the struct request needs to be farther
initialized by the caller. It is passed a struct bio, which describes the memory info of the I/O transfer.
The caller of blk_make_request must make sure that bi_io_vec are set to describe the memory buffers. That bio_data_dir will return the
needed direction of the request. (And all bio's in the passed bio-chain are properly set accordingly)
If called under none-sleepable conditions, mapped bio buffers must not need bouncing, by calling the appropriate masked or flagged
allocator, suitable for the target device. Otherwise the call to blk_queue_bounce will BUG.
When allocating/cloning a bio-chain, careful consideration should be given to how you allocate bios. In particular, you cannot use
__GFP_WAIT for anything but the first bio in the chain. Otherwise you risk waiting for IO completion of a bio that hasn't been submitted
yet, thus resulting in a deadlock. Alternatively bios should be allocated using bio_kmalloc instead of bio_alloc, as that avoids the
mempool deadlock. If possible a big IO should be split into smaller parts when allocation fails. Partial allocation should not be an error,
or you risk a live-lock.
Kernel Hackers Manual 2.6. July 2010 BLK_MAKE_REQUEST(9)